Your ePub Is Fine. Kobo Disagrees. Blame Adobe

A perfectly good ebook got called “corrupt,” and commenters are dragging Adobe hard

TLDR: An author’s ebook passed every official check but still failed on Kobo, with Adobe’s old reading software emerging as the likely culprit. Commenters turned it into a mini-drama about outdated tech, messy standards, and why some people have given up and gone back to PDF.

A writer did everything “right,” handed readers a clean, checked ebook file, and still got hit with the dreaded “corrupted” label on Kobo devices. That sent the community straight into detective mode — and blame landed fast on Adobe’s aging ebook software, the hidden engine behind Kobo’s reader. The mood in the comments? Equal parts rage, smug validation, and tired laughter. One person basically said this is why they stick to PDF: if the “official” format turns into a standards maze, why bother? Another dropped the killer line of the thread: “It’s always CSS.” Translation for normal people: somehow, some tiny formatting rule is always the villain in these tech meltdowns.

But not everyone was ready to burn Adobe in the town square. One commenter pushed back, arguing the software may be old, but that doesn’t automatically make it “broken” if newer styling tricks were never guaranteed to work in the first place. That kicked off the classic standards war: is the real problem bad software, or a modern file format that keeps moving the goalposts while old devices get left behind? Meanwhile, another commenter tossed in a corporate plot twist: Adobe already sold this ebook tech off to Wipro Engineering, which only added to the “abandonware energy” of the whole saga. And for pure comedy, one reader compared the author’s pain to a student crying over a thesis that wouldn’t compile — because nothing says tech trauma like discovering your masterpiece fails at the very last second.

Key Points

  • André Klein says his newly published DRM-free EPUB passed epubcheck validation, including epubcheck 3.3.
  • A reader reported that the book was shown as corrupted on Kobo devices, and the problem persisted even with a compliant EPUB2 version.
  • The same EPUB reportedly worked on Amazon Kindle, Apple Books, Thorium, and other reading platforms.
  • Klein found that Kobo uses Adobe’s RMSDK rendering engine, which the article describes as an older EPUB stack originating around 2010 and only lightly updated for EPUB3.
  • Testing the file in Adobe Digital Editions reproduced the failure, and the software did not provide a useful error message.

Hottest takes

"It’s always CSS." — L-four
"I’ve avoided epub opting for pdf" — anenefan
"I wouldn’t call the renderer broken" — charcircuit
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.