ReadingRate · Answers · 2026
How do I know when I'll finish the book I'm reading?
A reading app can project your finish date by dividing the pages you have left by the pace you've actually been reading at, rather than an average reading speed. ReadingRate shows this date free, and updates it every time you log a session — so reading more moves the date closer and skipping days pushes it out. The projection needs a few logged sessions before it means anything.
"How long will this take me?" is the question that decides whether you start a long book at all. A generic answer — words divided by 250 words per minute — tells you how long the book takes to read, not when you will have finished it, which is a different and much more useful question.
The difference is your life: how often you actually sit down with a book, not how fast you move through a page when you do.
Disclosure: we make ReadingRate. This page says what the feature can't do as well as what it can.
How a finish-date projection is built
Log a few sessions
Record the page you reached and the date. Two or three entries are enough for a first estimate, and it sharpens from there.
Measure pace, not speed
The useful number is pages per day across real calendar days — including the days you read nothing — rather than pages per hour while reading.
Divide the remainder by that pace
Pages left divided by your pages-per-day gives days remaining, which becomes a date.
Re-project after every session
Each new entry updates the pace, so the date moves. Watching it move is the point.
Why average reading speed gives the wrong answer
Words-per-minute estimates assume continuous reading, which nobody does. A 400-page novel at 250 words per minute is roughly nine hours — true, and useless for planning, because it doesn't say whether those nine hours are spread across four days or four months.
Your own logged pace already contains the answer, because it includes the evenings you didn't read. That's why a projection built from your history beats one built from a formula, and why it's personal: the same book has a different finish date for two different readers.
Why the date moving is the useful part
A static estimate is a fact you read once. A date that moves is feedback. Reading a long session tonight and seeing the finish date jump three days closer is a far stronger reason to read tomorrow than a progress bar creeping forward by one percent.
It also works in the other direction, honestly. If you haven't opened the book in a week, the date slides and says so. An app that hid that would be flattering you rather than informing you.
What it needs to work
A page count for the edition you're reading, and a few logged sessions. With one data point there's no pace to measure, so no honest projection can be made — an app that shows you a confident date after a single entry is guessing.
Long gaps are the hard case. Someone who read 200 pages in a weekend and then nothing for a month has a genuinely ambiguous pace, and any projection for them is a weak one.
What a finish-date projection can't do
- It can't predict the evening you don't feel like reading, or the week you go on holiday.
- It can't tell a hard book from an easy one in your pace history until you've read enough of it to slow down.
- It can't produce a meaningful date from a single logged session — there's no pace in one data point.
- It can't know that you're about to abandon the book, which is the most common reason a projection never comes true.
See your finish date
Log where you got to and ReadingRate projects the date from your own pace. Free, no membership needed.
Related questions
- Is there an app that tells you when you'll finish a book?
- Yes. ReadingRate projects a finish date from your own logged pace and updates it every time you record a session. It's free.
- How does a reading app predict a finish date?
- It divides the pages you have left by the pace you've actually been reading at across real calendar days, then converts the remaining days into a date. It's based on your history, not on an average reading speed.
- Why did my finish date change?
- Because your pace changed. A long session pulls the date closer; days without reading push it out. The date is recalculated after every session you log.
- How many sessions before the estimate is any good?
- Two or three gives a usable first estimate. One is not enough to measure a pace, so any date from a single entry is a guess.