GIMP for Chromebook: the Linux route and a browser fallback

A compatible Chromebook can run GIMP’s Linux package. Check permissions and processor support, keep Flatpak commands in one user scope, and open a copy of your picture.

Cream-bordered prints of a potted cactus and blue cup stand on a closed graphite laptop with a grey back card

You can run GIMP on a Chromebook through its Linux development environment, provided the device supports Linux and your administrator allows it. Set up Linux, install Flatpak, then install the stable GIMP package from Flathub. I'd use this local route for layered photo work because the project stays on the Chromebook and you can keep an editable XCF alongside the finished image.

If Linux isn't available, use an approved browser editor or a remote GIMP service. Those are separate routes with different file-handling requirements; a Chrome Web Store extension doesn't install the desktop application into ChromeOS.

Check the Chromebook before downloading anything

Open Settings → About ChromeOS → Developers. Look for Linux development environment and Set up. This is the route in Google's current Linux setup instructions; older tutorials may put Developers under Advanced.

A school or work administrator can disable Linux. If the option is missing or blocked, check for an available ChromeOS update and ask the administrator whether Linux apps are permitted. Don't switch the Chromebook into OS Developer Mode to get around the restriction. The supported Linux environment doesn't require Developer Mode, and replacing ChromeOS or following a Crouton tutorial is a different project.

Select Set up and follow the prompts for the Linux account and storage allocation. When setup finishes, Terminal opens into a Debian environment. Use that Linux Terminal for the commands below, rather than Chrome's address bar or the separate crosh shell.

Read the Linux package architecture

In Terminal, run:

dpkg --print-architecture

This command prints Debian's package architecture. Match it to the builds listed on the official GIMP download page, which offers Flathub packages for x86_64 and ARM64.

Terminal resultWhat it means for this route
amd6464-bit x86, including compatible Intel and AMD processors. This corresponds to GIMP's x86_64 build.
arm6464-bit ARM, also called AArch64. This corresponds to GIMP's ARM64 build.
armhf, i386 or another resultDon't force an x86_64 or ARM64 download. Check the Debian package available for that environment or use the browser route.

Debian distinguishes amd64, arm64 and 32-bit architectures. A Chromebook being described as “ARM” doesn't by itself establish that its Linux environment can run the current ARM64 package. Flatpak normally selects the matching architecture; you don't need to download an Intel file manually.

Check storage in Linux as well as ChromeOS

Run df -h ~ in Terminal and read Avail for the filesystem containing your Linux home folder. The df command reports free filesystem space; this is more useful than assuming all free Chromebook storage is already available inside Linux.

Read the download and installed-size prompts before confirming an installation. Flatpak may need a runtime as well as GIMP, and an image project needs room for the source, XCF, exports and backups. There isn't one reliable download-size figure for every Chromebook. If space is tight, review the Linux storage allocation in Settings and the files you can safely move before installing.

ChromeOS Settings, About ChromeOS: Developers card with Linux development environment, Run developer tools, IDEs, and editors, and a Set up button
Use Set up in the Linux development environment card when the Chromebook and its administrator permit Linux apps. Open the ChromeOS Linux setup at full size.

Install stable GIMP in one Flatpak scope

Keep the Flathub repository and GIMP in the same per-user installation. The commands use --user consistently. Only installing Debian's Flatpak tool needs sudo; don't add it to the later Flatpak commands.

1. Install the Flatpak tool

Run these commands one at a time. Let each finish, read its proposed changes and confirm when you're satisfied.

sudo apt update
sudo apt install flatpak

Flathub's ChromeOS setup uses the Linux environment and Debian's Flatpak package. If APT reports an error, resolve that error before continuing; a later command won't repair an unfinished installation.

2. Add Flathub for your Linux user

flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

The Flatpak user option keeps this repository separate from a system-wide one. After adding it, save any work in other Linux apps. Right-click Terminal's shelf icon, choose Shut down Linux, then reopen Terminal. Flathub includes this Linux restart in its ChromeOS setup.

3. Install the stable application

flatpak --user install flathub org.gimp.GIMP//stable

Check that the proposed application is org.gimp.GIMP from flathub, on the stable branch. Review the permissions and size, then confirm. The app ID comes from GIMP's official Flatpak instructions; the Flatpak reference syntax lets you specify the stable branch explicitly.

Wait for the installation to finish successfully before closing Terminal. A Windows .exe or Mac .dmg isn't the package for this Linux environment. You also don't need a browser extension or a paid activation key: GIMP is free software.

If you visit GIMP's download page, its first Linux button may offer an AppImage. The current AppImage requires Debian 13 or a newer distribution. Don't substitute it for the Flatpak commands without checking your Linux environment; the existence of Linux support alone doesn't meet that package's requirement.

4. Launch that copy and check its version

flatpak run --user org.gimp.GIMP//stable

Use this command for the first launch even if a GIMP icon appears in the Launcher. It selects the same user installation and stable branch you just installed. In GIMP, open Help → About to read the version of the application that's running. The official stable release is GIMP 3.2.8; compare with the current download page when installing.

Once the correct app opens, you can launch it from the Chromebook Launcher. If the icon is missing, save work and restart Linux as above. Keep the command available until you've confirmed which copy the icon opens, especially if GIMP was previously installed through APT.

Open a picture from ChromeOS in GIMP

I'd start with one ordinary JPEG or PNG copied into Linux files. It makes the first open/save check simple and leaves the original alone. A camera RAW file or a complicated PSD adds a separate import question before you've established that file access works.

  1. Open the ChromeOS Files app and find a picture.
  2. Copy the picture, select Linux files in the sidebar, then paste it there. Use a copy rather than moving your only original.
  3. In GIMP, choose File → Open…. Browse your Linux home folder, select the copied picture and open it.
  4. Check that you recognise the image and that GIMP shows its layer in the Layers dock.

The ChromeOS developer guide documents copying files into Linux and sharing folders with Linux. If you want to work from an existing folder instead, right-click that folder in Files and choose Share with Linux. Shared locations appear inside Linux under /mnt/chromeos; browse that location from GIMP's file chooser.

ChromeOS Files app open in Linux files with harbour.jpg, 2.4 MB, JPEG image, while Downloads under My files keeps the original
Copy a practice picture into Linux files before opening it in GIMP; keep the original separately. Open the ChromeOS Linux files at full size.

There are two permission boundaries. ChromeOS must expose the file to Linux, and the application must be allowed to read that Linux path. Granting Flatpak access can't expose a folder ChromeOS hasn't shared. Conversely, sharing a folder with Linux doesn't override an app-specific restriction.

Google warns that files and permissions shared with Linux are available to its Linux apps. Share the folder you need, rather than your whole collection. The current official GIMP Flatpak declares broad Linux filesystem access, so don't assume the Flatpak label makes a shared folder private from GIMP.

Keep an editable XCF and a separate PNG or JPEG

Make a small edit to the practice copy, such as cropping its frame. Then complete the file round trip before starting an important project.

  1. Choose File → Save As… and save a clearly named project.xcf in your Linux working folder.
  2. Choose File → Export As…. Give the delivery image a separate name ending in .png or .jpg, choose its destination and complete the format's export dialogue.
  3. In ChromeOS Files, open Linux files and find both files. Copy the finished PNG/JPEG to the location you'll use to send it.
  4. Open that exported copy in ChromeOS and inspect the crop, dimensions and appearance. Reopen the XCF in GIMP to confirm that the working project is available for another edit.

GIMP saves its editable project as XCF and uses Export for other image formats. PNG can retain transparency; JPEG can't. Neither finished format replaces the layered XCF, and XCF doesn't preserve the session's undo history.

For a durable second copy, use storage such as Google Drive or an external backup, following your organisation's file policy. Google describes Downloads as temporary storage and warns that downloaded files can be deleted when space runs low. Copying an export into Downloads for an immediate upload is useful; leaving your only XCF there isn't a backup plan. Confirm that a cloud copy has finished syncing or an external copy has completed before deleting a local file.

Match the problem to the installation or file path

Start with the exact error. Repeating installation commands, changing permissions broadly or removing Linux can make a small problem harder to identify.

What you seeCheck next
No Linux setup optionCheck device support, ChromeOS updates and school/work policy. Use an approved browser route if Linux isn't offered or permitted.
flatpak: command not foundUse the Debian Terminal and check that sudo apt install flatpak finished successfully.
Flathub remote or GIMP “not installed”Inspect the user and system scopes below. A repository or app added to one scope doesn't appear in the other.
No matching package or architectureRead dpkg --print-architecture and the full Flatpak error. Don't force a different processor build.
GIMP opens, but the picture is missingFind the file in ChromeOS Files. Copy it into Linux files or share its folder, then browse the Linux path.
Linux sees the file; GIMP reports access deniedCheck effective app permissions, whether the file is readable and whether its folder is writable for saving. Avoid a blanket permissions reset.
Installation or saving runs out of spaceCheck Linux's df -h ~, ChromeOS storage and the selected destination. Move backed-up files deliberately; don't remove the Linux environment to free space while it holds your only project.
Two GIMP icons or an unexpected older versionLaunch the explicit Flatpak command and read Help → About. Check APT separately before removing either copy.

These read-only commands help identify a scope mismatch:

flatpak --user remotes
flatpak --user list --app
flatpak --system list --app
flatpak info --user --show-permissions org.gimp.GIMP//stable

The Flatpak info command can show the installed app's permissions. A failed user-scope info lookup can mean that copy isn't installed; it isn't evidence that GIMP lacks every file permission. For a shared-folder problem, copy one picture into Linux files and try that local copy. If it opens, the shared path is the place to investigate. If you previously restricted GIMP with a permissions tool, review that app's specific folder rules before granting broader access. If another Linux app also can't open, save your work and restart Linux, then the Chromebook if needed, as Google's Linux troubleshooting guidance recommends.

Large, layered images need more working space than a small JPEG. If the interface becomes unresponsive, preserve the XCF, close unrelated work and compare with a small ordinary image. Record the Chromebook model, ChromeOS version, GIMP version, installation route and exact message when seeking help. A claim that every 4 GB or 8 GB Chromebook performs the same won't diagnose your project.

Use Debian's APT package only after checking the candidate

APT is an alternative when you prefer the package maintained for your Debian environment. Its GIMP version follows the configured repositories, so don't assume sudo apt install gimp installs the same release as Flathub.

sudo apt update
apt-cache policy gimp

Read Installed and Candidate. The APT cache reports package selection from the configured sources; a candidate of (none) means this lookup offers no version to install. If the candidate is suitable, install and launch it with:

sudo apt install gimp
gimp

Check Help → About again. Instructions for GIMP 3 can differ from those for a repository's older 2.10 package, particularly for plug-ins. Don't add an Ubuntu PPA to Debian as a shortcut or install both routes simply to chase a missing Launcher icon. I'd keep one identified installation once the version, files and resources are confirmed.

Update the chosen package and protect Linux work

Before an update that changes the major GIMP version, back up your projects and custom resources. Then, for the per-user Flatpak route, save your work, quit GIMP and update that installation:

flatpak --user update org.gimp.GIMP//stable

Use flatpak --user update if you want to review updates for all Flatpak apps and runtimes in that user scope. Flatpak updates manage Flatpak applications and their runtimes; APT and ChromeOS updates are separate. For Debian packages, sudo apt update refreshes package information and sudo apt upgrade proposes available upgrades. APT's update command alone doesn't install them.

Back up projects and resources before replacing an installation

Identify any custom fonts and plug-ins in the copy you're using, save and quit, then back up your XCF files and resources. A second package can have different folders even when its icon looks the same.

ChromeOS also offers a complete Linux backup. In Settings, open the Linux development environment settings and find Back up and restore → Back up. Save the resulting .tini outside Linux and retain a durable copy. Google's backup instructions warn that this operation needs substantial free space.

Restore replaces the current Linux apps and data. Copy out newer projects before using it. Google also requires matching processor architectures when restoring a complete Linux backup onto another Chromebook. Don't use Restore or Remove Linux as a routine fix for a missing file or app icon.

Choose a browser editor or remote GIMP deliberately

If Linux isn't available, I'd choose an approved browser editor for a small crop, resize or layered composition before setting up a remote desktop. Photopea runs in a web browser. In its File → Open route, open a copy of the image; use Save as PSD for its editable project and Export As for a finished PNG or JPEG, as Photopea's saving instructions describe. Retain your original XCF separately when moving existing GIMP work between editors.

A remote GIMP service runs the application on another computer and sends the interface to your browser. It needs an active connection and a way to transfer files into and out of that service. Check its publisher, account or payment requirements, retention policy and download process before uploading a private photograph. Save an XCF and download it before ending a remote session.

Be precise about a listing labelled “GIMP Online”. The OffiDocs Chrome Web Store listing describes a remote integration and website-content handling, including server-side scanning of browsed pages for images. Read those permissions and the publisher's policy before installing it. Its name alone doesn't establish that it's the GIMP team's native application.

Local GIMP can edit local files offline once the app and required components are installed. Downloads, updates, cloud files and remote GIMP sessions still need their respective connections. On a managed Chromebook, both Linux apps and browser services remain subject to the organisation's policy. Choose the permitted route that lets you keep the editable project and retrieve the finished image.

Elena Morris

Elena Morris

Elena Morris is the GIMP image-editing and compositing editor at TheGIMP.net. She writes about selections, masks and layers, restrained retouching, compositing and export.