Export Final Cut captions: check language, time origin and receiver
A Final Cut movie share can deliver captions differently from a separate caption export. Decide whether the recipient needs sidecar files, supported embedded captions or permanently visible text. Then verify the saved resources, language and time origin instead of assuming the timeline preview proves the final delivery retains selectable captions.
Open the relevant downloader · Platform tools and access limits
Choose the actual caption delivery and retain the parent
Keep the authorized movie and recoverable project with its reviewed captions. Identify the language subroles the recipient needs and their current formats. Multiple subtitle languages are separate text resources, not additional audio recordings. If format conversion is required, retain and review the source through the separate caption-conversion workflow first.
Confirm what the target player or editor supports. A visible burn-in can satisfy one viewing need while removing the option to turn text off; a sidecar can remain editable but needs an accessible association with the matching movie. Do not substitute one deliverable for another silently or label permanently rendered words a selectable embedded track.
Use the native export controls and select the timing origin
With the project open in the timeline, use File > Export Closed Captions, choose a new name and destination and select the intended language subroles in Roles. Apple documents a separate file for each selected subrole. Inspect the actual selection rather than relying on which language happened to be visible in a preview.
The Start Time choices differ: Relative to Timeline subtracts the project’s start, while Absolute retains each caption’s actual start time. Choose according to the receiving movie or timeline. For SRT, review Include Formatting against receiver support. Readable text is not proof that arbitrary SRT formatting will render as intended in another application.
Check share-destination limits separately
When exporting or embedding through a share destination, inspect that destination’s actual caption options. Not every destination carries independent caption resources. Some destinations permit visible burn-in without sidecar or embedding. Choose the intended supported arrangement, and include the separate caption files with the actual movie when that is the agreed handoff.
For batches, verify every project’s language and caption choices rather than assuming a single active subrole applies correctly throughout. Keep output identities and resource associations clear. The general native export guide explains completed job and file verification; a queued share or closed dialog is not a finished captioned delivery.
Verify each saved language and its matching timing
Reopen the movie and caption resources in the recipient’s workflow. Select each required language and compare the first spoken passage, a later scene and the final cue. An incorrect origin can shift otherwise accurate text, so resolve that timing context before rewriting every cue. Check names and supported formatting independently of synchronization.
Retain the original and any intentionally simplified resource with clear version notes. Report missing or unusable languages as unresolved rather than calling a video-only export complete. SocialVidDownloader’s local text-track extractor and supplied-SRT burn-in tool do not certify all native Final Cut caption formats or receiver support. This native handoff is accepted only when the actual required text resources and their presentation have been checked.
Worked example
Example: a project uses a nonzero timeline start, but its review movie begins at local zero. The editor chooses and verifies the corresponding caption origin, exports the required subroles and checks the actual files. A captions-visible timeline alone is never used as proof that the review movie contains selectable text.
Related guidance
Sources and verification
Reviewed 2026-10-13. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.