Reading plan calculator that turns pages left and reading days into a finish date
Put the total page count, the pages you have read, a start date and the weekdays you actually open a book into the input row at the top, and the result row below fills in your pages per reading day, the finish date, a cumulative chart and a checkpoint table. There is no calculate button; the plan updates as you type.
- Pages left
- — Total pages minus pages already read
- Finish date
- — The day you turn the last page
- Daily reading time
- — Pages per reading day times minutes per page
- Total time left
- — Time needed to read every remaining page
| Point | Pages in span | Cumulative | Date |
|---|
This calculator spreads the pages you have left across the days you actually read, then multiplies by your minutes per page to show reading time. Minutes per page differ from reader to reader and from book to book, so put in a rough figure at first and replace it with a measured one after a few sessions. The finish date assumes you keep every reading day you selected.
ready to use.
- Visible firstKeep the input and result positions clear.
- Results firstPut the main number up front and keep the process secondary.
- Less to askNo sign-up or extra information before using the tool.
How many pages a day does this book actually take
The hard part of a reading goal is not the length of the book, it is the split. You can decide to finish a 336-page paperback in a month and still have no idea how many pages that is per sitting. Most reading plans break right here, because 336 divided by 30 gives eleven pages, and eleven pages a day is only true for someone who reads every single day.
This tool asks a question before it divides: how many days a week do you actually open a book? For someone who reads on Monday, Wednesday and Friday, thirty days is not thirty chances, it is thirteen. What follows explains where that thirteen comes from, what the rounding leaves you on the last day, and why the minutes-per-page figure has to come from your own stopwatch rather than a published average.
The short version: pages left divided by the reading days you really have
The maths is two lines. Subtract the pages you have read from the total to get what is left, then count how many times your chosen weekdays appear on the calendar between the start date and the end of the window. Divide and round up. The table below uses the same units and the same rounding you will see on screen.
- Pages left = total pages minus pages already read
- Reading days = how often your chosen weekdays fall inside the window
- Pages per day = pages left divided by reading days, rounded up
- Finish date = the reading day on which the last page is turned
| Item | Value | Where the value comes from |
|---|---|---|
| Pages left | 296 pp | 336 total minus the 40 already read |
| Reading days in the window | 13 days | How often Mon, Wed and Fri fall in the 30 days from 3 September 2026 |
| Pages per reading day | 23 pp | 296 divided by 13 is 22.77, rounded up |
| Finish date | 2 October 2026 | The thirteenth reading day counted from 3 September |
| Daily reading time | 46 min | 23 pages at 2 minutes per page |
| Total time left | 9 h 52 min | 296 pages at 2 minutes per page is 592 minutes |
| Final session | 20 pp | What is left after 276 pages over the first twelve days |
What to type, in order
One number is enough to get a plan. Leave the other fields empty and the faint example numbers are used as they stand; type into a field and your value takes over immediately. Because there is no calculate button, every edit refreshes the result row, the chart and the checkpoint table together.
- Read the total page count off the back cover or the last numbered page.
- If you are mid-book, enter the pages you have finished. Leave it empty for a new book.
- The start date is set to today. Change it if you plan to begin next week.
- Leave minutes per page empty at first, then enter a measured value after a few sessions.
- Under "Plan by", choose whichever side you have already decided.
- Switch off the weekdays you do not actually read on.
A deadline and a daily amount answer different questions
The two modes are the same calculation run in opposite directions. A deadline answers "how many pages a day to finish in thirty days"; a daily amount answers "if I read twenty pages a day, when am I done". Book clubs and exam prep usually need the first. Building the habit first usually needs the second.
- Plan by a deadline — enter days to finish and the daily page target is decided.
- Plan by a daily amount — enter pages per reading day and the finish date is decided.
- Switching modes clears the target field and changes its label and unit.
- Both modes honour your selected weekdays in exactly the same way.
Selecting your reading days is what makes the plan honest
For a three-day-a-week reader, thirty days is thirteen chances. Starting on Thursday 3 September 2026 and reading only on Monday, Wednesday and Friday, those weekdays land thirteen times inside a thirty-day window. Splitting 296 pages across thirteen days gives 23 pages, more than double the 10 pages a seven-day plan would have promised. That gap is why optimistic plans collapse in the first week.
- The weekday buttons follow the local calendar order; the English page starts on Sunday.
- All seven start switched on, so you work by switching off the days you skip.
- Turning every day off shows a notice rather than a silent zero.
- Changing a weekday moves the daily target and the finish date at the same time.
Minutes per page is something you measure, not something you look up
A page is not a fixed unit. Trim size and type size change how much text sits on one, so a page of a mass-market paperback and a page of a textbook are different quantities. That is why this tool ships no national average and asks for your own figure instead. Measuring it takes ten pages: read them the way you normally read, then divide the elapsed time by ten.
- Start a timer, then read ten pages in your usual chair and usual light.
- Twenty-two minutes for ten pages means 2.2 minutes per page. Two decimals are accepted.
- Measure fiction and technical books separately; the same reader can differ by a factor of three.
- If you take notes as you read, include that time or the plan will run short.
What published reading-rate research can and cannot tell you
Reading-rate studies report words or characters per minute, never pages. Brysbaert pooled 190 studies covering 18,573 participants in a 2019 meta-analysis and put adult English silent reading at 238 words per minute for non-fiction and 260 for fiction, with oral reading at 183. The IReST standardised texts, measured across 17 languages with 436 readers, gave an oral average of 184 ± 29 words and 863 ± 234 characters per minute. Useful numbers, but they stop one step short of a page.
- Words per page vary widely with trim size, type size and leading.
- Most studies time short standardised passages, not three hundred continuous pages.
- Oral and silent rates differ, and the IReST figures are read-aloud values.
- So this tool keeps those numbers out of the calculation and in the explanation.
What rounding up leaves you on the final day
The daily target always rounds up. Splitting 296 pages across thirteen days gives 22.77, and reading 22 would leave a handful of pages that need a fourteenth session. Rounding to 23 avoids that. The trade is that the final day is lighter: twelve days at 23 pages covers 276, so the last session is 20 pages. That is why the bottom row of the checkpoint table is smaller than the rows above it.
- Because of the rounding, a plan finishes on or before the deadline you set.
- The remainder for the final stretch is visible in the last row of the table.
- The same rule applies when you plan by a daily amount.
- The day the pages left drop below the daily target is the finish day.
Reading the checkpoint table
The table breaks the plan at a fixed number of reading days. Short plans get one row per reading day; longer ones widen to a week or a multiple of it so the table stays under twelve rows. Each row carries the pages for that stretch, the running total at that moment, and the calendar date it falls on. The last row is always the finish.
- Pages in span — what to read since the previous checkpoint
- Cumulative — total pages read by that point; it equals the book length on the last row
- Date — the actual reading day that checkpoint lands on
- The caption above the table states how many reading days each row covers.
What the slope of the cumulative chart is telling you
The line starts at the pages you have already read and climbs to the full page count on the finish date. A steeper slope means more pages per session; switching off a weekday makes the line steeper because the same height has to be climbed in fewer steps. The axes and gridlines are drawn before you enter anything, so the range is visible from the first paint.
- The vertical axis runs from zero to the total page count.
- The horizontal axis runs from the start date to the finish date.
- The left dot marks pages already read; the right dot marks the finish.
- The figure above the chart is the total length of the plan window in days.
When you fall behind, rebuild the plan instead of catching up
Missing three sessions does not mean tripling the next one. Correct the pages-read field to the real number, move the start date to today, and the tool produces a fresh daily target for the time that is actually left. Seeing how far the missed days push that number up makes the choice between extending the deadline and adding a weekday much easier.
- Update pages read to the real value; open the book instead of estimating.
- Move the start date to today so past days drop out of the window.
- If the new daily target is too heavy, extend the deadline first.
- If the deadline cannot move, switch on one more reading day instead.
Where this calculator stops being right
The maths spreads pages evenly. Real reading is not even. Some books start dense and speed up; others bury a hundred pages of tables and footnotes in the middle, where a single page takes three times as long. In the cases below, the output needs adjusting before you trust it.
- Ebooks — page numbers shift with type size, so track position percentage or locations instead.
- Academic titles with long back matter — enter the last page of the body text, not the last printed page.
- Workbooks and problem sets — solving time dwarfs reading time, so minutes per page stops meaning anything.
- Comics and picture books — per-page time varies too much for a page-based plan.
- Several books at once — this tool plans one book, so calculate each separately.
Check these before the first week is out
A plan is worth revisiting once, early. Running through the list below catches most of the reasons a reading plan falls apart in its first seven days.
- Is the total the last page of the body text? Counting front and back matter inflates the plan.
- Are the weekdays you switched off really days you skip? Wishful days cause week-one slippage.
- Did you measure minutes per page, or leave the example value? Reading time is meaningless until you do.
- Is the daily reading time something you can actually find? Forty-six minutes is a problem if you have twenty.
- Does the finish date land before your real deadline? If not, add a reading day or lower the target.
- Did you copy the plan? It makes restoring the same conditions next time much quicker.
Evidence and review date
Content reviewed on 2026-09-03. The calculation uses only the pages left and the reading days inside your plan window. The reading-rate studies below support the explanation in this article; they are not inputs to the maths.
Related tools
Reading plan questions
There is no calculate button. When does it run?
On every keystroke. The moment a number lands in the total pages field, the result row, the progress bar, the chart and the checkpoint table all refresh, and the same happens when you press a weekday button or switch planning mode. A calculate button would add one click without changing a single number, so it is not there.
What if I do not know my minutes per page?
Leave the field empty. The faint example value of two minutes is used as it stands, so daily reading time and total time left still appear. Treat those as a starting estimate rather than a measurement. After a few sessions, time ten pages, divide by ten, and enter the result; the time figures become far more useful once you do.
I only read at weekends. Can I still plan?
Yes. Switch on Saturday and Sunday only and the plan runs on two days a week. Over a thirty-day window starting 3 September 2026 those two days come round eight times, so 296 pages left works out at 37 pages a session. Compared with 10 pages on a seven-day plan that is a big jump, so extending the deadline or adding one weekday is usually more realistic.
Why does the daily target always round up?
Because rounding down costs you an extra session. Splitting 296 pages across thirteen days gives 22.77; reading 22 leaves a remainder that needs a fourteenth day. Rounding to 23 keeps you inside the window, and the cost comes back as a lighter finish: twelve days at 23 pages covers 276, leaving 20 for the last session.
My ebook shows different page numbers on each device
Ebook pagination moves with type size, which makes a page-based plan unstable. Two options work. Fix the type size and enter the total pages you see at that setting, or enter the print edition page count and track your position by percentage in the reader. The second survives a change of device.
The finish date comes out earlier than the deadline I entered
That is expected. Rounding the daily target up means a plan lands on or before the deadline. Reading every day with 296 pages left over thirty days gives a target of 10 pages, and 296 divided by 10 finishes on the thirtieth reading day exactly. Change the total slightly and the plan will often close a day or two early; treat the gap as your buffer for a missed session.
What changes when I fill in pages already read?
Three things move together. The remaining pages shrink, so the daily target drops; the progress figure switches from a dash to a real percentage; and the cumulative chart starts from the height of the pages you have read rather than from zero. With 40 pages of a 336-page book behind you, progress reads 12% and only the remaining 296 pages get divided.
Can I plan several books at once here?
Calculate them one at a time. The tool divides the remaining pages of a single book, so combining two would hide which one gets which days. What does work is running each book separately and adding up the daily reading times. If that sum is larger than the time you can protect, one of the books needs to wait.
Does this work for audiobooks or research papers?
Audiobooks do not fit; their runtime is already fixed, so there is nothing to divide by pages. Papers do fit, but the minutes-per-page figure has to be much larger. Following equations and tables can take seven minutes or more on a single page, so read one paper with a timer running and use that measured value.
I am three sessions behind. How do I recover?
Rebuild rather than binge. Correct the pages-read field, set the start date to today, and read the new daily target. If it is heavier than you can manage, extend the deadline; if the deadline is fixed, switch on one more weekday and the per-session load drops. Refusing to revise the plan stops more books than missing a session ever does.