Open Captions vs Closed Captions: What's the Difference?

The difference is one word: control. Closed captions live in a separate track the viewer can turn on or off; open captions are burned into the video's pixels and are always visible, for everyone, forever. Everything else — when to use which, why platforms differ, what accessibility law expects — follows from that split.

The vocabulary, untangled

• Closed captions (CC): a text track delivered alongside the video (SRT, VTT and friends). Toggleable, selectable, machine-readable, editable after publishing.

• Open captions: text rendered onto the video itself during export. Not toggleable, not machine-readable as text, fixed at export time.

• Subtitles vs captions: in common usage, subtitles assume you can hear and translate or transcribe the dialogue; captions assume you can't hear, so they also note sound effects and music — [door slams], [tense music]. US usage leans "captions" for accessibility text; much of the world says "subtitles" for everything. Practically: if your audience includes viewers who can't hear the audio, include the non-speech information.

When closed captions win

Closed captions are the right default everywhere they're supported:

• Accessibility done properly. Screen readers and assistive setups work with text tracks; accessibility standards like WCAG expect captions for prerecorded audio content, and toggleable tracks are the canonical implementation. US broadcast rules (the FCC's closed captioning requirements) are built on the same model.

• Viewer choice. Multiple languages on one video, on/off per preference, adjustable size on many players.

• Fixability. A typo means re-uploading a text file, not re-exporting a video.

• Search. Platforms index caption text; burned pixels are invisible to them.

When open captions win

Open captions earn their permanence in specific places:

• Short-form social. Reels, TikTok, Shorts: autoplay is muted, and caption-track support is inconsistent — burned-in text is the only rendering you control. This is why polished short-form video ships with styled open captions as a design element.

• Anywhere you can't trust the player — embedded contexts, digital signage, conference screens.

• Stylistic intent. When the captions are part of the visual identity — kinetic text, brand fonts — you're designing, not just captioning.

Open vs closed at a glance

The practical workflow: one master, both outputs

You don't choose once — you choose per destination, from the same source:

1. Generate and review captions once with a caption generator — accurate text, phrase-based line breaks, speaker changes marked. (Auto-captions alone aren't that; we've shown why platform auto-captions disappoint.)

2. Export SRT/VTT for YouTube, your site and courses — closed captions, toggleable, indexable. (Format details: SRT vs VTT.)

3. Export a burned-in version for short-form cuts — same reviewed text, styled for the format.

4. Need other languages? Translate the caption file, and repeat the exports per market.

The reviewed transcript is the asset; open vs closed is just rendering.

Platform by platform: what actually renders

The open/closed decision is really a per-platform decision, because each platform decides what it will do with a caption file:

• YouTube — full closed-caption support: upload SRT or VTT per language, viewers toggle, the text is indexed and shown in the transcript panel. YouTube documents the upload flow in its Help Center. Burn in only for stylistic reasons.

• Your own website — closed captions via VTT tracks in the HTML5 player. Multiple languages, styling, positioning; the most controllable environment of all.

• LinkedIn and Facebook native video — accept SRT uploads for closed captions on desktop, but playback behavior varies by surface and app version. Many teams burn in anyway for feed video, because muted autoplay is the norm and they can't verify every client.

• Instagram Reels, TikTok, Shorts — open captions, full stop. Platform auto-captions exist and are improving, but you control neither their accuracy nor their styling, and third-party subtitle files are not a first-class citizen. Burned-in is how professional short-form ships.

• Course platforms and LMS — usually closed captions via uploaded files; accessibility requirements in education make toggleable tracks the expected implementation.

• Email, presentations, digital signage — assume no caption support and burn in.

How to burn in captions well

Open captions are permanent, so the styling mistakes are permanent too. The rules that keep burned-in text readable on a phone:

• Respect the safe zone. Platform UI — captions, buttons, usernames — covers the bottom and right edges of vertical video. Keep text in the middle-lower third, not pinned to the bottom.

• Two lines maximum, short lines. The same readability rules as any subtitle apply, tightened for a narrow vertical frame: two lines, roughly 30 characters each, held long enough to read.

• Contrast by construction. A semi-opaque box or a strong outline behind the text; never rely on the video staying dark behind white type.

• Size for a phone at arm's length. If it looks slightly large on your monitor, it's about right on a handset.

• Keep the position stable. Captions that jump around the frame cost viewers a re-fixation on every cue.

• Keep the SRT master. Burned-in is an export, not a source. When the platform changes its rules — or you spot a typo — you regenerate from the file, not from scratch.

Frequently asked questions

Are open captions bad for accessibility?

They're better than nothing and always visible — but they can't be resized, restyled or read as text by assistive tech, and one burned language serves one audience. Closed captions are the accessibility-grade implementation; open captions are the social-video pragmatic.

Why does "closed" mean toggleable?

Broadcast heritage: the captions are "closed" inside the signal until the viewer's decoder opens them. The terminology stuck.

Do I need captions and subtitles?

If your captions include non-speech information and your subtitles exist per language, you're covering both audiences. Most creators maintain one good caption file per language and call it done.

Which should I use on YouTube?

Closed — upload the SRT. YouTube renders it well, indexes it, and lets viewers choose. Burn-in on YouTube only for stylistic reasons.

The bottom line

Closed captions wherever the player is trustworthy; open captions where it isn't or where the text is design. Make one accurate, reviewed caption file per language, and render it both ways as destinations demand — the decision is per platform, the work is done once.