AppImage /AppImageKit

Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat

★ 9,467⑂ 587👁 193⑃ 373● 922▤ 14
NOASSERTIONCreated 2013-04-14appimage.org
Download: obsoleteobsolete-13 ↓132020-12-31
-2
Daily
9,467
stars
587
forks
193
watchers
373
prs
922
issues
14
releases

README

AppImageKit   

The __AppImage__ format is a format for packaging applications in a way that allows them to
run on a variety of different target systems (base operating systems, distributions) without further modification. 

Using the AppImage format you can package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, Ubuntu, Fedora, Debian and derivatives.

Copyright (c) 2004-24 Simon Peter  and contributors.

https://en.wikipedia.org/wiki/AppImage

Providing an AppImage for distributing application has, among others, these advantages:
- Applications packaged as an AppImage can run on many distributions (including Debian, Ubuntu, Fedora, openSUSE, Linux Mint, and others)
- One app = one file = super simple for users: just download one AppImage file, make it executable, and run
- No unpacking or installation necessary
- No root needed
- No system libraries changed
- Works out of the box, no installation of runtimes needed
- Optional desktop integration with appimaged
- Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
- Can optionally GPG2-sign your AppImages (inside the file)
- Works on Live ISOs
- Can use the same AppImages when dual-booting multiple distributions
- Can be listed in the AppImageHub central directory of available AppImages
- Can double as a self-extracting compressed archive with the --appimage-extract parameter

Here is an overview of projects that are distributing AppImages.

If you have questions, AppImage developers are on AppImage on irc.libera.chat.

 AppImage usage

Running an AppImage mounts the filesystem image and transparently runs the contained application. So the usage of an AppImage normally should equal the usage of the application contained in it. However, there is special functionality, as described here. If an AppImage you have received does not support these options, ask the author of the AppImage to recreate it using the latest tooling).

 Command line arguments

If you invoke an AppImage built with a recent version of AppImageKit with one of these special command line arguments, then the AppImage will behave differently:

- --appimage-help prints the help options
- --appimage-offset prints the offset at which the embedded filesystem image starts, and then exits. This is useful in case you would like to loop-mount the filesystem image using the mount -o loop,offset=... command 
- --appimage-extract extracts the contents from the embedded filesystem image, then exits. This is useful if you are using an AppImage on a system on which FUSE is not available
- --appimage-mount mounts the embedded filesystem image and prints the mount point, then waits until it is killed. This is useful if you would like to inspect the contents of an AppImage without executing the contained payload application
- --appimage-version prints the version of AppImageKit, then exits. This is useful if you would like to file is

Top issues

Discussions

Latest release

obsolete 13 2020-12-31
[!WARNING]
 Obsolete version. DO NOT USE THIS VERSION ANYMORE.
 
 Please switch to the new version at
 https://github.com/AppImage/appimagetool/releases/tag/continuous
 
 If this causes issues in your CI workflow you are unable to resolve, please comment here so that we can help you.

This version is merely kept around for legacy compatibility. It is not recommended to be used anymore and is no longer actively supported.


Build log: https://github.com/AppImage/AppImageKit/runs/454445892

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON