Reading Time Calculator: How Long Will This Book Take?

I was in the library doing math on my phone

I was standing in the library stacks with a paperback open to some random page, doing math on my phone, and nothing was adding up. The back cover said something like 400 pages, the audiobook version was around 12 hours, and my brain was trying to translate that into: “So… am I finishing this by Sunday or am I canceling plans?”

I nodded like I understood “average reading speed.” I didn’t.

So I built the habit I wish someone had handed me earlier: estimate the time based on words, not vibes.

And yeah, pages matter, but pages are slippery. Font size, margins, dialogue-heavy chapters, dense nonfiction with footnotes… it’s all over the place. Word count is the thing that behaves.

What you’re actually calculating (and why pages lie)

If you’ve ever compared two “300 page” books and one felt like a weekend snack while the other felt like a small emotional mortgage, you already know the problem. A page isn’t a unit of effort. It’s a unit of printing.

Word count is closer to the real workload, but even word count isn’t the whole story because your speed changes with difficulty. A breezy romance with clean prose, short paragraphs, and lots of white space? You’ll fly. A technical classic where every paragraph is a compact little argument (and you keep re-reading sentences because they’re pretty)? Slower. And then there’s your mood, which is basically the hidden variable no spreadsheet wants to admit exists.

But you still want a number. You want the ballpark. You want to know if “just one more chapter” is a lie.

So here’s the core idea: estimate total words, pick a realistic words-per-minute (WPM) for you and for the kind of book, then convert to minutes and hours. That’s it. That’s the whole trick.

So what do you use for WPM? People throw out 200–300 WPM as “average,” and that’s not wrong, but it’s also not very helpful unless you anchor it to your own reality. I’ve tested myself on a bunch of stuff, and my speed swings wildly depending on how chewy the prose is and whether I’m taking notes (or highlighting like a maniac, which is kind of the same thing).

A quick table I actually use (with sane defaults)

Here’s a set of defaults that won’t embarrass you later. They’re not laws. They’re starting points.

But the thing is, WPM is only half of it. The other half is “how many words are in this book,” which publishers don’t always hand you nicely.

How to estimate book word count (and then your reading time)

If you can find the word count, use it. If you can’t, estimate it from pages. And if you’re thinking “pages are slippery, you just said that,” yes — but we can still get a decent estimate if we use a reasonable words-per-page number.

One sentence: you don’t need perfection.

So here’s how I do it when I’m being practical (which is most of the time):

• If you have word count: use it directly. Some ebooks show it, some author sites list it, and sometimes you can find it in publishing metadata.
• If you only have pages: estimate words using a words-per-page assumption. For many typical novels, I’ll use about 250 to 300 words per page. For roomy large-print editions, it can be lower. For tight mass-market paperbacks, it can be higher.
• If you’re reading on a phone: ignore “pages” entirely and look for word count or use time-per-chapter once you’ve read a couple chapters.

And now the worked example, because this is where it clicks.

That 7.3 hours is the “clean” number. Real life isn’t clean. You’ll stop to stare out the window, you’ll re-read a paragraph because the rhythm was good, you’ll dog-ear a page and tell yourself you’ll come back (you won’t), and you’ll get interrupted. So I usually pad by about 10–20% if I’m planning a schedule. That’s not scientific, it’s just me being honest about being human.

So if you want to finish that book in 5 days, you’re looking at roughly 7.3 hours ÷ 5 ≈ 1.5 hours/day. That’s a real plan. That’s not “I’ll read more.”

And if you’re a writer, this is secretly useful too, because you start feeling what 100,000 words actually means in a reader’s week.

Use the calculators (the lazy way, which I fully support)

I built these because I got tired of redoing the same napkin math and also because, honestly, it’s nice when the numbers don’t fight you.

If you already know your total word count (or the book’s word count), use this:

If you’re starting from pages and you want a quick estimate, this one gets you to words first:

estimate word count from pages

If you’re editing your own draft and you want to sanity-check pacing (or you’re trying to keep a newsletter under a certain time), this one’s handy:

words per minute calculator

And if you’re the kind of person who likes readability scores (I am, and I had no idea what half of them meant at first), this helps you connect difficulty to speed expectations:

Two more that come up more than you’d think:

• chapter length calculator — because “12 chapters left” is meaningless without context.
• book word count calculator — if you want a cleaner estimate than a single words-per-page guess.

So why does everyone get this wrong? Because pages are what we can see, and word count is what actually matters, and the visible thing always wins until you’ve been burned by it a few times.

That’s a lot of reading time!

FAQ (the stuff people ask me in DMs)