How to hand off a finished video with captions and clear files

A finished video needs a clear handoff. The recipient should know which file to upload, whether captions are included, what each version is for and who has approved it. A folder full of similar exports leaves those decisions to someone who may not have been part of the edit.

This guide is for clients, producers and editors preparing delivery after approval. It focuses on a useful file package and an acceptance check, rather than a universal export preset. The example is fictional. Confirm the actual destination's requirements before exporting, and agree separately whether project files or camera originals are part of the assignment.

Give every deliverable a destination and an owner

Start with a delivery list. For each output, name its purpose, destination, aspect ratio, language, caption treatment and person responsible for uploading it. Have the editor and destination owner confirm the technical specification, including resolution, frame rate, format, audio arrangement and color requirements where applicable. “Send the final video” is too vague when several versions will leave the edit.

Distinguish the main film from a short extract, an alternate language version or a captioned social version. Decide which outputs need their own approval. If someone requests another crop after the main film is approved, give that version a review step rather than assuming it is ready because the underlying interview was accepted.

The production brief and edit-approval guide helps establish these responsibilities before filming. At delivery, use the agreed brief as a checklist and record any approved changes. If an output has no known destination yet, label that decision as open instead of guessing the export settings.

Say exactly how captions will be supplied

Ask whether the destination needs a separate caption file, text permanently visible in the picture, or another supported arrangement. Adobe's export reference distinguishes a sidecar text file from captions burned into the video. Burned-in text cannot be turned off during playback. Embedded caption options depend on the export format and playback support, so do not assume an exported movie contains usable selectable captions.

A separate caption file is a deliverable that needs to travel with the matching video. State its language and identify the exact version it accompanies. If the edit changes, review the caption timing against the revised output. Keep a clearly named copy of any video with burned-in text so an uploader does not accidentally choose it when they intended to use selectable captions.

For YouTube specifically, its current help page supports basic SubRip files with the .srt extension, requires plain UTF-8 and says that styling markup is not recognized for that format. A styled caption reference from the edit is therefore not proof that an uploaded SRT will look the same in the player. Check the destination's accepted format and preview the result there.

Agree who reviews the words, speaker identification, names, specialist terms and meaningful sound descriptions. Read along while watching the matching export, including pauses and the ending. Treat automatic text as material to review. If translations are requested, name the person responsible for language review instead of implying that a file export establishes translation accuracy.

Use filenames that distinguish the actual versions

Choose a short naming pattern that the receiving team understands. Include a project identifier, output purpose, language or caption treatment when relevant and an agreed version identifier. Avoid a chain of names such as “final-new-final-approved” that offers no reliable way to select the correct file.

For example, a fictional package might use ProjectA_main_landscape_en_v03.mp4 and ProjectA_main_landscape_en_v03.srt. An alternate with visible text could be labeled ProjectA_short_portrait_en_burned-v01.mp4. These names illustrate the relationship; they do not prescribe a codec, platform specification or naming standard.

Keep superseded review exports outside the delivery folder. If an approved file must be replaced, tell the recipient which named file is superseded and provide an updated manifest. Avoid silently replacing a file at an old link while a separate person is preparing to publish the earlier version.

A fictional finished-video package

Imagine a client receiving a main interview film and one portrait extract. The client will upload them through its own accounts. This is an illustrative delivery plan, not an actual RackFocus Cinema project, standard package or statement of platform requirements.

The manifest can be a brief text document or an agreed handoff message. Include the delivery date and version, filenames, purpose, caption relationships and any remaining limitations. Keep private access instructions separate from a public-facing description. For more on preparing extracts as their own outputs, see the interview repurposing guide.

Watch the exported file, then test the receiving path

Review the actual exported files before sending them. Check the opening, ending, picture, sound, titles, spelling, transitions and any alternate crop. Compare the delivery list with what was actually exported. A correct timeline or export preset does not replace checking the saved file.

Ask the recipient to download the package through the intended transfer route and open it. Confirm that every listed file is present and usable, and distinguish a transfer preview from the downloaded original. Resolve access or missing-file problems before treating the handoff as accepted.

Where the client controls the destination, ask its uploader to test the intended video and caption pair in the available preview or review process before public release. Check text timing, selected language, framing and sound there. The client should control publication and account access; there is no need to share account credentials just to review a delivery.

If the result looks different from the approved reference, describe the exact file, player and observed issue to the editor. The color-workflow preparation guide explains why the intended output and viewing setup deserve explicit agreement. Do not repeatedly re-export from guesses without identifying the problem.

Agree what remains available after delivery

Ask about transfer-link availability, retention, backup ownership and how future changes will be requested. A download link is not an archive plan. Keep the approved deliverables, caption files, manifest and approval record in the client's agreed storage, with responsibility for copies clearly assigned.

Editable project files, licensed assets, camera originals and long-term storage are separate scope questions. Confirm what is included and what any receiving editor would need to use it. The footage backup guide covers source-copy decisions; finished-film delivery should identify its own retained materials too.

Plan delivery while the project is still being scoped

Share the intended destinations, languages, versions, caption needs, uploader and approval deadline when discussing a production. That gives the team a concrete delivery target and exposes questions while there is time to resolve them.

Contact RackFocus Cinema to discuss your production and delivery plan. Start with the film's purpose and how the finished files will be used so the scope can include a practical handoff.

Sources and limits

Primary documentation inspected November 9, 2026. The package, filenames and acceptance process are original editorial recommendations. No client account, physical export test or actual production is represented. Destination specifications and software options must be confirmed for the project.

• Adobe: Export settings reference — sidecar, burned-in and supported embedded caption distinctions.
• Adobe: Export caption tracks — format-dependent caption export options.
• YouTube: Supported subtitle and closed caption files — basic SRT support, UTF-8 and styling limitations.