How to Burn Subtitles Into a Video (FFmpeg, Editors and Online)

To burn subtitles into a video means drawing the caption text directly onto every frame, so the words become part of the picture. The result is one ordinary MP4 file that shows captions everywhere it plays — on Instagram, TikTok, YouTube Shorts, WhatsApp or a laptop — with no separate subtitle file and no player setting to switch on. You can do it with a command-line tool such as FFmpeg, inside a desktop editor, or in a browser tool that transcribes the audio and exports the finished MP4.

This guide explains what "burned-in" really means, when it is the right choice, the three practical ways to do it, and the checks worth making before you publish.

Burned-in subtitles in one sentence

Burned-in subtitles (also called hardcoded subtitles or open captions) are pixels, not data. Once exported, they cannot be turned off, restyled or searched by the player, because the player only sees an image of the words.

That single fact drives every trade-off below. It is why burned-in captions look identical on every platform, and also why they cannot be edited after export without re-rendering the video.

When burning in is the right choice

Burn subtitles into the video when:

• The platform has no reliable subtitle upload. Short-form apps generally expect captions to be part of the video or produced by their own auto-caption feature. A separate .srt file has nowhere to go.
• You want a designed look. Animated, word-by-word or highlighted captions are a visual style. They only exist as burned-in graphics.
• You need the same result everywhere. A file shared in a chat app or reposted to another platform keeps its captions.
• Many viewers watch without sound. Text on screen carries the message when audio is muted.

Prefer a separate subtitle file (closed captions) when viewers need to switch captions off, choose a language, or resize text, and when the platform supports uploads — for example long-form video on YouTube. See hardcoded vs soft subtitles for the full comparison.

Method 1: FFmpeg (free, command line)

FFmpeg is a free, open-source tool. Its subtitles filter renders an existing subtitle file onto the video frames. A typical command looks like this:

ffmpeg -i input.mp4 -vf "subtitles=captions.srt" -c:a copy output.mp4

What this does: it reads input.mp4, draws the cues from captions.srt onto each frame, copies the audio unchanged, and writes output.mp4. The filter is documented in the official FFmpeg filters documentation, including options for styling through the ASS format. 1

Strengths: free, scriptable, precise. Limitations: you must already have an accurate, timed subtitle file; styling is limited to what the subtitle format describes; and animated word highlighting requires hand-built ASS files. It also re-encodes the video, so choose a sensible quality setting.

Method 2: A desktop or mobile video editor

Most editors let you add text layers or import subtitles and then export with captions rendered. This gives full visual control, but timing every line by hand is slow for anything longer than a few seconds. Many editors now offer automatic transcription; check whether it supports your language and whether export requires a subscription or adds a watermark.

Method 3: A browser caption tool (transcribe + style + export)

Browser tools combine the steps: upload a clip, get an automatic transcript with timings, pick a caption style, then export an MP4 with the captions burned in.

CaptionLabs works this way. It transcribes English, Hindi and Hinglish speech, lets you edit every word and adjust timings on a timeline, applies one of 50+ animated templates, and renders the final MP4 in your browser. The export has no watermark and keeps your clip's frame rate. Word timings are estimated from the transcript and audio, so review a few key moments before exporting. Pricing is per export: $3 for a standard export or $5 for Pro FX outside India, with no subscription. Open the studio or see pricing.

Step-by-step checklist for any method

1. Start with clean audio. Background music and overlapping speakers reduce transcription accuracy.
2. Get the words right first. Correct names, brand terms and numbers before styling. Burned-in mistakes are permanent in that file.
3. Check timing at the start and end of each line. Captions that appear late feel disconnected from speech.
4. Keep lines short. One or two short lines are easier to read on a phone than a full sentence.
5. Place text inside the safe area. Platform buttons cover parts of vertical video. See the Reels safe zone guide.
6. Use contrast. A stroke, shadow or background pill keeps text readable over bright footage.
7. Watch the export once, start to finish, with sound off. If you can follow it muted, the captions are doing their job.

Quality and file size

Burning in always re-encodes video, because new pixels are being drawn. For social platforms, exporting at the platform's native shape (1080×1920 for vertical) and keeping the source frame rate avoids extra scaling and stutter later. Very low bitrates can blur small text, so thicker fonts and a stroke survive compression better than thin type.

Accessibility note

Burned-in captions help viewers watching without sound and many people who are deaf or hard of hearing, but they cannot be customised by the viewer. The W3C's guidance describes captions as including speech and relevant sound information, synchronised with the media. 2 If accessibility is a requirement — not just reach — consider also providing a closed-caption file where the platform allows it.

Frequently asked questions

Can I remove burned-in subtitles later?

Not from the exported file. Keep your original clip and project so you can re-export a corrected version.

Do burned-in subtitles reduce video quality?

They require a re-encode, which can soften fine detail at low bitrates. At reasonable bitrates the difference is usually hard to see on a phone.

Is FFmpeg or a browser tool better?

FFmpeg is ideal if you already have a correct subtitle file and are comfortable with the command line. A browser tool is faster when you also need transcription, editing and animated styles.

Will burned-in captions be read by search engines?

No. Text drawn into pixels is not machine-readable subtitle data. Put key words in your post description as well.