Burned-In Captions vs SRT: When to Use Which
A straight answer per platform, why you should usually export both, and what an .srt does for discovery that burned-in text cannot.
Summary — the short answer
- Burned-in captions and .srt files do different jobs — mature creators export both.
- Burned-in gives you typographic control and works everywhere, including platforms with no caption support.
- An .srt is machine-readable, so it feeds search, recommendation and translation.
- Short-form needs burned-in; long-form and accessibility need the .srt.
- Exporting both costs one checkbox and materially improves discovery.
Key facts
- Reels
- Burned-in only
- Shorts
- Burned-in + SRT recommended
- YouTube long-form
- SRT essential
- Both supported
- SRT benefit
- Indexable by search
These are not competing options. They solve different problems, and treating them as an either-or choice is why so many creators leave discovery value on the table.
Burned-in captions
The text becomes part of the pixels. It cannot be switched off, it looks identical on every device and platform, and you control the typography completely — weight, colour, stroke, animation, position. This is what short-form needs, because platform auto-captions are typographically generic and frequently inaccurate with code-mixed speech.
The trade-off is that burned-in text is invisible to machines. A search engine cannot read it, a translation system cannot use it, and a viewer who needs a different font size cannot change it.
SRT caption files
An .srt is a plain timed-text file the platform reads. It can be toggled, restyled by the viewer, translated automatically, and — most importantly — indexed. YouTube uses caption text to understand what a video is about, which affects both what it recommends and what surfaces in search.
For any video you want discovered rather than merely consumed, the .srt is the part doing SEO work.
Which to use where
| Destination | Burned-in | SRT | Notes |
|---|---|---|---|
| Instagram Reels | Yes | Not supported | Style them yourself |
| YouTube Shorts | Yes | Recommended | SRT aids search |
| YouTube long-form | Optional | Yes | SRT is the primary track |
| Yes | Yes | Autoplay is muted by default | |
| Website embed | Optional | Yes | Needed for WCAG compliance |
| WhatsApp / DM sharing | Yes | No | File travels without metadata |
Accessibility is not the same as captions being present
Burned-in captions help a lot of people, but they are not a complete accessibility solution. Screen readers cannot access them, viewers cannot resize them, and they cannot be replaced with a translated track. WCAG expects a real caption track for pre-recorded video, which in practice means the .srt.
Practical export settings
- 1Burn in captions styled for the platform, inside the 16–84 percent safe band.
- 2Export a matching .srt from the same word-level transcript so the two never drift apart.
- 3Name files consistently — slug, ratio, resolution — so a batch stays organised.
- 4Upload the .srt at publish time rather than later; retrofitting captions loses the early distribution window.
- 5Keep the transcript itself, because it becomes your post caption, your blog copy and your Shorts description.
Frequently asked questions
Does Instagram support SRT uploads?
Not for Reels. Instagram offers auto-generated captions, but for branded short-form burned-in captions remain the practical option.
Will burned-in captions hurt my YouTube SEO?
They do not hurt, but they do not help either, because they are not machine-readable. Attach an .srt so the text is indexable.
Can I generate an SRT from burned-in captions?
Only by re-transcribing, which introduces drift. Export both from the same original transcript instead.
Should the SRT match the burned-in text exactly?
Yes. Divergent tracks confuse viewers who have both visible and undermine trust in the captions.
Sources and further reading
- YouTube — supported subtitle and caption filesOfficial list of accepted caption formats, including SRT.
- W3C WCAG 2.1 — captions for prerecorded mediaThe success criterion that a real caption track satisfies.
- W3C WAI — planning audio and video captionsPractical guidance on producing quality caption tracks.
- VerbCraft: caption safe areasWhere the burned-in version must sit.
- VerbCraft: word-level captionsThe transcript both exports are generated from.
Use this article elsewhere
Copy a structured brief for ChatGPT, Claude, Perplexity or Gemini — it includes the key points and the canonical link so the assistant can cite VerbCraft properly.
https://verbcrafts.in/blog/burned-in-captions-vs-srt
