ToolsHub4u

Estimate how long your text takes to read

Paste a script, an article or a talk and see how long it takes to read, to say aloud and to skim. Three speeds drive the estimate, and all of them are yours to change.

  • Read, speak and skim
  • Adjustable speeds
  • Updates as you type
Ready Text & Writing
Estimates, not measurementsA 1,000-word page takes five minutes at 200 words per minute. Dense technical text is slower, and a familiar topic is faster.
1Enter
2Adjust
3Copy result

Reading Time Calculator

1

Text and speeds

Nothing is uploaded. The estimate is words divided by your chosen speed.

Show time for
wpm
wpm
wpm
No text yet Live
2

Time estimate

Reading time

20 sec

At 200 words per minute

Reading time at other speeds
SpeedRead timeWith 20% thinking time
150 wpm27 sec32 sec
200 wpm20 sec24 sec
250 wpm16 sec19 sec
300 wpm13 sec16 sec
Words
67
Reading
20 sec
Speaking
31 sec
Skimming
9 sec
Sentences
5
Minutes (read)
0.3

The estimate is words divided by speed. It does not include time to look at images, follow links or re-read a difficult paragraph.

If readers must understand rather than scan, add time for reflection. A five-minute read can take fifteen minutes to work through with notes.

Paste a draft and it reports three times: how long it takes to read silently, to read aloud, and to skim. The sample that loads with the page is 67 words in 5 sentences, which comes out at 20 seconds to read at 200 words per minute, 31 seconds to speak at 130, and 9 seconds to skim at 450.

Those three speeds are the whole tool. Everything else — the table, the stats, the warning — is arithmetic on top of them, which is why they are editable.

The formula

seconds = words ÷ words per minute × 60

Take 1,000 words at the default 200 words per minute: 1,000 ÷ 200 = 5 minutes. At 130 words per minute it is 7 minutes 42 seconds to read aloud, and at 450 it is 2 minutes 13 seconds to skim. The table below the result does the same sum at 150, 200, 250 and 300 words per minute, and repeats each with 20% added as thinking time.

Reading time for 1,000 words at four speeds, with and without 20% thinking time
Speed1,000 wordsWith 20% thinking time
150 wpm6 min 40 sec8 min
200 wpm5 min6 min
250 wpm4 min4 min 48 sec
300 wpm3 min 20 sec4 min

All of those figures come from this page's own calculation, not from a separate estimate. You can reproduce any of them by pasting 1,000 words and changing the speed field.

Choosing a speed that means something

The defaults are starting points, and they should be replaced with your own measurement if the number matters. The method is in the sample text: read a page you already know, time yourself, count the words, divide words by minutes. That gives a rate for your material rather than for a generic reader.

For context, the largest review of reading-rate studies — Brysbaert's 2019 meta-analysis in the Journal of Memory and Language — puts silent reading of English non-fiction at about 238 words per minute, with fiction slightly faster. The 200 default is deliberately conservative, which suits technical or unfamiliar material.

Speaking is slower because pauses are part of delivery. Presentation guidance commonly lands between 130 and 150 words per minute, and the 130 default sits at the careful end of that. Skimming is faster and harder to define; 450 is roughly double the reading rate, which is a reasonable pace for scanning headings and first sentences rather than reading every word.

The speed fields accept a range — 50 to 600 for reading, 50 to 400 for speaking, 100 to 1,200 for skimming — and the buttons above the result switch which of the three becomes the headline number. The other two stay in the stats row, so you can compare without changing anything.

What the numbers round to

Times are rounded to whole seconds, and minutes are shown to one decimal place. That produces a few edges: a single word at 150 words per minute reports 0 sec, and a 67-word text reports 0.3 minutes because 20 seconds is a third of a minute. Nothing is wrong with the arithmetic; it is display rounding on very short texts.

For anything under about 100 words the seconds figure is more useful than the minutes figure. For a report or a script, the minutes figure is what you quote.

What the estimate leaves out

The note under the result is honest about the main gap: the calculation counts words and nothing else. It does not add time for looking at images, following links, reading a table, re-reading a difficult paragraph, or stopping to take notes.

The reflection warning appears on every result, including a ten-word test, because it is a fixed message rather than a conditional one. Read it as a standing caveat: if a reader has to understand the text rather than scan it, the estimate is a floor, not a total. A five-minute read can take fifteen minutes to work through with a notebook open.

Three specific cases where the estimate runs short:

  • Code and tables. A code block counts as words, but reading code is much slower than reading prose.
  • Dense argument. Philosophy, law and maths are read at a fraction of 200 words per minute.
  • Non-native readers. Reading speed in a second language is typically lower, sometimes by half.

Where the number is actually useful

A video script, a conference talk and a podcast segment are all timed in minutes, and all three are spoken. Switch to speaking mode before you quote a length. A 1,200-word script is 9 minutes 14 seconds at 130 words per minute, which is over the usual 8-minute slot; at 150 it is 8 minutes, which fits.

For a blog post, the reading figure is the one readers see quoted at the top of an article. It is worth knowing that those labels are almost always calculated at 200 to 250 words per minute on the word count alone, so they are as rough as this tool. Paste your own text here rather than trusting a plugin's badge.

Limits

  • No per-section timing. One total for the whole paste, not a breakdown by heading.
  • No saved presets. Changing the speed is not remembered between visits.
  • Word counting rules apply. Hyphenated compounds count as separate words, so a hyphen-heavy draft reads slightly longer here than in Word.
  • Text stays in the tab. Nothing is uploaded and a reload clears the box.

Time one page of your own writing once. After that the defaults are guesswork you no longer need.

Questions

Common questions

Short answers to what people ask before using this tool.

How is reading time calculated?

Words divided by your reading speed, multiplied by 60 to get seconds. At the default 200 words per minute, 1,000 words is 5 minutes. The same sum runs for speaking and skimming with their own speeds.

What is a normal reading speed?

Around 238 words per minute for silent reading of English non-fiction, according to Brysbaert's 2019 meta-analysis. Fiction is a little faster. The 200 default here is deliberately conservative, and technical material is slower still.

How fast do people speak?

Presentation guidance usually lands between 130 and 150 words per minute. This tool defaults to 130, which allows for pauses. A script read at 130 will run longer than the same script read at 150.

Why does a short text show 0 minutes?

Because minutes are rounded to one decimal place. A 20-second read is 0.3 minutes, and anything under about three seconds rounds to 0. The seconds figure is the one to use for short texts.

Does it include images and links?

No. Only words in the box are counted. Time spent looking at a chart, following a link or re-reading a paragraph is not included, so treat the result as a floor for anything that has to be understood rather than scanned.

What is the 20% thinking time column?

Each speed is repeated with 20% added, to stand in for pauses, notes and re-reading. It is a single multiplier, not a model of comprehension — 1,000 words at 200 wpm becomes 6 minutes instead of 5.

Can I time a speech or a video script?

Yes — switch to speaking mode. A 1,200-word script is 9 minutes 14 seconds at 130 words per minute and 8 minutes at 150. Set the speed to the pace you actually deliver at, not the default.

Is my text uploaded?

No. The calculation runs in the browser tab and nothing is stored. Reloading the page clears the text.