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

The first version of the UI was only added in October 2019. At that time I didn't know much about web development, but building on Vue 2 / Vuetify 2 helped me to build a good-looking UI that has worked quite well so far. It has become however quite difficult to maintain and evolve:

• There are practically no tests, meaning bugs can be introduced easily.
• There is a lot of duplicated code, mostly due to Vue 2 limitations.
• The whole development stack is tedious to work with, again due to what the javascript ecosystem was like in 2019.

While Vue 3 came out around the end of 2020, it brought so many breaking changes that it's practically impossible to migrate a project from Vue 2 to Vue 3. Vuetify itself only came up with its version 3 end of 2022, and even at that time most of the components were not ready yet.

This year I've started to work on a complete rewrite of the UI, using a more recent development stack, but also more experience under my belt.

As of now the foundations are sound and solid, and I've started rewriting the pages one by one. I am also using the rewrite as an opportunity to include feature requests that were difficult to add in the current version of the UI.

There is still quite a lot to do, so as usual I cannot provide any tentative release date, but I really hope this can be done in 2025. Stay tuned!

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.

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.

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.

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.