A client sends finished videos and a spreadsheet. Another sends only a folder of clips. Treating both deliveries as the same import problem creates avoidable confusion. First establish which files, descriptions and decisions already exist. Then choose a method that preserves them.
The key points
- Choose an import method around your existing material.
- A prepared table can carry approved text and dates, while direct upload suits finished videos whose descriptions still need writing.
- BestPost takes videos together and creates publishing text from their content.
- A CSV file contains data or references, not the video files themselves.
Which import methods are being compared?
Direct video upload transfers media files into a planning tool. A CSV importer reads structured values from a text table. Depending on the tool, those values may include media links or identify files that were uploaded separately.
A filename in a spreadsheet is not the media file. If someone receives only the table, they still need a supported way to access the recording. That distinction explains many apparently mysterious missing-video errors.
| Material you have | Possible method | What to verify |
|---|---|---|
| Local clips without descriptions | Upload video files directly | How publishing text is prepared afterwards |
| Approved text and accessible media links | Import a supported CSV | How the service retrieves each video |
| Uploaded media and a separate text table | Match metadata to files | Which identifier creates the match |
These are different starting points, not a ranking from amateur to professional. A clean spreadsheet can be useful. Creating one solely to copy information back out may add preparation without solving a real problem.
Your videos can be the starting point
BestPost takes the files you have and writes publishing text from their content.
- No spreadsheet, no CSV file
- Takes 100 videos and more in one go
- Writes the description, YouTube title, hashtags and first comment from your video
When is a spreadsheet worth keeping?
Keep a table when it already contains decisions you need to preserve: approved descriptions, identified media and agreed publishing dates. Its value comes from those decisions, not from the CSV extension.
Before using it, check the receiving system:
- Confirm the current template and expected field names.
- Confirm how media files are associated with each row.
- Confirm which fields are required and which may stay empty.
- Confirm how dates, times and time zones are interpreted.
Those checks establish whether your table can be imported as intended. A generic export from one application is not automatically a valid input for another.
Use the destination tool's current instructions. An old template can appear familiar while containing fields with changed meanings. Do not silently convert a client's local publishing time into your own time zone.
How do you keep text attached to the correct clip?
Give each planned item a clear identifier in your working records. Use it to connect the approved video, its subject and its description. The identifier can remain internal; it does not have to appear in the public post.
This invented example is a planning table, not an import-ready file:
| Identifier | Video file | Description subject |
|---|---|---|
| light-fit | fitting-light.mp4 | Attaching the light to its mount |
| light-release | releasing-light.mp4 | Taking the light off the bicycle |
| light-charge | charging-light.mp4 | Connecting the correct charger |
If a video changes, review its associated text instead of assuming the filename proves continuity. A replacement recording might demonstrate a different model or procedure.
Check access separately from matching. A media link that works while you are signed in may be unavailable to the importing service. Follow the supported access method rather than making private material public simply to get an import working.
When is direct video upload the simpler starting point?
Direct upload fits a collection of finished recordings when publishing text still needs to be prepared. You can start with the content instead of writing a spreadsheet solely for import.
BestPost takes 100 videos and more in one go and creates descriptions, YouTube titles, hashtags and first comments from the videos. You can review the suggested text beside the relevant clip. The bulk upload feature and automatic descriptions support this starting point.
An existing approved description still matters. A generated suggestion does not override a client's instructions. Keep the approved wording or make agreed corrections before scheduling.
This workflow does not require a CSV. That does not establish support for arbitrary spreadsheet imports into BestPost. Importing tables and working directly from videos are separate capabilities.
Finished clips get their publishing dates
BestPost organises the schedule and publishes from the server.
- Spreads the dates across your weekly pattern and posts on its own
- Shows every date in one calendar you rearrange with a click
- Publishes from the server, your browser can stay closed
How should you test the handover?
Start with a representative sample rather than the easiest file alone. Include an item with a different description or date so that a mistaken default becomes visible. Review the prepared entries without accidentally triggering public test posts.
Inspect the source
Match the identifier, video and approved wording.
Inspect the destination
Open the uploaded or imported item.
Compare the fields
Check its text, account, date and time separately.
Record the result
Note which values transferred and which required manual work.
Stop before importing the full collection if a value lands in the wrong place. A repeated mapping error becomes more expensive to untangle as the batch grows. First determine whether the issue concerns field format, media access or file identification.
A successful test means the intended values arrived correctly. It does not mean every later item has already been reviewed or that the videos have been published.
What should decide your next workflow?
Choose around the work already completed and the work still needed. Structured metadata is useful when the destination understands it. Missing descriptions do not automatically mean someone must build a table first.
Ask these questions before committing:
- Are the finished media files accessible through the intended method?
- Have descriptions and dates already been approved?
- Does the destination support the data structure you have?
- Can you inspect the resulting entry for each clip?
The answers identify the practical route. Keep a table when it preserves valid structured decisions. Start with the files when the video content is the foundation for the text and publishing plan. In either case, verify the resulting entries before treating the handover as complete.
For a closer look at the related task, read Bulk Upload Videos: Build a Reliable Queue. To check the next decision, see Client Video Handoff for Publishing: A Template.