Captions vs. Subtitles

They are not interchangeable.

Most people use the terms "captions" and "subtitles" as if they mean the same thing. In everyday conversation, that's understandable.

In accessibility work, the distinction matters.

Subtitles are a text translation of spoken dialogue.

They assume the viewer can hear:

• Tone
• Music
• Sound effects
• Speaker changes

Subtitles are primarily used when dialogue is in a language the viewer does not understand.

They typically:

• Translate speech
• Do not describe sound effects
• Do not identify speakers unless necessary for clarity
• Do not include non-speech audio

Subtitles are about language access.

Captions are a full transcription of the audio experience.

They are designed for viewers who cannot hear the content.

Captions include:

• Dialogue
• Speaker identification
• Relevant sound effects (e.g., [door slams], [phone buzzing])
• Music cues when meaningful
• Non-speech audio that affects understanding

Captions are about audio equivalency.

They attempt to provide the complete informational experience of the soundtrack.

There is also a delivery distinction:

Closed captions (CC) can be turned on or off by the viewer.

Open captions are permanently burned into the video.

Closed captions are common on broadcast and streaming platforms. Open captions are sometimes used on social media or in theatrical releases.

The method of delivery does not change the purpose.

When platforms say they "support subtitles," they may only support translated dialogue.

That is not the same as supporting full accessibility.

A video can have subtitles and still:

• Omit critical sound cues
• Fail to identify speakers
• Exclude meaningful audio context

If a viewer depends on captions, subtitles alone are not sufficient.

Precision in language leads to precision in implementation.

"I turned on subtitles, so it's accessible."
Not necessarily. If sound effects and speaker shifts are missing, it is incomplete.

"Auto-generated captions are the same as subtitles."
Auto-generated text may transcribe dialogue, but often omits non-speech audio and requires human review.

"Most viewers don't need captions."
Many viewers watch without sound. Others rely on captions entirely. Captions serve both groups.

In professional media workflows, the distinction is formal:

• Caption files often follow standards such as CEA-608 / CEA-708 for broadcast.
• Subtitles are typically delivered as translation tracks.
• Accessibility compliance frameworks (such as ADA-related guidelines and WCAG references) focus on caption equivalency, not translation alone.

If accessibility is the goal, captions, not subtitles, are the benchmark.

If you are a creator:

• Use captions when your goal is accessibility.
• Use subtitles when translating dialogue for a multilingual audience.
• Ideally, provide both when content is distributed internationally.

Access and translation are complementary, not competing, objectives.

Subtitles translate words.
Captions translate sound.

If access depends on hearing, captions are not optional.

They are infrastructure.