A reading-time estimate is a planning tool. It is not a measure of understanding. The simplest estimate divides the number of words by a chosen pace in words per minute. That is useful when the input describes the reading task reasonably well, and misleading when a single number is treated as a promise.
Start with words, not pages
A page can contain a dense block of text, a diagram, a few equations, or large margins. If your document editor provides a word count, use that instead of assuming that all pages contain the same amount of material.
Reading minutes = word count ÷ words per minute
For a 1,200-word passage at 200 words per minute, the estimate is six minutes. The pace of 200 is an editable example in our tool, not a claim about the average reader. A 2,400-word passage at the same pace takes an estimated 12 minutes.
Measure a pace for this kind of material
Choose a sample similar to what you will read. Record its word count and time how long you take at your intended level of care. If 600 words take four minutes, that sample gives a pace of 150 words per minute. Use that number as a starting input, then revise it as you read more.
A sample full of familiar concepts may not describe the difficult section later in the chapter. You can calculate a range instead: estimate the same text at two plausible paces and reserve time near the slower result when the material is unfamiliar.
Budget for the work around reading
Suppose 1,800 words take an estimated 12 minutes at your measured pace. You also want to write a five-minute summary and spend eight minutes answering questions. The whole task is about 25 minutes before any extra allowance for getting stuck. A reading-only estimate of 12 minutes would leave more than half the intended work unplanned.
Diagrams, proofs, code examples, and exercises may take substantial time without adding many words. Add separate work blocks for them. When your task is to solve the examples while reading, a raw word-count calculation is especially limited.
Understand the result
The calculator rounds up to the next whole second and displays minutes and seconds. That precision is for a consistent calculation; it does not mean your pace is precise to the second. Treat the output as a starting estimate and round your actual calendar allocation sensibly.
The text field counts whitespace-separated units as words. This is a practical approximation for English prose. Hyphenation, symbols, and languages that do not generally separate words with spaces may produce a different count from a dedicated word processor.
Improve the next estimate
After one session, note the estimate, the actual duration, and what made the difference. “Stopped to solve two examples” tells you more than “read slowly.” Use that observation to separate reading time from exercise time in your next plan. The objective is a workable schedule, not reaching somebody else's reading-speed number.
Found an unclear step or a calculation error?
Help us improve this guide →