Reading Time Estimator
Estimate reading and speaking time instantly. Paste any text to get word count, character count, reading time, and speaking time — CJK-aware.
Calculator
0 bytes
You just tested your Reading Time Estimator — Try Cover Letter Builder next →
What Is a Reading Time Estimator?
Reading speed is not one number — it varies by language, content density, reader expertise, and reading mode. English adult silent reading averages 238 words per minute for non-fiction and 260 WPM for fiction (Brysbaert 2019 meta-analysis of 190 studies). Speed-readers and skim-readers clock 400-700 WPM with comprehension drops past 500 WPM. Speaking aloud sits around 130-150 WPM for clear narration (podcasts target 150 WPM; TED talks average 163). The default 200 WPM in this estimator is deliberately conservative — it is the rate where 95% of adult readers maintain comprehension on unfamiliar topics. Languages differ: Chinese reads 158 characters per minute (Brysbaert's CJK correction); Japanese 193 cpm including kana; Korean 222 cpm; Spanish 218 WPM (slightly faster than English due to phonetic regularity); Arabic 138 WPM (right-to-left + dense morphology); Finnish 161 WPM (long agglutinative compounds). The estimator detects CJK content via the Intl.Segmenter API (grapheme-aware) and switches to char-per-minute math; otherwise it splits on whitespace + punctuation per the Unicode Lo category.
How to Use the Reading Time Estimator
Paste any text. The output shows: total words (or characters for CJK), paragraphs, sentences (split on . ! ? plus locale-specific terminators), silent reading time at your chosen WPM, speaking time at your chosen speaking WPM, and scanning time (which assumes 400 WPM — the rate at which a reader extracts only headings and bold phrases). Two sliders adjust the rates: silent-reading WPM (default 200; lower to 150 for technical content with terminology, raise to 260 for fiction or familiar topics) and speaking WPM (default 130; lower to 100 for slow narration like audiobooks, raise to 175 for fast podcast pacing). The estimator updates live as you type or paste. A copy button outputs a Markdown line you can paste at the top of articles or docs: 5 min read • 1024 words.
Why Reading Time Estimates Improve Content
Reading-time labels boost click-through by 7-12% on long articles (Medium's 2014 internal study reproduced by The Atlantic, Substack, and Stratechery). The mechanism is loss-aversion: an unknown commitment feels riskier than a known 7-minute investment. For documentation, accurate estimates let teams plan sprint capacity (a 1500-word RFC takes ~8 min to read; reviewers can batch realistically). For conference talks, the 130-150 WPM speaking range maps directly to talk-length planning — a 30-minute slot is 3900-4500 spoken words including pauses, not the 6000+ words a text would suggest. SEO research from Backlinko and Ahrefs (2024) shows long-form (1500-2500 words, 7-12 min) over-indexes in top-3 SERP positions for informational queries, but only when content density justifies length — bloated articles get bounce-rate penalties that erase the ranking gain. Calibrating word count to a target reading time is the discipline; estimating before writing is the cheap version of that discipline.
Frequently Asked Questions
How is reading time calculated?
Reading time = word count ÷ reading speed (WPM). The default speed is 200 WPM — the average adult reading speed. Adjust the slider to match your pace.
How does it handle Chinese or Japanese text?
CJK (Chinese/Japanese/Korean) text is counted by character, not word. When your text is mostly CJK, the calculator automatically switches to character-based counting using the Intl.Segmenter API for accuracy.
What is a good reading speed?
Average adult: 200–250 WPM. Speed readers: 400+ WPM. Comfortable speaking pace: 130–150 WPM. Academic/technical reading is often slower: 150–200 WPM.
Use this tool inside a bigger workflow
These collections group follow-up tools and guides that commonly belong in the same job.
Browse same tags
Jump to other tools that share the same workflow, format, or use case.