Subtitle Reading Speed Checklist: CPS and WPM Limits

Watch any subtitled show and you can feel when the captions are too fast. Your eyes lock onto the line, you race the clock, and you miss the next shot. That feeling has a number behind it — characters per second, or CPS — and broadcasters have spent decades arguing over exactly what it should be.

If you're producing subtitles or captions, "fast enough that anyone can read them" needs to become a hard limit you can check. This is that checklist. It covers reading-speed targets, line-length rules, duration minimums, and what to do when the dialogue genuinely can't slow down.

What counts as "too fast" for subtitles?

A subtitle is too fast when an average viewer can't finish reading it before it disappears. The two practical metrics are CPS (characters per second of display time, including spaces) and WPM (words per minute). CPS is the modern broadcast standard — it counts what the eye actually sees, including punctuation and numbers, which WPM ignores.

The BBC's published target is 160–180 wpm or roughly 17 CPS for English-language subtitles (source). Netflix sets a hard ceiling of 17 CPS for adult content and 13 CPS for children's programs (source). Anything above 21 CPS is treated as an error by most QC tools.

How is CPS actually calculated?

CPS is: (total characters in the subtitle, including spaces) ÷ (duration in seconds). A two-line subtitle reading "We need to talk about the schedule." — 35 characters — displayed for 2.0 seconds runs at 17.5 CPS. Already at the edge.

Practical targets by audience:

If a calculated CPS exceeds the ceiling, the fix is almost always to edit the dialogue (drop "well", "you know", "kind of") or split it across two subtitles. Don't extend display time, which throws off the cut.

When should you use WPM instead?

WPM is the older metric and still common in U.S. educational caption-style guides. The DCMP recommends 130–160 wpm for adult content (source).

CPS and WPM roughly map: 17 CPS is about 180 wpm. Use CPS for any subtitle file you ship — it's what professional QC tools measure. Use WPM if you're authoring a style guide that needs to read naturally to writers who think in words, not characters.

How many lines, and how long can each line be?

Two lines per subtitle, full stop. Three-line subtitles cover too much of the frame and force the eye to track too far. A single line is fine.

Line length for Latin scripts: 42 characters per line is the broadcast standard (BBC, Netflix). 37 characters is the older EBU norm and still appears in European workflows (source). CJK languages have their own conventions — typically 13–16 full-width characters per line.

When a sentence spans two lines, break it on a natural grammatical boundary: after a clause, before a conjunction, never mid-phrase. Don't dangle articles ("the | building") or split prepositional phrases ("in the | morning") across lines.

Need help producing clean subtitle files in the first place? You can transcribe a video and export an SRT in one step.

What are the minimum and maximum display durations?

A subtitle has to be on screen long enough to be noticed and read.

• Minimum: 5/6 of a second (about 833 ms). Anything shorter and the viewer's eye won't fully register it.
• Maximum: roughly 7 seconds for a two-line subtitle. Beyond that, the viewer re-reads it, which is distracting.
• Gap between subtitles: at least 2 frames (~83 ms at 24fps) so they don't visually bleed into each other.

If your transcription tool produces flash cues shorter than the minimum (common when a speaker says "Yes" or "Right" between sentences), merge those into the surrounding cue rather than displaying a flicker.

The pre-publish reading-speed checklist

Run this list before shipping any subtitle file. Skipping items is how you end up with captions that the audience complains about but can't quite name why.

Per-cue checks

• CPS ≤ 17 (adult) or ≤ 13 (children's). Flag any cue above the ceiling.
• Line count: 1 or 2 lines. Never 3.
• Line length ≤ 42 characters (Latin scripts), counted with spaces.
• Duration ≥ 0.83 s and ≤ 7 s.
• Line break falls on a natural grammatical boundary.
• No more than one sentence ends mid-cue (sentence overflows hurt comprehension).

File-level checks

• All cues have a minimum gap (≥ 2 frames) before the next.
• No overlapping cues unless the file format supports them (TTML allows positioned overlaps; SRT does not).
• Sound-effect tags (e.g., [door slams]) follow a consistent style — square brackets, lowercase or sentence case picked and held.
• Speaker labels follow one convention throughout. See speaker label format conventions.
• File parses cleanly. If your SRT timing is drifting, see how to fix subtitle timing drift.

Accessibility checks

• Non-dialogue audio (music, ambient, off-screen sounds) is captioned for SDH/CC.
• Speaker changes are clearly indicated.
• The file meets the WCAG captions checklist for the intended audience.

Which tools flag reading-speed violations?

Most professional subtitle editors compute CPS and WPM live as you type or import:

• EZTitles, WinCAPS, Spot — broadcast subtitle editors with built-in CPS limits and color-coded warnings.
• Subtitle Edit (free, Windows/Mac/Linux) — reading-speed indicators per cue and bulk fix tools.
• Aegisub (free) — older, still widely used in fansub workflows; CPS shown per line.
• YouTube Studio — flags very fast captions on upload but doesn't enforce a CPS target.

If you're starting from an AI-generated transcript, expect to need a pass for CPS — voice activity timing rarely aligns with reading-speed limits out of the box. For context on why timestamps drift, see what is forced alignment.

When should you break the rules?

Two situations justify going over 17 CPS:

1. Verbatim legal or medical material where editing for brevity could change meaning. Even then, prefer extending the cue and accepting a small overlap with the next cut.
2. Fast comedy or live news where viewers expect to skim rather than read in full. Sports captions often run at 20–23 CPS.

Everything else, edit the words. The reader isn't negotiating with you in real time — they're locked into whatever you publish. A 17-CPS hard cap costs you a few minutes of editing; ignoring it costs comprehension on every viewing.

If you're producing captions from scratch, start with a clean transcript. The cleaner the text, the easier the per-cue editing. A good SRT export from your transcript cuts the reading-speed pass from hours to minutes.

Sources

• BBC Subtitle Guidelines — official BBC reading-speed and line-length standards
• Netflix Timed Text Style Guide — 17 CPS adult and 13 CPS children's ceilings
• DCMP Captioning Key — U.S. educational captioning style and WPM guidance
• EBU TT-D Subtitling Standard (Tech 3380) — European subtitling line-length and timing standards