Subtitle Reading Speed, Line Length and Timing: A Practical Style Guide
A subtitle can be perfectly accurate and still be bad if viewers cannot read it in time. The difference between subtitles that feel invisible and subtitles that exhaust the viewer comes down to a handful of measurable things: how many characters fit on a line, how many lines appear at once, how quickly the text must be read, and how long it stays on screen. This guide explains the numbers professionals use, why they exist, and how to check your own file against them with nothing more than a spreadsheet.
Why these limits exist
Reading subtitles is a split-attention task. The viewer is also watching the picture, following the action and listening to the audio. If the text is too long, appears too briefly or breaks in awkward places, they either miss part of the message or spend the whole scene reading instead of watching.
Professional style guides, such as the English timed-text guidelines published by large streaming services and broadcasters, give numeric limits for this reason. They differ in details from one organization to the next, and they vary by language and by audience (children, for example, are given more time), so treat the figures in this guide as widely used starting points and follow the specification of whoever you are delivering to.
The key numbers at a glance
| Measure | Commonly used guideline | Why |
|---|---|---|
| Characters per line | Up to about 42 characters | Longer lines force the eye to travel too far and cover more of the picture. |
| Lines at once | Two lines at most | Three lines cover too much of the frame and take too long to read. |
| Reading speed | Roughly 15 to 20 characters per second, lower for children's content | Beyond this most viewers cannot finish reading before the text disappears. |
| Minimum duration | A little under one second | Anything shorter is only a flash. |
| Maximum duration | Around six to seven seconds | Longer than this and the text lingers after it has been read. |
| Gap between subtitles | At least a couple of frames | A tiny gap makes it visible that the text changed. |
Reading speed: characters per second
Reading speed is usually measured in characters per second, abbreviated CPS. It is simply the number of characters in the subtitle, counting spaces and punctuation, divided by the number of seconds the subtitle is on screen.
CPS = number of characters / duration in seconds
"Welcome back to the channel." = 28 characters
shown for 2.5 seconds -> 28 / 2.5 = 11.2 CPS (comfortable)
"Today we're color grading a short film in DaVinci Resolve."
= 58 characters
shown for 2.0 seconds -> 58 / 2.0 = 29 CPS (far too fast)The second example shows the most common real-world problem. Fast speech produces long lines in short windows. The fix is rarely to make the viewer read faster. Instead you shorten the text by condensing the phrase, dropping filler words and repetition, or you extend the duration if the next line allows it.
Line length and how to break lines
Keeping lines under roughly 42 characters is only half of the job. Where the line breaks matters just as much, because a bad break makes the sentence harder to parse. Good breaks follow the grammar:
- Break after punctuation where there is a natural pause, such as a comma or the end of a clause.
- Do not separate an article from its noun, a preposition from its object, or an auxiliary verb from the main verb.
- Do not leave a single short word on a line by itself if you can avoid it.
- When there are two lines, make the top line shorter than the bottom one, which gives a pyramid shape that covers less of the picture and is easier to follow.
Weaker:
Today we're color grading a short film
in DaVinci Resolve.
Better:
Today we're color grading
a short film in DaVinci Resolve.In the weaker version the top line is the longest and the break splits the thought at a less natural place. In the better version each line reads as a unit, and the top line is shorter than the bottom.
Duration and gaps
Even a very short line should stay on screen long enough to register. A subtitle with a single word needs less reading time but still needs a moment to be seen, which is why most guidelines set a minimum duration of a bit under a second. At the other end, a subtitle that stays up for much longer than it takes to read looks like a mistake and can hide the picture.
Between consecutive subtitles leave a short gap. If one subtitle ends on the exact frame the next begins, the viewer may not notice that the text changed. A gap of a few frames is enough to signal it. Subtitles should also never overlap in time, which causes two blocks of text to be shown at once in many players.
Finally, try to align subtitle starts and ends with the spoken audio and with scene cuts. A subtitle that straddles a hard cut is distracting, because the eye is pulled to the new shot while the text is still present.
Checking your own file in a spreadsheet
You do not need a dedicated subtitle editor to find speed problems. Convert the subtitle file to CSV with our SRT to CSV tool, open the result in Excel or Google Sheets, and you get one row per subtitle with the columns index, start, end and text.
Assuming the columns are A (index), B (start), C (end) and D (text), add two columns. The first calculates the duration in seconds from the timestamps, which are written like 00:00:04,000 with a comma before the milliseconds. The second divides the character count by that duration:
Duration in seconds (column E):
=(TIMEVALUE(LEFT(C2,8)) + VALUE(RIGHT(C2,3))/86400000 - TIMEVALUE(LEFT(B2,8)) - VALUE(RIGHT(B2,3))/86400000) * 86400
Characters per second (column F):
=LEN(D2) / E2Sort column F from highest to lowest and the subtitles that are too fast rise to the top. Add a rule that highlights anything above 20 and you have a quick quality check for the whole file. The same table also exposes durations that are too short or too long, and you can compare each row's end time with the next row's start time to find overlaps and missing gaps.
Other style conventions worth deciding on
- Dialogue between two speakers: put each speaker's words on their own line and start each with a dash, so viewers know the speaker changed.
- Off-screen voices, narration and sounds: many productions use italics for narration and a bracketed note, such as [door slams], for sounds when the subtitles are meant for deaf and hard of hearing viewers.
- Numbers, abbreviations and punctuation: choose one convention and apply it consistently throughout a project. The specific choice matters less than being consistent.
- Songs and music: decide in advance whether lyrics are subtitled and how they are marked.
Frequently asked questions
- How many characters should a subtitle line have?
- A commonly used limit is about 42 characters per line with at most two lines, although some languages and specifications use different numbers. Check the guidelines of the platform or client you are delivering to.
- What is a good subtitle reading speed?
- Many guidelines allow roughly 15 to 20 characters per second for adult audiences, with lower limits for children's content. If a subtitle is much faster than this, shorten the text or give it more time.
- How long should a subtitle stay on screen?
- Typically no less than a little under a second and no more than about six to seven seconds. The exact time should follow the length of the text and the reading-speed limit.
- Do the same rules apply to every language?
- No. Languages with different average word lengths, or scripts such as Chinese, Japanese and Korean, use different limits for characters per line and per second. Use the guidelines written for the specific language when they are available.