Reading Time Calculator: How Long Will Your Text Take to Read?
Published October 24, 2026 · 7 min read
Reading Time Calculator: How Long Will Your Text Take to Read?
"8 min read." You've seen that little label on countless articles. It seems trivial, but it answers a real question every reader asks before committing: how much of my time is this going to take? A reading time calculator gives you that number in seconds — and adding it to your own content is one of the easiest trust signals you can offer readers.

This guide explains exactly how reading time is calculated, what average reading speeds to use, how to display reading time on your articles, and the edge cases (images, code, non-native readers) that the simple formula misses.
The Simple Formula Behind Every Reading Time Calculator
Every reading time calculator uses the same basic math:
Reading time (minutes) = Total word count ÷ Average reading speed (words per minute)
The only variable is which reading speed you assume. The most commonly cited figures:
- 200 words per minute — a conservative estimate, often used for general audiences
- 225 words per minute — the middle ground many calculators and platforms use
- 250 words per minute — a slightly faster estimate for educated adult readers
So a 1,200-word article takes:
- 6 minutes at 200 wpm
- 5.3 minutes at 225 wpm
- 4.8 minutes at 250 wpm
Most calculators round up to the nearest whole minute — "6 min read" rather than "5.3 min read." Rounding up sets honest expectations; nobody complains that an article took less time than promised.
Want the word count first? Paste your draft into a free word counter, divide by your chosen speed, and you have your reading time.
What Is the Real Average Reading Speed?
The 200-250 wpm range comes from decades of reading research on silent reading for comprehension in adults. A few nuances worth knowing:
It's an average, not a rule. Individual speeds vary enormously — from under 150 wpm for struggling readers to 400+ for practiced speed readers. The calculator gives a population estimate, not a personal one.
Material difficulty matters. People read dense technical writing, legal text, or unfamiliar subjects much more slowly — sometimes under 100 wpm for difficult academic prose. Light fiction or familiar blog topics are read faster.
Language matters. Reading speeds differ across languages based on information density per word. English-language averages don't transfer directly to, say, Finnish or Chinese.
Purpose matters. Skimming for gist is far faster than studying for an exam. Most calculators assume "normal reading for comprehension" — engaged but not studying.
For a general-audience blog, 225 wpm is the safest default. It's the figure used by several major platforms and sits in the middle of the research range.
How to Display Reading Time on Your Articles
The convention is simple: show it near the headline or byline, before the reader starts.
Format options:
- "6 min read" (Medium's style — the most recognized)
- "Reading time: 6 minutes"
- "⏱ 6 min" (with an icon)
Where to put it:
- Under the headline, next to the publish date and author
- In article cards and archive listings, so readers can choose before clicking
- In newsletters, so subscribers know the commitment
Implementation:
- WordPress: plugins like "Reading Time" calculate it automatically
- Manual: word count ÷ 225, rounded up, typed into your template
- Static sites: a one-line JavaScript function or build-step calculation
One caution: if your CMS auto-calculates reading time, check what it counts. Some count every word in the HTML including navigation and footer text, inflating the number. The count should reflect article body text only.
What the Simple Formula Misses

Honest calculators acknowledge the blind spots:
Images. Medium's well-known algorithm added time for images: 12 seconds for the first image, 11 for the second, 10 for the third, decreasing from there. A photo-heavy article takes meaningfully longer to consume than its word count suggests.
Code blocks and data tables. Readers slow down dramatically on code, often re-reading lines. A tutorial with heavy code samples takes longer than its word count implies.
Videos and embeds. A 10-minute embedded video doesn't change the text reading time, but it changes the total time investment. Some sites note "6 min read + 10 min video" separately.
Non-native readers. Someone reading in their second language may read 30-50% slower. If your audience is global, consider the conservative 200 wpm figure.
Scanning vs. reading. Many web readers scan headings and skip sections. Actual time-on-page is often less than the calculated reading time — which is fine, since the label is about the full read.
None of this means the label is useless. It means it's an estimate, and readers intuitively understand it as one.
Reading Time Benchmarks for Common Content
To calibrate your expectations:
- Tweet / short social post (280 chars): seconds
- Email newsletter: 3-5 minutes
- Standard blog post (1,000-1,500 words): 4-7 minutes
- In-depth guide (2,500+ words): 11+ minutes
- Long-form feature (5,000 words): 20+ minutes
- Short book (50,000 words): ~4 hours
- Novel (90,000 words): ~7 hours
If your "quick tips" post clocks in at 12 minutes, that's a signal to tighten it — or to split it into a series. Reading time is a useful editorial mirror.
Does Reading Time Affect SEO?
Directly? No — Google has never listed reading time as a ranking factor. Indirectly, it can help:
- Sets expectations, reducing the chance a reader bounces in the first seconds because the article was longer than expected
- Signals completeness — a "12 min read" on a definitive guide reassures readers they've found the thorough resource
- Improves click-through on article listings where readers are choosing between options
The effect is modest but real, and the implementation cost is near zero. There's little reason not to show it.
Frequently Asked Questions
How does a reading time calculator work?
A reading time calculator divides the total word count by an average reading speed — typically 200 to 250 words per minute for adults — and rounds the result into minutes. Some calculators adjust for images or complex text.
What is the average adult reading speed?
Most studies place average adult silent reading speed for comprehension between 200 and 250 words per minute. Speed readers exceed this, while technical or dense material is read more slowly, often under 200 words per minute.
How do I add reading time to my blog posts?
Calculate minutes as word count divided by 225 (a common middle-ground speed), round up, and display it near the headline — e.g. '6 min read.' Many CMS platforms and SEO plugins do this automatically.
Should reading time include images?
Medium's original reading-time algorithm added 12 seconds for the first image, 11 for the second, and so on, decreasing per image. For most blogs, simply noting text reading time is fine; image-heavy posts can add a small buffer.
Does reading time affect SEO?
Not directly — reading time is not a ranking factor. But displaying it sets expectations, which can improve engagement and reduce bounce rates on long articles, and those engagement signals matter.
SUGGESTED RELATED POSTS
- How Many Words Should a Blog Post Be?
- Word Counter: Check Length, Characters & Reading Time
- Meta Description Length: The 2026 Guide
