Reading Time Calculator

Reading Time Estimates: A Small Feature With Outsized Impact

Medium introduced the per-article reading time estimate in 2013, and the feature produced a measurable improvement in reader engagement. The logic was simple: readers who knew approximately how long an article would take were more likely to start reading it (if the time seemed manageable), more likely to bookmark it for later (if the time seemed too long right now), and less likely to abandon it mid-read (having committed to the time investment upfront). Since then, reading time estimates have become standard practice across publishing platforms, news sites, and content-heavy products.

The estimate has a secondary benefit for the publisher: it signals content depth. A "12 min read" implies substantive coverage. A "2 min read" is digestible but signals brevity. Publishers use reading time to set reader expectations and to signal where an article fits in the editorial register — quick news brief or long-form analysis. This calculator gives you that estimate before publishing, so you can calibrate both the label and the content length to match the type of content you're producing.

The Science Behind the 200–250 WPM Standard

The reading speed used in most published reading time estimates — around 200–250 words per minute — comes from decades of reading research. Adult silent reading speed for comprehension (as opposed to skimming) has been consistently measured in the 200–300 WPM range across studies since the 1940s. The lower end (200 WPM) reflects careful reading of complex material. The middle range (220–240 WPM) reflects comfortable reading of well-written prose. The upper end (280–300 WPM) reflects fast reading of familiar material.

Skimming speed — which readers often use for web content they're evaluating rather than reading in depth — can reach 600–700 WPM for experienced readers. Speed reading claims of 1,000+ WPM are contested; research suggests that above approximately 350 WPM, comprehension drops significantly for most readers unless the material is already very familiar. The 220 WPM baseline used here is conservative and appropriate for the typical web reading context.

Adjusting for Content Type and Audience

The default reading speed assumption isn't equally valid across all content types. Technical documentation is read slower — developers carefully read code examples, stop to try things, re-read specification language. A 2,000-word technical tutorial takes longer to read than a 2,000-word narrative article, because reading and doing interleave. Adjust the WPM slider downward for technical content to account for this slower consumption rate.

Academic papers are often read even more slowly because readers evaluate claims, check references, and consider counterarguments rather than simply consuming information. News articles are typically read faster than average because the structure (inverted pyramid, simple vocabulary, short paragraphs) is optimised for quick scanning. Children's content is read significantly slower by the target audience — a 500-word children's article is not a "2 minute read" for a 7-year-old learning to read.

Speech and Podcast Script Timing

Reading time estimates also apply to spoken content: the time to speak a script aloud is approximately the word count divided by speaking speed (typically 120–160 WPM for clear, deliberate speech). A conference presentation needs to fill exactly 20 minutes. A podcast segment should run 5–7 minutes. A video script needs to match a target runtime. Knowing that 130 WPM is a reasonable baseline for formal speech — slower than reading, allowing for emphasis and pauses — lets you calculate the script length needed for a target duration, or conversely, how long a written script will run when delivered.

The Word Counter provides a speaking time estimate alongside the reading time when you paste content there. Use both tools together if you need both written and spoken consumption time estimates for the same piece of content.

Blog Post Length and Reading Time Benchmarks

Published research on blog content and engagement provides useful benchmarks for calibrating reading time targets. Orbit Media's annual blogger survey consistently finds that blog posts averaging 1,500–2,500 words (approximately 7–11 minutes reading time) receive the highest reader engagement and the most search traffic. HubSpot's data suggests 2,100–2,400 words is the sweet spot for SEO-oriented blog posts. For email newsletters, 200–300 words (under 2 minutes) maintains better read-through rates.

These are statistical averages, not universal rules — the right length for any given piece of content is the length needed to cover the topic thoroughly without padding. But if you're targeting a specific reading time for strategic reasons (a newsletter slot, a specific content tier), these benchmarks give you the word count targets to aim for. Paste your draft here to see where you are against those targets.

Educational Content and Student Reading Time

Teachers and curriculum designers use reading time estimates to gauge assignment load. A homework reading assignment of 35 minutes is appropriate for middle school students; the same content might take only 20 minutes for advanced high school readers. Knowing the word count and estimating at the appropriate grade-level reading speed allows teachers to calibrate assignments to a target time investment without having to time every student manually.

Online course creators similarly need to calibrate reading material length to fit within lesson time budgets. A 10-minute online lesson that includes 3 minutes of video and 7 minutes of reading needs approximately 1,400 words of text (at 200 WPM) to fill the reading time budget. This calculator makes that arithmetic immediate rather than manual.

Reading Speed Variability and Honest Estimates

No reading time estimate is accurate for every reader. Reading speed varies with: the reader's familiarity with the subject matter, the vocabulary complexity of the text, the sentence structure and paragraph density, the reader's cognitive load at the time of reading, and whether they're reading on a phone screen (typically slower) or a desktop (typically faster due to larger text and wider line measure). The estimate produced here is a useful average, not a precise prediction. Publishing it as "approximately X minutes" rather than a precise number is more honest about this variability — and most publishing platforms display ranges ("3–4 min read") rather than exact times for this reason.

✓Verified by ToollyX Team · Last updated June 2026