How reading-time estimates are calculated
Most blogs and article pages show a small estimate near the top: “6 min read.” The number comes from one simple calculation — word count divided by an assumed reading speed. What almost no site tells you is where that assumed speed comes from, or how shaky the ground under it actually is.
Where 200 words per minute came from
For decades, the standard figure was 200 words per minute. It traces back to reading research from the 1980s and earlier, some of it measuring specific tasks rather than ordinary silent reading. The number stuck around mostly because it was round and easy to remember, and because nobody who used it had a strong reason to question it. It became a convention, repeated by tool after tool, long after better data existed.
What the newer reading-speed research found
In 2019, the researcher Marc Brysbaert published a meta-analysis pulling together 190 studies on adult silent reading speed. The pooled result: roughly 238 words per minute for English prose read silently, for an average adult reader under normal conditions. That’s meaningfully faster than the old 200 wpm figure — enough to change a reading-time estimate on a long document by a full minute or more. This site uses 238 wpm for exactly that reason: it’s the better-supported number, not just the more common one.
Reading time isn’t speaking time
Silent reading and speaking are different tasks with different limits, so they need different numbers. A comfortable spoken pace for English runs closer to 140 words per minute — slower than silent reading, because a speaker also has to produce the sounds, not just process the meaning. This matters for anyone estimating how long a script, a voiceover, or a presentation will actually take to deliver. Using a silent-reading rate for a spoken piece will consistently make the estimate run short.
Reading a passage aloud is its own case again, distinct from both silent reading and free speaking — it’s paced by the text itself rather than by whatever the speaker would naturally say. The oral reading fluency test measures that specific pace, hands-free by listening for your voice, for anyone who needs it rather than the silent-reading number above.
Why 200 words per minute stuck around
Round numbers are memorable, and 200 is rounder than 238. A convention like this rarely gets challenged once it’s embedded in enough tools, because nobody building a word counter sets out to re-derive reading speed from first principles. They copy what every other tool already does. That habit is harmless most of the time, but it’s worth noticing when a “well-known fact” turns out to be an old estimate nobody rechecked.
Why one number can never be exactly right
Both of these figures are averages across large groups of readers doing ordinary reading. Neither one accounts for what actually varies from one reading session to the next. A reader skimming a familiar topic moves much faster than someone working through unfamiliar terminology for the first time. Dense, technical writing slows almost everyone down, regardless of their baseline speed. Reading on a phone during a commute is not the same task as reading at a desk with nothing else competing for attention.
None of this means the estimate is useless. A reading-time figure is a genuinely useful signal — it tells a visitor roughly how big a commitment an article is before they start, which is exactly the decision it’s meant to help with. The mistake is treating “6 min read” as a guarantee rather than what it actually is: a rough average, built from a rough average speed, applied to a specific piece of text that will read faster or slower than average depending on the reader and the day.
Why sourcing the number matters
Most word-counter tools use 200 words per minute and never say so, because the number has been copied forward for so long that it reads as common knowledge rather than a citable claim. That’s a small thing on its own, but it’s part of a larger habit worth pushing back on: presenting a specific-looking number without saying where it came from invites more trust than the number has actually earned. A reading-time estimate that cites its source isn’t meaningfully more accurate than one that doesn’t — but at least a reader can go check the number for themselves, or discount it if their own reading habits run faster or slower than average.
What this means in practice
None of this changes how you should write. A reading-time estimate is a byproduct of length, not a target to hit, and chasing a specific number down by cutting content usually hurts a piece more than it helps. Sentence length matters far more to how a piece actually reads than its total word count does — see how long should a sentence be for what actually makes text easy or hard to get through, independent of how long it takes to read from start to finish.
Check your own text
The word counter shows both reading time and speaking time for whatever you paste in, calculated from the figures in this article rather than an unsourced round number. It also shows a readability score alongside the raw counts, so you can see not just how long your text is, but how much effort it actually asks of a reader along the way.
That’s still a prediction, though — it applies the 238 wpm average to your text, not your actual pace. The reading speed test measures the other half: how fast you actually read, timed against a passage, compared back against the same 238 wpm figure this article explains. If you’re after a read-aloud pace instead — for practicing a script, or checking a child’s or a student’s oral reading rate — the oral reading fluency test times that hands-free, by listening rather than requiring a Start/Done click.