Skip to content
Redmoon Calculators
Writing utilities All languages

Reading Time Estimator

Estimate reading time at slow, average, and fast paces. Includes speaking / presentation time variant.

When to use this

Use reading-time estimation for blog post "X-minute read" labels, for sizing presentation scripts, for podcast transcript timing, and for any UX that needs to set time expectations before users commit to reading.

How it compares

Reading time is the simplest of all text metrics and the most widely understood by end users. Pair it with a readability score: a 5-minute read at grade 12 is very different from 5 minutes at grade 6.

0 chars

How it works

Reading time is calculated as words ÷ words-per-minute. Typical reading speeds: slow 150 wpm, average 200 wpm, fast 250 wpm.

For audio narration or presentations, speaking speed (around 130 wpm) gives more realistic estimates.

Use the custom-speed slider to compute time at any reading speed from 50 to 500 wpm.

Formula

FAQs

What reading speeds are typical?

Average adults read 200–300 words per minute. Slow readers and complex material: 150 wpm. Skimming: 400+ wpm.

How is speaking time different?

Conversational speaking is around 130 wpm; broadcast and audiobook narration around 150 wpm.

Does reading time depend on the type of content?

Yes; dense technical or academic text is read more slowly than light fiction or web copy, so the same word count can take noticeably longer. Choosing the slow pace is safer for complex material.

How accurate are reading-time estimates?

They are approximations based on average words-per-minute and ignore images, tables, and how carefully someone reads. Treat the number as a rough guide rather than an exact figure.

Worked example

Input

500 words.

Output

Reading time: 2:30 at 200 wpm; speaking time: 3:51 at 130 wpm.

At an average adult reading speed of 200 wpm, 500 words = 2.5 minutes. Spoken aloud at conversational pace it takes about 50% longer.

Common pitfalls

  • WPM varies enormously by reader, language, and content complexity; the number is an estimate, not a guarantee.
  • Code, formulas, tables, and images are not "words" and slow readers significantly.
  • Re-reading and pause-to-think add real time that the formula cannot capture.
  • Speaking time is dominated by pauses and emphasis, not just word count.

Related tools

Send feedback

We read every message. Tell us what could be better or what you love.