About Reading Time Calculator
Estimate how long it takes to read or speak any text. Paste content for instant analysis. Free, no sign-up required.
How to use
- Paste your full article, blog post, script, speech, or document body into the textarea. The tool counts every whitespace-separated token as a word, so URLs, numbers, hyphenated words, and code snippets all factor into the estimate.
- Watch the three stat tiles update live as you type or paste. The first tile shows minutes to read silently (calculated at 238 WPM, which is Medium's published average), the middle tile shows raw word count, and the right tile shows minutes to speak aloud (at 150 WPM, the standard public-speaking pace).
- Use the silent reading estimate to set expectations on your blog post or article — adding 'A 6-minute read' near the title boosts click-through and reduces bounce because readers self-select for the time they have available.
- Use the speaking time estimate when scripting a presentation, video, podcast intro, or speech. A 5-minute talk needs roughly 750 words; a 20-minute conference talk needs roughly 3,000. Plan slides and pacing accordingly.
- Compare formats: copy a draft into the tool, trim or expand to hit a target time, and paste back into your editor. Trim aggressively if the time exceeds your audience's tolerance — most blog readers bail at 7 minutes, conference talks lose attention past 18 minutes.
- Adjust mentally for content type. Technical or scientific text reads slower (150-200 WPM), light fiction reads faster (300+ WPM), and dialogue-heavy fiction is fastest of all. The 238 WPM baseline assumes a typical web article.
- Treat the speaking estimate as a floor — actual delivery includes pauses, audience reactions, and breath breaks. Add roughly 20% padding for a polished delivery: a tool-estimated 5 minutes will run closer to 6 minutes when delivered well.
Examples
Average blog post
1,200 words pastes in and shows 6 min read, 8 min speak. Pasting a 600-word listicle shows 3 min read, 4 min speak. The 'X min read' badge on Medium uses this same 238 WPM math.
Conference talk script
A 20-minute keynote needs roughly 3,000 words at the 150 WPM speaking rate. Paste your draft, watch the speak-time tile, and trim until it sits around 18 minutes — that leaves buffer for pauses, slide transitions, and audience laughs.
Audiobook narration estimate
A 50,000-word novel pastes in showing about 3.5 hours speak time at 150 WPM. Real audiobooks take 5 to 7 hours of finished audio for that length because narrators add character voices, dramatic pauses, and pacing variation.
Frequently asked questions
Why 238 WPM specifically?
238 WPM is the figure Medium uses publicly for its 'X min read' badges, derived from internal research on millions of articles. It sits in the middle of the published academic range for adult silent reading on screens (203 to 260 WPM, per Brysbaert's 2019 meta-analysis of 190 studies). It is faster than aloud speech (150 WPM) and slower than skimming (400+ WPM), which makes it a defensible default for general web content. For a more conservative estimate, the New York Times and other publishers use 200 WPM, which gives a slightly longer time and rarely overpromises.
How does silent reading speed compare to reading aloud?
Silent reading averages 200 to 250 WPM for adults, while reading aloud is 100 to 150 WPM — roughly half the speed. Public speaking and broadcast presentation typically aim for around 150 WPM (TED Talks land near 163 WPM on average). Audiobook narration is paced at 150 to 160 WPM. The gap exists because pronunciation, breathing, and audience comprehension all add time. If you write something to be read aloud, expect it to take twice as long as a silent reader would need.
Why is the silent reading speed adjustable in some tools but fixed here?
The 238 WPM and 150 WPM constants are baked in to keep the comparison meaningful — your readers vary widely (children read 80-150 WPM, teens 200-220 WPM, college students 300+ WPM, slow readers under 150 WPM), and there is no way for the tool to know your specific audience. For audience-specific estimates, take the word count from the middle tile and divide by your target group's average. A 1,200-word article reads in 6 minutes for a college audience (200 WPM) but 8 minutes for a general audience aged 50+ (150 WPM).
Does the calculator handle different content types?
It uses one universal speed regardless of content. In practice, technical documentation, legal text, and scientific writing read slower (150-200 WPM) due to specialized vocabulary and dense logic; light fiction and casual blog posts read faster (300+ WPM) because the brain predicts upcoming words. For a technical article, mentally add 25-30% to the displayed estimate. For a casual blog post on familiar topics, the estimate is usually accurate or slightly conservative.
What about skimming vs deep reading?
Skimming runs 400 to 700 WPM and gets you the gist with about 50-60% comprehension — fine for deciding whether to commit to a full read. Deep reading runs 100 to 200 WPM with 80-90% comprehension and is the realistic pace for technical material, contracts, and study text. Standard reading at 200-250 WPM gives roughly 70% comprehension. Speed reading courses claim to push 1,000+ WPM, but rigorous research shows comprehension collapses past about 500 WPM and the effect is closer to selective skimming than true reading.
How accurate is the speaking time estimate for video scripts?
The 150 WPM baseline matches polished broadcast and presentation pacing — TED Talks, audiobooks, news anchors all sit between 140 and 170 WPM. Casual conversation runs faster (180-200 WPM). YouTube creators average 150-180 WPM depending on style. For a tightly-edited explainer video, 150 WPM is accurate. For a loose vlog, expect to deliver 10-15% faster. Rehearsal will tell you your personal natural pace; record yourself reading a 100-word sample and time it.
Should I trust the estimate for non-English content?
Roughly. The 238 WPM figure is based on English research and translates poorly to languages with very different word definitions — German has long compound words that pack more meaning per token, and Mandarin uses characters rather than space-separated words. For Spanish, French, German, and Italian the estimate is reasonable; for non-Latin scripts it is unreliable. The character count (visible in the Word Counter tool) is a more universal metric across languages.
Part of ToolFluency’s library of free online tools for Productivity. No account needed, no data leaves your device.