Skip to content
CutConvert

How to add subtitles in Final Cut Pro

By Greg Thompson, Founder, CutConvertPublished

There are three ways to add subtitles in Final Cut Pro, and picking the right one up front saves real time: generate them automatically (the built-in Generate Captions feature, introduced in Final Cut Pro 11 as Transcribe to Captions), import a subtitle file you already have (SRT, iTT, or SCC), or build them as titles when subtitles are a designed, burned-in part of the picture. This guide covers all three, when each wins, and how to get the result out again — as a caption track, a sidecar file, or pixels.

Already holding an SRT file? Jump straight to the companion guide on importing SRT into Final Cut Pro — it covers the import dialog and its timing gotcha in detail.

Way 1: automatic captions (Generate Captions)

Final Cut Pro's built-in transcription — per Apple's documentation: requires an Apple silicon Mac, and speech recognition is U.S. English only for now.

  1. Select the clips (or the timeline range) to caption.
  2. Choose Edit > Generate Captions > Closed Captions (Shift-Command-C) — also available from the Enhancements pop-up under the viewer, or by control-clicking the selection.
  3. FCP downloads a language model on first use, then builds closed caption clips — in the iTT format — connected to the clips they were transcribed from, in a caption lane at the top of the timeline.

It's the fastest route when no transcript exists yet. The trade-offs, straight from Apple's docs: background music, noise, and overlapping dialogue hurt accuracy (Voice Isolation helps), the captions arrive as iTT (convertible to other formats afterward), and — like every auto-transcript — names and jargon need a proofing pass.

If your transcription already happened elsewhere (Rev, Whisper, a localization vendor), don't re-transcribe — convert what you have to SRT (TXT to SRT, Whisper JSON to SRT) and import it.

Way 2: import a subtitle file

When the subtitles exist as a file, File > Import > Closed Captions accepts SRT, iTT, and SCC, placing them in a caption lane organized by language role. Two decisions matter at import time — the caption role/language, and the insertion-time setting that determines whether a zero-based SRT lands at the right timecode. Both are covered step-by-step (with the an-hour-off failure mode) in the import SRT guide.

This is the standard route for localization workflows: each language arrives as its own SRT, imports under its own subrole, and exports independently.

Way 3: build subtitles as titles (the designed look)

Captions are delivery objects — the player controls how they look. When subtitles are part of the picture (styled documentary subs, social cuts with branded text, festival deliverables), build them as titles instead: fully styleable per cue, any font/color/position, burned in on export.

Nobody types hundreds of title clips by hand. The workflow: get the subtitles as SRT, convert with the SRT to FCPXML converter — one editable Basic Title per cue, frame-aligned at your timeline rate — then File > Import > XML and drag the titles over your footage. Style one, copy its attributes to the rest.

Which way for which job

  • No transcript exists, English dialogue, FCP 11+ → Transcribe to Captions, then proof.
  • Subtitles exist as a file (from a vendor, YouTube, a transcription service) → import them; convert to SRT first if they're in another format (VTT, SBV, ASS).
  • Styled, always-visible subtitles → titles via SRT to FCPXML.
  • Broadcast/platform caption deliverable (CEA-608, iTT) → captions, exported in the required format via roles.

Getting subtitles back out

  • Caption tracks: File > Export > Captions writes SRT/iTT/SCC sidecars; the share sheet can embed captions or export them alongside the movie.
  • Burn-in: captions can be burned into the picture on export; titles are always part of the picture.
  • Title-based subtitles → SRT: no native export exists — export the timeline as FCPXML and run the FCPXML to SRT converter, which resolves each title's real timeline position.

FAQ

How do I add subtitles in Final Cut Pro? Three ways: transcribe them automatically (Edit > Captions > Transcribe to Captions in Final Cut Pro 11), import an existing SRT/iTT/SCC file via File > Import > Closed Captions, or convert the subtitles to FCPXML titles when you want a fully styled, burned-in look.

Can Final Cut Pro generate subtitles automatically? Yes — Final Cut Pro 11 added Transcribe to Captions, which builds a caption track from clip audio on-device. Proof the result: auto-transcripts miss names and jargon, and language coverage is narrower than dedicated services.

Which subtitle formats can Final Cut Pro import? SRT, iTT, and SCC via File > Import > Closed Captions. Other formats (VTT, SBV, ASS) convert to SRT in seconds and import the same way.

Captions or titles — which should I use? Captions for anything a platform or broadcaster consumes (toggleable, spec-compliant, per-language). Titles when subtitles are a visual design element you want styled and permanently visible. Both can coexist in one project.

Why did my imported subtitles land an hour off? The Insertion Time setting — zero-based SRTs need "Relative to Timeline", hour-based ones need "Absolute". The import guide covers the fix in detail.

How do I export just the subtitles? File > Export > Captions writes the caption track as a sidecar (SRT, iTT, or SCC depending on the caption format). Title-based subtitles export via FCPXML plus the FCPXML to SRT converter.

Greg Thompson · Founder, CutConvert

Greg builds CutConvert, the post-production file converter — including the first working decoder for Premiere Pro’s binary .prtranscript format. He writes these guides from the format specs and real editor workflows.

↑ Back to top