Reading Time Calculator: Formula, WPM and Word Table

November 11, 2026 · 10 min read

Reading Time Calculator: How Reading Time Is Estimated

A reading time calculator divides a text's word count by a reading speed in words per minute, then rounds the result to whole minutes. At 238 wpm, the average adult rate for non-fiction, 1,000 words take about 4 minutes. This guide covers the formula, where the speeds come from, and what to strip before counting.

The Reading Time Formula Behind Every Calculator

Every estimator runs the same one-line calculation. Count the words, divide by a words-per-minute (wpm) rate, and round. The only things that change between tools are the rate they assume and what they count as a word.

reading time (minutes) = word count / words per minute

1,500 words / 238 wpm = 6.3 minutes
6.3 rounded up        = "7 min read"

Most blogs show whole minutes, so 6.3 becomes 7. Some tools round to the nearest minute instead, which would show 6. Hugo, for example, returns its built-in estimate as a whole number of minutes. A few calculators also show seconds, which is useful when you're timing a speech but adds false precision to a blog label.

We prefer rounding up and showing whole minutes. A reader who budgets 7 minutes and finishes in 6 feels fine. A reader told 6 who needs 7 feels misled.

What's the Average Reading Speed?

The best evidence comes from Marc Brysbaert's 2019 meta-analysis in the Journal of Memory and Language, which pooled 190 studies and more than 18,000 participants. The paper puts the average silent reading rate for adults reading English at 238 wpm for non-fiction and 260 wpm for fiction. Reading aloud averages 183 wpm.

Brysbaert also found that the popular figures are too high. For non-fiction, most adults fall between 175 and 300 wpm. Rates drop for children, older adults and people reading in a second language.

That spread explains why tools disagree. Here are the defaults you'll meet most often:

SourceDefault speed
reading-time npm package200 wpm
Hugo's .ReadingTime212 wpm
Our reading time calculator225 wpm
Brysbaert 2019, non-fiction average238 wpm
Medium's help centerroughly 265 wpm

None of these numbers is wrong. A slower default suits technical writing, and a faster one suits light reading. Dense material such as API references or tutorials with commands reads well below the average, which is one reason Markdown documentation benefits from short sections.

How Long Does It Take to Read 1000 Words?

If you only need to know how long to read 1000 words, it's about 4 minutes 12 seconds of silent reading at 238 wpm. At a cautious 200 wpm, it's 5 minutes. Read aloud at a presentation pace of 140 wpm, the same text takes just over 7 minutes.

The table below uses those three rates. The 140 wpm column matches our calculator's default speaking speed.

WordsSilent, 238 wpmSilent, 200 wpmAloud, 140 wpm
3001 min 16 sec1 min 30 sec2 min 9 sec
6002 min 31 sec3 min4 min 17 sec
1,0004 min 12 sec5 min7 min 9 sec
1,5006 min 18 sec7 min 30 sec10 min 43 sec
2,0008 min 24 sec10 min14 min 17 sec
4,00016 min 48 sec20 min28 min 34 sec
5,00021 min 1 sec25 min35 min 43 sec

So a 300-word blog post is a one- or two-minute read. How long does it take to read 5000 words? Plan on 21 to 25 minutes in one sitting. If you'd rather use Brysbaert's oral rate of 183 wpm, 1,000 words read aloud take about 5 minutes 28 seconds.

Reading Aloud vs Silent Reading for Speeches and Talks

Speaking time is almost always longer than silent reading time. Your mouth is slower than your eyes, and a speaker pauses for breath, emphasis and slides. Brysbaert's 183 wpm is for people reading text aloud in a study, not for presenting to a room.

A common rule of thumb for presenters is 130 to 150 wpm, though no single study fixes it. At that pace, a 1,000-word speech runs between 6 minutes 40 seconds and 7 minutes 42 seconds. A 5-minute slot therefore holds roughly 650 to 750 words.

If you're writing a talk, time one real rehearsal and divide your word count by the minutes it took. That personal rate beats any default, and you can reuse it for every script after that.

What to Leave Out When You Calculate Reading Time

A raw word count treats everything between spaces as a word. In a Markdown file, that includes front matter, link URLs, image syntax and code. None of those are read like prose, so they inflate the estimate.

Here's a short section of a Markdown post:

---
title: Deploy a Static Site with Docker
date: 2026-11-02
tags: [docker, deployment]
---

## Build the image

Run the build from your project root, then check the
[Dockerfile reference](https://docs.docker.com/reference/dockerfile/) if a step fails.

![Terminal output after a successful docker build](https://example.com/img/build.png)

```bash
docker build -t my-site:latest .
docker run --rm -p 8080:80 my-site:latest
```

Open **localhost:8080** and you should see the home page.

Splitting that file on whitespace gives 63 words. The prose a reader actually reads (the heading and two sentences) is 28 words. The rest is front matter, a URL, image syntax with alt text, code and Markdown markers.

Before you paste a draft into an estimator, strip these:

  • Front matter: the YAML block between the --- lines never appears on the page.
  • URLs and image paths: readers see the link text, not the address.
  • Markdown markers: #, **, | and list dashes are symbols, but a naive split can count them as words.
  • Code blocks: count them separately. Readers either skip code or slow right down to study it, so prose rates don't fit.

Images go the other way. A reader pauses on a screenshot or chart, so some estimators add time for images. Hugo and the reading-time package don't, but Medium's help center describes its read time as word count at about 265 wpm with an adjustment for images.

Adding Article Reading Time to a Markdown Blog

Static site generators can calculate reading time at build time, so you never update it by hand. Three common approaches cover most Markdown blogs.

Hugo has a built-in page method. Put .ReadingTime inside double curly braces in a template and Hugo prints whole minutes at 212 wpm:

<span>{{ .ReadingTime }} min read</span>

Per the Hugo docs, pages containing Chinese, Japanese or Korean use 500 wpm instead when hasCJKLanguage is true in your site configuration.

Astro documents a reading time recipe built on a small Markdown plugin, with one version per Markdown processor. The remark version, for the unified() processor, installs reading-time, mdast-util-to-string and @astrojs/markdown-remark, then stores the result in each page's front matter:

import getReadingTime from "reading-time";
import { toString } from "mdast-util-to-string";

export function remarkReadingTime() {
  return function (tree, { data }) {
    const textOnPage = toString(tree);
    const readingTime = getReadingTime(textOnPage);
    data.astro.frontmatter.minutesRead = readingTime.text;
  };
}

A content collection page reads minutesRead from the remarkPluginFrontmatter that render() returns, while a Markdown layout reads it from Astro.props.frontmatter. Either way it shows a label such as "3 min read". The reading-time package defaults to 200 wpm and accepts a wordsPerMinute option if you want a different rate.

A hand-set field works on any platform that reads front matter. Calculate the value once and store it:

---
title: Deploy a Static Site with Docker
readingTime: 6
---

Your theme decides what to do with it. Our guide to Markdown front matter covers the YAML syntax and which fields each platform reads. On a long post, pair the estimate with a table of contents so readers can jump to the section they came for.

How Accurate Is a Reading Time Estimator?

An estimate is accurate for the average reader of average prose, and few readers are average. Brysbaert's own range for non-fiction runs from 175 to 300 wpm, so the same 1,500-word post takes one reader 5 minutes and another nearly 9.

Three things push real times away from the estimate:

  • Skimming. Many readers scan headings and stop early, so they finish well under the label.
  • Difficulty. Unfamiliar terms, formulas and dense paragraphs slow everyone down.
  • Language. Word counts don't transfer across languages, which is why Hugo and Medium switch rules for CJK text.

Treat the number as a budget, not a promise. It tells a reader whether a post is a two-minute skim or a twenty-minute session, and that's all it needs to do.

Checking a Draft With Our Reading Time Calculator

Paste your text into our reading time calculator and it shows both a reading time and a speaking time. It defaults to 225 wpm for reading and 140 wpm for speaking. You can pick a slower or faster speed to match your audience, and images in the text add time to the estimate.

It runs in your browser, and browser-based tools on our site have no daily limit. The limitation is the same one every estimator shares: it counts words and doesn't know how hard your text is. A page of dense formulas gets the same estimate as a page of chatty prose with the same word count.

If you write in the Markdown editor, its status bar shows a live word count. Divide it by your chosen wpm for a quick estimate while you draft.

A reading time calculator is a word count divided by a reading speed, rounded to whole minutes. Pick a rate that suits your readers, strip front matter, URLs and code before counting, and add a little time for images. For an instant estimate, paste your draft into our reading time calculator and compare silent and spoken times for the same text.