Which columns does the video-link CSV contain?

The export contains filename and url. It includes only rows that have completed successfully and have a URL; pending, failed, cancelled, and uploading rows are excluded.

Does cancelling a batch remove videos that already uploaded?

No. Cancel stops the active browser request and leaves completed rows available. It is not a deletion action, and stopping a request does not establish whether the server stored the interrupted upload.

Should I retry the whole batch after a 429 response?

Preserve completed URLs and wait for the applicable request or daily allowance to recover. The uploader stops advancing after a 429. Review pending rows separately from failed or cancelled rows, then resume without re-uploading successful files.

Batch Video Links to CSV: A Reliable Handoff Workflow

A delivery containing twelve clips needs twelve verified links, not twelve guesses about which uploads finished. A CSV can make that handoff manageable, provided you understand what the export records and what still needs a human check.

This workflow uses Bulk Video to Link. The current browser queue accepts up to 20 files, with a 100 MiB per-file limit. Daily upload allowance, request limits, and available storage also apply. Files upload sequentially through the site's existing video upload endpoint; this is a browser queue, not a separate batch API or an unlimited upload plan.

Start with a delivery manifest

Create a local list of the clips you intend to deliver before opening the uploader. Include an asset identifier, revision, intended placement, and approval state in your own worksheet. Those are your project columns; the site's export does not create them.

Use filenames that distinguish both content and revision:

onboarding-01-account-setup-v03.mp4
onboarding-02-first-project-v02.mp4
onboarding-03-share-results-v01.mp4

Avoid reusing final.mp4 for different clips. Two local files can share a name, but identical names make a filename-based reconciliation ambiguous. Rename them before upload and retain the original source files separately. Keep private customer names and account identifiers out of filenames intended for a public handoff.

Check permission to publish, file size, and playback locally. A file extension is not a complete description of its codec. If one clip needs conversion, handle it first through a suitable workflow such as MOV to MP4, then review the exported result before publishing.

Upload a small, named batch

Add the prepared files and inspect the queue before starting. Invalid files can appear as failed immediately; retrying cannot make an oversized or unsupported file valid. Replace or correct that source file instead.

Keep the page open while the batch runs. Read each row's status rather than treating the first visible URL as proof that every clip finished. The completed count is a useful checkpoint, but it should agree with your manifest.

Queue state	Handoff meaning	Next action
Pending	No completed URL for this row	Start or resume remaining uploads when allowed
Uploading	The current request is in progress	Wait before making a completion claim
Done	A returned URL is available	Open the link and match it to the filename
Failed	Validation or an upload attempt failed	Read the message and correct the cause
Cancelled	The active browser request was stopped	Check the outcome before deciding to retry

Cancel is useful when you selected the wrong material. It does not remove already uploaded files. An interrupted request can also have an uncertain server outcome, so cancellation should not be treated as confirmation of deletion.

Understand the actual CSV

The download is named bulk-video-links.csv. Its exact header is:

filename,url
"onboarding-01-account-setup-v03.mp4","https://example.com/clip-a.mp4"
"onboarding-02-first-project-v02.mp4","https://example.com/clip-b.mp4"

These URLs illustrate the format; replace them with your own results. Only successful rows with URLs are exported. There is no status, upload time, file-size, or failure-reason column. Downloading while other rows remain incomplete creates a partial success list, not a complete batch audit.

The export uses UTF-8 with a byte-order mark, quoted values, and CRLF record separators. Quotes inside values are escaped. Filenames beginning with certain spreadsheet formula markers receive a leading apostrophe as a precaution. If a filename looks slightly different in your spreadsheet, inspect the imported text before assuming the uploader renamed the original file.

Import the file as UTF-8 CSV if your spreadsheet opens it incorrectly. Avoid splitting lines manually on commas: a legitimate filename can itself contain a comma or quotation mark. RFC 4180 documents the common CSV quoting conventions behind this distinction.

Reconcile before sending

Save the first export with a delivery-specific local name, then compare its filenames against your manifest. If you planned twelve clips and the CSV contains ten data rows, the handoff is incomplete even if those ten links work.

Open each returned URL, preferably in a signed-out browser. Confirm that it plays the intended clip and the correct revision, including audio where relevant. A successful upload response establishes a returned URL; your playback check establishes whether the recipient can use that particular result.

Add verification date and reviewer in your own working copy. Keep an untouched copy of the original two-column export so later reconciliation remains straightforward. Share the CSV with a short note identifying the intended delivery, any missing clips, and whether the links have been checked.

Recover partial failures without duplicating successes

Ordinary failures do not automatically invalidate completed rows. Preserve successful URLs, fix the failed source or connection issue, and use the retry control for valid failed or cancelled rows. The implementation also includes pending rows when starting a retry; review the queue before doing so.

A 429 response stops the queue from advancing. It can reflect request throttling or a daily upload allowance. Repeated clicks will not create more allowance. Wait for the applicable limit to recover, consult any reset information available, then review which rows remain pending. A 503 capacity response needs a later attempt rather than a filename change.

Download a fresh CSV after recovery and reconcile again. Remove or clear queue rows only after saving the information you need: those controls change the browser list, not the already published objects. Keep local backups because public hosting is not a permanent archive, and anyone who receives a public URL can pass it on.