Closed Captions vs Subtitles, Explained (2026)

People say "captions" and "subtitles" like they are the same thing. On YouTube, in a video editor, and in most casual conversation, they mostly are. But the terms have distinct original meanings, and knowing the difference matters the moment someone asks for one specifically, or an accessibility requirement is on the line.

Short version: closed captions include non-speech sound information (like [music] or [door slams]) and are meant primarily for viewers who are deaf or hard of hearing. Subtitles are text of the dialogue, historically meant for viewers who can hear the audio but do not understand the spoken language. Both are usually delivered in the same file formats today, which is exactly why the terms blur together.

If you also want the SDH definition (subtitles that add sound description), see what are SDH subtitles. If you landed here from search wanting the sharper open vs closed distinction, see open captions vs closed captions.

The core difference in plain terms

Notice the file formats are identical. The difference is the intent and content of the text, not the technical container.

Why the terms get mixed up constantly

Three reasons the line has blurred:

1. Modern captioning tools generate one file that does both jobs loosely. Auto-generated captions on YouTube or in most transcription software give you dialogue text, sometimes with light labeling, and call it either "captions" or "subtitles" depending on the platform's marketing.
2. Most viewers turn captions on for silence, not deafness. Watching video with the sound off on a bus or in an office has made "subtitles" and "captions" functionally the same feature for a huge share of viewers, regardless of the original accessibility intent.
3. Streaming platforms use both words inconsistently. Netflix, YouTube, and various players each have their own settings labeled "captions," "subtitles," or "CC" without a strict shared standard.

For most creators publishing to YouTube or social platforms, the practical difference is small: you need a timed text file (SRT or VTT) with accurate dialogue. Whether you call it captions or subtitles will not change what a viewer sees.

When the distinction actually matters

It stops being academic in a few specific situations:

• Accessibility compliance (ADA, WCAG, broadcast regulations): If a client or institution requires "closed captions" for accessibility, they usually mean the fuller version: dialogue plus relevant non-speech sound, sometimes speaker identification. Plain dialogue-only subtitles may not satisfy the requirement. Check the specific standard you are complying with; see the W3C's overview of captions and subtitles for the accessibility-first framing.
• Foreign-language delivery: If you are localizing a video for a different-language audience, you want subtitles in the strict sense: translated dialogue, no sound-effect tags cluttering the reading experience.
• Legal or broadcast contracts: Some contracts specify "closed captioning" as a deliverable with defined technical standards (timing, formatting, FCC-style rules in some regions). Read the actual spec before you assume any auto-generated SRT satisfies it.

If none of those apply to your project, dialogue-accurate SRT or VTT covers you either way.

How to generate captions or subtitles from a video

The practical workflow is the same regardless of which word you use:

1. Upload your audio or video file to a transcription tool.
2. Get a timed transcript with speaker labels if multiple people are talking.
3. Clean up names, terms, and any misheard words in the editor.
4. Export as SRT or VTT, the two formats nearly every video platform and editor accepts.
5. If you need sound-effect tags for accessibility captions specifically, add them manually; most AI transcription tools transcribe speech, not ambient sound cues.

File Transcribe covers steps 1 through 4 directly: upload a file, get speaker-labeled segments, export SRT or VTT after signing in free. There is also a dedicated subtitle generator if captions are the only thing you need from the file, without the rest of the transcript workspace.

Open captions vs closed captions (a related, different question)

Do not confuse the captions-vs-subtitles question with the open-vs-closed question. "Open" captions are burned permanently into the video and cannot be turned off. "Closed" captions are a separate track a viewer toggles on or off. Both open and closed captions can carry either "caption-style" (with sound effects) or "subtitle-style" (dialogue-only) text. The full breakdown lives at open captions vs closed captions explained.

Practical rule of thumb

If someone asks you for "captions" or "subtitles" without more context, ask two questions before you build the file:

1. Is this for accessibility, or for a different-language audience? Accessibility usually wants sound-effect tags; translation usually does not.
2. Does a contract or compliance standard define the deliverable? If yes, read the actual spec instead of guessing from the word choice.

Absent a specific requirement, one clean SRT or VTT file with accurate dialogue timing satisfies both use cases for the vast majority of creators and small teams.

FAQ

Is closed captioning the same as subtitles?

Not originally. Closed captions were built for deaf and hard-of-hearing viewers and include sound-effect information. Subtitles were built for translating dialogue. Today, most auto-generated files blur the distinction, and the practical difference is small for casual creator content.

Do I need closed captions or subtitles for YouTube?

YouTube calls its feature "subtitles/CC" and accepts the same SRT or VTT file for either use case. Upload dialogue-accurate captions; add sound-effect tags manually only if you need true accessibility-grade closed captions.

What file format works for both captions and subtitles?

SRT and VTT work for both. The distinction between captions and subtitles lives in the text content, not the file format.

Can File Transcribe generate closed captions with sound effects?

File Transcribe transcribes speech and exports SRT/VTT for the dialogue. Non-speech sound tags (like [music] or [applause]) are not auto-generated; add them manually in the exported file if a project requires full accessibility-grade closed captions.

What is the difference between subtitles and SDH?

SDH (Subtitles for the Deaf and Hard of hearing) is subtitles with added sound-effect and speaker information layered in, essentially a hybrid of the two categories. Full explanation: what are SDH subtitles.

Generate your caption file

Whatever you call the end result, the workflow is the same: upload the video, clean up the transcript, export SRT or VTT. Start on the homepage, or go straight to the subtitle generator.

Related: Open captions vs closed captions · What are SDH subtitles · What is a VTT file · How to export VTT captions for YouTube

More guides

• Transcription guides
• Try File Transcribe free
• Transcript format guide
• Best transcription software
• Transcribe Zoom meetings

Further reading

• Zoom cloud recording help
• W3C captions overview