Integrating AppImages into Linux

Krita’s website recommends using the AppImage for Linux. AppImages are self-contained executables that bundle an application with everything it needs to run, which means fewer compatibility issues across distributions. In practice, it works well.

There is one minor hiccup: AppImages don’t automatically create .desktop files. These are a Linux convention that lets your system recognise applications in the launcher so you can pin them to menus or taskbars. A typical .desktop file looks like this:

[Desktop Entry]
Name=Your Application
Exec=/path/to/your/application.appimage
Icon=/path/to/icon.png
Type=Application
Categories=Utility;
Terminal=false

Without one, your AppImage will work fine when launched from a terminal or file manager, but it won’t appear in your application menu. Fortunately, creating one is straightforward.

Creating a .desktop file for an AppImage

1. Make the AppImage executable In a terminal, run:

   chmod +x ~/Applications/Krita.appimage

Note: When you see the ~ it means your home directory. It’s the same as typing /home/yourusername.

2. Create a .desktop file Create a new file in ~/.local/share/applications/:

   nano ~/.local/share/applications/krita.desktop

Use whatever editor you’re comfortable with – nano, Neovim, Kate, Gedit, or anything else.

3. Add the entry Paste the following, adjusting paths and details as needed:

   [Desktop Entry]
   Name=Krita
   Exec=/home/yourusername/Applications/Krita.appimage
   Icon=/home/yourusername/Applications/icons/krita-icon.png
   Type=Application
   Categories=Graphics;Photography;
   Terminal=false

Note: .desktop files don’t expand ~, so use the full path here instead of the shorthand.

4. Refresh your desktop environment Log out and back in. Alternatively, run:

   update-desktop-database ~/.local/share/applications/

Note that update-desktop-database works reliably in some environments but not all. When in doubt, a log out and in is the safest option.

Krita should now appear in your application launcher.

Managing multiple AppImages

If you use several AppImages, a bit of organisation goes a long way.

• Use a dedicated folder – ~/Applications/ is a common choice. It keeps everything in one place and makes backups easier.
• Include the version in the filename – e.g. krita-5.2.16.appimage. You’ll always know what version you have.
• Store icons in a subfolder – ~/Applications/icons/ keeps icon paths consistent and prevents broken references when you update an app.
• Updating is simple – replace the old AppImage with the new one. If you follow the naming convention above, it’s easy to track what’s current. Many AppImages also include a built-in updater.

Why AppImages?

I switched from Windows to Linux in 2024, moving through a dual-boot setup before eventually settling on Arch. My illustration workflow shifted from Affinity Designer to Krita, and Krita’s AppImage has been stable and dependency-free from day one.

The appeal of AppImages is straightforward: one file, self-contained, runs on any distribution. For tools you rely on daily, that portability and predictability is worth a lot.