Komga is 6 years old !

Back then Komga didn't even have a user interface, and at first it could only be used as a Tachiyomi (now Mihon) source.

Komga has been using SQLite to store its data for around 5 years (v0.48.0 - July 2020), and while it works very well most of the time, some users have experienced bottlenecks on some systems.

In order to boost performances, Komga will enable the SQLite WAL mode (Write-Ahead Logging) by default in the near future.

Since WAL does not work over a network filesystem, release 1.23.0 has introduced a startup check to ensure the databases are located on a local filesystem. Even without WAL, this is a good practice for SQLite performance.

If Komga does not start anymore after the upgrade to 1.23.0, check the logs or the documentation.

Version 1.9.0 contains the second feature drop for Ebooks support.

It brings nice additions to the initial release, most notably the read progress will be kept when reading and restored, same as with other books.

The analysis process of EPUB files was also revamped, and some EPUB files that were not analyzed before should be working fine now.

While the first release forced all the EPUB files through the Epub Reader, this release brings back compatibility with the Divina Reader for pre-paginated EPUB files containing only images. This also restores support for the Pages API, and thus the compatibility with Tachiyomi, or any OPDS-PSE client.

Head over to the Release Notes for more details on all the new features and fixes.

Version 1.8.0 is bringing a long awaited feature: proper eBook support!

Github issue #221 has been opened for more than 3 years, and has finally been tackled.

What you need to know​

• eBooks behave like any other book in Komga, in regards to series or metadata. You can even mix comic books and ebooks in the same series.
• only EPUB format is supported. Other formats will not be supported in the future.
• existing EPUB files will be re-analyzed. If you had image-only EPUB, those may not be compatible anymore with third-party clients.
• the web EPUB reader is a very first version, and does not support saving progress. Read progress saving and restore will come in a future release.
• any book in Komga can be read with WebPub compatible clients.
• There will be issues. EPUB is a complex format, and many EPUB files are not properly built. Raise issues on Github for support.

Other recent changes you may have missed​

In case you haven't kept up with the release notes since version 1.0.0, here are the most significant changes:

• Komga is now available as a desktop app, and is available in the Microsoft Store
• Multiple settings are now configurable from the Server Settings screen. You may need to cleanup your configuration file and remove deprecated entries.
• Thumbnails size can now be configured in Server Settings.
• Background task management has been revamped, and now supports proper parallel executions (configurable in Server Settings).
• Komga now has support for One-Shots.
• a Command Line Interface was added to update forgotten password for the admin account.

The future v1.0.0 will bring some breaking changes, this guide will help you to prepare for the next major version.

Before upgrading​

• If you run Docker, it is advisable to use the 0.x tag instead of latest. You will be able to decide when you want to upgrade, especially if you are updating containers automatically.
• Backup your database.sqlite. You can find it in the configuration directory, by default:
  • on Windows: %USERPROFILE%/.komga/database.sqlite
  • on Unix: ~/.komga/database.sqlite
  • on Docker: in the directory you mounted as /config

Breaking changes​

• The minimum Java version required will be Java 17:
  • If you run Komga using the jar, you will need to make sure your Java version is sufficient by running java -version.
  • If you run Komga using Docker, you don't need to do anything.
• The hashing algorithm for files and pages will change. Previous hashes for files and pages will be deleted. On startup, if hashing is enabled, Komga will re-hash files and pages using the new algorithm.
• The default port will be changed from 8080 to 25600:
  • If you use Docker, you will need to update your container or compose configuration to expose the new port.
  • You may need to adjust your reverse proxy settings.
  • You can still change the port through configuration.