Reading Time vs Word Count: What the Numbers Really Mean
That "5-minute read" badge at the top of an article is not magic — it is arithmetic. Reading time is a word count divided by an assumed reading speed. Knowing the formula tells you when to trust it and when to ignore it.
The formula
Reading time = words ÷ words-per-minute. The Word Counter uses 225 words per minute for silent reading and 130 for speaking aloud. So a 900-word post is about a 4-minute read and a 7-minute talk. Under a minute, the tool switches to seconds so short pieces still get a useful estimate.
Why 225 and 130?
Studies of adult silent reading cluster around 200–260 words per minute for general non-fiction, so 225 is a sensible middle. Speaking is much slower: clear, audience-friendly delivery runs 120–150 words per minute. Newsreaders push higher; nervous speakers race faster and lose the room. The gap is why a script that "looks short" can overrun a time slot.
Where the estimate breaks down
- Dense or technical text reads slower — equations, jargon, and tables all force re-reading.
- Skimmable formatting (headings, lists, short paragraphs) reads faster than the raw count suggests.
- Code blocks and tables inflate the word count without adding reading time, since people scan rather than read them.
Treat reading time as a planning guide, not a promise.
How to use it
For blog posts, a visible read-time sets expectations and lifts completion rates. For speeches, work backward: a 10-minute slot is roughly 1,300 spoken words, so write to that and rehearse. For email and updates, if the read time tops two minutes, consider a summary line at the top.
See reading and speaking time update live as you write.
Open the Word CounterRelated reading
Length drives reading time, so start with the right length: How Long Should It Be?. To trim a piece down to its read-time target, see Cut Your Word Count Without Losing Meaning.