Reading Time & Text Analyzer
Estimate how long a draft takes to read or present, with running totals for words, characters, paragraphs, and lines.
Reading time and document metrics
This browser tool measures words, characters, sentences, and paragraphs from a draft, then estimates how long it takes to read silently and how long it takes to say out loud. It is useful when you want a quick overview before editing, presenting, or handing work to someone else.
How the estimates are calculated
Reading time assumes 225 words per minute, a widely used average for silent reading of general non-technical prose. Speaking time assumes 140 words per minute, which leaves room for the pauses people actually take when talking through material they have prepared. Both are averages rather than predictions.
Counting rules
- Words are separated by whitespace, so “don’t” is one word.
- Characters counts every character, including spaces and line breaks.
- Sentences are counted wherever a full stop, question mark, or exclamation mark is followed by a space or the end of the text.
- Paragraphs are separated by line breaks.
Worked example
Paste The quick brown fox jumps over the lazy dog. and the panel reports 9 words, 44 characters, 1 sentence, and 1 paragraph, with a reading estimate of 0m 2s and a speaking estimate of 0m 4s. Paste exactly 225 words and the reading estimate reaches 1m 0s, which is a quick way to confirm the tool is behaving as described.
Practical uses
- Timing a talk or one segment of a lecture. Speaking time gives you a defensible number to plan against, and unlike reading time it already allows for pauses.
- Estimating a reading assignment. Useful when an instructor quotes a duration rather than a word count.
- Checking narration length. For voiceover and audio, speaking time is closer to the recorded pace than reading time is.
- Comparing drafts. Measure before and after editing to see whether a cut genuinely shortened the read.
Where the estimates drift
These figures are averages, and several things push the real number away from them. Headings, references, and footnotes are usually skimmed rather than read. Code, tables, and diagrams are read at a different speed from prose. Technical writing is slower than narrative, and so is material in a second language. A reader who stops to re-read a passage, or a presenter who pauses to check a detail, will both run longer than the estimate. Treat the result as a planning figure and leave yourself a margin.
For a plain count without the time estimates, use the word counter. To review how often individual words appear, use the keyword density checker. You can also browse all twelve tools.
