Open Captions vs Closed Captions: Which Should Your Video Use?

You've exported a video and you need captions on it. The editor asks a question that sounds minor: burn them in, or export a separate file? That choice affects who can watch, how it looks on every platform, whether you can fix a typo later, and whether search engines can read a single word.

Quick answer

Open captions are rendered into the video frames. Everyone sees them, everywhere, and nobody can turn them off. Closed captions live in a separate track or file (SRT, WebVTT, or embedded broadcast data) and viewers switch them on when they want them. Use open captions for short social video that autoplays muted. Use closed captions for almost everything else, and when in doubt, publish closed captions and keep a burned-in version only where the platform needs it.

What "open" and "closed" actually mean

The words come from television. A closed caption was hidden in the broadcast signal and only appeared when a decoder (later built into the TV) was switched on. An open caption was part of the picture for everyone. "Closed" never meant restricted; it meant hidden until requested.

Online, the same split applies:

• Closed: a caption track the player overlays at playback time. It might be a sidecar file you upload (SRT or WebVTT), a track muxed into an MP4 or MKV container, or captions embedded in a broadcast stream.
• Open: text drawn onto the frames during export. To the player, it's just part of the image. You'll also hear "burned-in", "hardcoded" or "hard subs" for the same thing, and "soft subs" for closed.

When open captions win

Muted autoplay feeds. Many people scroll social feeds with the sound off. If the first seconds of a clip don't make sense silently, they keep scrolling. Burned-in captions show immediately, with no tap required, on every app.

Platforms with weak caption support. Some apps, embedded players, digital signage, in-store screens and conference displays don't support caption files at all, or handle them inconsistently. Burning the text in is the only reliable way to guarantee it appears.

Design control. Open captions look exactly as you designed them: font, color, position, word-by-word highlighting. That's why short-form creators often use stylized burned-in captions as part of the visual identity of a clip.

Simple handoff. One file, nothing to forget. When you send a video to a partner or a client who will re-upload it, captions can't get separated from it.

When closed captions win

Accessibility that adapts to the viewer. People with low vision may need bigger text; others need higher contrast or a different background. Modern players let viewers change those settings for closed captions. Burned-in text can't change, and if it's small or low contrast, it fails the people it's meant to help.

Choice. Some viewers find captions distracting. Closed captions respect that. Open captions force a decision on everyone.

Many languages. One video can carry English captions plus Spanish, French and Japanese subtitles as separate tracks. With open captions, every language is a separate rendered video.

Corrections and updates. Spot a misspelled name after publishing? With closed captions you fix a line of text and re-upload a small file. With open captions you re-export and re-upload the whole video, often losing view counts or comments in the process.

Search and reuse. A caption file is text. Platforms, search engines and AI tools can index it, and you can reuse it as a transcript, blog post or summary. Burned-in captions are pixels; the words are effectively invisible to software unless you also provide them as text.

Accessibility and the law

Neither type is automatically compliant or non-compliant. The Web Content Accessibility Guidelines ask for captions that are accurate, synchronized, complete and include speaker identification and important sounds. Open captions can meet that bar. Closed captions are usually the better route because viewers can customize them, and some regulations and procurement policies specifically expect user-controllable captions.

Two practical cautions for open captions:

• Contrast and size are locked. Use a solid or semi-opaque background behind the text, a clean sans-serif font, and a size that's legible on a phone.
• Placement can collide with platform UI (like/comment buttons, progress bars) and with on-screen text in the video itself. Keep captions within the safe area of each platform you publish to.

This isn't legal advice. If you have a specific obligation (education, government, broadcast), check the rules that apply to you. Our video accessibility guide walks through the WCAG criteria.

Broadcast captions: CEA-608 and CEA-708

If you deliver to TV or to platforms that ingest broadcast-style masters, you'll meet two standards:

• CEA-608 (also called Line 21) is the older format from the analog era. It supports a limited character set, a small number of styling options and a fixed grid of positions.
• CEA-708 is the digital TV successor. It supports more languages and characters, more fonts and colors, and more flexible positioning.

Both are closed caption formats carried inside the video stream rather than as a separate file. Professional tools usually generate them from a timed text source such as SCC or a caption project, and many streaming workflows convert between these and WebVTT or TTML. For most web publishers, a WebVTT or SRT sidecar is all you need. Our SRT vs VTT guide explains those formats.

How to make each

Both start the same way: an accurate, timed caption file. The difference is what you do with it at the end.

Closed captions

1. Create or export an SRT or WebVTT file.
2. Review it: names, technical terms, speaker labels, sound cues, timing.
3. Upload it to your video platform as a caption track, or reference it from an HTML5 player:

<video controls src="lecture.mp4">
  <track kind="captions" src="lecture.en.vtt" srclang="en" label="English" default>
</video>

Open captions

Most editors have a "burn in captions" export option. On the command line, ffmpeg can render an SRT file onto the frames:

To control the look, convert the SRT to ASS (Advanced SubStation Alpha) and style it there, or pass styling through the filter's force_style option. The video is re-encoded, so choose a quality setting you're happy with, and keep the original un-captioned master so you can re-export later.

Doing both

The most robust approach for many teams: publish the clean video with closed captions on your website and main platform, and export a burned-in version only for social feeds that autoplay muted. Same caption file, two outputs.

Common myths

"Closed captions means the video isn't captioned." It means the captions are available on request. Look for the CC button.

"Open captions are more accessible because they're always on." Always-on helps some viewers, but fixed size and contrast can make them harder for others. Accessible captions are about accuracy and readability more than visibility.

"Burned-in captions help SEO." Search engines don't read text inside video frames as reliable content. If you want the words indexed, upload a caption file or publish a transcript alongside the video.

"You have to pick one forever." You can keep a caption file and generate burned-in versions whenever you need them.

Where the caption file comes from

Whichever delivery you choose, the hard part is the timed text. If your source is a YouTube video, YouTubeTranscript.dev pulls the existing captions or transcribes the audio when there aren't any, and exports SRT or VTT ready for your editor or player. The subtitle downloader handles a single video; the API handles a whole library. Then review it, burn it in or upload it as a track, and you're done.

For a deeper look at the terms themselves, read captions vs subtitles vs transcripts.