Estimate reading time at slow, average, and fast paces. Includes speaking / presentation time variant.
Built and maintained by Paul Clark, Redmoon Software
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.
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.
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.
Average adults read 200–300 words per minute. Slow readers and complex material: 150 wpm. Skimming: 400+ wpm.
Conversational speaking is around 130 wpm; broadcast and audiobook narration around 150 wpm.
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.
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.
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.
The estimate is words divided by a words-per-minute rate, and this tool reports three: 150 wpm for slow or careful reading, 200 for average, 250 for fast. Publishing a single figure would imply a precision that does not exist — adult silent reading speeds for ordinary prose span roughly 150 to 300 wpm, and comprehension-checked speeds cluster lower than people assume.
Speaking is much slower again, which is why the spoken figure is reported separately. Conversational delivery runs near 150 wpm and prepared presentation slower still, so a page that takes two minutes to read takes appreciably longer to say aloud.
Word count is a weak proxy for effort. Dense technical prose at 800 words takes longer than narrative at 1,200, and nothing in a word count registers that. Anything the reader stops at — a code block, a table, a diagram, a formula — costs time that is not in the model at all.
Non-prose content breaks it hardest. A tutorial where the reader follows along takes many times the estimate, because the estimate measures reading and the reader is doing.
Used well, a reading-time figure sets an expectation rather than makes a promise, and its main value is relative: it tells a reader whether they are looking at three minutes or thirty.
Turn text into fill‑in‑the‑blank exercises.
Writing & editingTwitter-weighted character counter with thread split.
Writing & editingTitle + description pixel-width validator with SERP preview.
Writing & editingCounts sentences, paragraphs, and length distribution.