The best subtitle workflow for creators using Final Cut Pro
ยท 6 min read
Final Cut Pro has no built-in transcription, which leaves creators choosing between typing captions by hand, importing a flat SRT, or importing FCPXML. Only one of those three gives you subtitles that are both fast to produce and easy to restyle afterward.
Why FCPXML instead of SRT here specifically
SRT imports into Final Cut fine, and it arrives as flat, unstyled captions โ no font, no position, no per-word control. FCPXML describes a timeline rather than a cue list, so subtitles come in as title clips on their own lane: editable, movable, and stylable exactly like any other title in the project.
The frame rate step people skip
Transcription returns timings as decimal seconds. Final Cut thinks in frames. Converting between the two at the wrong rate produces drift that's invisible in the first minute and obviously wrong by minute ten โ round every cue to the nearest frame at 25 fps and drop it into a 23.976 timeline, and the captions end up visibly late well before the video's over.
Setting the correct frame rate before export โ matching your actual Final Cut project, not a default โ and exporting rational timecodes rather than decimal seconds is what keeps a long cut in sync from the first frame to the last.
The workflow
- Drop in your audio or video file; video is decoded to audio in the browser.
- Transcribe and run forced alignment, so every word carries its own timestamp.
- Set line breaks and edit anything that reads awkwardly โ splitting a line never drifts timing, since every word already has a real timestamp.
- Choose the frame rate matching your Final Cut project, then export FCPXML.
- In Final Cut Pro: File โ Import โ XML. Titles land on lane 1 above your video, already styled.
If you're also publishing to YouTube or anywhere else, export SRT from the same session โ it's generated from identical timings, so the two exports can't disagree with each other.