About Reading Time
Reading Time estimates how long a passage takes to read aloud or to scan, based on a word count and a fixed reading speed of about two hundred words per minute. The result is given as a number of minutes, or as seconds when the passage is short enough that a fraction of a minute would be unhelpful.
That fixed speed is the whole basis of the estimate, and it is worth knowing which way it can be wrong. Two hundred words a minute is a reasonable average for adult prose; technical material with unfamiliar terms, code, or long sentences slows a reader down considerably, while a list of short items is read faster. Treat the figure as a planning aid rather than a measurement.
The word count uses the same rule as the standalone counter, splitting on whitespace, so the two tools agree on the same input. Text that does not separate words with spaces will report a very small number of words and therefore an implausibly short reading time.
How to use Reading Time
- 1 Paste the passage you want estimated.
- 2 Read the word count alongside the estimated reading time.
- 3 Adjust the estimate upward in your head for dense or technical material.
Frequently asked questions
What reading speed is assumed?
About two hundred words per minute, which is a common average for adult non-fiction. If your audience reads faster or the material is technical, adjust the estimate accordingly — the tool has no way to know which situation you are in.
Short passages show seconds rather than minutes. Why?
Because a fraction of a minute is not a meaningful unit for a couple of sentences. Reporting seconds keeps the figure precise enough to be useful, which minutes rounded to one decimal place would not be.
Does it count the words the same way as the word counter?
Yes, both split on whitespace, so the word count matches exactly. That also means both inherit the same limitation for languages that do not separate words with spaces, where the count is far lower than the number of actual words.
Free, online, and private
Free to use
Reading Time is completely free. There is no account to create, no login, and no hidden charge or usage limit.
Runs online in your browser
It is a free online tool that runs entirely in your browser. Nothing to download or install — open the page and start using it right away.
Your data stays private
All processing happens locally on your device. Your input is never uploaded, stored, or tracked, so it never leaves your browser.
How Reading Time behaves in detail
These are the specifics of this implementation — the exact ranges, defaults and fixed settings you are working with.
| Parameter | Value |
|---|---|
| Reading rate | fixed at 200 words per minute — the only rate used and not adjustable |
| Below one minute | reported in whole seconds, rounded up with Math.ceil |
| One minute and above | reported in minutes with one decimal place, via toFixed(1) |
| Word counting | whitespace splitting — the same rule the Word Counter uses, with empty input counting as 0 words |
| Output rows | two lines: the word total, then the reading time |
Compiled from the implementation of this tool and checked against it by itoolnet.
What Reading Time does not do
Knowing the edges of a tool saves more time than another list of its features. These are the cases where it will not do what you might expect.
- The 200 words per minute constant is hard-coded and there is no control to change it. Technical material, dense reference tables and light fiction are all estimated at the same pace, which makes the figure a rough planning number rather than a measurement.
- The two output branches round differently and the numbers can look odd as a result: under a minute the value is rounded up, so a single word still reports "1 seconds", while at a minute or more the value is rounded to the nearest tenth and the unit word is never inflected.
- Only the word count feeds the estimate. Headings, code blocks, tables and images are counted as ordinary words and nothing is subtracted for skimming, so the figure is a lower bound derived from one input, not a prediction of how long a particular reader will need.
Tested and documented by itoolnet, the team that builds and maintains this site.