⏳ Reading Time Calculator
Paste your text to estimate how long it takes to read silently or read aloud, based on word count and an adjustable words-per-minute rate.
How the estimate is worked out
The tool counts the words in your text and divides by a words-per-minute rate. Two rates are used, because reading silently and reading aloud are not the same job:
| Rate | Default | Used for |
|---|---|---|
| Reading | 200 wpm | Silent reading of ordinary prose |
| Speaking | 130 wpm | Reading aloud — presentations, scripts, voiceover |
Both boxes are editable, and anything between 50 and 1000 wpm is accepted. Change them and the answer updates against your own pace rather than an average.
Choosing a realistic rate
200 wpm is a fair default for an adult reading general text on a screen. It is not a universal figure, and the gap between contexts is wide enough to matter:
- 150–180 wpm — dense or technical material, or reading in a second language.
- 200–250 wpm — articles, blog posts, most non-fiction.
- 250–300 wpm — familiar, light material being skimmed rather than studied.
- 100–130 wpm — reading aloud at a pace an audience can follow.
Speaking time is the one people get wrong
A common mistake is sizing a talk with a reading rate. At 200 wpm a 2,000-word script looks like ten minutes; delivered aloud at 130 wpm it runs past fifteen, before any pause, question or slide change.
For a spoken piece, take the speaking figure and add roughly 10–15% for pauses. Rehearsed talks tend to land slower than the estimate, not faster.
What the word count does not capture
Word count is a good proxy and a poor measure of effort. The same 1,000 words take very different amounts of time depending on what they contain:
- Code blocks, tables and formulae are read far more slowly than prose, and are often re-read.
- Images and diagrams add time the word count knows nothing about.
- Reference material is scanned, not read start to finish, so the estimate overstates it.
Treat the number as a floor for straightforward prose, and add your own margin for anything denser.
Frequently asked questions
What reading speed should I use for a blog post?
200 words per minute is the usual figure and matches what most "x min read" labels on publishing platforms assume. If your audience is reading technical material, 150 to 180 is closer.
How long does a 1,000-word article take to read?
About five minutes silently at 200 wpm. Read aloud at 130 wpm the same text runs closer to seven and a half minutes.
How many words should a 10-minute presentation be?
Around 1,300 words at a 130 wpm speaking pace, and less if you want room to pause or take questions. Aiming at 1,100 to 1,200 leaves that room without rushing.
Is my text sent anywhere?
No. The counting and the arithmetic happen in your browser, so the text never leaves the page.
Does it count words the same way as my word processor?
Close, but not always identical. Whitespace-separated runs are counted as words, so hyphenated compounds and numbers with units can be split or joined differently from Word or Google Docs. The difference is normally under a percent and does not change the estimate.