If you bought a Kobo, you probably bought it for the same reason most people did. It reads EPUBs, it doesn't lock you into Amazon, it has Bluetooth on the higher-end models, and the Pocket integration means your saved articles show up beside your books. The Kobo Libra Colour, Clara Colour, Sage, Elipsa — they are good devices, made for people who care about owning their books rather than renting them.
What you probably did not buy your Kobo for was text to speech. And that is good, because it does not have any.
This is the honest piece on Kobo audio in 2026. What works, what doesn't, what the Kobo subreddit threads keep asking, and the one path that actually lets you turn an ebook you already paid for into something you can listen to on the commute. The path goes through Kobo Web Reader at readnow.kobo.com, and it requires CastReader. Everything else either doesn't exist or doesn't work.
What Kobo Hardware Actually Does
Let's get the device story out of the way. Kobo's current eReader lineup — Libra Colour, Libra 2, Clara Colour, Clara BW, Sage, Elipsa 2E, Forma — has zero on-device TTS for ebooks. Not "limited TTS." Not "TTS for some books." None at all. There is no menu, no setting, no firmware toggle, no jailbreak. The hardware does not include a text-to-speech engine. Kobo never shipped one.
The Bluetooth-enabled models (Sage, Libra 2 onwards, Elipsa) can stream audio over wireless headphones, but only audio that already exists. Specifically: audiobooks you separately purchased through the Kobo store, or audiobooks included with a Kobo Plus Listen subscription. Putting a Kobo Sage next to a Bluetooth speaker and pressing play on an ebook does not produce audio. It produces nothing.
This trips up new Kobo owners constantly. The Bluetooth icon on the device suggests audio capability — and there is audio capability, but it's audiobook playback, not TTS conversion of the ebook you're reading. Different feature, same hardware, gets confused all the time.
If you are reading this on a Kobo eReader and wondering whether you missed a setting: you didn't. There is no setting. The hardware is silent on purpose.
Why Kobo Doesn't Have TTS
The same reason Amazon doesn't, basically. Audiobook publishers pay for narration rights separately, and they consider TTS of the ebook a competing product. When Amazon shipped TTS on the Kindle 2 in 2009, the Authors Guild publicly threatened legal action. Amazon backed down within weeks. Every subsequent Kindle either dropped TTS entirely or made it publisher-controllable per title. By 2016 it was effectively gone.
Kobo, owned by Rakuten since 2012, watched that fight from the side and made a pragmatic choice: don't ship the feature in the first place. No press, no controversy, no Authors Guild lawsuits. Just no TTS. Build a parallel audiobook business — Kobo Plus Listen, launched as a subscription in 2024 — and direct customers there.
This is not a Kobo-specific failing. It is the entire e-reader industry colluding (informally, by mutual exhaustion) to keep TTS out of e-readers because the audiobook publishers will not have it.
What Kobo can do, and what it does well, is the open-format reading experience. EPUB without DRM is a real thing on Kobo. Adobe Digital Editions transfers work. OverDrive library books open natively. Pocket articles sync. None of that helps you listen, but all of it makes the platform genuinely better than Kindle in other ways. Use the Kobo for what it's good at; route the listening through somewhere else.
The Kobo Mobile App Story
Same answer. Kobo for iOS and Kobo for Android render books beautifully, support all the standard adjustments — fonts, line spacing, margins, light/dark mode — and have no built-in read-aloud.
The system-level workarounds exist on both platforms but are imperfect.
On iOS, you can enable Speak Screen (Settings → Accessibility → Spoken Content → Speak Screen). Then in the Kobo app, swipe down from the top with two fingers, and iOS reads the visible page using Siri's voice. Works. Two complications: it doesn't auto-flip pages, so you read a page, the voice finishes, you swipe forward, repeat for 12 hours of a novel; and it reads everything visible, including the page number and the chapter heading every page, which gets old fast.
On Android, TalkBack does roughly the same thing. Enable it under Settings → Accessibility → TalkBack, then long-press a paragraph in the Kobo app to start reading from there. Same drawbacks: no auto page turn, robotic voice, accessibility-tool quirks like reading every UI element you accidentally touch.
For occasional use these work. For listening to a whole book on a commute, neither is what you actually want.
Kobo Plus Listen Is a Different Thing
Kobo Plus Listen is the audiobook subscription. It launched as part of the broader Kobo Plus subscription, which also has Kobo Plus Read for ebooks. The Listen tier gives you access to a curated catalog of professionally narrated audiobooks for a monthly fee.
It is genuinely a good audiobook service. The catalog is smaller than Audible's, but the price is significantly lower, and the books that are in it are properly narrated rather than TTS-generated.
Kobo Plus Listen is not what this post is about, though, because it doesn't help you with books you already own. If you bought The Goldfinch as a Kobo ebook three years ago and now want to listen to it on the way to work, Kobo Plus Listen requires you to find that the audiobook version exists in their catalog (it might) and pay for the subscription that includes it (probably yes). Or you skip Kobo Plus Listen entirely and pay Audible separately for the same audiobook (also a thing many people do).
Either way you are paying twice for the same book — once as ebook, once as audio. Which is fine if that's what you want, but it is not the same as "I want to listen to the book I already own."
The One Path That Works: Kobo Web Reader + CastReader
This is the actual answer. If you want to listen to a book you already own on Kobo, the path is:
- Open Kobo Web Reader at readnow.kobo.com on a desktop or laptop computer
- Sign in with your Kobo or Rakuten account
- Open the book you want to listen to (any book — paid, free preview, or library borrow)
- Install CastReader and click the extension icon
That's it. The book reads aloud with paragraph highlighting, pages flip automatically, and you can adjust speed, change the voice, or send the audio to your phone via Telegram for hands-free commute listening. It works on every book in your Kobo library, including OverDrive library borrows, regardless of language or publisher.
Why does this only work in the web reader and not the Kobo desktop app? Because Kobo's desktop apps render books inside an embedded WebKit / Chromium webview that browser extensions can't inject into. Same content, but the extension layer can't reach it. The web reader at readnow.kobo.com is the one surface that's open to extensions.
Why CastReader and not other TTS extensions? Because Kobo's web reader is built unusually. Each chapter loads as a separate iframe with srcdoc HTML — the actual book text lives inside iframe.contentDocument trees that standard extensions can't reach. Most TTS extensions read document.body, find nothing, and give up silently. CastReader was rebuilt specifically for this iframe-based layout in early 2026.
What Makes Kobo Web Reader Hard for TTS Extensions
If you want the technical detail (skip this section if you don't), here's what's going on under the hood.
Kobo's web reader is a spread reader. When you open a book at readnow.kobo.com, the page loads up to ~13 chapters into separate same-origin iframes, arranged horizontally. Each iframe contains an entire chapter's worth of HTML, paginated internally into horizontal CSS columns. Flipping pages applies a CSS transform: translateX(...) to the iframe stack, sliding the next page into view.
For a TTS extension to read this, it has to:
- Walk every accessible same-origin iframe and stitch them in reading order. The DOM order doesn't always match reading order; visual position does.
- Identify which iframe the user is currently looking at. The "first" iframe might be three chapters back. The visible iframe is whichever one has the largest intersection area with the outer viewport, which moves around as the user flips pages.
- Within that iframe, find the first paragraph that's actually onscreen. Not just "in the iframe somewhere" — visible right now, in the current viewport, after accounting for the column layout.
- Read forward across iframe boundaries with continuous audio and paragraph-level highlighting that crosses iframe edges seamlessly.
- Trigger Kobo's next-page button when the highlighted paragraph's last fragment is about to leave the viewport.
- Never roll the viewport backwards, because Kobo's transform animation can briefly leave paragraphs straddling two pages with negative coordinates, and a naive backward-pager would chase stale highlights into the previous page.
Standard TTS extensions do approximately none of these. They were built for normal web pages where document.body has the article in it. Kobo's reader is a different shape entirely.
CastReader's Kobo extractor handles all six. The result is that you click play, the book reads in your ear, the highlight follows along on screen, and when you reach the end of a page CastReader presses the next-page button without you touching anything. The experience is closer to a real audiobook than to a TTS hack.
Library Books Work Too
This is worth saying explicitly because it surprises people. If you borrow a book through OverDrive (also branded as Libby), and you read it on your Kobo, that book also shows up in Kobo Web Reader. CastReader reads it just like any other book. The borrow source doesn't matter — CastReader only sees the rendered text inside the iframe.
So your public library plus your Kobo plus CastReader equals: free audiobook access to the entire OverDrive library. Borrow a book, open it in Kobo Web Reader, click CastReader, listen on your commute. Return it through Libby when you're done. No subscription required.
This works around two parallel paywalls — the audiobook publisher paywall (which is why Kobo doesn't have TTS) and the audiobook-version-availability paywall (which is why even Kobo Plus Listen doesn't have every book). For library readers especially, it's the most practical single tool in the listen-to-books toolkit.
What About the Foreign-Language Catalog?
Kobo, owned by Rakuten, has the strongest non-English ebook catalog of the major platforms. French (FNAC partnership in France), German, Italian, Dutch, Japanese, and Portuguese-Brazilian catalogs are all substantially larger on Kobo than on Kindle for those markets.
CastReader supports natural AI voices in 40+ languages, and auto-detects the book's language from the EPUB metadata's <html lang> attribute. So a French Kobo book sounds French, a German Kobo book sounds German, and a Japanese Kobo book sounds Japanese — without you switching anything.
This is the part of Kobo's catalog that benefits most from CastReader, actually. Audiobook catalogs are heavily weighted toward English. If you read in another language regularly, your audiobook options are much more limited than your ebook options. CastReader closes that gap — every Kobo book in your library, in any of those languages, becomes listenable.
Send to Phone for the Commute
CastReader has a Send to Phone feature that's worth flagging here because it pairs particularly well with Kobo. The feature streams the audio from your desktop browser to a private Telegram bot that you can listen to on your phone. The desktop continues to flip pages automatically. You sit in the car, put on your earbuds, listen to your Kobo book without touching anything.
For commute listening this means: you don't have to move your Kobo library to your phone (you can't anyway, since the Kobo app has no TTS), and you don't have to buy the audiobook version separately (you can't always anyway, since not every book has one). You just have your laptop at home auto-flipping pages while you listen on your phone.
The setup is a one-time link of your CastReader extension to a Telegram bot, then it just works. No data plans, no extra apps beyond Telegram (which most people already have), no recurring fees.
The Pragmatic Recommendation
Use your Kobo eReader for distraction-free reading. That's what it's good at. The eInk screen, the long battery, the no-notifications environment — perfect for sitting down with a book.
Use Kobo Web Reader plus CastReader on a laptop for listening. Open the book on the laptop, press play, listen through speakers or headphones, or send to your phone for the commute. The laptop flips pages automatically. You don't touch anything.
This is split-device reading, which sounds awkward but works in practice better than trying to make any single Kobo surface do both jobs. The eReader is for the focused 30 minutes after dinner. The web reader plus CastReader is for the 45-minute commute, the dishes, the walk to the post office.
What I Wish Kobo Would Do
It is worth saying: this whole arrangement exists because Kobo cannot ship TTS without picking a fight with audiobook publishers. That is not Kobo's fault. The fight is impossible to win — Amazon already lost it.
What Kobo could do, without picking a fight, is officially support TTS extensions in the web reader. Document the iframe API. Provide hooks for accessibility tools that need to read the rendered content. Stop forcing third parties to reverse-engineer their iframe layout to make TTS work for users who already own the books.
Some of this is happening passively — the web reader is more accessible than the desktop app, and OverDrive integration brings library readers in. But formally embracing the accessibility extension ecosystem would be a small good thing Kobo could do that costs them nothing.
In the meantime: CastReader, Kobo Web Reader, your existing library, and a laptop. Free audiobook listening on every book you own, with no Kobo Plus Listen subscription, no Audible, no separate purchase, no DRM circumvention. It is the workaround. Use it.
