Reading Time Calculator

How to Use the Reading Time Calculator

1. Paste or type any passage into the input area — a blog post, video script, conference talk, audiobook chapter, or marketing email.
2. Pick an audience preset that matches your readers — Slow, Average adult, Blog reader, Speed reader, Audiobook, or Spoken / presentation.
3. Or drag the words-per-minute slider to model any custom audience between 50 and 1000 wpm.
4. The headline reading time updates instantly as you type or change the speed.
5. Scroll to the "Reading time across audiences" grid to see how the same text reads for every audience side by side — useful for quoting a realistic range in your CMS or video description.

What Reading Speed Should You Use?

Reading speed varies far more by audience and content type than most people realise. A 2019 meta-analysis by Marc Brysbaert (Journal of Memory and Language) covering 190 studies and more than 17,000 readers found that silent reading of non-fiction English averages 238 words per minute, while fiction is slightly higher at around 260 wpm. Web content is typically skimmed and is usually estimated at 265 wpm — the figure used by Medium, Pocket, and most popular reading-time plugins. Audiobook narrators speak more slowly at roughly 150–160 wpm, and public speakers at 130 wpm.

Reading Time Formula

The reading time calculation is intentionally simple — and that simplicity is why it is the standard across CMS plugins and content management systems:

• Reading time (seconds) = (words ÷ words-per-minute) × 60
• Reading time (minutes) = words ÷ words-per-minute

The hard part is choosing a defensible WPM. Pick the slowest realistic audience for compliance-style estimates (e.g. healthcare content for an average reader) and a middle figure for blog "x min read" labels. Showing both a quick-read and a careful-read estimate is a useful pattern for documentation and tutorials.

When to Use This Calculator

• Blog "x min read" badges — use the Blog reader preset (265 wpm) to match what readers expect from Medium-style sites.
• YouTube video and podcast scripts — use the Spoken / presentation preset (130 wpm) to estimate runtime before recording.
• Audiobook narration planning — Audiobook (1×) at 160 wpm gives a realistic unabridged runtime; trim if you target audiobook chapters under a target length.
• Conference talks and keynotes — a 20-minute slot at 130 wpm is roughly 2,600 words. Drag the slider down to 110 wpm if you want pauses, emphasis, and audience laughter built in.
• Email and newsletter previews — quoting reading time at the top boosts open-to-read rates; use 238 wpm for non-fiction newsletters.
• SEO planning — search-engine "dwell time" correlates loosely with content length; a reading-time figure helps you size pillar posts versus quick-take articles.
• Tutorial / documentation tagging — show both a quick-read and a careful-read figure so learners self-select.

Reading Time vs. Listening Time

Listening is consistently slower than reading because the ear can't skim. A 1,500-word article that an adult reader finishes in about 6 minutes takes roughly 11–12 minutes as an audiobook and 13 minutes as a podcast. If you produce both written and audio versions of the same content, quote both numbers — your audience will pick the format that fits their commute, gym session, or coffee break.

Tips for Quoting Reading Time Honestly

• Round up, not down — a 4 min 35 sec read should be shown as "5 min read", not "4".
• Use the slowest reasonable speed for healthcare, legal, and accessibility-critical content.
• Quote a range ("4–6 min read") for technical tutorials where comprehension matters more than throughput.
• Strip code blocks before measuring — most readers skim or skip them, which inflates the word count unrealistically.
• For multilingual sites, set the WPM per language — Chinese reading is measured in characters per minute, typically 250–350 cpm for adults.