To calculate time for reading, divide your word count by a words-per-minute (WPM) rate. The formula is reading time in minutes = total words divided by WPM, with the decimal portion converted to seconds. Two numbers matter: the word count, which for a typical online article runs between about 200 and 1,000 words, and the rate, which is the only place a real disagreement is possible. Average adult silent reading sits at roughly 238 words per minute for English non-fiction, while reading the same text aloud runs closer to 183 words per minute, which is why the same passage can take noticeably longer when spoken. The math is trivial; choosing a defensible WPM is the actual decision. A reading-time estimate is honest only when both inputs are visible, because the arithmetic on top of them is just division. Any tool that hides the word count, hides the rate, or hides the rounding rule is asking you to trust an opaque number that you could verify in a moment by hand. That is why an auditable reading time, with both the count and the rate printed next to the result, is worth more than a fancier-looking estimate that you cannot check.
The Reading-Time Formula: Words Divided by WPM
The reading-time formula has only one shape. Take the total number of words in the piece, divide by the WPM rate that matches the situation, and convert the decimal part into seconds. The full expression is:
Reading time (minutes) = word count divided by words per minute
To turn the decimal part into seconds, multiply it by 60. If the result rounds to less than a full minute, report it as seconds rather than as zero minutes, because a non-empty text is never really a zero-second read.
A worked example using the default silent-reading rate. Suppose you have a 1,000-word article and you want the silent reading time at the non-fiction default of 238 wpm:
- 1,000 divided by 238 = 4.2016... minutes
- 0.2016 multiplied by 60 = 12.10 seconds, which rounds half up to 12 seconds
- Result: 4 min 12 sec
If instead you read the same article aloud at 183 wpm, the math becomes 1,000 divided by 183 = 5.4644... minutes, or 5 min 28 sec. That gap of roughly 75 seconds between silent and spoken reading of the same text is exactly the kind of difference that disappears if a tool quietly picks a rate for you without saying which one.
How to Calculate Time for Reading Step by Step
The Reading Time Calculator runs the formula above and shows every input it used. The fastest path from text to a defensible estimate is three steps.
- Paste your text into the input field, or switch to word-count mode and type the word count directly if you only have a number to work with.
- Pick a preset reading rate for silent reading or type your own, and set a separate speaking rate for the read-aloud estimate. The two rates are independent because silent reading and oral reading are different tasks with different speeds.
- Read both durations side by side, then check the word count and the counting rule printed under the result. The number of seconds is rounded half up to whole seconds, and any non-empty text is reported as at least one second so a page never shows a misleading "0 min" figure.
If the displayed word count does not match what you pasted, the counting rule under the result will explain why. The rule treats a hyphenated compound like state-of-the-art as one word, a contraction as one word, and a number such as 3.14 or 1,000 as one word. Strings of punctuation alone are not counted. When the rule is printed next to the result, the number is no longer something you have to take on faith.
Choosing the Right WPM for Silent vs Spoken Reading
The WPM you choose changes the answer more than any other input. The presets below come from named measurements rather than from folklore, and you can replace any of them with a custom rate if you know your own pace or your reader's pace.
| Rate (WPM) | Source | What it measures |
|---|---|---|
| 238 | Brysbaert 2019, meta-analysis of 190 silent-reading studies | Average adult silent reading, English non-fiction |
| 260 | Brysbaert 2019 | Average adult silent reading, English fiction |
| 183 | Brysbaert 2019, 77 oral-reading studies | Average adult reading aloud |
| 228 | IReST 2012 standardized texts | Reading short standardized paragraphs under a stopwatch |
| ~150 | Speech-coach convention, no retrievable study asserts it | Presentation pacing rule of thumb |
Silent reading and reading aloud are not the same activity. The 238 figure is what a typical adult does with eyes alone, and the 183 figure is what the same adult does when forming each word with their mouth. The IReST 228 figure is a separate measurement taken on standardized paragraphs under test conditions, which is why it sits between the two. The 150 figure is honest about being a coaching convention rather than a measured average, and it remains useful for budgeting presentation time because most public speakers are slower than their natural reading pace when an audience is watching.
A reasonable working default is 238 for silent reading and 183 for reading aloud. If the text is unusually dense, drop the rate; if it is simple, raise it. The calculator lets you type any number, so the rate is yours to set.
Why Two Reading-Time Tools Can Give Different Numbers
When two reading-time calculators disagree, they almost never disagree about the division. They disagree about what they counted as a word, and about which rate they applied silently. Three sources of drift are common.
The first is the counting rule. A page that splits on every dash will count state-of-the-art as three tokens; a page that treats dashes as word-joining separators will count it as one. The same logic applies to contractions, decimal numbers like 3.14, and thousand-separator numbers like 1,000. Two tools can both claim to count "words" while producing different totals on the same paragraph.
The second source of drift is rounding. A reading time of 4.2016 minutes is often displayed as 4 min, which silently drops the 12 seconds. A page that rounds half up to whole seconds and prints both minutes and seconds keeps that information visible.
The third source of drift is undisclosed rate selection. If a tool picks 200 wpm for everything without telling you, every estimate is biased in a direction you cannot see. Showing the rate, the count, and the rounding rule next to the result is the only way to make the math reproducible by hand.
What a Population Average WPM Actually Predicts
A reading-time estimate is a population average, not a prediction for one person. The Brysbaert review that produced the 238 wpm figure also reports that most adults read silently at somewhere between 175 and 300 wpm, which means a particular reader's true time can differ from the estimate by roughly a third in either direction. The estimate is precise about the arithmetic and open about the inputs, and that is all a reading-time estimate can honestly be.
Three situations where the average is enough: budgeting a presentation slot when the speaker is not yet known, comparing two drafts of the same article to see which one will take longer, and setting reader expectations on a blog post where most visitors are unknown strangers. Three situations where it is not enough: timing a live speech by a known speaker, planning a study session for a slow reader, or scheduling a test with a hard time limit for someone with a documented accommodation. In those cases, the right input is the specific reader's measured WPM rather than a population average, and the calculator's custom-rate field is the place to enter it.
Practical Uses for a Reading-Time Estimate
Reading-time numbers earn their keep in five common planning tasks. Bloggers use them to flag posts as a 5 min read so visitors can decide whether to commit. Teachers use them to size reading assignments against class time, then trim or extend a passage to fit a slot. Conference organizers use them to keep panels from running long, especially when each speaker gets the same fixed window. Editors use them to compare a long and a short version of the same article before sending revisions. Accessibility reviewers use them, alongside readability scores, to flag long passages that may be tiring for some readers.
In every one of those uses, the value is relative rather than absolute: the estimate lets you compare, budget, and warn, not promise. A page that prints the count, the rate, and the rule makes the comparison possible without forcing anyone to trust an opaque result, which is the whole point of choosing an auditable tool over a friendly-looking one.