Reading Time Calculator for Articles

What Is Reading Time?

Reading time is the estimated duration a person needs to read a piece of text at a given pace. It’s used by publishers, bloggers, and content teams to set expectations for readers — Medium pioneered showing “5 min read” at the top of articles, and the practice spread across the web because it works: readers who know what they’re committing to are more likely to engage.

For writers and editors, reading time is a practical production tool. A conference talk slot is 20 minutes. A podcast segment is 8 minutes. A landing page hero section should take under 30 seconds to scan. Knowing the reading time before publishing lets you trim, expand, or restructure accordingly.

How Reading Time Is Calculated

The formula is simple:

Reading Time (minutes) = Word Count ÷ Reading Speed (wpm)

The only variable that changes between tools is the assumed reading speed. This calculator defaults to 238 words per minute, based on a 2019 meta-analysis by Marc Brysbaert (Ghent University) covering 190 studies and 18,573 participants — the most comprehensive dataset on adult silent reading speed available. Earlier estimates of 250–300 wpm came from studies using simpler texts and less rigorous methodology.

Why Reading Speed Varies

Reading speed is not fixed. The same person reads at different speeds depending on:

Content complexity — academic papers, legal contracts, and technical documentation slow most readers to 100–150 wpm because comprehension requires re-reading and processing unfamiliar concepts. Casual fiction can sustain 300+ wpm.

Purpose — skimming a news article is faster than studying a textbook chapter. Proofreading is slower than reading for enjoyment.

Individual factors — vocabulary breadth, familiarity with the subject, and reading practice all affect speed. Speed readers using techniques like chunking can reach 500–700 wpm, though comprehension typically drops above 300 wpm.

This calculator lets you choose slow (150 wpm), average (238 wpm), fast (300 wpm), or a custom speed to match your audience.

A Worked Example

A 1,800-word blog post on personal finance:

• At 238 wpm (average): 1,800 ÷ 238 = 7 min 34 sec
• At 150 wpm (slow/careful): 1,800 ÷ 150 = 12 min 0 sec
• At 300 wpm (fast): 1,800 ÷ 300 = 6 min 0 sec
• Speaking time at 130 wpm: 1,800 ÷ 130 = 13 min 51 sec

If this post were to be read as a podcast script, the host would need nearly 14 minutes — which means it’s a full podcast episode, not a quick segment. If the editor wants it under 10 minutes of reading time, they need to cut about 420 words.

Reading Time by Content Type

Blog Posts and Articles

The standard web article runs 800–2,000 words. At 238 wpm:

• 800 words → ~3:22 (short read, low bounce for mobile)
• 1,200 words → ~5:03 (sweet spot for engagement)
• 1,800 words → ~7:34 (in-depth, good for SEO)
• 2,500 words → ~10:30 (long-form, requires high reader intent)

SEO data consistently shows that longer content ranks better for informational queries — but only when the length is justified by depth, not padding. A 2,000-word article that answers the question thoroughly outperforms a 3,000-word article that repeats itself.

Books and Long-Form Content

The average non-fiction book is 60,000–80,000 words. At 238 wpm reading 1 hour per day:

• 60,000 words → ~4.2 hours → about 4 days of dedicated reading
• 80,000 words → ~5.6 hours → about 6 days

Fiction tends to be faster because prose is simpler and readers are in flow state. Non-fiction with dense argument or data is slower.

Emails and Newsletters

The ideal marketing email is 200–250 words — under 1 minute to read. Research from HubSpot and Litmus consistently shows response rates drop after 200 words. Internal emails over 300 words are often skimmed or deferred. If your email needs more than 1 minute, consider whether it should be a document instead.

Speeches and Presentations

Speaking rate varies: conversational speech runs 130–150 wpm, formal presentations 120–140 wpm, podcasts 140–160 wpm, auctioneers 250+ wpm. For public speaking:

• 5-minute talk: ~650–750 words
• 10-minute conference slot: ~1,300–1,500 words
• 18-minute TED Talk: ~2,340–2,700 words
• 45-minute keynote: ~5,850–6,750 words

The speaking time output in this calculator uses 130 wpm — appropriate for a measured, clear presentation pace.

Technical Documentation

Technical docs slow readers significantly. API documentation, code tutorials, and legal text are typically read at 100–150 wpm because readers stop to verify, re-read, and think. If you’re writing developer docs, use the Slow preset. A 2,000-word tutorial may take 15–20 minutes in practice, not 8 minutes at average reading speed.

Key Assumptions and Limitations

This calculator counts words by splitting on whitespace — code blocks, URLs, and special characters count as words, which may overstate the count for technical content. Reading time is an estimate; actual time varies by reader and content. The 238 wpm baseline applies to adult silent reading of English prose; non-native speakers and children read slower. Speaking time at 130 wpm is calibrated for formal presentations — conversational podcasts run faster (140–160 wpm), audiobooks faster still (150–175 wpm). Use the custom speed input to adjust for your specific use case.