# Captions vs Subtitles: What's the Difference and When to Use Each

Captions vs subtitles: what separates them, the open vs closed distinction that changes your workflow, and how to pick the right one for every platform.

Most people use "captions" and "subtitles" as if they were the same word wearing two hats. They are not. They were invented for different viewers, they carry different information, and on some platforms picking the wrong one is the difference between a video that lands and a video that scrolls past on mute. The good news: once you see what each one is actually for, the choice takes about five seconds.

## What subtitles assume: you can hear, but not understand

Subtitles were born in foreign-language cinema. They assume the viewer can hear the audio perfectly well but does not speak the language. So subtitles carry one thing: the spoken words, transcribed or translated. No sound effects, no "[door creaks]," no speaker labels. If a doorbell rings mid-scene, subtitles stay silent about it: they carry what people say, not the sounds around them.

Reach for subtitles when the barrier is language, not hearing: a French film for an English audience, your English tutorial shown to viewers in Brazil, a product demo you want to sell in three markets.

## What captions assume: you cannot hear the audio at all

Captions assume the opposite. The viewer cannot hear, either because they are deaf or hard of hearing, or because the sound is off. So captions carry everything the audio was doing: the dialogue, plus non-speech sound written out ("[tense music]," "[crowd cheering]"), plus who is speaking when it is not obvious.

That extra layer is why captions, not subtitles, are the accessibility standard, and why broadcast, education, and most corporate work require them. It is also why they are the right call for social feeds, where the vast majority of people watch with the sound off. On mute, your video is a silent film, and captions are the only reason it still makes sense.

One regional wrinkle worth knowing: in the United States the word is usually "closed captions," while much of the UK and Europe says "subtitles" for the same accessibility track. If a client hands you a spec, read what they describe, not just the label they used.

## The distinction that actually changes your workflow: open vs closed

Here is the part most explainers skip, and it is the one that matters when you sit down to publish. Captions and subtitles each come in two forms, and the form decides how the file behaves everywhere it travels.

**Open** means burned into the picture. The text is part of the video pixels, always on, impossible to switch off. It travels with the file no matter where it is re-uploaded or downloaded, and you control exactly how it looks.

**Closed** means a separate track: a sidecar file like an SRT, or a toggle-able track the platform reads. The viewer turns it on or off, can often pick a language, and the platform decides some of the styling.

That single choice, burned in or separate file, has real consequences:

- **Burned-in wins on social.** TikTok, Reels, and Shorts autoplay on mute, and a burned-in caption is guaranteed to show, styled the way you want, above the platform's buttons. A separate track that the feed ignores helps no one.
- **A separate file wins on control and reach.** On YouTube or Vimeo, an SRT lets viewers toggle captions, switch languages, and read them at their own size. It is also the format accessibility tools and platforms expect, and you can fix a typo without re-rendering the whole video.
- **The honest answer is usually both.** A burned-in version for the muted social feed, and a separate SRT for the platform, search indexing, and anyone who needs to toggle. You are not choosing a side, you are covering two viewing contexts.

## Which one your video needs

Skip the theory and match it to where the video is going:

- **Short-form social (TikTok, Reels, Shorts):** burned-in captions, styled and placed high so the app's buttons do not bury them. Most viewers are on mute.
- **YouTube long-form:** a separate SRT so viewers can toggle and translate, and optionally a burned-in version for the first few silent-autoplay seconds.
- **Selling in more than one language:** subtitles as selectable closed tracks, one per language, so each viewer picks their own.
- **Accessibility or compliance (broadcast, courses, corporate):** closed captions with sound descriptions and speaker labels, not just a transcript of the words.

## What makes captions good, not just present

Getting captions onto a video is easy. Getting them right is a craft, and viewers feel the difference even when they cannot name it:

- **Timing is the whole game.** Each line should land on the word being spoken, not half a beat early, not a beat late. Everything else is a distant second.
- **Short cues read, long ones stall.** Aim for a line every one to three seconds, six or seven words at most, and break on natural phrase boundaries, never mid-clause.
- **Style for the phone, not the desktop.** A clean sans-serif, a soft shadow or a translucent background so the text survives bright footage, and placement lifted higher on vertical video so the platform UI does not swallow it.
- **Color is a tool, not decoration.** One accent color on the word that matters, at most. No rainbow, no bouncing letters. Legibility first.

## Getting both from one video

You do not have to run this as two separate jobs. Upload a video to Chat Octopus, describe the look you want, and it transcribes the speech with word-level timing and produces the captions for you. Say ["bold white captions with a soft shadow, placed high for vertical"](/tools/subtitle-generator) and that is what you get, delivered as a captioned MP4 with the text burned in and a standalone SRT whose timings match it line for line. The open version for your social feed and the closed file for the platform, from one request.

From there it stays a conversation. Ask for a language you do not have yet ("now make Spanish captions from the English ones") and both versions live in the same thread. Spot a typo? "Fix 'their' to 'there' at 2:14" and it corrects that cue without re-rendering the project. If you have not worked this way before, [here is how a Chat Octopus conversation flows](/docs/using-chat), and if your source is an audio recording rather than a video, it can [transcribe that first](/tools/audio-transcription) and caption from there.

Captions or subtitles, open or closed, is not a trivia question. It is a decision about who is watching and how. Once you know that, the file practically picks itself.