That little “8 min read” label under article titles looks authoritative — but what does it actually mean, and how is it computed? Learning how to calculate reading time is simple arithmetic (words divided by speed), but the interesting part is everything the formula hides: which reading speed to assume, why baselines differ, and what “reading” even means for a skimmed article.
This guide is written for bloggers and writers: what the label means, the honest story on words-per-minute baselines (with sources, not invented numbers), a side-by-side table of what different speeds imply, and how to display reading time on your own blog.
To get your article’s reading time instantly, paste it into our free Reading Time Calculator — or count the words first with the Word Counter.
Table of Contents
- How to Calculate Reading Time: The Formula
- What “X Min Read” Actually Means
- Reading Speed Baselines: The Honest Numbers
- Skim Reading vs. Deep Reading: Why One Number Lies
- How to Display Reading Time on Your Own Blog
- How to Calculate Reading Time for Video Scripts and Audio
- Try It: Check Any Article’s Reading Time
- Frequently Asked Questions
How to Calculate Reading Time: The Formula
The formula behind every reading-time label:
Reading time (minutes) = word count ÷ words per minute (WPM)
Worked example. This article is about 1,700 words. At 225 WPM: 1,700 ÷ 225 = 7.56 minutes → displayed as “8 min read” (always round up — nobody wants to finish “early” and feel the label lied; rounding up sets expectations you can beat).
Once you internalize it, you know how to calculate reading time for anything: blog posts, documentation, newsletters, scripts. Everything else — the debates, the differing labels across sites for the same article — comes from the WPM assumption and from what gets counted as “words.” Code blocks, image captions, and tables: some calculators count them, some do not. There is no standard, which is why two tools can disagree by a minute on the same article without either being wrong.
What “X Min Read” Actually Means
The label is a commitment device, not a measurement. It answers the reader’s real question — “how much of my life will this cost?” — in the two seconds before they decide to click. Research on reading behavior consistently shows readers use length signals to decide whether to start; the label converts an unknown cost into a known one.
What it does not mean: that you will finish in exactly that time, that the article is worth that time, or that two “5 min read” articles demand equal effort. A 1,100-word dense technical explainer and a 1,100-word breezy listicle both say “5 min read” at 225 WPM — the first takes most readers far longer. The label measures length, not difficulty. Honest writers know the difference; good writers adjust for it (more on that below).
Reading Speed Baselines: The Honest Numbers
Here is where most guides invent authority. You will see “the average adult reads 238 WPM” stated as fact across the web — usually without a source, and usually traced back to old, small-sample studies. The honest version: there is no single scientifically settled average reading speed. What we have are commonly used baselines, each with a context:
| Baseline | WPM | Context / source |
|---|---|---|
| Slow / careful | 200 | Used by many readability tools for technical content |
| Medium’s classic | 275 | Medium’s published reading-time basis for its “X min read” labels |
| Common default | 225–250 | The range most reading-time plugins default to |
| Fast / light content | 300+ | Skimming speeds; not a serious baseline for full comprehension |
See what happens to the same 1,700-word article across baselines:
| Baseline | Calculation | Displayed |
|---|---|---|
| 200 WPM | 1,700 ÷ 200 = 8.5 | 9 min read |
| 225 WPM | 1,700 ÷ 225 = 7.56 | 8 min read |
| 250 WPM | 1,700 ÷ 250 = 6.8 | 7 min read |
| 275 WPM (Medium) | 1,700 ÷ 275 = 6.18 | 7 min read |
A three-minute spread on the same article, from defensible baselines. The takeaway is not that the numbers are meaningless — it is that the baseline is a choice, and you should make it deliberately and state it. Our Reading Time Calculator lets you pick the WPM so the label matches your audience: use 200 for technical or academic writing, 225–250 for general blog content. Consistency within your own site matters more than which number you pick.
One more honesty note: published “average reading speed” figures come largely from mid-20th-century studies on silent reading of straightforward prose, often with college-student samples. Applying them to a 2026 audience reading dense documentation on a phone is an extrapolation, not a measurement. Treat WPM as a convention, not a fact — which is exactly how the serious tools treat it.
Skim Reading vs. Deep Reading: Why One Number Lies
Real reading is not one speed. Eye-tracking research distinguishes at least three modes, and your readers use all of them on the same article:
- Skimming (400+ WPM effective) — headings, first sentences, bold text. Most readers skim first and decide whether to commit.
- Normal reading (200–300 WPM) — the baseline the label assumes.
- Study reading (under 200 WPM) — re-reading, following code, working examples. Technical content lives here.
Practical consequences for writers. First, write for skimmers: descriptive headings, short paragraphs, bold key terms — the skim path should still deliver the gist. Second, adjust the baseline to the content: a tutorial with code samples labeled at 275 WPM will systematically under-promise time; use 200. Third, remember the label is marketing as much as information — “12 min read” filters for committed readers, “3 min read” invites casual ones. Neither is better; they select different audiences.
This is also why word count alone is a weak quality signal — a 3,000-word article padded with repetition says “13 min read” and delivers 5 minutes of value. Readers learn which sites’ labels they can trust. For more on what word counts actually signify, see our Word Counter and the broader question of how reading speed is studied.
How to Display Reading Time on Your Own Blog
Adding the label is a solved problem on every major platform:
- WordPress: reading-time plugins compute it automatically from the post’s word count — install one, set your WPM (we suggest 225 for general content), and the label appears under every title.
- Manual: count words (our Word Counter), divide by your chosen WPM, round up, and type “X min read” under the headline. Thirty seconds per post.
- Static sites / custom: most generators (Hugo, Jekyll, Next.js) have a reading-time helper or plugin — typically word count ÷ 200–275 with configurable WPM.
Three rules for doing it well: round up, not down (under-promising time beats over-promising); use one baseline site-wide (a “5 min read” should mean the same length on every page); and recalculate after major edits (that “4 min read” on a post you tripled is now a lie). The label is a promise — keep it.
How to Calculate Reading Time for Video Scripts and Audio
The same formula answers a different question for creators: how long will this script take to speak? Spoken delivery is much slower than silent reading — the conventional baseline for English speech is about 150 words per minute (conversational pace; 130 for dramatic or heavily technical narration, up to 160–170 for energetic delivery). The math for how to calculate reading time as speaking time is identical, only the WPM changes:
Speaking time (minutes) = script word count ÷ 150
Worked example. A 900-word YouTube script: 900 ÷ 150 = 6 minutes of spoken audio. Add ~10–15% for pauses, emphasis, and on-screen transitions, and you have a realistic 6:30–7:00 video. Podcasters use the same math: a 3,000-word episode script ÷ 150 = 20 minutes of talk time.
A common mistake when learning how to calculate reading time for scripts is using the silent-reading 225 WPM and wondering why the “5-minute” video runs 7:30. Silent reading and speaking are different activities with different speeds — match the baseline to the medium. Whether you are labeling a blog post or timing a script, the principle of how to calculate reading time is the same: words divided by the speed of the activity, with honest rounding.
Try It: Check Any Article’s Reading Time
Now that you know how to calculate reading time, paste any text into the free Reading Time Calculator — pick your WPM baseline and get the honest “X min read” figure instantly. Pair it with the Word Counter for the full length workup before you publish.
Frequently Asked Questions
How is reading time calculated?
Word count divided by reading speed in words per minute, rounded up. Example: 1,700 words ÷ 225 WPM = 7.56 minutes → “8 min read”. The WPM baseline (commonly 200–275) is a chosen convention, not a measured universal.
What is the average reading speed in words per minute?
There is no single settled scientific figure — commonly cited baselines range from 200 to 300 WPM depending on content difficulty and study methodology. Most reading-time tools default to 225–250 WPM for general content; Medium has published 275 WPM as its basis.
How do you calculate reading time from word count?
Divide the word count by your chosen WPM and round up: 900 words at 225 WPM = exactly 4 minutes → “4 min read”. Count the words with a word counter tool first if you do not have the count.
What is a good reading time for a blog post?
It depends on intent, not a magic number: 3–5 minutes for news and quick takes, 7–12 for substantive explainers, longer for definitive guides. Match the length to the promise of the headline — the failure mode is a 12-minute article with a 3-minute idea, not any particular duration.