Reading time calculator. Four speeds, content-aware.
Paste content. We count words and render reading time across four speed bands — slow (180 wpm), average (238 wpm per Brysbaert 2019), fast (300 wpm), scan (450 wpm). Content-type adjusters for technical, narrative, casual prose.
Paste your text. We count words and render reading time across four speed bands. Pick a content type to apply a density multiplier — technical reads slower, casual reads faster. Override the WPM in the custom field if your CMS uses a different baseline.
Privacy: word counting happens in your browser. Nothing is sent or logged.
Four bands. All from one count.
Slow / careful (180 wpm). Adult readers approaching the slower end of the distribution: children at 12+, second-language English readers, anyone reading dense academic or technical prose for full comprehension. Use this band as the conservative figure when you need to set a realistic upper bound for reader time commitment.
Average adult (238 wpm). The Brysbaert 2019 baseline. Synthesized across 100+ reading-rate studies of adult silent reading on medium-difficulty English text. The most defensible single-number choice; the figure you should put on a "5 min read" badge by default.
Fast (300 wpm). Practiced reader on familiar topic. A well-trained editor going through their own subject area at speed. A subject-matter expert skim-reading a paper in their field. Useful as the lower-bound figure when you need to estimate the fastest a typical reader could complete the content.
Scan / skim (450 wpm). Not really reading — searching for specific information. The reader who lands on your page from a Google query, scans for the answer to their question, and bounces. The figure that matters for measuring "did the answer surface fast enough" rather than "did they read the whole thing."
Four jobs this tool covers.
Job 1: Set the reading-time badge on a blog post. Paste the published text, take the average reader time, round to the nearest minute, render as "X min read" near the title. Medium's research found 7 minutes is the optimal length for retention. Show the badge on posts over 4 minutes; below that, the figure is noise.
Job 2: Plan content length for a target reader commitment. Working backward — if you want a 5-minute read, you need ~1,200 words at average reading speed. If you want a 15-minute deep dive, ~3,500 words. Use the calculator in reverse to set word-count targets for editorial briefs and outlines. Pair with our Character Counter for the live word count during writing.
Job 3: Match your CMS's existing reading-time figure. If your blog already shows reading times calculated at 200 or 250 wpm and you want consistency, override the WPM in the custom field. Useful when migrating from Medium / Wordpress / Ghost to a custom CMS — the new figures should match what readers were used to seeing.
Job 4: Audit a content marketing pipeline. Paste each piece in your editorial calendar and check the reading-time distribution. A pipeline where every piece is 8-12 minutes signals you're shipping nothing for the quick-answer audience; a pipeline where every piece is 2-4 minutes signals you've got nothing for the deep-research audience. The mix should match your audience's needs across both ends.
Six questions users ask.
Why 238 words per minute?
It's the empirical average from Brysbaert (2019), the most-cited meta-analysis of adult silent reading rates. The paper synthesized 100+ reading-speed studies covering medium-difficulty English text. The 200 wpm figure many tools use is a Medium / Pocket / Wordpress convention that pre-dates this research; 238 is the better default. Real reading speed varies dramatically — 100-450 wpm depending on familiarity with the topic, age, reading purpose, and language. Use 238 as the central estimate; show all four bands so readers can self-pick.
What do the content-type adjusters do?
They multiply the base speed by a factor for the prose density. Technical content (research papers, API docs, finance reports) reads slower — denser sentences, unfamiliar vocabulary, more re-reading. We apply a 0.75× multiplier (so 238 → 178 wpm). Narrative content (fiction, journalism, blog posts) reads at base speed (1.0×). Casual content (tweets, chat messages, simple lists) reads faster — predictable structure, simple sentences. We apply a 1.25× multiplier. Pick the type that matches your audience expectation.
How does this differ from the Character Counter?
Character Counter is the all-purpose live counter — chars, words, sentences, paragraphs, lines, plus format-threshold badges and top-words analysis. Reading Time Calculator is the dedicated reading-rate tool with multiple speed bands, content-type multipliers, and the breakdown by section. If you need format-threshold badges (tweet, SEO title, ad copy), use Character Counter. If you need a defensible reading-time figure to show readers, use this one.
Should I show reading time on my blog?
Yes for posts over 4 minutes. Below 4 minutes the figure is noise — most readers will start reading anyway. Above 4 minutes, the figure helps readers decide whether to commit; Medium's research showed the ideal post length is 7 minutes (about 1,600 words at 238 wpm). For long-form pieces (~15+ minutes), the reading time is a contract — readers self-select for that length. For very short pieces, omit the badge entirely; the visible content count is enough.
Why am I getting different numbers from other reading-time tools?
Most use 200 wpm — the older Medium / Pocket convention. Some use 250 wpm (Hemingway). A handful use 275 (Wordpress's plugin default). We use 238 as the Brysbaert-validated default, but show all four bands so the answer doesn't depend on which tool you used. If your CMS uses a different default, override the WPM in the Custom field below to match — useful for keeping reading-time consistent across the rest of your stack.
Is the text I paste sent anywhere?
No. Word counting happens in your browser. The text is never uploaded to Digital Heroes servers, never logged. The page is static HTML; the only network request is the initial page load. Safe for unpublished article drafts or any sensitive content.
Published · Last updated .