A reading time calculator converts an assignment's size into minutes: words divided by reading speed. This one takes words or pages, and adds the adjustments that change real study plans — a density multiplier (a textbook page reads slower than a novel), an optional study re-read (×1.7), a session splitter with a 25/5 break rhythm, and a due-date back-calculator that reports pages per day with a feasibility verdict. Everything runs in your browser.
Published reading-speed research places adult silent reading in a wide band, roughly 150 to 350 words per minute depending on the material and the purpose. No calculator can collapse that band to one number for your brain, your course and Tuesday night. This page therefore picks three honest anchors — slow 150, average 225, fast 325 — and multiplies or divides from there.
The multipliers are documented defaults, not measured laws. The ×1.25 textbook density and ×1.7 re-read settings exist so the estimate bends toward harder reading; edit the custom speed whenever your own timing disagrees. What this page cannot promise is comprehension — finishing in 80 minutes says nothing about what you can recall afterward.
The cheapest accuracy upgrade on the whole page: time yourself reading one typical page at your normal pace, and enter a custom speed. One measurement beats every default.
Run the reading time calculation
Start with the size of the assignment. Switch between words (if the syllabus states a word count) and pages (if it states chapters or page ranges), then set words-per-page — 250 fits a double-spaced essay, 300 a single-spaced report or dense textbook page, 500 a two-column journal article. Pick a speed profile, a density, and the re-read toggle if this reading has to survive an exam. Press Calculate and the minutes, the clock form and the words↔pages cross-calculation fill in below. Your settings save in this browser only (key csw-rtc-v1), nothing is uploaded, and Reset wipes them. If you want to see the shape of a plan first, load the demo — invented, illustrative numbers for a 48-page textbook week.
Reading time calculator
100% private — runs in your browserThe estimate carries the settings that produced it — speed, density, re-read — so it still makes sense pasted into your notes or a group chat.
That is the whole flagship: four settings and a button. The two planners below inherit its numbers, so set the assignment up once and the session split and the due-date check both stay in sync. The sections after them unpack the math, the speed anchors and the honest limits — including why "I read fast" is usually the wrong thing to optimize.
The math this page runs, line by line
No black boxes. Every output above comes from six small steps, and you can check each one with a phone calculator:
| Step | Formula | Worked example (demo settings) |
|---|---|---|
| Pages → words | pages × words-per-page | 48 × 300 = 14,400 words |
| Effective speed | chosen wpm ÷ density multiplier | 225 ÷ 1.25 = 180 wpm |
| Base minutes | words ÷ effective speed | 14,400 ÷ 180 = 80 min |
| Study re-read | base × 1.7 (toggle only) | 80 × 1.7 = 136 min |
| Session split | total ÷ sessions, plus 5-min breaks between | 136 ÷ 4 = 34 min each |
| Pages per day | pages ÷ calendar days until due | 48 ÷ 12 days = 4 pages/day |
Three choices in that table deserve a sentence each. The density multiplier divides your speed rather than inflating the word count, because harder material slows the reader, not the page. The re-read factor applies to the whole total, not just the hard chapters — it is a planning approximation, and mixed weeks deserve a manual override. And the due-date math counts calendar days, not working days: students read on weekends precisely when plans pretend they do not. If you would rather plan in pages than minutes, the words-to-pages converter runs the same formatting presets from the other direction.
Reading speed profiles: where 150, 225 and 325 come from
Published reading-speed research keeps landing in the same neighborhood: adult silent readers move somewhere between roughly 150 and 350 words per minute, with the middle of the range in the low 200s for ordinary prose. The spread inside that band is not noise — it tracks material difficulty and purpose. A first pass through an unfamiliar theory chapter is genuinely slower than a reread of last week's lecture summary, and pretending otherwise is how reading plans die on day one.
The page's three anchors map onto that reality:
| Profile | Speed | Use it when | An hour buys you (300-word pages) |
|---|---|---|---|
| Slow | 150 wpm | New domain, heavy notation, reading in a second language, late-night reading | ~24 pages (before density) |
| Average | 225 wpm | Typical college reading at a normal pace with occasional stops | ~45 pages |
| Fast | 325 wpm | Familiar material, review before an exam, skimming for structure | ~65 pages |
Two cautions belong next to that table. First, self-reported speeds run optimistic: people remember their best page, not their average one, which is why the custom field and a one-page timing beat any profile. Second, claims far above the band — thousand-words-a-minute "speed reading" — do not survive controlled testing; comprehension collapses long before the claimed speed does. Reading faster is real but bounded. Planning honestly beats planning bravely, which is the entire reason the anchors start at 150.
Timing yourself takes two minutes: read one typical page at your normal study pace, divide its word count by the seconds it took, multiply by 60, and enter the result as a custom speed. If your page is 300 words and the timer says 95 seconds, your speed is 300 ÷ 95 × 60 ≈ 190 wpm — a number no generic profile would have guessed, and the one that makes every other output on this page yours.
Text density: why a textbook page is not a novel page
Word-per-minute math assumes the words arrive at the same effort. They do not. A narrative chapter feeds you one line of argument at a time, and your eyes ride the sentence. A textbook page interleaves the argument with figures, worked examples, definitions and boxes, and every one of those interrupts the ride. Dense academic prose goes further: embedded citations, methodological hedges, terminology you must hold in your head, and footnotes that pull you out of the paragraph entirely.
The density setting prices that gap with three documented defaults:
- Light fiction / narrative — ×1.00. The baseline. Novels, long-form journalism, course readings written to be read straight through.
- Textbook / how-to — ×1.25. Figures, examples and definitions interrupt the flow; 225 wpm becomes an effective 180.
- Dense academic — ×1.45. Jargon, citations and footnote detours; 225 wpm becomes an effective 155, and a 20-page chapter now costs about 38 minutes instead of 27.
These multipliers are planning conventions chosen inside the published speed band — the honest way to say "harder material reads slower" without inventing a decimal you cannot defend. They are also why the words-per-page setting matters even in pages mode: the preset answers how many words a page holds, and the density answers how fast those words go by. A two-column journal page packs roughly 500 words into the same sheet that holds 250 double-spaced essay words — five choices in the preset row cover most formats, and the custom field covers the rest.
One more trap worth naming: page counts lie across devices. A "page 12" on a PDF reader at two-page zoom is not a printed page 12, and an e-reader's page 12 is neither. When the syllabus points at a PDF, count the PDF's pages; when it points at the print edition, count those. Mixing the two quietly doubles or halves an estimate.
Session planner: split the reading into sittings
A total like "136 minutes" is an abstraction; a plan like "four sittings of 34 minutes, done by 9 pm" is a Tuesday. The planner below divides the flagship total into equal sessions and adds a five-minute break between them — the half of a 25/5 rhythm most plans forget to schedule. Reading research on spaced practice consistently favors distributed sessions over one massed binge, and so does basic fatigue: hour three of contiguous reading is slower and retain-less than hour one. The planner also reports each session's share of the pages and words, so "session 2 of 4" is a concrete 12 pages rather than a mood.
Session planner
Uses the totals from the calculator aboveCalculate the reading total first — the planner splits whatever sits in the flagship results.
| Session | Reading | Pages | Words | Ends at |
|---|
Break policy: 25 minutes of focus and 5 minutes of rest is a widely used rhythm; this planner applies the 5-minute rest between sessions. Sessions longer than about 50 minutes are where the plan starts lying — add a session instead of stretching one.
Deadline back-calculator: pages per day to the due date
Reading plans usually fail in reverse: the total was never impossible, it just started too late. This planner flips the direction. Enter the due date, and the page counts the calendar days between today and it, divides the assignment by that count, and reports pages and minutes per day with a verdict. The verdict bands are this tool's own, stated so you can argue with them: up to 30 minutes a day is comfortable — a commute or one lecture's worth; 31 to 90 is tight — doable, but it owns a fixed slot in your day; past 90 minutes a day, or no days left, is not feasible as a normal schedule and the honest fix is re-planning, not heroics.
Deadline back-calculator
Calendar-day math, verdict bands documentedThe verdict uses the day you press the button — re-check it after losing a weekend, because the math will notice even if the plan does not.
When the verdict comes back tight, change a variable before you change your sleep: start today instead of Monday, drop the re-read on the chapters the lecturer skimmed, or split dense chapters away from light ones so the average stops lying. When it comes back not feasible, the fix is scope or dates — talk to the course, share notes with a group, or move the deadline if the course owns one. For a triage of every deadline on the plate at once, the deadline triage tool ranks the whole pile, not just this reading.
What this calculator cannot promise
Every tool page here states its limits, and this one has more than most because it estimates something happening inside your head. The honest list:
- No comprehension guarantee. The output is minutes, not understanding. A fast total achieved by skimming is a real number and a worse grade.
- Per-page counts wobble. Format, margins, font size and device change how many words a page holds. The presets are good midpoints, not measurements of your PDF.
- It does not know your stops. Lookups, re-reading a confusing figure, answering one message — the estimate assumes contiguous reading. Real sessions carry overhead the calculator cannot see.
- The multipliers are defaults. ×1.25 and ×1.45 encode "harder reads slower," not a law of textbooks. The custom speed field is the escape hatch.
- The 25/5 rhythm is a convention. A widely used focus pattern, useful as a default; some courses and some readers do better with 50/10. The planner keeps the break fixed at 5 minutes so the math stays simple.
- Digital pagination drifts. E-reader and PDF pages do not match print. Count from the same edition the syllabus names.
None of these make the tool useless — they make it a first draft. Run the estimate, time one real page, correct the speed, and the second draft is calibrated. That loop, run once per course, is worth more than any precision the calculator could fake.
Making the estimate come true
An estimate becomes a plan through four moves, none of which require reading faster. First, time one page and set the custom speed, so every number on this page inherits your real pace instead of a research average. Second, put sessions on the calendar — the session planner gives you wall-clock end times precisely so they can become appointments; a plan that lives only in a tab dies with the tab. Third, match material to hour: dense academic chapters at your best hour, light review at your worst, because the same page costs different minutes at 9 am and 11 pm. Fourth, re-read on purpose — the ×1.7 toggle is for reading that ends in an exam or a paper, and it belongs to chapters you will annotate, not chapters you will nod at.
If the back-calculator says the plan is tight, the earlier sections hold the levers: more sessions of the same 25 minutes, density honestly set, and the fast profile only for genuine review. And if the assignment in front of you is also one you have to write, the reading minutes are only the first line of the budget — the study guides hub covers the writing side, and the free writing tools hub holds the counters and converters that pair with this page. Timing a talk instead of a reading? The words-to-minutes planner runs the same math at speaking pace.
Reading done, but the writing clock is the real problem?
If the chapters are finished and the paper is not started, a quoted, deadline-bound writer can draft the assignment from your notes and sources while the argument stays yours. Get a free price quote and see the terms first.
Quiz: five questions on reading time
Five questions on the math and the honest limits — multipliers, per-page timing, and what no calculator can promise. Every wrong answer explains itself, and four options keep the guessing honest.
1. You switch density from light fiction (×1.00) to dense academic (×1.45) at 225 wpm. What happens to the estimate?
2. One 300-word page at an average 225 wpm, with no adjustments, takes about how long?
3. When is the ×1.7 study re-read toggle the honest setting?
4. The back-calculator says 24 pages a day for two days. What is the right first move?
5. What does this calculator actually promise?
Frequently asked questions
How accurate is a reading time calculator?
It is a range, not a stopwatch. Published reading-speed research spans roughly 150 to 350 words per minute for adult silent reading, so any single figure is a midpoint choice. This page tightens the estimate with a density multiplier and an optional re-read, and the honest calibration is empirical: time yourself on one typical page, set a custom speed, and expect the final total to land within about ten or fifteen percent — not to the minute.
How long does it take to read 20 pages?
At the site's defaults — 300 words per page, 225 wpm, light density — 20 pages is about 6,000 words, or 27 minutes. The same 20 dense academic pages carry the 1.45 multiplier, so the estimate climbs to about 38 minutes, and switching the study re-read on pushes any of these totals up by 70 percent. Pick the density that matches the material and the answer stops being generic.
How many pages can I read in an hour?
Divide 60 by the minutes one page takes you. At 225 wpm on 300-word pages that works out to about 45 light pages an hour, around 36 textbook pages once the 1.25 density multiplier applies, and roughly 31 dense academic pages. With the study re-read switched on, a textbook hour drops to about 21 pages — which is why cramming plans that assume novel-pace reading fall apart by Wednesday.
Should I count a study re-read in my plan?
If the reading feeds an exam, a cold-call seminar or a paper you have to write, yes: a second pass plus notes routinely takes longer than the first read on difficult material, which is why the toggle multiplies the estimate by 1.7. If you are reading for gist or a general discussion, leave it off. The multiplier is a documented planning default, not a measured law — a custom speed absorbs a different method.
How do I plan reading sessions before an exam?
Work backward from the date. Enter the pages due and the exam date to get pages per day, split each day's pages into 25-minute reading blocks with 5-minute breaks, and give dense chapters their own session instead of mixing them with lighter ones. Then move the plan onto a calendar: a schedule that lives in a browser tab dies with the tab, and one that lives in your calendar survives contact with the week.
Did the estimate change how you planned the reading?