Open Captions vs Closed Captions: What's the Difference (2026)
Open captions are burned permanently into the video pixels — always visible, no toggle. Closed captions are a separate track (SRT/VTT file) viewers turn on or off. Use open captions for platforms without caption toggles (social media, some ads); use closed captions for anything requiring accessibility compliance or viewer control (YouTube, streaming, broadcast).
The difference in one table
| Feature | Open captions | Closed captions |
|---|---|---|
| Always visible | Yes | No (viewer toggle) |
| Delivery | Burned into video pixels | Sidecar SRT/VTT file |
| Editable after export | No (re-render required) | Yes (edit the SRT/VTT) |
| Multi-language per file | One track only (re-render per language) | Multiple tracks per file |
| Accessibility toggle | None — always shown | User can hide |
| File size overhead | Zero (part of video) | Tiny sidecar file (~10-100 KB) |
| Player support | Universal — any player | Requires caption-aware player |
When to use open captions
Open captions are baked into the pixels. If you can't rely on the viewer, the player, or the platform to show closed captions consistently, burn them in.
| Platform / context | Why |
|---|---|
| Instagram Reels | Caption toggle behavior is inconsistent across app versions and autoplay contexts |
| TikTok | Feed autoplay does not consistently show sidecar captions |
| LinkedIn video | Feed autoplay behavior varies; burned-in captions guarantee visibility |
| Ads / promotional video | You cannot rely on viewers toggling captions on |
| Karaoke, music videos, artistic captions | Styling is part of the creative product, not accessibility |
When to use closed captions
Closed captions ship as a sidecar file. Any platform with a caption toggle should get them — they're smaller, more accessible, and multi-lingual by default.
| Platform / context | Why |
|---|---|
| YouTube | Native SRT/VTT support, multi-language upload, SEO benefit from caption indexing |
| Netflix / Amazon / Disney+ | Streaming platforms enforce closed-caption tracks for accessibility compliance |
| Broadcast TV (US) | FCC 47 CFR §79 requires closed captions on broadcast |
| Vimeo, HTML5 <video> | WebVTT is the standard track element for HTML5 web video |
| Multi-language audiences | One video file with separate tracks per language |
Which one does VexaScribe produce?
Closed captions. VexaScribe generates SRT and VTT files that you attach as separate tracks — the sidecar model. This gives you multi-language, edit-later, toggle-on/off flexibility by default.
For open captions: export the SRT from VexaScribe, then burn it into the video with FFmpeg, HandBrake, or a video editor (CapCut / Premiere / DaVinci). The FFmpeg one-liner:
ffmpeg -i input.mp4 -vf "subtitles=input.srt" output.mp4To style the burned-in captions (font, color, background), extend the filter: -vf "subtitles=input.srt:force_style='Fontname=Arial,FontSize=24,PrimaryColour=&Hffffff,BorderStyle=3,Outline=1'". Every video editor has an equivalent inspector panel for subtitle styling.
Accessibility law quick reference
Not legal advice — consult a specialist for your specific situation. As a general orientation:
| Jurisdiction / standard | Requirement |
|---|---|
| US — ADA | Closed captions required on video for public accommodation entities (DOJ guidance) |
| US — FCC 47 CFR §79.1 | Closed captions required on broadcast TV and pre-recorded internet video previously shown on TV |
| EU — EAA (Directive 2019/882) | Captions required on platform-provided content from June 28, 2025 |
| WCAG 2.2 Level AA | Captions required for all pre-recorded audio content in synchronized media (Guideline 1.2.2) |
For compliance purposes, closed captions (as a sidecar file that the viewer can toggle) generally satisfy these requirements. Open captions also satisfy accessibility because they're always visible, but they don't allow the viewer to hide the caption — which some frameworks (WCAG 2.2 Level AAA, some platform-specific rules) treat differently. When in doubt, ship both: closed captions as the primary compliance format, open captions for platforms without reliable caption toggles.
Frequently asked questions
What's the difference between open and closed captions?
Open captions are burned permanently into the video pixels — always visible, no toggle. Closed captions live in a separate track (typically SRT or VTT file) that viewers can turn on or off. Same text, different delivery: open captions ship with the video and can't be edited or hidden, closed captions ship as a sidecar file and can be toggled, edited, translated, and multiplied across languages. Which one you use depends on the platform and whether your audience needs the option to hide them.
Are subtitles the same as closed captions?
No, though they overlap. Subtitles translate spoken dialogue for viewers who can hear but need the language translated. Closed captions transcribe dialogue plus non-speech audio (music cues, sound effects, speaker identification) primarily for deaf and hard-of-hearing viewers. Regulated broadcast contexts (US FCC, EBU) require closed captions specifically; a streaming platform's Spanish subtitle track and its Spanish closed-caption track may or may not be the same file. See our full explainer at /captions-vs-subtitles.
How do I turn closed captions into open captions?
Burn the SRT or VTT into the video pixels using FFmpeg, HandBrake, or your video editor. FFmpeg one-liner: `ffmpeg -i input.mp4 -vf "subtitles=input.srt" output.mp4`. In CapCut, Premiere, or DaVinci Resolve: import the SRT to a subtitle track, style it, then render/export with the subtitle track burned in. Once burned in, the captions become part of the video pixels and can't be turned off — that's the whole point of open captions.
Which is better for YouTube?
Closed captions. YouTube supports SRT and VTT upload natively — you get toggle-on/off for viewers, multi-language tracks per video, and better SEO (YouTube reads the caption file for search indexing). Open captions on YouTube waste that infrastructure. The one exception: if your channel targets audiences on platforms that will re-share your videos to feeds where captions don't display by default (Reddit auto-play, Twitter feed video), also burn in open captions for the re-share ecosystem while keeping closed captions for the YouTube view.
Do open captions work on Instagram Reels?
Yes — and they're often the safer bet on Reels because Instagram's caption toggle behavior is inconsistent across app versions, autoplay contexts, and devices. Creators who want to guarantee every viewer sees the caption burn them in. Instagram does support closed captions on Reels (upload SRT via the caption feature), but the safest workflow for social-first videos is burn-in for reliability + keep the SRT sidecar for accessibility compliance where required.
What's SDH?
SDH stands for Subtitles for the Deaf and Hard of Hearing. It's a specific type of subtitle track that adds non-speech audio descriptions (like [door slams], [ominous music]) and speaker identification to what would otherwise be dialogue-only subtitles. In practice SDH is closer to closed captions than to regular subtitles, but the term is used mostly on streaming platforms (Netflix, Amazon Prime, Disney+) for their accessibility-focused caption tracks. See our full definition at /what-is-closed-captioning.
Related reading
- What is closed captioning? — full definition, history, and SDH.
- Captions vs subtitles — a related but distinct comparison.
- AI caption generator — generate SRT/VTT closed captions from any audio or video.
- How to add subtitles to a video — step-by-step for YouTube, CapCut, Premiere, DaVinci Resolve.
- What is an SRT file? — the format VexaScribe exports.