Subtitle speed · CPS

Subtitle reading speed calculator

Paste your .srt or upload the file and see, line by line, whether your subtitles read comfortably or go by too fast for a short video.

Clear
#TextDurationCPSWPMStatus
🔒 100% private — nothing is uploaded to any server

How it works

1

Upload or paste your .srt

You can also paste just the text if you haven't set the timings yet.

2

Read the line-by-line traffic light

Green: comfortable. Yellow: fast. Red: too fast. Blue: stays on screen too long.

3

Adjust the timings that need it

Use the line-by-line breakdown to know exactly which ones to fix in your editor.

What a healthy CPS looks like

A mistimed subtitle fails in two opposite ways, and both are common in vertical video: if the text stays on screen too briefly relative to its length, no one finishes reading it before it changes; if it lingers too long for the little it says, reading feels slow and the person loses interest or skips ahead. The metric the professional subtitling industry uses to measure this is CPS (characters per second): how many characters of that line the viewer has to process for each second the subtitle is visible. It's a simple calculation —text length divided by time on screen— but very sensitive: the same sentence, with a third of a second less duration, can go from perfectly readable to impossible to follow.

In short-form, this problem gets worse for two reasons specific to the medium. First, a large share of Reels, TikToks and Shorts consumption happens with the audio off (on public transport, in the office, in shared spaces), which makes the subtitle the main channel —sometimes the only one— through which the message arrives; if that subtitle can't be read in time, the video simply isn't understood. Second, the editing pace of this format tends to be fast, with cuts every one or two seconds, leaving very tight time windows for each line of text. A script that sounds fine read aloud can produce subtitles with a very high CPS as soon as fast editing cuts are added.

There's a second, less-discussed but equally frequent problem: translations or adaptations from one language to another usually change the length of the text without changing the time available. A sentence in English that fits perfectly in the original duration may need considerably more characters in Spanish, and that translated subtitle ends up with a much higher CPS than the original without anyone planning it that way. Reviewing CPS line by line after translating or adapting a script is the only way to catch this before publishing.

Under 8 CPS — the line stays on screen longer than needed; you can shorten its duration.
8 to 17 CPS — a comfortable reading pace for short-form.
17 to 21 CPS — fast but still acceptable.
Over 21 CPS — too fast: a good part of the audience won't finish reading it.

Real use cases

  • A 42-character line that stays on screen for barely 1.2 seconds gives a CPS of 35, well above readable: even if the script sounds natural read aloud, on screen it's impossible to follow for someone just starting to read that sentence.
  • A short 4-word subtitle that stays 6 seconds on screen (because it got stuck to a long shot with no cut) feels artificially slow and creates the sense that the video "isn't moving", even though the CPS itself isn't a problem.
  • When translating a script originally recorded in English, a sentence that had 30 characters in the original grows to 48 in Spanish while keeping the same time on screen — the CPS climbs from a comfortable range to a risky one without the timing being touched.
  • A video with subtitles auto-generated by a transcription tool splits lines by audio pauses, not by reading length: some resulting lines end up with a very high CPS (lots of text, little time) while others are needlessly slow.

Frequently asked questions

What is CPS in subtitles?

CPS stands for characters per second: how many characters of text the audience has to read for each second the line is on screen. It's the standard metric for measuring whether a subtitle reads comfortably or not.

What is a healthy CPS for short-form video?

Up to 17 characters per second is considered comfortable, 17 to 21 is fast but acceptable, and above 21 is usually too fast to read without losing context of the video.

Do I need an .srt file or can I paste text?

You can upload an .srt file or paste its contents directly into the text box. If you don't have timings yet, use the "I don't have timings yet" tab: paste the script and we suggest how long each line should last.

How are words per minute (WPM) calculated?

We count the number of words in each line (separated by spaces) and project it to one minute based on that line's real duration in the video.

What happens if a line has a duration of 0 or an invalid one?

It's flagged as "too fast" (red), since technically the text has no real on-screen time to be read.

Is my subtitle file uploaded to a server?

No. The .srt file is read and analyzed entirely in your browser with JavaScript. It's never sent to any server.

Why does the tool also flag "too slow" lines in blue?

Because a very low CPS (a lot of time on screen for little text) isn't a legibility error, but it does affect the video's perceived pace: it can feel like the content stalls, especially in short-form where a fast rhythm is part of what keeps attention.

Do CPS and words per minute (WPM) measure the same thing?

Not exactly. WPM is useful for a general sense of speaking speed, but it doesn't distinguish between short and long words: two lines with the same word count can differ hugely in actual character count, and therefore in reading difficulty. CPS is more precise for evaluating legibility line by line.

Does it work for subtitles in any language?

Yes. The characters-per-second calculation applies to any language that can be measured in characters, though it's worth keeping in mind that some languages naturally need more characters than others to say the same thing (as typically happens translating from English to Spanish), which may require adjusting the timing when adapting a script from one language to another.

What do I do if a line comes up flagged in red?

The practical options are: extend that line's time on screen a bit if the editing pace allows it, or shorten the text without losing the central meaning of that part of the script.

Does the tool automatically fix the .srt file?

No — the calculator analyzes the file and flags line by line what's in range and what isn't, so the timing or text correction is decided by whoever edits the video, since that adjustment depends on the context of each scene.

Is this analysis only useful for short-form content?

The CPS calculation is valid for any kind of subtitling, but the ranges considered comfortable tend to be a bit stricter for short-form, precisely because fast editing and sound-off consumption are more common there than in long-form content.

More tools in the kit