easycaptions - Complete Guide to Captions and Subtitles

People use the words "captions" and "subtitles" interchangeably, and platforms do not help by labeling everything "CC." But they are different tools built for different audiences, and confusing them leads to real mistakes: subtitles that leave deaf viewers without sound information, or captions offered to an audience that actually needed translation. Understanding the distinction, and when each is appropriate, is foundational to serving a global and diverse audience well. This guide draws the line clearly and then explores the subtitling side, where translation and localization introduce their own craft.

Want expert help putting this into practice? EasyCaptions can guide you through it.

The real difference between captions and subtitles

The distinction comes down to an assumption about the viewer. Captions assume the viewer cannot hear the audio, so they convey everything a hearing person would perceive: the dialogue, yes, but also who is speaking, and meaningful non-speech sounds like a phone ringing or ominous music. Subtitles assume the viewer can hear the audio but does not understand the language, so they translate or transcribe only the spoken words, leaving out sound cues the viewer can hear for themselves.

This is why "subtitles for the deaf and hard of hearing," sometimes labeled SDH, exists as a hybrid: it is a subtitle track that adds back the sound information captions include, for viewers who need both translation and non-speech cues. Getting the category right means asking a simple question about your audience: do they lack the sound, or lack the language? The answer tells you which you need.

When to use captions

Related: easycaptions - Tips and Strategies for Effective Captioning.

Use captions whenever your goal is accessibility for people who cannot hear the audio, which is most domestic video content. Captions are what accessibility laws and guidelines require, because they provide equivalent access to the full audio experience, not just the words. They serve deaf and hard-of-hearing viewers, and they equally serve the large audience watching muted in public or noisy places.

• They include speaker identification so viewers know who is talking off screen
• They describe significant sounds and music that carry meaning
• They are the standard for compliance with accessibility requirements
• They keep content usable when the sound is off, wherever that happens

If you are captioning content in the same language your audience speaks and your concern is inclusion, captions are the correct choice.

When to use subtitles

Use subtitles when your audience can hear the audio but may not understand the spoken language. This is the tool of localization: making content in one language watchable by speakers of another. A film in French shown to English speakers, a training video localized for regional offices, a creator reaching audiences in several countries, all of these call for subtitles that translate the dialogue.

Because subtitles assume the viewer hears the soundtrack, they conventionally omit non-speech information; the viewer can hear the doorbell themselves. The focus is entirely on rendering the meaning of the speech accurately and readably in the target language, which turns out to be a demanding craft in its own right. This is also why offering only subtitles on domestic content is a mistake: a deaf viewer who speaks the language fluently still needs the speaker labels and sound cues that a translation-focused subtitle track leaves out.

The craft of subtitle translation

See also: easycaptions - expert advice for creating effective captions.

Translating subtitles is not word-for-word conversion. It is meaning-for-meaning adaptation constrained by time and space, which makes it one of the harder translation tasks. A subtitle must convey the sense of a line, fit within the reading time available, and stay short enough to fit two lines on screen. Often the literal translation is too long, so the subtitler condenses to the essential meaning while preserving tone.

Idioms, humor, and cultural references demand real judgment. A pun rarely survives literal translation, so the subtitler finds an equivalent that lands in the target culture, or conveys the intent if no equivalent exists. Register matters too: formal and informal address, slang, and politeness levels differ across languages and must be matched to the character and situation rather than defaulted. A line rendered too formally can make a warm exchange sound stiff, while over-casual phrasing can flatten a character meant to seem authoritative, so the subtitler is constantly weighing tone alongside literal meaning.

Localization beyond the words

Good localization considers more than translation. Reading speed varies by language and audience, and some languages simply take more characters to express the same idea, which affects how much you can fit and how long captions must stay on screen. Numbers, dates, currencies, and units may need adapting to local conventions so they read naturally. On-screen text in the video, signs, titles, labels, may also need translating, sometimes through additional subtitles positioned near the text.

Directionality and typography enter the picture for some languages, and character encoding must support the target script; saving files as UTF-8 prevents accented and non-Latin characters from turning to garbage. The aim throughout is that the localized version feels native to its audience, not like a foreign product with text pasted over it.

Managing both from one source

In practice, many projects need both captions in the original language and subtitles in several others, and the efficient way to handle this is to work from one clean source. Start with an accurate, well-timed caption file in the original language; its timings and segmentation become the template. Translated subtitle tracks can then reuse that timing structure, with translators adjusting text length to fit rather than re-timing from scratch.

• Build one accurate original-language caption file first
• Keep it as the timing template for every translated track
• Have translators adapt meaning to fit the existing time slots
• Store each language as a separate closed track the viewer can select

Offering multiple selectable tracks lets each viewer pick captions for accessibility or subtitles in their language, from the same video. Understanding the difference is what lets you build that correctly: captions for those who cannot hear, subtitles for those who cannot understand the language, and SDH for those who need both. Tools such as EasyCaptions help you produce the original caption file and manage translated tracks from it, so a single piece of content can reach a deaf viewer and a foreign-language viewer alike without compromise.