What playback speed does to an audiobook
Playback speed is a multiplier applied to recorded audio. At 1× you hear the narrator at the pace they were recorded, which for most audiobooks is somewhere between 150 and 160 words a minute — the range narrators are typically directed to read at. Move the dial to 1.5× and the same recording plays in two thirds of the wall-clock time. Nothing is cut. Every word is still there; they just arrive faster.
The number that changes is runtime, and runtime is what people actually budget. A full-length novel usually runs 10 to 12 hours. That's two weeks of half-hour commutes at 1×, and a little over one week at 1.5×. Choosing a speed is really choosing how many days the book takes, which is why the question gets typed into a search bar so often: how long is an audiobook at 1.5x, on the platform screen, right before a drive.
The math is one division. The reason nobody does it in their head is that audiobook runtimes are awkward numbers — 12h 20m, 6h 50m 30s, 32h 51m — and dividing those by 1.75 while merging onto a motorway is not a reasonable ask. That's the whole job of the audiobook speed calculator. The same division works for podcasts and recorded lectures, which is where most people first notice that speed is a dial rather than a setting.
How to use the audiobook speed calculator
- Type the runtime into the hours and minutes boxes. Copy it straight off the book's detail screen. The seconds box is optional — fill it in when you want the answer exact, which matters more than it sounds on a long book.
- Don't bother normalising the numbers. Anything 60 or over rolls up on its own, so typing 90 into minutes reads as 1h 30m. Decimal hours work too: 1.5 in the hours box becomes 1h 30m.
- Pick a speed. The chips cover the eight multipliers every major listening app offers, from 0.75× up to 3×. You can also type any speed between 0.25× and 5× into the field — 1.4× and 1.85× are perfectly valid, and the table makes room for them.
- Read the three numbers. Listening time is how long the book will take. Time saved is what you get back. The percentage tells you whether the trade is worth it.
- Scan the table underneath. It shows your book at every speed at once — computed from the runtime you typed, not from a generic ten-hour example — so you can see exactly where the returns flatten out. The Copy button puts the whole line on your clipboard.
There's no Calculate button, because there's nothing to wait for. The answer updates on every keystroke, and the page ends when the answer does.
The formula behind listening time
There is exactly one formula here, and it has no variants, no regional differences, and no expert disagreement behind it:
Listening time = runtime ÷ playback speed
Time saved = runtime − listening time
Runtime is the book's length as recorded. Playback speed is the multiplier your app is set to. That's both variables. Work one all the way through with a real book — a 12h 20m recording at 1.5×:
- Convert the runtime to seconds: (12 × 3,600) + (20 × 60) = 44,400 seconds.
- Divide by the speed: 44,400 ÷ 1.5 = 29,600 seconds, which is 8h 13m 20s.
- Subtract to get the saving: 44,400 − 29,600 = 14,800 seconds, or 4h 6m 40s — 33.3% of the book.
Now do the check that matters: 8h 13m 20s + 4h 6m 40s = 12h 20m, exactly. Listening time and time saved have to add back to the runtime you started with. If they don't, one of them is wrong.
That check is the reason step 3 subtracts instead of dividing again. Round the listening time and the saving separately and they drift a second or two apart, which is how a calculator ends up publishing 6h 50m 30s at 2× as 3h 25m 17s in its own worked example. The correct answer is 3h 25m 15s. The audiobook speed calculator rounds once, to the nearest whole second, and derives everything else from that single rounded number — so the two figures reconcile at every speed you try.
A 10-hour book at every speed
Here's the same recording — ten hours flat — across the eight speeds you'll find in a listening app. The audiobook speed calculator builds this table live from whatever runtime you enter; this one is printed so you can see the shape of it before you type anything.
| Speed | Listening time | Time saved | Share of the book |
|---|---|---|---|
| 0.75× | 13h 20m | 3h 20m added | 33.3% longer |
| 1× | 10h 0m | — | 0% |
| 1.25× | 8h 0m | 2h 0m | 20.0% |
| 1.5× | 6h 40m | 3h 20m | 33.3% |
| 1.75× | 5h 42m 51s | 4h 17m 9s | 42.9% |
| 2× | 5h 0m | 5h 0m | 50.0% |
| 2.5× | 4h 0m | 6h 0m | 60.0% |
| 3× | 3h 20m | 6h 40m | 66.7% |
Read down the Time saved column and the argument for moderate speed makes itself. The step from 1× to 1.5× hands back 3h 20m. The step from 2× all the way to 3× — a far more aggressive change, and a much harder one to follow — hands back only another 1h 40m. The savings are front-loaded, because you're dividing by a growing number: each extra quarter-step buys less than the one before it.
That's the practical case for sitting at 1.5× rather than pushing for 2.5×. You capture the bulk of the time at a speed most people can follow comfortably, on the first or second book. Note also that 1.75× is the row with seconds in it. Ten hours doesn't divide cleanly by 1.75, so the honest answer is 5h 42m 51s — not a tidied-up 5h 43m that no longer adds back to ten hours.
A quick way to audit any calculator like this one: add its two outputs together. If the listening time plus the time saved doesn't equal the runtime you typed, the tool is rounding twice and at least one number on your screen is wrong.
Where the arithmetic stops being the whole answer
Division tells you the ceiling, not the experience. A few things sit outside the formula and it's worth knowing which:
- Silence trimming. Some apps shorten the gaps between sentences on top of the speed setting. When that's on, you'll finish a little sooner than runtime ÷ speed predicts. Treat the answer here as the longest it will take.
- Pitch correction. Apps resample the audio and correct the pitch so the narrator doesn't turn into a chipmunk. The artefacts of that make 2× feel more effortful than the raw multiplier suggests.
- The material, not the multiplier. Comprehension holds up well to around 1.5× for most listeners, and recall starts to drop past 2×. But a memoir at 2× is fine where a philosophy text at 1.25× is already too fast. The reliable signal is rewinding: more than once a chapter means you've passed your speed for that book.
- The narrator's own pace. Narrators vary widely inside that 150–160 wpm band. A brisk reader at 1× can outrun a deliberate one at 1.25×, which is why runtime is the number worth comparing between books, not the speed setting.
Two boundaries in the audiobook speed calculator are deliberate. Below 1× it reports time added rather than a negative saving, because 0.75× is a real setting — language learners and note-takers live there — and "−3h 20m saved" is a worse way of saying "3h 20m longer". And speeds above 5× are capped, since no app plays faster than that and the answer would be fiction.
Related calculations
If you're deciding between the audiobook and the print edition, the reading time calculator does the other half of the comparison: words divided by reading pace, rather than runtime divided by playback speed. Pair it with the reading speed test first, so the words-per-minute figure you feed it is yours rather than an average — the two usually differ by more than people expect.
For studying from a lecture recording, the pomodoro timer is the natural companion: work out the listening time here, then split it into sessions you'll actually finish. If you're on the writing side of this and want to know how long your own script will run as audio, the word counter gives you the word count to divide by 150. And for the distance-over-time kind of speed rather than the playback kind, there's a separate speed calculator.
Frequently asked questions
What playback speed do most audiobook listeners settle on?
Between 1.5× and 1.8× is where regular listeners tend to land once they've adjusted. Almost nobody jumps straight to 2× and retains much, but almost everybody finds 1.25× indistinguishable from normal within a few hours. Step up a quarter at a time and stay at each speed until it sounds unremarkable. The adaptation is real, and it's faster than you'd guess.
How long is a 12-hour audiobook at 1.25x?
9h 36m, which gives you 2h 24m back — 20% of the book. The same 12-hour recording is 8h 0m at 1.5× and 6h 0m at 2×. The pattern holds for any runtime: 1.25× always returns a fifth of the book, 1.5× always returns a third, and 2× always returns half, regardless of how long the book is.
Why does 1.75x give an answer with seconds in it?
Because most runtimes don't divide evenly by 1.75. Ten hours at 1.75× is 5h 42m 51s — 20,571 seconds and a remainder that has to go somewhere. Rounding it up to 5h 43m would look neater but would no longer add back to ten hours when combined with the time saved. The seconds are shown only when they're not zero, so clean results stay clean: 6h 40m, not 6h 40m 0s.
Can it tell me what day I'll finish a book?
Not yet — that's a different question and it needs a second input, your daily listening budget. For now, take the listening time the audiobook speed calculator gives you and divide it by the hours you listen per day. A 12h 20m book at 1.5× comes to 8h 13m 20s, so at 45 minutes a day you're looking at about eleven days.
Does the time saved account for the pauses between chapters?
Yes, in the sense that those pauses are already inside the runtime you typed — the published length includes every silence in the recording, and dividing by the speed shortens them along with everything else. What the formula can't know is whether your app is trimming silence separately. If it is, expect to finish slightly ahead of the number here.
Is anything I type stored or sent anywhere?
No. The division runs in your browser and nothing leaves it. There's no account, no saved library, and closing the tab is all the cleanup there is. Microapp makes its money from membership rather than from your data, and 10% of every dollar it earns goes to charity, off the top, audited quarterly.