> ## Content Index
> Fetch the complete content index at: https://thegimp.net/llms.txt
> Use this file to discover other available public pages before exploring further.

# Install GIMP on Ubuntu: Snap, Flatpak, AppImage or APT
- URL: https://thegimp.net/install-gimp-linux/
- Published: 2026-11-15T14:13:00.000Z
- Updated: 2026-11-18T11:38:54.000Z
- Description: Choose a current GIMP package for Ubuntu, keep its update route clear, and check personal resource folders before removing an older installation.
- Author: Elena Morris
- Tags: Install, versions and devices

To install GIMP on Ubuntu, use the stable Snap or the official Flatpak linked from [GIMP's download page](https://www.gimp.org/downloads/?ref=thegimp.net). I'd choose the Snap on an Ubuntu desktop that already has snapd, because installation and updates stay in one familiar package manager; choose Flatpak if you already use Flathub. Ubuntu's APT package is another option, but 22.04 and 24.04 still supply GIMP 2.10\. The current AppImage needs a recent distribution, so it isn't a universal workaround for an older Ubuntu installation.

Pick one route below and finish its installation before launching it. If you're replacing an existing GIMP, first [find and back up the old copy's personal resource folders](#resources), then close it before opening the replacement. Some current packages share settings.

[Choose a package](#choose) · [Snap](#snap) · [Flatpak](#flatpak) · [APT](#apt) · [AppImage](#appimage) · [Fix installation problems](#problems) · [Keep your resources](#resources)

## Which GIMP package should you use on Ubuntu?

Check your Ubuntu release and CPU if you're unsure which download fits. The system's [os-release file](https://www.freedesktop.org/software/systemd/man/latest/os-release.html?ref=thegimp.net) identifies the distribution and release; [uname -m](https://manpages.ubuntu.com/manpages/noble/en/man1/uname.1.html?ref=thegimp.net) reports the machine architecture:

```
cat /etc/os-release
uname -m
```

Read `PRETTY_NAME` or `VERSION_ID` for the release. For GIMP's AppImages, `x86_64` selects the x86\_64 file and `aarch64` selects the ARM64 file. An unsupported CPU or distribution needs a compatible package, not a renamed download.

The [Snap Store listing](https://snapcraft.io/gimp?ref=thegimp.net) names the verified **GIMP team** publisher, and the [Flathub repository](https://github.com/flathub/org.gimp.GIMP?ref=thegimp.net) identifies itself as the upstream team's official package. Both carry GIMP 3.2.8, the stable release linked by the project. Check those identities when a software centre offers several results with similar names.

__Choose the installation route, then use that route for updates__
| Your priority                                  | Choose                | What to check first                                       |
| ---------------------------------------------- | --------------------- | --------------------------------------------------------- |
| Current GIMP with Ubuntu's existing Snap setup | [Snap](#snap)         | GIMP team publisher and latest/stable channel             |
| Current GIMP through Flathub                   | [Flatpak](#flatpak)   | Whether you're keeping a user or system installation      |
| A package maintained in Ubuntu's repositories  | [APT](#apt)           | The candidate version for your Ubuntu release             |
| A standalone application file                  | [AppImage](#appimage) | The CPU architecture and current distribution requirement |

Snap and Flatpak include supporting components, so their first installation can download more than the application alone. Don't use the app's listed download size as a total disk-space requirement, or assume one package format will edit images faster without comparable measurements.

These are desktop Linux instructions. [A Chromebook needs its Linux development environment](https://thegimp.net/gimp-on-chromebook/) before Linux package commands apply. Other distributions need their own Snap or Flatpak setup; Ubuntu's `apt` commands don't apply to every Linux system.

## Install the stable GIMP Snap

Open Terminal and enter `snap list`. If it lists installed snaps, continue below. If Ubuntu reports that `snap` isn't found, the [Snap Store's Ubuntu instructions](https://snapcraft.io/install/gimp/ubuntu?ref=thegimp.net) give this prerequisite:

```
sudo apt update
sudo apt install snapd
```

After adding snapd, log out and back in, or restart, so the session picks up its paths. Ordinary Ubuntu desktop installations usually already have it; some flavours don't.

1. Check the package with `snap info gimp`. Look for the GIMP team publisher and the version under `latest/stable`.
2. Install that stable channel:  
```  
sudo snap install gimp --channel=latest/stable  
```  
Read the prompt, enter your administrator password if requested, and wait for the installation to finish.
3. Launch the Snap directly:  
```  
snap run gimp  
```
4. For a terminal version check, close GIMP and use `snap run gimp --version`. A bare `gimp --version` can resolve to a different installed package.

Snap refreshes packages automatically. To request an update for this one now, use `sudo snap refresh gimp`. If `snap info gimp` shows that an existing copy tracks a preview channel, first back up its resources, then use `sudo snap refresh gimp --channel=latest/stable` to follow the ordinary stable track.

## Install the official GIMP Flatpak

On Ubuntu, install Flatpak using the package command in [Flathub's Ubuntu setup instructions](https://flathub.org/en/setup/Ubuntu?ref=thegimp.net):

```
sudo apt update
sudo apt install flatpak
```

The following route installs GIMP for your Linux account, using the reference file supplied by GIMP's download page. It also offers to add the required remote when it's missing. You don't need to install a separate graphical Flatpak shop to use these commands.

If Flatpak already has a GIMP installation, inspect it before adding another:

```
flatpak list --app --columns=application,version,installation
```

[Flatpak distinguishes user and system installations](https://docs.flatpak.org/en/latest/using-flatpak.html?ref=thegimp.net) for both applications and repositories. A system copy is available to all accounts; a user copy belongs to the account that installed it. Keep the scope consistent through installation, launch, updates and removal.

1. Install the per-user package:  
```  
flatpak install --user https://flathub.org/repo/appstream/org.gimp.GIMP.flatpakref  
```  
Check that the proposed application is `org.gimp.GIMP` from Flathub. Accept the required repository and runtime prompts, then wait until installation completes.
2. Restart after the initial Flatpak setup so the desktop can pick up application integration. Launch the stable user copy with:  
```  
flatpak run --user org.gimp.GIMP//stable  
```
3. Close GIMP, then check its version with:  
```  
flatpak run --user org.gimp.GIMP//stable --version  
```  
The `//stable` suffix selects the branch; it doesn't freeze GIMP at one patch release.

Update this installation with `flatpak update --user org.gimp.GIMP`. For a deliberately system-wide installation, use `--system` instead of `--user` in the install, run, info, update and uninstall commands. Adding a user remote doesn't automatically add the same remote to the system installation.

## Install Ubuntu's APT package after checking its version

The distribution package follows Ubuntu's repositories. It doesn't necessarily follow the release on GIMP's website: [Ubuntu's package archive](https://packages.ubuntu.com/search?section=all&keywords=gimp&searchon=names&exact=1&suite=all&ref=thegimp.net) lists these GIMP series.

__GIMP versions in the Ubuntu archive__
| Ubuntu release | GIMP version | Practical consequence                                  |
| -------------- | ------------ | ------------------------------------------------------ |
| 22.04 LTS      | 2.10.30      | GIMP 3 plug-ins and interface instructions won't match |
| 24.04 LTS      | 2.10.36      | Choose Snap or Flatpak if you need GIMP 3              |
| 26.04 LTS      | 3.2.2        | GIMP 3.2, with Ubuntu's own package updates            |
| 26.10          | 3.2.6        | GIMP 3.2, behind the upstream 3.2.8 patch release      |

Your configured repositories, including any added PPA, determine the actual candidate. Refresh the index and inspect it before installing:

```
sudo apt update
apt-cache policy gimp
```

`Installed` is the APT-managed version already present; `Candidate` is the version APT proposes. The [apt-cache manual](https://manpages.ubuntu.com/manpages/noble/en/man8/apt-cache.8.html?ref=thegimp.net) explains that these queries use local package metadata, which is why updating the index comes first.

If the candidate meets your needs, install it through [Ubuntu's package manager](https://documentation.ubuntu.com/server/how-to/software/package-management/?ref=thegimp.net):

```
sudo apt install gimp
```

Wait for completion, then launch `gimp`. If you have several packages, close all GIMP windows first and check `command -v gimp` before trusting that launcher. Use APT for later updates to the APT package; it won't update a separate Snap, Flatpak or AppImage.

If APT reports no installation candidate, check that its index updated successfully and that Ubuntu's **universe** component is enabled in your software sources. GIMP is in universe. Fix repository errors before installing; an old tutorial's PPA command isn't a substitute for diagnosing the configured sources.

## Run the AppImage on a supported distribution

GIMP supplies AppImages for **x86\_64** and **AArch64/ARM64**. Its [current AppImage requirement is Debian 13 or a newer distribution](https://www.gimp.org/downloads/?ref=thegimp.net). The file bundles an application, but it doesn't replace every system library. I'd use Snap or Flatpak on an older Ubuntu release rather than alter system libraries to satisfy an AppImage.

1. Download the file for your CPU from GIMP's official page. Save it in a folder where you intend to keep it, rather than moving it after creating a shortcut.
2. Open Terminal in that folder and calculate its SHA-256 checksum. For the current x86\_64 file:  
```  
sha256sum GIMP-3.2.8-x86_64.AppImage  
```  
Compare the complete value with the checksum beside that exact file on GIMP's download page. If it doesn't match, stop and download the correct file again.
3. Make the file executable, then run it, following the [AppImage launch procedure](https://docs.appimage.org/introduction/quickstart.html?ref=thegimp.net):  
```  
chmod +x GIMP-3.2.8-x86_64.AppImage  
./GIMP-3.2.8-x86_64.AppImage  
```  
Use your downloaded filename throughout. The ARM64 build is `GIMP-3.2.8-aarch64.AppImage`.

Launch this file directly if a desktop shortcut keeps opening an old GIMP. To update, download and verify the new AppImage, then change any shortcut to point at the new file. APT, Snap and Flatpak won't replace the AppImage you kept in a folder.

## Fix the common installation and launch problems

### GIMP is installed, but the launcher is missing or opens an older version

First close every GIMP window. Run the package-specific launch command above, then check the version of that copy. A successful Snap or Flatpak install doesn't remove an older APT launcher, and the command `gimp` doesn't identify every installed package.

If the explicit command works but GIMP isn't in the application menu, complete the restart or new-login step for the package manager you just added. Don't reinstall through another format simply to make an icon appear. Once the correct copy opens, pin that launcher and remove an obsolete shortcut only after checking where it points.

### Flatpak says GIMP or the Flathub remote isn't installed

List the installed applications and configured remotes:

```
flatpak list --app --columns=application,version,installation
flatpak remotes
```

Look at the installation scope as well as the application ID. A system installation won't be found by a run command restricted to `--user`; a remote added for one scope isn't automatically present in the other. Use the matching scope, or rerun the reference-file installation for the scope you've chosen.

### The AppImage reports Permission denied, FUSE or a missing library

For `Permission denied`, check that you've marked the correct file executable and that its storage location permits execution. If the terminal specifically reports FUSE, follow the [AppImage project's distribution-specific FUSE instructions](https://docs.appimage.org/user-guide/troubleshooting/fuse.html?ref=thegimp.net). On Ubuntu 24.04, the library package was renamed `libfuse2t64`; older instructions name `libfuse2`. Don't replace Ubuntu's FUSE 3 installation with an obsolete FUSE package.

A `GLIBC` version error is a different problem. Recheck GIMP's distribution requirement and CPU download, then choose a supported package route. Installing a FUSE library doesn't make an older system meet the AppImage's library requirements.

### GIMP opens, but can't reach pictures on an external drive

Confirm the drive is mounted and that your Linux account can open the file in the file manager. For the Snap, inspect its connections:

```
snap connections gimp
```

If the `gimp:removable-media` plug has an empty slot and you want GIMP to access that storage, connect it with:

```
sudo snap connect gimp:removable-media
```

The [removable-media interface](https://snapcraft.io/docs/reference/interfaces/removable-media-interface/?ref=thegimp.net) covers mounted storage under `/media`, `/run/media` and `/mnt`. It grants access to those locations subject to normal file permissions; don't assume it's disconnected without checking.

The official GIMP Flatpak requests broad host-filesystem access in its [package manifest](https://github.com/flathub/org.gimp.GIMP/blob/master/org.gimp.GIMP.json?ref=thegimp.net). A blanket claim that it can only open files in your home folder is inaccurate. Inspect your installed copy with `flatpak info --user --show-permissions org.gimp.GIMP`; local overrides can change the permissions. The [Flatpak command reference](https://docs.flatpak.org/en/latest/flatpak-command-reference.html?ref=thegimp.net#flatpak-info) also documents `--file-access=PATH` for checking a particular location. Investigate the mount, Unix permissions and any overrides before granting broader access.

## Keep brushes, plug-ins and settings when changing packages

Before first opening a replacement package, inspect the existing GIMP: choose **Edit > Preferences > Folders** and select a category such as **Brushes**. Note its personal paths, close GIMP and back those folders up. Once the replacement is running, inspect its Preferences too. The [Data Folders preferences](https://docs.gimp.org/3.2/en/gimp-prefs-folders-data.html?ref=thegimp.net) distinguish the supplied system folder from your personal folder; add resources to a personal writable folder and leave the supplied files alone.

[![GIMP Brush Folders on Linux: writable personal /home/editor/.config/GIMP/3.2/brushes and system /app/share/gimp/3.0/brushes.](https://storage.ghost.io/c/da/21/da2186e6-6044-4206-b621-584ed1984ab7/content/images/2026/11/install-gimp-linux-imagefix-ui-20261117.webp)](https://storage.ghost.io/c/da/21/da2186e6-6044-4206-b621-584ed1984ab7/content/images/2026/11/install-gimp-linux-imagefix-ui-20261117.webp?ref=thegimp.net)

Read the writable personal folder from the GIMP copy you will keep; this Flatpak example uses the host configuration directory. [Open the Linux Brush Folders preferences at full size](https://storage.ghost.io/c/da/21/da2186e6-6044-4206-b621-584ed1984ab7/content/images/2026/11/install-gimp-linux-imagefix-ui-20261117.webp?ref=thegimp.net).

For current official GIMP 3.2 builds, the usual host configuration is `~/.config/GIMP/3.2`. GIMP's [configuration-directory code](https://github.com/GNOME/gimp/blob/GIMP%5F3%5F2%5F8/libgimpbase/gimpenv.c?ref=thegimp.net) deliberately resolves the host GIMP folder for Flatpak and Snap too, with build and environment overrides. A generic Flatpak path under `~/.var/app/org.gimp.GIMP/`, or Snap's `~/snap/gimp/` data root, is therefore insufficient to identify your brushes. Two packages can share personal settings.

1. Save your open work, close all GIMP copies, and back up the personal configuration/resource folders identified in Preferences. Keep this backup outside any application-data directory you plan to delete.
2. Back up your XCF projects separately. An application backup and a project backup serve different purposes.
3. Launch the replacement explicitly. Check its version, open a copy of an existing XCF, and confirm the layers and resources you need before retiring the old package.
4. For missing custom resources, copy only the compatible items into the personal folder shown by the replacement. Before [installing a plug-in](https://thegimp.net/install-gimp-plugins/), check its GIMP version and package support. A GIMP 2.10 executable doesn't become compatible with GIMP 3 by moving it.

For a missing typeface, follow the [font setup guide](https://thegimp.net/add-fonts-to-gimp/) using the folder shown by this build. Keep the previous configuration backup while you check the new copy; avoid running two versions against shared settings at the same time.

## Remove the old package after checking the replacement

Use the command for the package you intend to remove. Read its proposed changes before confirming; don't run every removal command in this table.

__Remove only the old installation route__
| Old package    | Removal                                                  | What to protect                                                                              |
| -------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| Ubuntu APT     | sudo apt remove gimp                                     | Review dependent removals. A routine switch doesn't require \--purge or blanket cleanup.     |
| User Flatpak   | flatpak uninstall --user org.gimp.GIMP                   | Keep the explicit scope; omit \--delete-data during a routine switch.                        |
| System Flatpak | flatpak uninstall --system org.gimp.GIMP                 | Check the prompt identifies the system installation you intended.                            |
| Snap           | sudo snap remove gimp                                    | Back up relevant data first. Don't add \--purge if you want Snap's normal recovery snapshot. |
| AppImage       | Close it, then remove the old file and obsolete shortcut | Keep your separate projects and personal resource folders.                                   |

[Flatpak's \--delete-data option](https://docs.flatpak.org/en/latest/flatpak-command-reference.html?ref=thegimp.net#flatpak-uninstall) removes the application's data directory under `~/.var/app` and its permissions. [Snap removal](https://snapcraft.io/docs/tutorials/get-started/?ref=thegimp.net) removes internal application data and normally creates a recovery snapshot beforehand. Neither mechanism justifies deleting a shared GIMP configuration folder or skipping your own backup.

Open the remaining GIMP through its explicit package route once more, confirm the version and check an image. Use that same route to [update GIMP later](https://thegimp.net/update-gimp/), and keep the project and resource backups until you're satisfied with the replacement.