Reading Time and Words per Minute
A reading-time estimate answers a planning question: roughly how long will this text take someone to read? On WordCntr.com the answer is one division — the word count divided by 238 words per minute — and everything the reading time calculator shows follows from it. This guide explains where the rate comes from and what a population average can and cannot say, how the word count is found, how the result is rounded into the label you see, and when to round that label up or down. Every figure below was computed at build time by the engine that runs the tools, not typed in by hand.
The formula: word count divided by a rate
The engine computes reading minutes as words ÷ 238. Nothing else enters: not sentence length, not vocabulary, not paragraph breaks. Two texts with the same word count receive the same reading time whatever they say. The estimate is therefore linear — every word costs the same 0.25 seconds, so doubling the words doubles the time — and the only lever that moves it is the count.
A short original paragraph shows the arithmetic end to end. Take this text: "The night bus leaves the depot at ten past eleven and stops at every shelter along the river road. Most evenings the driver waits an extra minute at the hospital stop for the late shift, then takes the bridge rather than the tunnel because the tunnel closes for cleaning after midnight. The last passengers usually get off near the market, where the bakery has already started its ovens." The engine finds 68 words in 3 sentences. Divided by 238, that is 0.286 minutes, or 17.14 seconds before rounding, displayed as "17 sec". The sentence count was reported alongside but played no part; the word count alone did.
Where 238 words per minute comes from
238 words per minute is the average adult silent-reading rate for non-fiction in Brysbaert's 2019 meta-analysis of reading-rate studies — a meta-analysis being a study that pools the measurements of many separate studies into one estimate. The site uses it because it is the most defensible single published figure, not because any individual reads at exactly that speed. Three words in that description carry the weight. Adult: the pooled studies measured adult readers. Silent: the figure describes reading to oneself, not aloud — the engine keeps a separate and slower constant, 150 wpm, for speaking time. Average: the figure sits in the middle of a wide range, with real readers on both sides of it. The engine applies the one rate to every text and reader, because it has no information about either.
Read the result as "a typical adult reading silently would take about this long", never as "you will take this long". An average describes a population; it is neither a measurement of an individual nor a target, and this guide offers no adjusted rates for particular readers or kinds of text, because any such adjustment would be a guess laid on top of a published figure.
The word count is the only input
Because the word count is the only input, every convention of the word counter passes straight through to the reading time. The rule, set out in full in what counts as a word, treats a word as an unbroken run of letters, digits, apostrophes, and hyphens: "it's" and "state-of-the-art" are one word each, "2026" is a word, and "3.14" is two words because the period splits the run. A pasted address such as https://example.com/guide/counting contributes five tokens, because colons, slashes, and dots all separate.
The methodology page's own example makes the smallest case concrete. "Dr. Smith arrived at 9 a.m. She left early." is 10 words — "a.m." splits at its periods into two tokens — and 10 divided by 238 comes to 2.52 seconds, which the display shows as "under 5 sec". The over-counted sentence total (3 rather than the human answer of two, because "Dr." triggers the sentence rule) has no effect on the time at all.
Figures and links push the other way, and a release note shows how far. "Version 2.3.1 fixes the export bug reported at https://example.com/issues/418 and the 0.5 second delay described at https://example.com/issues/422, while version 2.4.0 adds the settings page documented at https://example.com/guide/settings." Counting each address and each version number or decimal as one item, the note has 27 words. The engine finds 44 tokens, because each address splits into five and each figure into its digit groups, and it charges every fragment the same 0.25 seconds as "fixes" or "adds". The display reads "11 sec"; counted as a reader takes it in, the same note would show "7 sec".
How the estimate is rounded and displayed
The formula returns minutes as a decimal; the display rounds that to the nearest whole second and then picks a format. A total of zero shows "0 sec" — an empty box, but also a single word, whose 0.25 seconds round away to nothing. A positive total too small to state honestly shows "under 5 sec" rather than a figure with false precision; the methodology sentence lands there. Under a minute the display shows seconds only, as the bus paragraph's "17 sec" does. At an exact number of minutes it shows minutes only: exactly 238 words divide to 1 minute and show "1 min". Otherwise it shows both, as 1,000 words do with "4 min 12 sec".
Rounding produces two effects worth knowing. The first is a threshold. 17 words come to 4.29 seconds and show "under 5 sec", but 18 words come to 4.54 seconds, round up to 5, and show "5 sec" — one added word changes the label. The second is a stray second on long texts: 5,000 words come to 1260.504 seconds, which rounds to 1261, so the display reads "21 min 1 sec". That second is the remainder of a division, not a measurement of anything.
Reading time for common word counts
The table answers the question most people arrive with — how long does a text of a given length take? Each row was produced by dividing the word count by 238 and passing the result through the engine's formatting function, the same calls the reading time calculator makes on your text. The speaking column divides the same count by 150, the constant explained in the guide on speaking time and speech length.
| Words | Reading time (238 wpm) | Speaking time (150 wpm) |
|---|---|---|
| 100 | 25 sec | 40 sec |
| 250 | 1 min 3 sec | 1 min 40 sec |
| 500 | 2 min 6 sec | 3 min 20 sec |
| 750 | 3 min 9 sec | 5 min |
| 1,000 | 4 min 12 sec | 6 min 40 sec |
| 1,500 | 6 min 18 sec | 10 min |
| 2,000 | 8 min 24 sec | 13 min 20 sec |
| 3,000 | 12 min 36 sec | 20 min |
| 5,000 | 21 min 1 sec | 33 min 20 sec |
| 10,000 | 42 min 1 sec | 66 min 40 sec |
Read the rows as a scale, not as targets: the table says nothing about how long a text should be, only what the formula returns for a given count. Between rows the relationship is linear, so a count halfway between two rows takes halfway between their times.
How many words fit in a given reading time
Planning often runs the other way: a slot of known length, and a question of how many words it holds. Invert the formula — words = minutes × 238. The last column is a check: each word count was fed back through the engine, and the display it produces is shown exactly as the engine formats it.
| Reading time | Words (minutes × 238) | Engine display for that count |
|---|---|---|
| 1 min | 238 | 1 min |
| 2 min | 476 | 2 min |
| 3 min | 714 | 3 min |
| 5 min | 1,190 | 5 min |
| 10 min | 2,380 | 10 min |
| 15 min | 3,570 | 15 min |
| 30 min | 7,140 | 30 min |
The check matters because the display rounds to the nearest second, so a whole-minute label is a band, not a point: every count from 237 to 239 words shows "1 min", 3 words in all, and a count outside it shows minutes and seconds.
When to round down, and when to round up
The reading time calculator shows the estimate to the second; what to do with it is a judgement, and the mechanism above says which way to lean.
Round down for text dense with addresses, code, version numbers, or decimals. The release note is the pattern: 44 tokens for 27 items a reader takes in, so the display overstates the time by 4 seconds on one paragraph and by proportionally more on a long changelog. Round down, too, when the pasted text carries material nobody reads through — headings, captions, footers, a reference list, an email's boilerplate. The estimate covers everything pasted; trim to what will actually be read, or accept that it covers the whole document.
Round up when the reader must do something between the words. Studying a table, following a step, checking a figure against another page — each costs time and adds no tokens, so the formula cannot see it. When the text will be read aloud, do not round at all: switch to the speaking constant of 150 wpm, which exists for that case. The guide on speaking time and speech length covers the pauses that even it cannot see.
Do not adjust for the reader. Individuals sit on both sides of the average, and the estimate is the middle of a wide range; adjusting it for a reader you have not timed replaces a published figure with a guess. If one reader's speed matters, time that reader.
For a whole-minute label, let the seconds decide. 1,000 words show "4 min 12 sec", nearest to a 4-minute read; 1,100 words show "4 min 37 sec", nearest to 5 minutes. Whether a byline rounds to the nearest minute or always up is the publication's convention; the engine itself never rounds to minutes.
Reading time versus speaking time
Speaking time is computed the same way from the second constant, 150 words per minute, a common prepared-delivery pace: words ÷ 150. Because both estimates are linear in the same count, their ratio is fixed — silent reading at 238 wpm runs 1.59 times as fast as speech, for every text — so the bus paragraph reads in "17 sec" and speaks in "27 sec", 10 seconds apart on 68 words. The calculator shows both side by side; the speaking-time guide covers the spoken side in full.
Frequently asked questions
How long does it take to read 1,000 words?
About 4 min 12 sec at the 238 words-per-minute average this site uses — an estimate for a typical adult reading silently, not a measurement of any one reader. Read aloud at 150 wpm, the same 1,000 words take about 6 min 40 sec.
How many words is a 5-minute read?
1,190 words — 5 minutes multiplied by 238 words per minute. Paste a text of that length into the reading time calculator and the display reads "5 min". Because the display rounds to whole seconds, every count from 1,189 to 1,191 words shows that same label.
Where does the 238 words-per-minute figure come from?
It is the average adult silent-reading rate for non-fiction in Brysbaert's 2019 meta-analysis of reading-rate studies, chosen because it is the most defensible single published figure, not because any individual reads at exactly that speed. It is the middle of a wide range, so the estimate describes a typical reader rather than you or your audience.
Why does another tool give a different reading time for the same text?
Two reasons, sometimes both: the other tool assumes a different rate, or it counts words differently at the margins — hyphenated compounds, decimals, web addresses, headings. On this site an address with a path is five tokens and "3.14" is two, so the release note in this guide counts 44 tokens where a reader sees 27 items. Small differences on long texts are normal.
Does harder text get a longer reading time?
No. The estimate is words divided by 238, and sentence length, vocabulary, and punctuation never enter it. Two texts of equal word count get the same reading time however difficult they are; the sentence count shown beside the time is reported for its own sake and has no effect on the minutes.
Is reading time the same as speaking time?
No. Speaking time divides the same word count by 150 wpm, a common prepared-delivery pace, so it is always longer: silent reading at 238 wpm runs 1.59 times as fast. The bus paragraph in this guide reads in 17 sec and speaks in 27 sec.
Every figure in this guide was computed at build time by the engine that runs the tools, which executes locally in your browser — nothing you type is transmitted or stored. Reading speed is a population average, as documented on the methodology page.