How to burn subtitles into a video on Mac

To burn subtitles into video on a Mac, you render the subtitle text into the picture during an export, so it appears on every player and cannot be switched off. The free route is HandBrake: open the video, add your SRT file in the Subtitles tab and tick Burn In. If you already edit in Final Cut Pro, DaVinci Resolve, Premiere Pro or cinemaOS, each has a burn-in option at export. The harder parts are deciding whether to hardcode at all, making the text readable on a phone, and checking the file before it goes public.

Burn in or ship a sidecar file?

Burned-in subtitles are often called open captions or hardsubs. A sidecar file, such as SRT or WebVTT, travels next to the video and the player draws the text.

Hardcoding is the right call when:

• The platform or player ignores subtitle files. Many short-form apps, messaging apps, presentation software and venue playback systems show the picture and nothing else.
• Most people watch without sound. Social feeds autoplay muted, and a viewer who has to tap to enable captions often never does.
• The subtitles are part of the story. Translated lines for a scene in another language, or a sign the audience must read, belong to the film itself.
• A screener must look the same everywhere. A festival or client link that might be opened on any device is safer with the text fixed in the picture.

A sidecar is better when:

• Viewers need control. Accessibility depends on being able to turn captions on, resize them or pick a language. Burned-in text removes those choices.
• You deliver more than one language. One master with several subtitle files is lighter than a render per language.
• The recipient has a specification. Broadcasters, streaming services and distributors usually ask for subtitle files and a textless master, not hardsubs.
• Text may change. A typo in an SRT is a one-minute fix. A typo in burned-in text means a new render and a new upload.

The safest habit is to keep subtitles as data for as long as possible and burn them in only for the deliverable that needs it. If you are unsure which file format a platform wants, our guide to subtitle formats explains SRT, WebVTT, EBU-STL and the rest.

Finish the subtitle file before you burn

Burning in freezes every mistake, so correct the text first.

• Words and names. Check proper nouns, numbers and anything a speech model may have guessed.
• Timing. Each line should appear when the speaker starts and leave shortly after they stop, without flashing past.
• Line length and reading speed. Two lines at most, broken at natural phrase boundaries. Professional style guides set limits on characters per line and characters per second. The Netflix English timed text style guide is a widely used reference; check its current version for the exact numbers.
• Shot changes. Lines that hang a few frames over a cut look sloppy once burned in. Snap them to the cut or hold them clearly past it.

If your subtitles are a translation, have a fluent speaker read them now. Our article on translating subtitles locally on a Mac covers that review step.

Readable styling that survives compression

Burned-in text has to work on bright and dark shots, on a small phone screen, and through the platform's own re-encode.

• Typeface. A plain sans serif with open letter shapes reads best at small sizes. Avoid thin and condensed weights.
• Size. Judge it on the smallest screen your audience will use. Vertical video watched on a phone usually needs larger text than a widescreen file watched on a laptop.
• Contrast. White or off-white text with a dark outline or soft shadow handles most shots. On busy footage, a semi-transparent dark box behind the text is the most reliable option.
• Position. Keep text inside the title safe area. For 9:16 posts, leave room at the bottom and sides for the app's buttons, captions and progress bar, which often means placing subtitles higher than you would on a widescreen film.
• Conflicts. When on-screen text or a lower third already sits at the bottom of the frame, move the subtitle to the top for that line instead of overlapping.
• Characters. Make sure the font covers every accent and script in your file. Missing glyphs show up as empty boxes.
• Consistency. Use italics only for a clear reason, such as off-screen voices, and keep the style the same across the whole piece.

Burn in at the final delivery resolution and frame size. If you reframe a 16:9 film to 9:16, add subtitles after the reframe, never before, or they will be cropped. Our guide to reframing horizontal video to vertical covers the rest of that process. Finally, export from your best master rather than from an already compressed file, and give the encoder enough bitrate. Fine text edges are the first thing low bitrates damage.

Ways to burn subtitles in on a Mac

Apple's free apps will not do this job. QuickTime Player and iMovie have no option to import an SRT file and burn it in, so in iMovie you would have to retype every line as a title by hand. For anything longer than a few lines, use one of the routes below. Menu names match recent versions of each app and can move between releases, so check the vendor's help pages if something has shifted.

HandBrake: free, for a finished video

HandBrake is a free, open-source transcoder. Open your finished video, go to the Subtitles tab, and use the Tracks menu to add an external subtitle file. Set the character encoding if your SRT contains accented characters, then tick Burn In for that track. Only one subtitle track can be burned in per encode. Plain SRT files render in a simple default style, while ASS or SSA files keep their own fonts, colours and positions, which is how many people get custom styling out of HandBrake. Choose a high-quality preset, because the picture is re-encoded either way.

ffmpeg: for scripted batches

If you are comfortable in Terminal, ffmpeg's subtitles filter burns an SRT or ASS file into the picture, and its force_style option sets font, size and outline for SRT input. It needs an ffmpeg build that includes libass.

Final Cut Pro

Import the subtitle file with File ▸ Import ▸ Captions, or create captions on the timeline. Adjust text and placement in the inspector, within what each caption format allows. When you share, the Roles tab lets you choose which caption role to burn in.

DaVinci Resolve

Import the subtitle file into the media pool and add it to the timeline as a subtitle track. Track and caption styling, including font, size, colour, outline, shadow and background, lives in the inspector. On the Deliver page, open the subtitle settings, enable subtitle export and choose to burn the subtitles into the video.

Premiere Pro

Import the SRT to create a caption track, then style it with Premiere's caption and graphics controls. In the export settings, the Captions section offers an option to burn captions into the video.

cinemaOS

In cinemaOS, subtitles live in Finisher (⌘2) ▸ Localize ▸ Captions. You can import a subtitle file or transcribe the dialogue locally, correct it, translate it on the Mac if you need another language, and preview it against the picture. QC checks the subtitles before delivery. From there you either export a sidecar file in formats such as SRT, WebVTT, ASS, SCC, EBU-STL or Apple iTT, or choose Burn In to render the subtitles into the picture as a new deliverable. Exports do not silently overwrite an existing file: if the name is taken, cinemaOS writes a new, uniquely named file, so the burned-in copy sits next to your clean master instead of replacing it. The offline subtitles tutorial shows the whole path, from captions to a French version to Burn In.

The limits, honestly: cinemaOS runs only on Apple silicon Macs for now, with Windows planned for November 2027, and it is a young app at version 0.2, Build 9. Local transcription and translation still need a human language review, and platform-specific subtitle requirements still need checking against the recipient's current specification. If you already have a finished video and a correct SRT, HandBrake is the quicker tool for that single job.

QC the burned-in file before upload

Check the exported file, not the timeline.

1. Play the whole file on the device your audience uses, at full screen. For social cuts, that means a phone.
2. Check sync at the start, middle and end. Drift that is invisible in the first minute can be obvious by the last.
3. Read every line once. Look for typos, wrong line breaks, missing accents and empty boxes where a glyph was missing.
4. Watch the hard shots. Bright skies, white walls, snow and fast motion are where outlines and boxes fail.
5. Look at the edges. Confirm nothing is cropped, and that platform buttons will not cover the text.
6. Check cuts and fades. Subtitles should not flicker across a shot change or vanish during a dissolve.
7. Confirm it is the right version. Language, aspect ratio, duration and audio should match what was ordered.
8. Upload privately first. Post as private or unlisted, watch the platform's own re-encode, and only then publish.

Keep three things after delivery: the textless master, the subtitle file, and the burned-in render. The first two let you fix or re-version without starting again.

FAQ

Can I remove burned-in subtitles later?

Not cleanly. The text is part of the pixels, so removing it means covering or repainting those areas. Keep a textless master and the subtitle file so you never need to.

Does YouTube need burned-in subtitles?

No. YouTube accepts uploaded caption files, which viewers can switch on and off, and on many videos auto-translate. Burn in only for clips you will repost on platforms that ignore subtitle files.

Why do my burned-in subtitles look blurry or blocky?

Usually the bitrate is too low, the video was scaled after burning in, or the source was already heavily compressed. Burn in at the delivery resolution, from a high-quality master, with enough bitrate for sharp text edges.

Next step

Decide which deliverables truly need hardsubs, and keep everything else as subtitle files. If you want captions, translation and Burn In in the same project as your edit, try cinemaOS: it is $9.99 USD per month excluding VAT, with 60 days free, no card and no automatic charge.