Reading Time Calculator – Estimate Read Time Instantly (Free)

How long will it take to read this text?

That’s the exact question this tool answers. Paste any block of text — an article draft, an email, a chapter, a speech — and the reading time calculator counts the words instantly, then divides by a reading speed you choose (225 words per minute by default, a widely cited average for adult silent reading of straightforward prose).

If you already know your word count and don’t want to paste the full text, switch to “Enter word count” mode and type the number directly — useful when you’re working from a manuscript, a CMS word-count field, or a brief that only states the total.

The result updates live as you type or adjust the reading speed slider, so you can immediately see how a faster or slower audience changes the estimate — handy when you’re writing for a general audience versus a specialist one.

Average reading speed by content type

225 words per minute is a reasonable default, but real reading speed varies more than most people expect:

If you’re writing for a technical audience working through documentation, 225 wpm will make your reading time estimate look shorter than it actually feels — drop the reading speed calculator down to 175 or 150 wpm for a more honest number. If you’re writing punchy, easy-to-skim blog content, you can reasonably push it up to 275–300.

Why blogs and articles show estimated reading time

The “X min read” label you see at the top of most blog posts isn’t decorative — it measurably affects behavior. Readers use it to decide whether to commit now, save the article for later, or skip it entirely, especially on mobile where scrolling to gauge length is awkward.

An accurate reading time estimate can reduce bounce rate on long-form content, because it sets the right expectation before someone starts reading rather than mid-way through. A number that’s obviously wrong — showing “2 min read” on a 3,000-word article — does the opposite: it erodes trust in the rest of the page.

That’s the main reason this reading time calculator exists as a standalone tool rather than a fixed plugin setting: it lets you sanity-check the number before you publish, using the actual reading speed your audience is likely to have, not a platform default.

Reading time vs. speaking time

These two numbers are often confused, and they’re not interchangeable. Reading time (what this tool calculates) is based on silent reading speed — roughly 200–300 words per minute for most adults. Speaking time is based on comfortable spoken pace, which is much slower: around 130–150 words per minute for a clear, well-paced presentation or video script.

If you’re estimating how long a video, podcast script or speech will run, don’t use this tool’s default 225 wpm setting — drop it down to 130–150 wpm instead, which is exactly what the reading speed calculator’s slider is for. Using a silent-reading speed to estimate spoken content is one of the most common reasons a “5-minute video script” turns into an 8-minute video.

Words to reading time converter — how the math works

The formula behind every words to reading time converter, including this one, is simple: reading time = word count ÷ words per minute. A 900-word article at 225 wpm comes out to exactly 4 minutes; the same article at 150 wpm — a slower, more technical reading speed — comes out to 6 minutes.

This tool rounds to the nearest whole minute for anything over a minute, and shows seconds instead for very short pieces, rather than a confusing “0 min” — a 40-second read reported as zero looks like a bug, not a helpful estimate.

One nuance worth knowing: word count alone isn’t a perfect proxy for reading difficulty. A 500-word passage full of long technical terms and dense sentences takes longer to read than a 500-word passage of short, simple sentences, even at the identical words-per-minute setting. The estimate is a very good guide, not a physics law — use the reading speed slider to compensate when you know your content skews technical or simple.

Tips for a more accurate reading time estimate

A few adjustments make this tool’s estimate more useful for your specific situation. Match the reading speed to your actual audience, not a generic default — a developer documentation site and a lifestyle blog shouldn’t use the same words-per-minute setting.

Exclude boilerplate you don’t want counted, like a recurring newsletter signup block or a long list of related-post links, by pasting only the body content rather than the whole rendered page. Round conservatively rather than optimistically — readers forgive a “6 min read” that takes five minutes more than they forgive a “3 min read” that takes eight.

And if your content includes large images, embedded videos, or code blocks that readers pause on, add roughly 10–12 seconds per image as a rough manual adjustment, since this calculator — like virtually all reading time tools — only counts words in the text itself.

Finally, if you’re publishing across multiple platforms — your own blog, Medium, LinkedIn articles — recalculate for each one rather than reusing a single number. Fonts, line spacing and mobile rendering all change how long a page “looks,” which subtly affects how a reader perceives the stated reading time even when the underlying word count hasn’t changed at all.

Common questions