Reading Time Calculator

What does the Reading Time Calculator do?

The Reading Time Calculator tells you how long a piece of writing will take to read. Paste in your draft — a blog post, an article, a script, a chapter, a newsletter, anything — and the tool reports an estimated reading time based on average reading speed.

Paste in a 1,500-word blog post and you'll see "about 6 minutes" at the default speed of 250 words per minute. Drop the speed to 150 for a careful reader, or push it to 400 for a fast scanner, and the estimate updates instantly. There's no signup, no upload, and your text never leaves your browser.

The math is simple: total words divided by reading speed equals minutes. The reason this gets its own tool instead of a sticky note is that the inputs matter more than the math. Who is reading affects the answer. Whether they're reading silently or out loud changes it. Whether the text is plain prose or dense technical material changes it again. The calculator handles all three.

Why reading time matters

If you've ever clicked on an article and immediately wondered "how long is this going to take?" — you already know why. A reading-time estimate at the top of a blog post is one of the simplest reader-friendly things a site can do. It sets expectations. It lets people decide whether to read now or save for later. It cuts bounce rates, because readers who know what they're committing to are more likely to actually commit.

Medium pioneered this in 2015. Now you see it on The New Yorker, on The Verge, on every Substack newsletter, on most news sites. The reason it caught on is that it works: post-Medium A/B tests showed that adding a reading-time label increased read-through rates by double digits on long-form posts.

Plenty of other contexts need the same number:

• Bloggers and writers — labeling posts so readers know what they're getting into
• Newsletter authors — keeping issues to a target length ("a 5-minute weekly read")
• Speech writers and presenters — translating a script into actual stage minutes
• Podcasters and YouTubers — estimating script length before recording
• Students — figuring out how long it will take to read tonight's assigned chapter
• Editors — sanity-checking length against a brief ("this should run 4 to 6 minutes")
• UX writers — estimating how long users will spend on an in-app help article
• Marketers — predicting attention time on ad copy, landing pages, and case studies

The number isn't precise to the second. It's an estimate. But it's a useful one — and a calibrated estimate beats no estimate every time.

How the math works

The formula is:

Default words per minute (WPM) for silent reading is 250 — the consensus average across the major studies (Brysbaert 2019, summarizing data from over 17,000 readers). Some tools use 200, some use 265; 250 is the middle of the published range and works as a reasonable default for adult non-fiction. The calculator lets you change it.

If the result is under one minute, the calculator switches to seconds. Over an hour, it switches to "1h 23m" format. Round numbers are rounded — "5.7 minutes" displays as "about 6 minutes," because nobody plans their day in fractional minutes.

A worked example

Take a 1,500-word blog post — a common length for SEO-targeted articles. Run the numbers at three different speeds:

• Slow / careful reader (150 WPM): 1,500 ÷ 150 = 10 minutes
• Average reader (250 WPM): 1,500 ÷ 250 = 6 minutes
• Fast scanner (400 WPM): 1,500 ÷ 400 ≈ 3.75 minutes

The same article is a "10-minute read" or a "4-minute read" depending entirely on who's reading. That's why a one-size-fits-all label can be misleading — but it's also why a label of any kind helps: it gives readers a reference point.

For comparison, take a 280-word newsletter intro at the default 250 WPM: 280 ÷ 250 ≈ 1.1 minutes. The calculator shows "about 1 minute." Take a 50,000-word novella: 50,000 ÷ 250 = 200 minutes, or "3h 20m" — about the length of a long flight. Take a 12,000-word academic paper at a careful 150 WPM (because academic prose demands it): 80 minutes, or "1h 20m" — roughly a real evening of work.

Reading speeds by audience

Not every audience reads at the same pace. The literature on reading speed is surprisingly large — these are the averages that come up most often:

A few patterns worth noticing. Adult silent reading clusters tightly around 240-260 WPM regardless of education level — what differs is comprehension at that speed, not the speed itself. Reading aloud is much slower than reading silently, because the mouth becomes the bottleneck. And "speed reading" past 700 WPM almost always means trading comprehension for speed; the research on that has been consistent for fifty years.

Audio versus visual reading

If you're writing something that will be heard, not read, the math changes. Audiobooks are typically narrated at 150-160 WPM at 1x speed. A typical podcast host speaks at 150-180 WPM. Public speakers reading from notes average 120-150 WPM, slower than narration because they pause for emphasis.

The Reading Time Calculator handles both — set the WPM to 150 for narration, 130 for stage delivery, and the estimate updates accordingly. If you're writing a 15-minute conference talk, target around 1,950-2,250 words of script. If you're writing for an audiobook chapter that should run 30 minutes, target around 4,500-4,800 words. Going much beyond those numbers means cutting in rehearsal — usually painfully.

What changes the number besides speed

Three things bend reading time in ways the basic word count can't capture:

• Difficulty. Dense prose, technical material, and unfamiliar topics slow readers down by 30-50% versus easy material. If your text is at college reading level, drop the WPM to 180-200. If you're writing for general audiences at sixth-grade level, the default 250 holds. The Readability Checker measures this directly.
• Images, equations, and code blocks. Readers pause on these. A page with three diagrams reads slower than the same word count of plain prose. A rough adjustment: add 12 seconds per image, 30 seconds per equation, and 20 seconds per code block.
• Layout. Wide columns (over 75 characters) slow readers down because the eye has to track too far back to find the next line. Narrow columns (45-65 characters) hit the sweet spot. The same article in a phone-friendly layout reads faster than in a wide desktop layout.

How the calculator counts words

The word counter inside the Reading Time Calculator uses the same rules as the Word Counter: any sequence of non-whitespace characters counts as one word. Hyphenated compounds ("state-of-the-art") count as one. Numbers count as words. URLs count as one. That's consistent with how Microsoft Word and Google Docs count, give or take edge cases at boundaries.

If your draft has Markdown formatting, footnote markers, or pasted-from-PDF artifacts, those can inflate the count by a percent or two. Strip them first if you need a tight number — for a "about 6 minutes" label, it doesn't matter.

Privacy and how it runs

Everything runs in your browser using JavaScript. Your text is counted locally, divided by the WPM you pick, and rendered. No data is sent to any server, no analytics tracks your input, no AI service stores your draft. Close the tab and the text is gone from memory.

That makes the Reading Time Calculator safe for unpublished drafts, internal documents, confidential briefs, and anything else you wouldn't paste into a third-party tool. It's also why the calculator is instant: there's no server round-trip to wait for.

Related text tools

The Reading Time Calculator pairs naturally with the rest of the text-analysis family on Microapp:

• Word Counter — full breakdown of words, characters, sentences, paragraphs, and reading time in one paste.
• Readability Checker — measures Flesch-Kincaid grade level and Reading Ease, so you know how hard your text is, not just how long.
• Sentence Counter — counts sentences and computes average sentence length, useful for pacing.
• Character Counter — for tweets, bios, meta descriptions, and anything else with a character cap.
• Word Frequency Counter — shows your most-used words at a glance, helpful for spotting repetition.
• Case Converter — quickly switch case for headlines, slugs, and code variables.

Frequently asked questions

What words-per-minute should I use?

For general web writing, 250 WPM is the standard default. Use 200 for technical or academic material, 150 for spoken delivery (narration or reading aloud), and 300-330 for casual content like a recipe blog or magazine listicle. If you're not sure, leave it at 250 — that's what Medium, Pocket, and most major sites use.

Why does Medium say "5 min read" but your tool says 6 minutes for the same article?

Medium uses 265 WPM as its default and adds a 12-second adjustment per image. This calculator uses 250 WPM and doesn't auto-adjust for images. For a 1,500-word post the difference is usually one minute. Both are reasonable estimates — neither is "correct."

How accurate is the estimate?

For a single reader, the actual time can vary by ±40% depending on familiarity with the topic, fatigue, and reading conditions. For a population of readers, the average converges quickly: a "6 minute" label is correct (within a minute) for about 70% of adult readers on mainstream non-fiction. Tighter accuracy is impossible without knowing the specific reader.

Does the calculator work for languages other than English?

The word count works for any language that uses spaces between words — Spanish, French, German, Portuguese, Italian, and most European languages. The 250 WPM default is calibrated for English; reading speeds in other languages vary slightly (Spanish averages 218 WPM, Mandarin around 158 characters per minute), so adjust the WPM accordingly. For non-spaced languages like Chinese and Japanese, use characters per minute instead of words per minute.

Can I estimate speaking time, not just reading time?

Yes — set the WPM to 130-150 (the typical range for spoken delivery). For audiobook narration use 150-160, for a TED-style talk use 130, for a slower, more deliberate keynote use 110-120.

What's the longest text I can paste in?

There's no hard limit. The calculator runs in your browser and handles documents over a million words without slowdown. Full novels work fine. The reading time will switch from minutes to hours past the 60-minute mark.

Is my text stored anywhere?

No. Everything runs in your browser as JavaScript. Your text never reaches any Microapp server. Closing the tab clears it from memory permanently.