Calibre 9.13 Update Adds Tolino Firmware Compatibility and Resolves PDF Errors
230427, according to the Calibre project's release notes.
Calibre 9.13 is now available, addressing PDF output regressions and adding native support for Tolino firmware 5.11.230427, according to the Calibre project's release notes. The update is directly relevant for readers who route newspaper PDFs and Tolino-sourced content through Calibre's library and conversion pipeline, since PDF output stability affects downstream E-Ink rendering and on-device file integrity.
PDF Output Regression Fixes
The release lists PDF output regression fixes as the primary change set. Calibre's existing PDF Input engine — which performs automatic header and footer detection based on document analysis — is not the target of this patch; the fix applies to the output stage of the conversion chain. Users reprocessing newspaper PDF archives should verify output on their target E-Ink device before committing to batch conversion, as the release notes do not specify which prior version introduced the regression. Conversion behavior can be reverted via the PDF Input section of the Conversion dialog if a specific workflow requires the previous output path.
Tolino Firmware 5.11.230427 Support
Driver coverage now extends to Tolino firmware 5.11.230427. Tolino e-readers will be detected by Calibre without manual driver configuration, restoring direct sideload of PDFs and KEPUB files into the device's local library. For users maintaining parallel collections across Tolino and other E-Ink hardware — Kobo, PocketBook, Onyx Boox — this closes the typical post-firmware detection gap that previously required waiting for a follow-up Calibre build before new Tolino units could sync reliably.
Content Server Advisory
The 9.13 release does not address the previously disclosed remote code execution vulnerability affecting the Content server component introduced in Calibre 6.9.0. Any deployment exposing the Content server beyond localhost still requires password protection or network-level access controls, regardless of this update. Local desktop installations that do not run an active Content server are not affected. Users on Chromebooks who rely on folder-based device emulation should confirm that the new folder-as-USBMS behavior continues to work with their existing sideload paths after upgrade.