GIMP 3.2.8 is out, and whether you get it today depends less on GIMP than on how you installed it. OMG! Ubuntu's report on the release calls it the fourth maintenance update in the 3.2 series, which first launched in March 2026. It's a routine fix release: faster Preferences loading, better dialog positioning, improved right-to-left text support, and a small set of security updates for libraries GIMP bundles. There are no new features, but the security fixes are a good reason to know how your copy gets updated.
Publishing speed for each channel varies. The release report only says that vendor-store installs will receive the update there, so check. Nothing below claims one format is always first.
The commands are marked unverified because they follow each tool's standard usage and have not been run. Run the verification step after each one.
Step one: find out how your GIMP was installed
Before comparing anything, work out what you have. Run these in a terminal (unverified):
type -a gimp
gimp --version
flatpak list --app | grep -i gimp
snap list gimp
type -a gimp lists every gimp launcher on your PATH. A path like /usr/bin/gimp points to a distro package or a snap wrapper, so check the other commands too. gimp --version should print a version string such as 3.2.x.
flatpak list prints a row with the application ID org.gimp.GIMP if you have the Flatpak. snap list gimp prints a row with a version and revision if the Snap is installed, or an error saying it is not.
If none of those match, you may be running an AppImage, which is just a file you downloaded. Check your Downloads folder or the launcher's Exec= line in your menu entry. You can also open Help > About inside GIMP to see the version. You can have more than one copy installed, which is a common reason the wrong version opens.
How each method gets updates
Start with the official GIMP download page. Per the release report, it offers Linux AppImages and points to Flathub and the Snap Store as alternatives. Those are the upstream-facing routes. The distro package is the odd one out, because your distribution decides when it changes.
| Method | Update mechanism | Version freshness | Sandboxing | Plugin and file access | Best for |
|---|---|---|---|---|---|
| Distro package (apt, dnf, pacman) | System updates | Set by your distro; stable releases often hold a version for the whole release cycle (general behavior, check yours) | None | Full access to system files and tools | People who want one update path and stability |
| Flatpak (Flathub) | flatpak update or your software center | Depends on when the Flathub maintainers publish; check | Yes, with permissions you can adjust | Plugins and files outside granted paths can be blocked | People who want newer builds on any distro |
| Snap | Automatic background refresh by snapd | Depends on the publisher's channel; check with snap info | Yes, via confinement and interfaces | Limited by connected interfaces | Ubuntu users who want hands-off updates |
| AppImage | You download a new file | Whatever you last downloaded from the official site | None by default | Full access as your user | People who want a portable copy or a second version |
The table leaves out speed rankings on purpose. GIMP's documentation does not publish a comparison of how quickly each channel ships a given release, so any claim of a permanent winner is unproven.
Commands to check and update, per method
All of these are unverified until you run them. The verification step is the same each time: run gimp --version or the format's own query and confirm the number changed. We cover related ground in see also: wine wow64 mode explained: should you switch prefixes?.
Distro package. On Debian or Ubuntu, apt policy gimp shows installed and candidate versions. If the candidate is older than the current release, updating won't help. The repository simply doesn't have the new version yet.
Update with sudo apt update && sudo apt install --only-upgrade gimp. On Fedora, use dnf info gimp and sudo dnf upgrade gimp. On Arch and Manjaro, use pacman -Qi gimp and sudo pacman -Syu. Verify with gimp --version.
Flatpak. flatpak info org.gimp.GIMP prints the installed version and commit. flatpak remote-info flathub org.gimp.GIMP shows what Flathub currently offers. Update with flatpak update org.gimp.GIMP.
If remote-info shows an older version than the release, the update hasn't landed yet. Launch it with flatpak run org.gimp.GIMP and confirm in Help > About.
Snap. snap info gimp lists channels and the version in each, so you can see what the stable channel carries. snap list gimp shows what you have. sudo snap refresh gimp forces a refresh now, and snap refresh --time shows the automatic schedule. Verify with snap list gimp again.
AppImage. Make the file executable with chmod +x, then run it with --version (for example ./GIMP-3.2.8-x86_64.AppImage --version; the real filename may differ). To update, download the new file from the official site and replace the old one. The release report does not say whether the official AppImage supports in-place updating, so check the download page before assuming it does.
Sandbox, plugins and file access
This is where most real headaches live. A distro package and an AppImage run as you, with access to your home folder, external drives and any scripts or helper programs on the system. Nothing to configure, and nothing protecting you either.
Flatpak and Snap restrict what GIMP can reach. That helps when you open files from unknown sources, but it can bite. A plugin that calls an external program installed on the host may not find it. A folder on a mounted drive may not show up in the file dialog.
For Flatpak, flatpak info --show-permissions org.gimp.GIMP lists what is granted, and flatpak override --user --filesystem=/path can widen access (unverified; read the flatpak documentation first). For Snap, snap connections gimp lists the connected interfaces.
Plugin paths also differ. Flatpak keeps its data under ~/.var/app/org.gimp.GIMP/, and Snap under ~/snap/gimp/, while native and AppImage builds normally use ~/.config/GIMP/. This is an inference from how those formats usually store data, so confirm the exact folders in Edit > Preferences > Folders inside your own GIMP. The version folder name may differ from the series number, so don't assume.
Switching and rolling back without losing settings
Back up before you change anything. Open Preferences > Folders to find your configuration folder, then copy it somewhere safe (unverified example: cp -a ~/.config/GIMP ~/GIMP-config-backup). Do the same for any custom brushes, patterns, scripts and plugins that live outside it. Check that the backup isn't empty with ls ~/GIMP-config-backup.
To switch, install the new format first. Launch it once so it creates its folders, close it, then copy the relevant files from your backup into its config location. Keep the old install until the new one opens your files and sees your plugins.
Don't copy a whole config folder blindly between very different versions. If something misbehaves, copy shortcuts and settings files selectively.
Rollback options differ:
- Snap:
sudo snap revert gimpreturns to the previous revision (unverified). - Flatpak: you can pin an older commit. List history with
flatpak remote-info --log flathub org.gimp.GIMP, then runsudo flatpak update --commit=HASH org.gimp.GIMP(unverified; use--userequivalents if installed per-user). - Distro package: rollback means installing the older package version from your repository, which varies by distro.
- AppImage: keep the previous file. It's the simplest rollback of all.
Decision checklist and who should choose what
Ask yourself four things. Do you need the newest release soon after it appears? Do your plugins rely on tools outside GIMP? Do you open files from untrusted sources? Do you want updates to happen without you? Your answers point at a method.
If you want the freshest build with minimal fuss on any mainstream distro, Flatpak is a sensible default. Check remote-info and accept the permission rules. If you're on Ubuntu and prefer updates to happen on their own, Snap fits, though it's worth reading snap info gimp to see which channel you follow.
If you rely on plugins that shell out to system programs, or you value one update path for everything, the distro package is the least surprising choice. You accept whatever version your release carries. If you want to try a new release alongside your working setup, or run GIMP from a USB stick, the AppImage is the cleanest tool, as long as you remember to download the next one yourself.
Whatever you pick, re-run the version check after the next release instead of assuming it arrived.
