On this page
Two kinds of captions, one real difference
The terms get used loosely, so it's worth pinning them down. Closed captions live in a separate track from the video — an SRT or VTT file, or a platform's own format — and the viewer can switch them on or off. Burned-in captions (also called open, hardcoded, or baked-in) are rendered permanently into the pixels of the frames and can't be turned off by anyone. Both show text synced to speech; the entire distinction is whether the viewer controls visibility, and that single difference is what determines which one you should use in any given situation.
When closed captions are the right call
Closed captions win wherever flexibility, compliance, or discoverability matter. On long-form YouTube content they're best practice, because YouTube's system supports multiple languages, makes the spoken words searchable, and lets viewers control the display — so uploading an SRT alongside the video is simply the correct move. For accessibility compliance they're often legally required: standards like the ADA and CVAA generally specify closed captions precisely because viewers with visual impairments can restyle them to their needs. Professional broadcast requires them in specific formats (CEA-608/708). They also suit visually busy content where some viewers would rather not have permanent text on screen, and any multi-language project, where separate tracks let each viewer pick their language. The common thread is that closed captions hand control to the viewer and the platform — which is exactly what these contexts demand.
When to burn them in
Burned-in captions win wherever you need control and guaranteed visibility. On short-form social — Instagram, TikTok, LinkedIn, X, all of which autoplay muted — the platform's own captions either don't fire in the feed or can't be styled, so burning in is the only way to guarantee your text appears, exactly as designed, in the silent scroll where it matters. Any animated caption style — highlight, karaoke, pop, bounce — has to be burned in, because separate caption files can't carry animation at all. Burned-in text always displays, removing the risk that a viewer never sees your captions because the toggle was off. It renders identically everywhere, sidestepping the per-platform rendering differences that plague closed captions. And it travels with the file, so when someone downloads or reshares your video, the captions come along. The thread here is the inverse: burned-in captions keep control with you, the creator.
Side by side
| Factor | Closed Captions | Burned-In |
|---|---|---|
| Viewer control | Yes | No |
| Styling options | Platform-dependent | Full control |
| Animation | No | Yes |
| Multi-language | Yes | One per video |
| File size | Smaller | Same |
| Accessibility compliance | Yes | Partial |
| Social media optimization | Poor | Excellent |
| YouTube SEO | Yes (searchable) | No |
What to do on each platform
In practice the choice resolves cleanly by destination. YouTube wants both: upload an SRT for accessibility and SEO, and add burned-in captions on top if you want styled text that shows in every playback context. Instagram, TikTok, Reels, and Shorts are burned-in only, since their platform captions can't be styled — generate and style your captions before uploading. LinkedIn is also best served burned-in, because its caption support is inconsistent and burning in guarantees visibility. Website embeds should use closed captions where the player supports them, with a burned-in version as a fallback for players that don't. And podcast clips are burned-in, because short social clips need visible text for muted scrolling.
Producing each one
Burned-in captions are straightforward to create: the captions tool transcribes your audio with word-level timing, lets you style font, color, and animation, and renders the result directly into the exported video, so the words are part of the frames. Closed captions are a separate artifact — an SRT file, which you can get from paid services like Rev, Otter.ai, or Descript, from YouTube's free auto-generate, or by hand in any text editor following the SRT format, then upload alongside the video on platforms that support it.
Most serious creators end up doing both, and the workflow is simple: produce the video with burned-in captions as the primary deliverable for social, export a separate SRT for the YouTube upload, and keep that caption source file around as the basis for future translations. The burned-in version carries the styled, social-ready look; the SRT covers accessibility compliance and search.
That split also resolves the two points people most often get wrong. First, animation only exists burned-in — highlight effects, word-by-word reveals, bounce, pop, and glow can't live in a closed-caption file at all, so if you want them, you generate them and burn them in. Second, on accessibility, burned-in captions don't fully satisfy strict requirements, because viewers can't resize, recolor, reposition, or screen-read them. So for content that must meet a compliance bar, provide closed captions; treat burned-in as a supplement to them, never a replacement.
Related: How to add captions automatically | Auto captions vs manual subtitles
Tagged