Burned-In vs Soft Subtitles: Which Should You Use?
Every subtitle you publish is either burned into the video image or delivered as a separate toggleable track — and the choice affects who sees your text, whether viewers can turn it off, and how much work localization takes later. Here's how the two approaches compare and a clear rule for picking the right one per platform.
What “burned-in” and “soft” actually mean
Burned-in (open/hardcoded) subtitles are rendered into the video frames themselves during export. They're part of the picture — always visible, on every device, in every player, with no action from the viewer. Soft (closed) subtitles travel as a separate file or stream (SRT, VTT, or an embedded track) that the player overlays on demand. The viewer toggles them, switches languages, and restyles them; the underlying video is untouched.
Where burned-in wins
Burned-in subtitles dominate short-form social video — TikTok, Reels, Shorts — for one reason: most viewers never enable captions, and on mute-first feeds, invisible captions might as well not exist. Burned-in text also gives you full stylistic control: karaoke-style word highlighting, brand fonts, kinetic typography. If the platform's caption support is unreliable or the audience skews casual, burning in is the pragmatic choice. The cost is permanence: typos require re-exporting, and there's exactly one language.
Where soft subtitles win
Soft subtitles win everywhere else. Viewers choose their language from multiple tracks. They restyle text for readability. Search engines and platforms index the text. Files stay small because you're not re-encoding video to change words. And accessibility tooling — screen readers, braille displays — works with text tracks, not pixels. For YouTube, streaming, courses, and anything with a shelf life, soft subtitles are the professional default.
Head-to-head comparison
- Visibility: burned-in always shows; soft requires the viewer to opt in.
- Languages: burned-in = one; soft = as many tracks as you upload.
- Styling: burned-in = total design freedom; soft = player-controlled (ASS soft tracks are the exception).
- Fixing typos: burned-in = re-export the video; soft = re-upload a text file.
- File size: burned-in can bloat encodes slightly; soft adds mere kilobytes.
- SEO/discovery: soft caption text is indexable; burned-in pixels are not.
- Accessibility: soft tracks integrate with assistive tech; burned-in is just picture.
The practical rule
Ask one question: will my viewer bother turning captions on? On YouTube and streaming platforms — where audiences expect a CC button and watch with sound — use soft subtitles. On muted autoplay feeds — TikTok, Reels, Shorts, LinkedIn — burn them in. Many creators do both from a single timed transcript: generate the master SRT with SubEasy, upload it as the soft track for YouTube, then use the same file to drive styled burned-in captions for the social cut. One transcript, every platform covered.
Deliverable checklist for client work
If you're subtitling for clients, deliver both formats by default: the master SRT (and VTT for web) as the editable, archivable source, plus a burned-in MP4 sized for the client's social channels. Name files unambiguously (project_master_en.srt, project_social_1080x1920.mp4), and note the font and styling used for the burned-in version so future edits match. Clients rarely know which format they need — handing them both, with a one-line explanation of when to use each, is the kind of professionalism that gets you hired again.
Frequently asked questions
Can I convert soft subtitles to burned-in?
Yes — any editor (Premiere, DaVinci Resolve, even ffmpeg) can render an SRT onto the video during export. That's the standard path: author soft, burn a copy for social.
Do burned-in subtitles hurt YouTube performance?
They don't directly hurt, but you lose the SEO benefit of indexable caption text and the multi-language option. For YouTube-first content, soft tracks are the better investment.
What about karaoke-style word highlighting?
That's a burned-in (or ASS-styled) technique — it needs per-word timing, which basic SRT display can't do. Generate word-level timestamps, then render with an editor or ASS styling.
Which is better for client work?
Deliver soft subtitle files (SRT + VTT) as the master deliverable — they're editable, archivable, and platform-agnostic. Provide a burned-in export only if the client specifically needs it for social.
Try it now
Ready to put this into practice? Generate one master transcript with SubEasy, then use it for both soft tracks and burned-in social cuts.