The Three-Second Decision
When someone lands on an article, they make a rapid decision: is this worth my time? Reading time estimates help them decide by setting expectations upfront. A "3 min read" signals a quick scan. A "15 min read" signals a deep dive. Both are valuable — but the reader needs to know which they are getting.
Medium popularized the reading time indicator, and it has since become standard across blogs, news sites, and documentation. Research consistently shows that adding reading time estimates increases both click-through rates and completion rates.
How Reading Time Is Calculated
The formula is simple:
Reading time = Word count ÷ Reading speed
The standard reading speed used by most platforms is 200–250 words per minute for English text. Medium uses 275 wpm. Most implementations round up to the nearest minute.
A 1,500-word article at 230 wpm = 6.5 minutes → "7 min read"
Average Reading Speeds
Reading speed varies significantly based on the type of content and the reader's purpose:
Casual reading (novels, articles): 200–300 wpm. This is the range most people fall into when reading for comprehension.
Skimming (scanning for key information): 400–700 wpm. Readers jump between headings, bold text, and opening sentences of paragraphs.
Technical documentation: 50–100 wpm. Complex code examples, mathematical formulas, and dense technical content require careful reading and often re-reading.
Academic papers: 100–200 wpm. Specialized vocabulary, complex arguments, and citations slow reading speed.
Speed reading (trained): 400–1,000 wpm. Achievable with practice but with reduced comprehension. Most speed reading involves sophisticated skimming rather than full comprehension.
Why 230 Words Per Minute?
Most reading time calculators use a speed between 200 and 275 wpm. This is based on decades of research:
- Average adult reading speed in English: 238 wpm (Brysbaert, 2019)
- College students: 260–280 wpm
- Non-native English speakers: 130–200 wpm
Using 200–250 wpm produces estimates that are accurate for most readers and slightly generous for fast readers — which is better than underestimating (telling someone "3 min" for an article that takes them 7 minutes feels deceptive).
Content That Breaks the Formula
Word count alone does not capture reading time for all content types:
Code-heavy articles. A 500-word article with 200 lines of code takes much longer to read than a 500-word article of plain prose. Some calculators add extra time for code blocks.
Image-heavy content. A photo essay or infographic-based article adds viewing time that word count does not capture. A rough estimate adds 12 seconds per image.
Interactive content. Tutorials where readers are expected to follow along and perform actions take 2–3x longer than passive reading time.
Lists and tables. Scannable content reads faster than continuous prose. A 1,000-word reference table can be scanned in 2 minutes, while 1,000 words of narrative prose takes 4 minutes.
How to Use the Toobits Reading Time Estimator
Paste your text and see the estimated reading time instantly, based on standard reading speeds. The tool also shows word count, character count, and other text statistics. Use it to add reading time estimates to your blog posts, check whether an article hits your target length, or evaluate content density. Everything runs in your browser — your text never leaves your device.