Burn-in vs sidecar subtitles: which export, and when
Should you burn subtitles into the video or export a separate subtitle file? A practical guide for video editors and content creators — including transparent, alpha-channel caption assets for Premiere and DaVinci.
Once your captions are timed and clean, you hit a fork that trips up more editors than it should: burn them into the video, or keep them as a separate file? Both are right — for different jobs. Pick wrong and you’re re-exporting at midnight, or worse, sending a client the version they can’t turn off when they needed the one they could.
Let’s make the decision easy.
Burn-in (baked into the pixels)
Burned-in (or “hardcoded”) captions are part of the video frame itself. They can’t be turned off, can’t be re-styled by a platform, and always look exactly how you designed them.
Use burn-in when:
- You’re posting to social — TikTok, Reels, Shorts — where captions must always show and match your brand style.
- You want total control of font, size, position, weight, and animation.
- The platform doesn’t reliably render uploaded subtitle files (many don’t, or render them ugly).
- You want a single, self-contained file that looks identical everywhere.
The trade-off: permanence. The captions are now pixels. A typo means a re-render, and you can’t offer the viewer a language toggle or turn them off for the hearing audience who’d rather not have them.
Sidecar / asset (a separate layer)
A “sidecar” is a separate subtitle file (like an SRT) — or, better for editors, a rendered caption asset with a real alpha channel that drops onto its own track in Premiere, DaVinci Resolve, or Final Cut.
Use a sidecar or asset when:
- The captions go to an editor who wants them on their own layer, above the picture.
- You need selectable, accessible captions — YouTube, broadcast, or accessibility compliance (many contexts legally require toggleable captions).
- You want to reuse the same styled captions across multiple cuts or aspect ratios.
- You’re delivering multiple languages and want one clean base to translate from.
The pro move: a transparent, alpha-channel caption asset gives editors burn-in-quality styling plus the flexibility of a separate layer. They can slide it, fade it, or swap language versions without ever touching your typography. It’s the best of both worlds, and it’s what separates a “captioner” from a subtitle workflow.
The quick-decision table
| Situation | Best export |
|---|---|
| Social, always-on captions | Burn-in |
| Handing off to an editor | Alpha-channel asset |
| Accessibility / selectable | SRT sidecar |
| Multiple language versions | Sidecar/asset + re-translate |
| Broadcast / compliance | SRT or asset (toggleable) |
| One self-contained file | Burn-in |
A real-world flow
Say you cut a brand video that lives in three places: a 60-second vertical cut for Reels, a 16:9 version for YouTube, and a master handed to the client’s in-house editor. The smart delivery is: burn-in for the Reel (always-on, styled, self-contained), an SRT for YouTube (selectable, accessible, good for SEO — YouTube reads caption text), and a transparent asset for the client’s editor to place on their own timeline. Three destinations, three correct formats, one set of captions.
Why this should come from one project
The mistake is timing and breaking your captions once, then rebuilding them per format. The whole point of a real subtitle tool is that you get the captions right once and export them however each destination needs. SubSlap does exactly that — burn-in for the post, an alpha-channel asset for the editor, an SRT for the platform, all from the same timed, broken, translated project. Time it once. Ship it everywhere.