Guide
Burned-in vs soft subtitles
Every subtitle is either drawn into the picture or handed to the player as instructions. That single decision determines where your video works, what viewers can control, and whether a typo costs you a text edit or a re-encode.
The two approaches
Burned-in subtitles, also called hardcoded subtitles, hard subs, or open captions, are rendered into the video frames during encoding. Once that is done the text is pixels. Soft subtitles, also called closed captions or sidecar subtitles, live in a separate file or a separate track, and the player draws them at playback time.
| Playback support | Burned in works in every player without exception. Soft depends entirely on the player and platform. |
|---|---|
| Viewer control | Burned in cannot be switched off or swapped. Soft can be toggled and switched between languages. |
| Appearance | Burned in looks the way you made it, everywhere. Soft is styled by whatever is playing it. |
| Search engines | Burned-in text is not machine readable. An uploaded subtitle file is, which is why it helps a video get found. |
| Fixing a mistake | Burned in requires a re-encode. Soft is a text edit. |
| Multiple languages | Burned in means one file per language. Soft can carry several tracks alongside one video. |
| Font coverage | Burned in always renders, because the glyphs became pixels. Soft shows boxes if the viewer device lacks a font for the script. |
When to burn in
- Social feeds, which mostly do not read subtitle files and mostly autoplay muted. If the text is not in the picture, most viewers never see it.
- Anywhere the playback environment is unknown: embeds, messaging apps, downloads, and files that get passed around.
- Non-Latin scripts, where a missing font on the viewer's device turns a soft subtitle into a row of boxes.
- Anything where the positioning or styling is part of the point rather than incidental.
When to keep them soft
- Video platforms that read subtitle files properly and index them, which is how the spoken content becomes findable.
- Content you will publish in several languages from a single video file.
- Anywhere accessibility settings matter, since viewers can resize, restyle, or reposition soft subtitles to suit them.
- Anything still in flux, because corrections cost a text edit rather than a re-encode.
The answer is usually both
These are not mutually exclusive. Publishing the burned-in version where subtitle files are ignored, and the soft file where they are honoured, gets you the reach of one and the flexibility of the other. Every job here returns both: an MP4 with the subtitles burned in, and SRT files in the original and translated languages.
Get both from one job with 50 free credits.
Continue with Google50 free credits. No credit card needed.Frequently asked questions
Are hardcoded and burned-in subtitles the same thing?
Yes. Burned in, hardcoded, hard subs, and open captions all describe subtitles rendered into the picture rather than supplied separately.
Can I remove burned-in subtitles later?
Not cleanly. The text is part of the image, so removing it means covering or reconstructing what was underneath. Keep the original file if you might need a clean version.
Do burned-in subtitles help SEO?
Not directly, because search engines cannot read pixels as text. Publishing the transcript or an uploaded subtitle file alongside the video is what makes the spoken content findable.
Which should I use for social media?
Burned in. Most feeds do not read subtitle files and autoplay without sound, so text that is not in the picture usually goes unseen.