How to Estimate Reading Time for Any Text
The 7-Minute Estimate That Made Nobody Happy
The editor had labeled the article "7-minute read." Readers bounced after three minutes. Not because the content was bad, but because the estimate was based on a generic 200 WPM average applied to a dense technical piece about database indexing. The real time was closer to 12 minutes for the target audience.
Reading time estimates fail in exactly this way: a single number applied carelessly, without accounting for content type, audience, or format.
Getting the estimate right changes what you build.
Why the Average Reading Speed Is Not One Number
238 words per minute is the figure most reading time tools default to. It comes from a widely cited research average for silent reading of English prose. A reasonable starting point for general blog content, but "average" conceals a lot.
A reader skimming a listicle for a single data point will move at 700+ WPM. Someone working through a legal contract reads at 100 WPM or slower. Medical instructions, code documentation, and academic papers all pull reading speeds down toward 150 WPM. Fiction sits somewhere in the 250-300 WPM range for engaged readers.
The fix is adjusting your speed assumption to match your actual reader, not the statistical average.
Speaking Time Is Different, and Not Just Because It's Slower
Speaking out loud at 150 WPM sounds natural in conversation. A formal keynote presentation runs 120-130 WPM to let points land. A podcast host talking casually hits 160-180 WPM before it feels rushed.
The practical difference: a 1,500-word script reads in 6-7 minutes silently, but takes 10-12 minutes to deliver aloud with normal pauses, emphasis, and breathing.
Presenters regularly underestimate this. They write a script, read it once silently at 7 minutes, and step on stage to discover it runs 11. The panic that follows mid-presentation is very avoidable.
If you're preparing a speech, conference talk, or podcast script, use a dedicated speaking time estimate rather than a reading time estimate. The two numbers serve different purposes and shouldn't be confused.
How to Use the Reading Time Calculator
The reading time calculator at ToolFlip handles both reading and speaking estimates from a single paste. Here's how to get the most out of it:
For blog posts and articles: Paste your draft. Leave the reading speed at 238 WPM. Check the Flesch-Kincaid grade level shown at the bottom. If you're writing for a general audience and the score is above 10th grade, the actual reading time will run longer than the estimate because your readers will slow down.
For presentations and speeches: Paste your script. Switch your focus to the speaking time output and drop the speaking speed slider to 130-140 WPM if you want a more conservative estimate. Most first-time speakers underestimate pauses by 20-30%.
For technical documentation: Bump the reading speed slider down to 150-180 WPM before trusting the output. Your readers are not reading for pleasure; they're searching for answers and re-reading sections.
For podcast scripts: 150 WPM in the tool maps well to a natural conversational pace. Adjust upward to 170-180 if your style is faster.
The slider range goes from 100 to 400 WPM for reading and 80 to 250 WPM for speaking, so every use case fits. The estimates update in real time as you type or adjust speeds.
What the Flesch-Kincaid Score Tells You
The reading level indicator in the tool uses the Flesch-Kincaid Grade Level formula. A score of 8 means an eighth-grader can follow it. A score of 12 means high school senior level. Above 16, you're writing for specialists.
This matters for time estimation because grade level and reading speed correlate. Grade 6-8 content at 238 WPM is a fair estimate. Grade 12+ content at 238 WPM is an underestimate for most readers.
It also matters for audience fit. A readability checker gives you a fuller picture here, but the Flesch-Kincaid number in the reading time tool is a useful quick signal without needing a separate tool.
If you find your content is reading at grade 14 and you're writing for a general consumer audience, you've diagnosed two problems at once: the time estimate is off, and the writing needs simplification.
Real Scenarios with Real Numbers
A 1,200-word travel blog post at 238 WPM: 5 minutes. At 300 WPM for a reader who skims: 4 minutes. That's close enough that a "5-minute read" badge is accurate for most visitors.
A 2,000-word SaaS comparison article at 238 WPM: 8.4 minutes. The same article with dense feature tables, code snippets, and technical terminology: realistically 12-15 minutes for the buyer evaluating the tools.
A 10-minute keynote at 130 WPM: approximately 1,300 words. Add 15% buffer for pauses and you want a 1,495-word script. Most speakers write 1,800 words and wonder why they always run over.
A 30-minute podcast episode at 150 WPM: 4,500 words for a fully scripted show.
Track these against the word counter once you have a target word count, then verify with the reading time tool as you draft.
FAQ
What's the difference between reading time and speaking time?
Reading time is how long it takes to silently read a text. Speaking time is how long it takes to read that text aloud at a spoken pace. Speaking is slower because of natural pauses, emphasis, and breath. A 1,000-word text takes roughly 4 minutes to read silently (at 238 WPM) and about 6-7 minutes to deliver as a speech at a conversational 150 WPM.
How many words is a 5-minute blog post?
At the research-average reading speed of 238 WPM, a 5-minute read is about 1,190 words. At 200 WPM (more typical for dense content), it's 1,000 words. If you want your audience to actually spend 5 minutes with your piece, write to the lower end of that range.
Why do Medium and Substack reading times feel wrong so often?
Both platforms use a static WPM estimate applied to word count. They don't account for images (which add time), code blocks (which slow readers), or content complexity. Their estimates work for narrative prose and fail for technical writing. Running your own estimate with an adjustable tool and then calibrating to your actual content type gives better results.
Does text complexity affect reading time?
Yes, meaningfully. Sentence length, vocabulary difficulty, and information density all affect reading pace. The Flesch-Kincaid score is a reasonable proxy. Simple content (grade 6-8) reads close to the WPM default. Technical content (grade 12+) often reads 25-40% slower than the estimate suggests.
Get Your Estimate
Paste your draft into the reading time calculator, adjust the speed sliders to match your audience, and check the grade level against your reader's expectations. Three numbers, thirty seconds.
If you're still in the drafting stage and need to hit a target length first, the word counter gives you live counts as you type. Once the draft is solid, the readability checker catches complexity issues the Flesch-Kincaid score alone won't surface.