Medium popularized the reading time estimate in the early 2010s, and it's now a standard feature across blogs, newsletters, and news sites. It turns out that a simple "5 min read" label measurably changes how readers engage with content — and understanding why helps you use it more strategically.
Why reading time estimates work
Reading time estimates reduce uncertainty. Before you added the label, a reader staring at a long article was making a bet: is this worth my time? The label removes the bet. They know the commitment before they start, which means they can make an informed choice to continue — and readers who make that choice are significantly more likely to finish.
A study by the Nielsen Norman Group found that users are more likely to start reading when they know how long it will take, particularly for content over 500 words. Medium's own data, shared in early blog posts by their engineering team, found that estimated reading times correlated with higher completion rates across articles.
Estimate your content's reading time instantly with our free Reading Time Calculator.
How reading time is calculated
The standard formula is straightforward:
Reading time = word count ÷ average reading speed
The most commonly used benchmark for online content is 200 words per minute (WPM) for silent reading. Research on adult reading rates consistently puts average silent reading speed between 200–250 WPM, with 200 WPM being the conservative, more inclusive estimate.
For spoken content — presentations, videos with narration, podcasts — the benchmark is 130 words per minute, which matches natural speech pace with pauses.
So a 1,200-word article = 6 minutes to read. A 2,400-word guide = 12 minutes. A 600-word newsletter = 3 minutes.
The formula is the same across tools, including ours. The difference between tools is rounding (some round to the nearest minute, some show decimal minutes) and whether they account for non-text content.
Adjusting for complex content
Pure word count doesn't always tell the full story:
Code blocks and technical content slow readers down significantly. A 1,000-word tutorial with 500 lines of code takes longer than 7.5 minutes because readers must parse and mentally execute the code.
Tables and lists can be faster or slower depending on how they're used. A quick reference table is scanned; a detailed comparison matrix is studied.
Images add viewing time that isn't captured in word count. A convention used by some publishers adds 12 seconds per image to the total reading time estimate.
Domain complexity matters. A 500-word piece on quantum computing takes most readers longer than a 500-word recipe. If your content is specialist knowledge, consider rounding the reading time up.
For most general web content — blog posts, guides, newsletter articles — the standard 200 WPM formula gives a close enough estimate that the added sophistication isn't worth the complexity.
Where and how to display it
Top of article, near the title. This is the highest-impact placement because readers see it when deciding whether to start. Showing it after the first paragraph or at the bottom of the page misses the decision moment.
In email subject lines or preview text. "How to negotiate salary (4 min read)" outperforms the same subject without the reading time, particularly for newsletters where competition for attention is high.
On blog index and archive pages. Listing reading time next to titles on a blog archive helps readers choose where to start, especially if your posts vary widely in length.
Format: Round to the nearest minute. "5 min read" is better than "4.8 min read." For very short content (under 2 minutes), some publishers use "Quick read" instead of a time.
Using reading time to improve your content
Beyond the label itself, tracking reading time as a content metric helps you calibrate your writing:
Map content type to expected reading time. If your how-to guides consistently come in at 8–10 minutes, you've implicitly committed readers to that length. Readers who bookmark your site calibrate to that expectation.
Use reading time to identify pacing problems. If a 5-minute-read article has a 40% completion rate but your 8-minute articles have 65%, the short article might be too dense — more words at the same length could paradoxically improve the experience.
Match reading time to where the content lives. A 15-minute article works well as a pillar page linked from a newsletter. It works poorly as the linked content in a Twitter thread where the audience expects a quick answer.
Calculate the exact reading time for any piece of content with our free Reading Time Calculator — paste in your text and get the result in seconds.