Reading Time Calculator

How to Use the Reading Time Calculator

Features

Why Reading Time Labels Improve Content Engagement

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 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.

This tool lets you generate the estimate before publishing — paste your draft, note the reading time, and add it to your post header. For deep analysis of word usage patterns and keyword density in the same article, the Word Frequency Counter runs the same text through a frequency analysis in a separate tab.

The psychology behind it is really about reducing uncertainty rather than the number itself being magical — an unlabelled article forces the reader to estimate the commitment themselves, which for a long piece often defaults to a pessimistic guess and a decision to skip it. A visible "6 min read" replaces that guess with a concrete number, and concrete numbers are easier to commit to than vague impressions of "this looks long."

Understanding Reading Speed Across Different Audiences

The 220 WPM default is calibrated for average adult comprehension reading of online content. But different content and different audiences justify different WPM settings. Children reading at grade 4 level (ages 9–10) read at approximately 140 WPM with comprehension. Non-native English speakers working in a second language often read at 150–180 WPM. Technical documentation, legal contracts, and medical text require slower processing — even skilled readers slow to 150–180 WPM when parsing dense technical language. Recreational fiction is often read at 250–300 WPM.

If you are writing content for a non-specialist audience — a general news article, a product description, or an FAQ — the default 220 WPM is appropriate. If you are writing for specialists (medical professionals, lawyers, software architects), their familiarity with the domain vocabulary means you can use a higher WPM setting (250–280) without overstating the reading time.

Screen reading also runs slightly slower than print reading for most people — studies comparing the two consistently find a modest speed penalty on screens, generally attributed to lower perceived urgency and more scanning behaviour rather than any technical limitation of displays. If your content is read primarily on mobile, where scanning behaviour is even more pronounced than on desktop, nudging the WPM setting down slightly from the 220 default reflects that more accurately than assuming print-reading speeds apply.

Speaking Time for Presentations, Speeches and Podcasts

The 130 WPM speaking speed default is calibrated for formal, measured public speaking — the pacing used by most TED Talk speakers, corporate keynote presenters, and trained public speakers. At this pace, a 10-minute presentation slot requires approximately 1,300 words of scripted content. A 20-minute conference talk needs about 2,600 words. A standard 45-minute keynote slot needs roughly 5,850 words of prepared material.

Podcast hosts and conversational narrators speak faster, typically at 150–175 WPM. If you are scripting a podcast or voiceover rather than a formal presentation, increase the speaking speed setting to 160 WPM for a more accurate estimate of your recording time.

Reading Time Targets by Content Type

Different content formats have different optimal reading times based on reader expectations and platform conventions. Short-form news articles and quick-answer pieces perform best at 1–3 minutes. Standard long-form blog posts targeting search traffic perform best at 5–8 minutes, which corresponds to about 1,100–1,700 words at 220 WPM. Comprehensive guides and pillar content for competitive search topics need 12–20 minutes (2,600–4,400 words) to provide the depth that both readers and search engines expect.

• LinkedIn article — 3–5 minutes (650–1,100 words)
• Email newsletter — 2–4 minutes (440–880 words)
• SEO blog post (competitive) — 8–12 minutes (1,760–2,640 words)
• Academic essay (undergrad) — 5–15 minutes (1,100–3,300 words)
• Conference paper — 20–40 minutes (4,400–8,800 words)

What a Word-Count Estimate Can't See

Every reading-time formula, including this one, is really just word count divided by a speed constant — which means it's blind to everything that isn't words. A 2,000-word tutorial packed with code blocks, screenshots, and diagrams takes noticeably longer to actually read than a 2,000-word opinion piece, because readers pause on images, re-read code examples, and process visual information at a completely different rate than prose. The word-count estimate treats both articles identically, even though one genuinely takes longer to get through.

Dense technical or legal content has the same blind spot in a different form — a contract clause or a mathematical proof often gets re-read two or three times before it's understood, which no word-count formula accounts for. Treat the number here as a reasonable floor for skimmable prose and add a rough buffer — 20-30% is a common rule of thumb — for anything with heavy visual or technical content mixed in.

Using Reading Time to Calibrate Content at Draft Stage

The most practical use of this tool is not calculating the final reading time — it is using the estimate during drafting to decide whether you need to expand or cut. Paste your draft, note the current reading time, and compare against your target. At 4 minutes aiming for 8 minutes, you need to double your content. At 15 minutes aiming for 8, you need to cut roughly half. The Word Counter gives the same word count alongside six other statistics if you need a fuller picture of the text's current state.

This works better as a running check throughout drafting than a single measurement at the end. Checking reading time every few hundred words while writing catches scope creep early — a piece that was tracking toward a tidy 6-minute read but has crept to 11 minutes by the halfway point is easier to rein in mid-draft than to cut down after the whole thing is finished and every section feels essential to its author.

Frequently Asked Questions