Closed Captions vs Subtitles and When You Need Each

You uploaded a video, opened the text track menu and found two options that look identical: captions and subtitles. Pick the wrong one and deaf viewers miss half the story, or a translated audience gets a file full of sound tags they never needed.

The difference between closed captions vs subtitles is not just vocabulary. It changes what goes in the file, how you label it on upload and who can actually follow your video. I have spent years cleaning up caption archives where the two were mixed up, so here is the practical version: what each one contains, when you need which, and how to produce both without doubling your workload.

Closed captions vs subtitles in plain terms

Subtitles assume the viewer can hear. They carry spoken dialogue, usually translated into another language, and nothing else. A French film with English subtitles gives you the words and trusts you to hear the door slam.

Closed captions assume the viewer cannot hear. They carry dialogue plus every sound that matters to the meaning: speaker names when the speaker is off screen, music cues, laughter, a phone ringing in the next room. "Closed" means the viewer can switch them on or off, as opposed to open captions, which are burned into the picture.

There is a third type that causes most of the confusion. SDH, short for subtitles for the deaf and hard of hearing, looks like subtitles on screen but includes the sound information of captions. Streaming services use SDH because their players handle subtitle files more easily than broadcast caption formats.

What goes into a closed caption file that subtitles leave out

A good caption file answers one question for a viewer with the sound off: what would I be missing right now? That covers four kinds of information.

• Speaker identification. When the speaker is not visible, or when two people talk over each other, a label like [MAYA] or a dash at the start of a line tells the viewer who is talking.
• Sound effects. Only the ones that matter. [door slams] matters if it ends an argument. Background traffic in a city vlog usually does not.
• Music. A note symbol or [upbeat music] at the start of a segment, plus lyrics if the lyrics carry meaning.
• Manner of speech. [whispering], [sarcastic] or [shouting] when tone changes the meaning of a line.

Keep sound tags short. Two to four words in square brackets, lowercase, is the convention most broadcasters and platforms follow. A tag like [dramatic orchestral music swells as the camera pans] takes longer to read than the shot lasts.

Speaker labels deserve their own care on multi-host content. If you run a show with three regular voices, the approach in labelling speakers in captions for a video podcast keeps viewers oriented without cluttering every line.

When you need captions, subtitles or both

Here is how I decide on most projects.

1. Your audience shares your language. You need closed captions. Subtitles in the same language without sound cues are only half the job.
2. You are reaching a new language market. You need subtitles in that language. If you also want deaf viewers in that market, make SDH instead of plain subtitles.
3. Your video is mostly watched muted. Social feeds autoplay without sound, and a large share of viewers never tap to unmute. Closed captions work here, but many creators use open captions so the text appears without a tap.
4. You publish for schools, government or large companies. Accessibility rules in many countries require captions, not subtitles, for public facing video. Check your contract or the relevant rule before you deliver.

Most channels end up with one caption track in the original language and one or two subtitle tracks for their biggest foreign audiences. A 12 minute video with 1,800 spoken words might take 40 to 60 minutes to caption properly from a decent auto transcript, and another 30 to 45 minutes per language to translate and retime.

Why burning captions in is not the safe default

The common advice for social video is to burn captions into every export so nobody misses them. I push back on that for most long form content. Burned in text cannot be resized, turned off, translated or read by a screen reader. It also gets cropped when platforms reframe your video for a different aspect ratio.

A closed caption file does more. Viewers with low vision can enlarge it. Search engines and platforms can index the text. You can fix a typo in two minutes instead of re-rendering a 4 GB export. The longer argument is in why burned-in subtitles are usually the wrong choice.

Open captions earn their place on short vertical clips under 60 seconds that live only in autoplay feeds. Everywhere else, ship a proper sidecar file and let the viewer choose.

Producing both from one transcript

You do not need to start from scratch twice. Build the caption file first, then strip it down.

1. Generate an auto transcript and correct every word against the audio. Budget about 4 minutes of editing per minute of speech.
2. Add speaker labels and sound tags to make a full closed caption file. Save it as your master, for example video-en-cc.vtt.
3. Duplicate the master and remove every bracketed tag and speaker label for a plain subtitle base.
4. Send the plain base to your translator. Translating sound tags wastes their time if the target track is subtitles only.
5. For SDH in another language, translate the full master instead, tags included.
6. Retime each translated file. German and Spanish often run 15 to 25 percent longer than English, so lines may need splitting.

File format matters at step two. WebVTT and SRT both work for most platforms, and the reasons to pick one over the other are covered in choosing a caption file format that actually survives re-uploads.

Labelling tracks correctly when you upload

Platforms let you name each text track. Use that field. A track called "English" tells a deaf viewer nothing about whether sound cues are included. Label tracks like this:

• English (CC) for the full caption track in the original language
• Spanish for plain translated subtitles
• Spanish (SDH) for translated subtitles with sound cues

Set the language code correctly too. A Spanish file tagged as English will show up in the wrong menu and can confuse automatic translation features that some players offer.

Frequently asked questions

Are closed captions and subtitles the same thing?

No. Subtitles carry only spoken dialogue, usually translated, for viewers who can hear. Closed captions add speaker names, sound effects and music cues for viewers who cannot hear the audio.

What does CC mean on a video?

CC stands for closed captions. It means a text track is available that you can switch on or off, and that it should include sound information as well as dialogue.

Is SDH better than closed captions?

Neither is better. SDH carries the same information as closed captions but uses subtitle formatting, which streaming players handle more consistently. Use whichever format your platform supports best.