“Your EPUB is fine. Kobo disagrees. Blame Adobe.”

An infuriating story about something most of us don’t really stop to think about: e-books and the rendering engines companies and software use to display them.

It’s the year 2026. Thanks to the horrendous [Adobe] RMSDK which Kobo decided to use as their backbone for all book rendering (probably for DRM reasons), a single line of perfectly valid CSS turns a perfectly valid EPUB file into a “corrupted file” on Kobo and just drops the whole book. No clear error message, no fallback. Just a massive fail.

↫ André Klein

The level of obnoxiousness goes even deeper: Kobo devices ship with a better, actually maintained renderer for e-books as well, but in order to have a book use it, the book file in question needs to have a specific file extension. Remember that e-book files are just packaged websites; there’s no reason to do any of this nonsense with two rendering engines, one of which is shit and frozen in time.

I have never had to do anything related to creating an e-book – I just put books on my own Kobo and read them – and even I am getting annoyed just reading this.

16 Comments

  1. 2026-06-15 12:02 pm
    • 2026-06-15 12:25 pm
    • 2026-06-15 12:33 pm
      • 2026-06-15 2:28 pm
        • 2026-06-16 6:46 am
          • 2026-06-16 12:21 pm
          • 2026-06-16 6:53 pm
          • 2026-06-17 4:07 pm
          • 2026-06-17 5:14 pm
          • 2026-06-19 2:25 am
          • 2026-06-19 2:34 am
  2. 2026-06-17 5:52 pm
    • 2026-06-17 7:53 pm
      • 2026-06-19 2:27 am
        • 2026-06-19 11:54 am
          • 2026-06-23 5:13 pm

Leave a Reply