How Reading Time Is Estimated

Every article, blog post, or report comes with an implicit question before you even start it: how long is this going to take? The “X minute read” label you see on most publishing platforms isn’t a guess pulled from thin air. It comes from a simple calculation: total word count divided by a reading speed, measured in words per minute. The math itself is basic, but knowing what feeds into it helps you treat the estimate as a useful approximation rather than a hard promise.

Words per minute, explained

Reading speed is measured in words per minute (wpm), which is exactly what it sounds like: how many words a person reads, silently, in sixty seconds. It’s the same unit used for typing speed, just applied to consumption instead of production.

Most adults reading general, non-technical text silently land somewhere between 200 and 250 words per minute. That’s a wide enough range that two readers can spend meaningfully different amounts of time on the same piece and both be “normal.” Speed readers claim much higher numbers, and slow, careful readers (or anyone reading in a second language) often fall well below 200. There’s no single correct value, which is exactly why the reading speed field in the calculator is adjustable rather than fixed.

Where does 200 to 250 wpm come from? It’s a rough average drawn from decades of reading-speed research on adult silent reading of everyday prose: news articles, blog posts, general nonfiction. It’s a starting point, not a law of nature, and it shifts depending on the reader and the text, which the next two sections cover in more detail.

The formula

The underlying formula is short:

Reading Time (minutes) = Word Count / Reading Speed (words per minute)

That division gives you a decimal number of minutes, which usually isn’t a clean whole number. To make the result readable, the calculator splits that decimal into whole minutes and whole seconds:

Minutes = floor(Reading Time)
Seconds = round((Reading Time - Minutes) x 60)

In other words, take the whole-number part of the minutes, then convert whatever fraction is left over into seconds. That’s the full calculation: one division and one split.

Worked examples

Say you have a 1,500-word article and you’re using the default reading speed of 200 words per minute:

• Reading time: 1,500 words / 200 wpm = 7.5 minutes
• Split into minutes and seconds: 7 whole minutes, plus 0.5 minutes x 60 = 30 seconds
• Result: 7 minutes 30 seconds

Now take a longer, 3,000-word piece at a slightly faster reading speed of 250 words per minute:

• Reading time: 3,000 words / 250 wpm = 12.0 minutes
• Split into minutes and seconds: 12 whole minutes, and no leftover fraction
• Result: 12 minutes 0 seconds

Notice that doubling the word count (1,500 to 3,000) didn’t double the reading time, because the reading speed also increased in that second example. The two inputs interact, which is exactly why the calculator asks for both instead of assuming a fixed pace for everyone.

What the estimate doesn’t capture

A word-count-based estimate is deliberately simple, and that simplicity comes with a few blind spots worth knowing about before you rely on the number too heavily.

Dense or technical material is read more slowly than casual prose, often closer to 100 to 150 words per minute instead of the 200 to 250 wpm baseline. A legal contract, an academic paper, or a piece full of unfamiliar jargon takes real cognitive effort per word, and no fixed formula captures that difference automatically. If you’re estimating reading time for that kind of content, it’s worth manually lowering the reading speed input rather than trusting the default.

The calculator also only counts words. It has no way to account for images, diagrams, tables, or code blocks, all of which take time to look at, parse, or run through mentally, but none of which show up in a word count at all. A 1,500-word tutorial with ten embedded code snippets will take noticeably longer to work through than a 1,500-word opinion piece, even though both would produce the identical estimate here. Treat the number as a floor for that kind of content, not a ceiling.

Finally, familiarity matters. A reader who already knows the subject matter moves faster through the same text than someone encountering the concepts for the first time. None of this means the estimate is useless, just that it’s a starting point built on an average, not a personalized prediction for any one reader on any one piece of text.

FAQ

What reading speed should I use? 200 to 250 words per minute is a reasonable default for adult silent reading of general text. If the material is technical, unfamiliar, or otherwise dense, try a lower value, closer to 100 to 150 wpm, for a more realistic estimate.

Why doesn’t the estimate match how long the article actually took me to read? Reading speed varies a lot between individuals and even between sessions for the same person, depending on familiarity with the topic, fatigue, and how carefully you’re reading. The formula uses a single speed value, so it will always be an approximation rather than a personal measurement.

Does this account for images, code blocks, or other non-text content? No. This is a pure word-count-based estimate, so content with a lot of images, diagrams, or code samples will generally take longer to properly absorb than the word count alone suggests.

Use the Reading Time Calculator to estimate your own.