The simple math
Reading time = word count ÷ words per minute, rounded up. A 1,000-word article at 200 WPM shows "5 min read." Most implementations round any fraction up (4.2 minutes → "5 min read") and show "less than a minute" below the threshold. Our word counter computes it live as you type.
Some calculators subtract code blocks or adjust for images (adding ~10–12 seconds per image, following Medium's well-known formula). These refinements matter less than consistency: pick one method and apply it everywhere.
What 200 WPM assumes
200–250 WPM is the standard estimate for adult silent reading of non-fiction. It assumes:
- A fluent adult reader, reading silently (not aloud, not studying).
- Average-difficulty prose — not dense academic text, not breezy dialogue.
- Continuous reading without re-reading, note-taking, or following tutorials step by step.
Actual silent reading speeds vary enormously — 150 to 400+ WPM across individuals — so 200 is a conservative middle that slightly overestimates time for fast readers and underestimates for slow ones. For speaking (video scripts, presentations), use ~130 WPM instead.
When the estimate breaks down
- Tutorials and documentation. Readers pause to try steps; real time can be 3–5× the estimate. Consider "X min read + exercises" or a difficulty label.
- Heavy code or math. Code is read far slower than prose. Either exclude code blocks from the count or add a fudge factor.
- Children's or ESL content. Reading speeds are much lower; 200 WPM will badly understate.
- Listicles and reference pages. Nobody reads these linearly — time-on-page bears little relation to word count.
Displaying it well
- Round up, never down. Under-promising time builds trust; a "3 min read" that takes 8 feels like a lie.
- Keep the format consistent ("5 min read" everywhere, not "5 minutes" here and "5'" there).
- Pair with word count for long-form content, so readers can judge depth.
- Recompute when content changes — stale reading times on updated articles erode credibility.
Reading time for video, audio, and presentations
The same math powers other media — with different speeds:
- Video scripts: ~130–150 words per minute of finished video. A 1,000-word script ≈ 7 minutes. Talking-head delivery runs slower than voiceover; leave pauses for emphasis.
- Podcasts: conversational speech is ~120–140 WPM, but editing, intros, and guest dynamics make word-count estimates rough. Scripted segments follow the video math; unscripted ones do not.
- Presentations: ~100–120 WPM once you account for slide transitions, pauses, and audience questions. A 15-minute talk ≈ 1,500–1,800 spoken words — far fewer than writers expect.
- Audiobooks: professional narration holds ~150 WPM; a 90,000-word novel ≈ 10 hours.
When scripting, draft in the word counter and divide by the medium's rate before recording — discovering your "5-minute video" needs 12 minutes of footage is an expensive surprise. And always do a timed read-through: real delivery with nerves and pauses differs from silent estimates every time.
For live talks, budget an extra 20% beyond the word-count estimate: audience laughter, questions, and demo hiccups all consume minutes that no script accounts for. Mark two or three "cut points" in your notes — slides you can skip gracefully if time runs short. Speakers who plan for overruns finish on time and look polished; speakers who do not, do not.
Reading time is a courtesy, not a contract: a helpful signal that respects the reader's schedule. Use it alongside sensible word count targets, and check drafts with the word counter before publishing.