Subtitles vs closed captions: what is the difference?

The difference between subtitles vs closed captions comes down to what your viewer needs from the text. Do they need help understanding the words, or do they need access to information they cannot hear? That distinction affects what you include, how you prepare the text, and which track you publish with your video.

The names can be confusing because video players and publishing platforms do not always use them consistently. A menu labeled “Subtitles” may contain accessibility captions. Instead of relying on the button’s name, look at what the text actually communicates.

Subtitles vs closed captions at a glance

Subtitles primarily convey spoken dialogue. They assume the viewer can hear the soundtrack but needs the words in writing, often because the dialogue is in another language. English subtitles for a film in Korean, for example, usually translate the dialogue without describing every meaningful sound.

Closed captions, often shortened to CC, convey dialogue and relevant audio information. They are intended to make the audio content accessible to viewers who are deaf or hard of hearing. They also help when you watch with the sound muted.

The word “closed” describes how the captions are delivered. You can turn them on or off through the player, provided the player supports the caption track. It does not mean the wording is shorter or that the text is available only to certain viewers.

A separate text track can serve either purpose. The difference is not simply the file extension or the language. A same-language subtitle track may still omit information that an accessibility caption track needs.

The same moment shown both ways

Suppose someone says “Wait here” just before a door slams out of view. The spoken words are identical in both versions, but the caption includes the sound that changes how you understand the scene.

Subtitle example: Wait here.

Caption example: Wait here. [door slams]

That small addition matters. Without it, a viewer watching silently may not realize that someone has left or that the conversation has ended abruptly.

What belongs in a caption track

Captions need to communicate meaningful sound, not provide a written inventory of everything audible. Include a sound when it helps your viewer understand an action, a reaction, the mood, or information conveyed only through audio.

Useful cues might include:

• [doorbell rings] when it interrupts a conversation.
• [ominous music] when the soundtrack signals a threat not yet visible.
• [glass breaks] when the breaking object is offscreen.
• [laughter] when a reaction changes the meaning of a remark.

Keep cues specific enough to be useful. “[Music]” tells you that music is present, but “[soft piano music]” may better explain the atmosphere when that distinction matters. Avoid guessing at details you cannot establish from the audio.

Timing matters as much as wording. A cue should appear when the sound happens, rather than giving away an event before it occurs. It also needs enough reading time without lingering over unrelated action.

You do not need to add a sound cue to every subtitle block. Too much description can crowd out dialogue and make the video harder to follow. The aim is equivalent understanding, not maximum text.

Open captions stay in the picture

Open captions are permanently embedded, or burned, into the video image. Your viewer does not need to enable a separate track, and there is no player control that removes them.

Closed captions remain separate from the picture. Depending on the player, your viewer may be able to change their size, colors, or background. Open captions generally do not offer those adjustments because they are part of the image itself.

This is a separate distinction from subtitles versus captions. You can burn translated subtitles into a film, or you can burn accessibility captions into a social clip. Burning dialogue text into the picture does not automatically make it a complete accessibility caption track.

Open captions are useful when you need text to remain visible wherever a video is played. The tradeoff is flexibility. Fixing a typo means changing the video, and offering another language usually means producing another version. A separate closed track is easier to replace or offer alongside other language tracks.

SDH subtitles include accessibility information

SDH stands for subtitles for the deaf and hard of hearing. These tracks include dialogue along with relevant sound information, so their content overlaps substantially with captions.

You will often encounter an “English SDH” option in a film’s language menu. Unlike an ordinary English subtitle track, it is intended to make meaningful audio information available in text. SDH can also be translated, giving viewers both language access and sound descriptions.

SDH and closed captions are not perfect opposites or completely separate categories. SDH describes an accessibility-oriented subtitle track. Closed describes a track you can switch on and off. Platform terminology and delivery requirements vary, so check the track’s contents rather than treating its label as proof of completeness.

If you are choosing a track for silent viewing, look for dialogue plus relevant sound cues. That is more useful than trying to infer everything from “CC,” “SDH,” or “subtitles” alone.

Choose the text your audience needs

Social clips watched without sound

For a social clip, assume some viewers will never hear the soundtrack. Your text should carry the message without requiring them to turn up the volume.

Open captions can keep that text visible when a clip is shared or embedded, but they are not the only option. If the platform supports closed captions reliably, upload a separate track too. Check the published result so you know whether text appears by default and whether it covers important visual content.

Do not treat large animated words as a substitute for complete captions. Highlighting a slogan may help the design, but viewers still need the rest of the meaningful audio.

Courses and accessibility

For a recorded lesson, prioritize accurate captions over dialogue-only subtitles. A notification sound, an audio demonstration, or a sound indicating an error may be part of what you teach.

WCAG accessibility guidelines call for captions for prerecorded video with audio in synchronized media, with an exception for media that is an alternative for text and clearly labeled as such. Dialogue-only subtitles may not meet that need when they leave out meaningful sounds.

A transcript can support reading and review, but it does not replace synchronized captions. Your learner needs the words and sound cues alongside the corresponding demonstration.

Films in another language

Translated subtitles usually work when your viewer can hear the soundtrack and needs the dialogue in another language. They can hear a crash, a musical shift, or an alarm without needing those sounds described.

For viewers who cannot hear those details, offer a translated accessibility track as well. Translating the dialogue alone does not turn ordinary subtitles into SDH or complete captions.

Start with a transcript and build the right track

A transcript gives you the words to work from. A usable subtitle or caption track also needs timing, readable breaks, and a review against the video.

1. Create and correct the text. Kotosay is a website that turns audio and video files into text online. You can start a subtitle track from your video, then fix words in the on-page editor while the timestamps stay in place. The editor is free for everyone.

1. Download a timed format. Kotosay’s Unlimited plan includes SRT and VTT downloads. Choose the format your video player or publishing platform accepts. These formats contain text and timing information rather than permanently adding text to the picture.

1. Add sound cues if you need captions. Open the downloaded file in a plain text editor and add relevant cues by hand. Preserve the timing structure. If a sound needs its own entry, set that entry to match the sound and check that it does not create confusing overlaps.

1. Review the track with the video. Watch once with sound to verify the words and cues, then watch muted to check whether the meaning still comes through. Fix crowded blocks, awkward line breaks, and captions that disappear before you can read them.

Kotosay’s subtitle output supports up to two lines of up to 42 characters and up to 17 characters per second, or a short mode with one line of about 20 characters. Treat your manual additions with the same care for readability. A sound cue adds text, so a block that worked as a subtitle may need adjustment as a caption.

Translate without losing the timing

Once the source text is correct, you can translate your timed subtitles. Translation is included in Kotosay’s Unlimited plan. It keeps every start and end time, so the translated SRT stays in sync. The translated lines replace the original lines rather than appearing in a side-by-side view.

Preserved timestamps do not remove the need for a reading check. A translated sentence may take more space than the original. Review line breaks, phrasing, and any sound cues before publishing.

Choose your final track by its purpose. Use subtitles for access to dialogue, captions for access to meaningful audio, and open captions when the text must stay in the picture. Then check the actual playback, not just the file name.