Reading Time Calculator
Paste content and estimate reading time. Standard 238 wpm baseline plus configurable speed for audience differences. Word + sentence + paragraph counts included.
Reading Time Calculator
How to use the Reading Time Calculator
Paste your content
Paste your blog post, article, newsletter, script, or any text. The tool counts words, sentences, and paragraphs in real time. HTML tags are auto-stripped so you can paste from your CMS preview without cleanup.
Set the reading speed
Default 238 wpm is the standard average for adult silent reading in their native language (industry consensus, based on multiple meta-analyses). Adjust for your audience: 180 wpm for non-native readers or technical content; 238 for general consumers; 300+ for educated/expert audiences. Speed readers and scanners hit 400-700 wpm but lose comprehension above 300.
Read the estimate
Get total reading time (minutes + seconds), plus word count, sentence count, and paragraph count. Use this to: (1) match content length to user attention span (commute-length articles, lunch-break reads, deep dives); (2) plan editorial calendars; (3) decide whether to split a long piece into a series; (4) add "X min read" badges to live posts.
Match length to purpose
Short content (under 300 words): tweets, micro-content, push notifications. Medium (300-1000): standard blog post. Long-form (1000-2500): SEO sweet spot for competitive keywords. Pillar (2500-5000): topic-cluster anchors, ultimate guides. Mega (5000+): chapter-length investment pieces — usually need TOC + scannable structure.
Reading time — the small UX touch that lifts engagement
Reading time estimates serve two purposes: they help WRITERS plan content length for audience attention spans, and they help READERS decide whether to invest before clicking. Both effects are well-documented. Medium pioneered "X min read" badges in 2014; bounce rate on Medium articles dropped ~10-15% after the badges launched as users self-selected. The math is simple: words divided by reading speed, expressed in minutes. The standard "238 words per minute" baseline comes from meta-analyses of adult silent-reading studies — published by Brysbaert (2019) and others — and is the de-facto industry default for content tools.
Why 238 wpm is the industry standard
For decades, content tools used 200 wpm or 250 wpm as the reading-speed baseline — both were rough estimates from older studies (mostly with reading-aloud measurements, which run slower than silent reading). Brysbaert\'s 2019 meta-analysis aggregated 190 studies covering ~18,000 readers and concluded the true average for silent adult reading is ~238 wpm in English. Different content types vary: fiction reads at ~260 wpm (familiar narrative patterns), nonfiction at ~238 (more cognitive load), technical/scientific at ~190 (vocabulary + structure costs). 238 is the most-cited modern default; this tool uses it as the baseline but lets you adjust for your specific audience.
Adult silent reading averages 238 words per minute (Brysbaert 2019, meta-analysis of 190 studies). The popular "200 wpm" rule was based on older read-aloud measurements, which run slower than silent reading.
Content length as a strategic decision
Article length should match audience context + content goal, not arbitrary "more is better" instincts. Under 300 words: tweets, micro-content, push notifications, social posts. 300-800 words: news updates, product announcements, single-topic posts. Average newspaper feature: 500-800 words. 800-1500 words: standard blog post for most B2C content. 1500-2500 words: SEO sweet spot for competitive keywords — Google\'s top-ranking pages for substantial queries average ~2,000 words. 2500-5000 words: pillar pieces, ultimate guides, technical deep-dives. 5000+ words: chapter-length investment content; reader retention drops sharply past ~12 minutes (~3000 words at 238 wpm), so use TOC + scannable headings. The "long-form ranks better" SEO trope is often misread: it\'s not the WORD COUNT that ranks; it\'s the THOROUGHNESS that long-form correlates with. A 1,500-word piece that covers a topic completely ranks better than a 3,000-word piece padded with fluff.
The ASEAN multi-language reading reality
The 238 wpm baseline applies to native English readers. L2 English readers (second language) read 30-40% slower — roughly 150-180 wpm. Most of ASEAN ex-Singapore reads English as L2, so use ~180 wpm if your content targets these audiences. Native-language reading (Bahasa Indonesia/Malaysia, Thai, Vietnamese, Tagalog) is typically faster than L2 English for those speakers — closer to the 238 wpm equivalent in their native language. Chinese reading is usually measured in characters per minute (CPM), not wpm — average ~250-350 CPM for fluent readers, roughly equivalent to ~250 wpm in English. Implication for ASEAN content: if you\'re writing English content for an ASEAN audience, your "X min read" estimate at 238 wpm will be optimistic for L2 readers — actual reading time may be 30-40% longer. Either adjust the wpm slider or note "approximate" in the badge.
10 Things to Know About Reading Time
Adult silent reading: ~238 wpm (Brysbaert 2019 meta-analysis, 190 studies, ~18,000 readers).
Read-aloud is slower: ~150-160 wpm. The popular "200 wpm" baseline came from older read-aloud studies.
Fiction reads ~260 wpm; nonfiction ~238; technical/scientific ~190. Genre matters.
L2 readers (English-as-second-language) read 30-40% slower than native — typically 150-180 wpm.
Medium\'s "X min read" badge reduced bounce rate ~10-15% by letting readers self-select before clicking.
SEO sweet spot for competitive keywords: 1,500-2,500 words. Long enough to cover the topic; short enough to maintain attention.
Reader retention drops sharply past 12 minutes (~3000 words). Long-form needs TOC + scannable structure.
Speed reading above 300 wpm reduces comprehension significantly. "Speed readers" are usually skimmers.
Reading speed declines with age: peaks 25-40, drops ~10% per decade after 50.
Bilingual readers tend to read their L2 language 30-40% slower than L1, regardless of fluency.
Frequently Asked Questions
-
The 200 wpm baseline came from older studies (1960s-1980s) that mostly measured read-aloud speed, which is slower than silent reading. Brysbaert\'s 2019 meta-analysis of 190 studies covering ~18,000 modern silent-reading measurements established 238 wpm as the true average for adult native readers. Most modern content tools (Medium, Ghost, WordPress reading-time plugins) now use 238 or similar updated baselines.
-
Almost always yes. Medium\'s deployment in 2014 dropped bounce rate 10-15% as readers self-selected before clicking. Standard placement: near the title/byline. Format: "X min read" (floor minutes, ignore seconds unless under 1 minute). Adds zero pixel weight, minimal dev work, measurable engagement benefit. Caveat: don\'t show for very short content (under 1 minute) — feels patronising.
-
Not directly. Google doesn\'t read the "X min read" badge on your page. Indirectly: Google measures "dwell time" (time on page before returning to SERP), and reading time is a rough proxy. Pages with longer dwell time tend to rank better, but causation is debated — high-quality content drives BOTH long dwell time AND good rankings. Optimise for content quality + engagement; reading-time signals are downstream consequences.
-
Within ±20% for the average reader. Individual variation is large: same content takes one reader 5 minutes and another 10. Variables: prior knowledge of topic, vocabulary level, content complexity, distraction level, reading purpose (skim vs deep read). The estimate is useful as a planning + UX tool, not as a precise prediction for any individual reader.
-
Depends on audience + goal. SEO-focused: 1,500-2,500 words for competitive keywords; Google\'s top-ranking pages average ~2,000 words. Newsletter: 500-1,500 words; short attention windows. Pillar content: 2,500-5,000 words; comprehensive guides. News/updates: 300-800 words; brevity matters. Thought leadership: 800-2,000 words; depth matters more than length. The "long-form ranks better" SEO trope is partially true but oversold — quality + topical thoroughness drive ranking, not raw word count.
-
Not really — they\'re skimming or scanning, not reading. Genuine comprehension drops sharply above 300-350 wpm. Famous "speed reading" courses (Evelyn Wood, etc.) don\'t actually train faster reading; they train more efficient SKIMMING — which is genuinely useful for previewing or finding specific info, but comprehension suffers vs careful reading. If a reader needs to retain or apply the content, slower reading wins.
-
Strip HTML tags first, then count. This tool auto-strips tags before counting so you can paste from a CMS preview or HTML source directly. Don\'t count alt text, captions, or footnotes as part of body word count — they\'re ancillary. Do count headings + subheadings (they affect reading time). Skip nav, headers, footers, sidebars.
-
No. All analysis runs in your browser via JavaScript. Open DevTools → Network and confirm zero outbound requests. Content text + word counts stay on your device. Safe for unpublished drafts, confidential reports, or pre-release content analysis.
-
Strong correlation with "average time on page" (Google Analytics) IF readers actually consume the content. Sanity check: if your article is "10 min read" but average time on page is 90 seconds, readers are bouncing — content isn\'t holding attention. Engaged read: average time should be 60-80% of estimated reading time. Skim read: 20-40%. Bounce: under 15%. Use the ratio to diagnose engagement quality.
-
Pair with: SEO Title Tag Checker (RT-SEO-011) + Meta Description Checker (RT-SEO-012) for full on-page SEO; Headline Analyzer (RT-SEO-014) for headline scoring; Reading Level Calculator (RT-EDU-XXX) for Flesch-Kincaid grade-level scoring (different metric — readability, not time). For full content brief planning: Hemingway Editor (free), Grammarly (free tier), Google Docs word count.
Related News
You may be interested in these recent stories from our newsroom.
-
Cognition raises US$1 billion at a US$26 billion valuation as Devin clears US$492 million in revenue
The maker of the AI software engineer Devin has raised US$1 billion, valuing the company at US$26 billion after the money. Eight months ago...
-
Singapore tested government AI agents in a sandbox. The hard part was trust, not capability.
Singapore and Google ran AI agents against real government work for four months, on an air-gapped cloud, and published what broke. As someon...
-
OpenAI Foundation commits US$250 million to workers displaced by AI
The OpenAI Foundation has pledged an initial US$250 million for research, grants and programmes to help workers and economies adjust to AI-d...
75 more free tools
Calculators, converters, security tools — no signup.