Important

As of October 10, 2025 the GIMP snap moved to the upstream project and is now taken care of by the GIMP project.

The new snapcraft.yaml can be found here, but existing users of the snap should notice no immediate changes.

GIMP - The GNU Image Manipulation Program

This is the snap for GIMP, "The Free & Open Source Image Editor". It works on Ubuntu, Fedora, Debian, and other major Linux distributions.

Install

snap install gimp

(Don't have snapd installed?)

Published for with 💝 by Snapcrafters

Third-Party Plugins

This snap contains a generic plug for supporting third-party plugins over snapd's content interface. To integrate such plugins, a content producer snap must provide a slot of the form:

slots:
  gimp-plugins:
    interface: content
    content: gimp-plugins
    source:
      read:
        - $SNAP/plugin-a
        - $SNAP/plugin-b
        - $SNAP/my-plugins.conf
        - $SNAP/libs-for-my-plugins

where plugin-a and plugin-b provide code for running two distinct plugins, and libraries for the plugins are installed in libs-for-my-plugins. Additionally, the gimp snap supports appending directories to LD_LIBRARY_PATH so it can find .so files shipped by content producer snaps that are connected to the gimp-plugins interface. It does so by searching for files named add-ld-library-path inside directories named with a .conf suffix (my-plugins.conf in the example above). The add-ld-library-path file should list one directory per line, with paths relative to top-level directory of the gimp-plugins content interface ($SNAP/gimp-plugins). For example, in the example above the add-ld-library-path file could be as simple as:

libs-for-my-plugins

This assumes that all .so files required by the plugins are shipped inside this single directory.

An example for the QT G'MIC plugins for GIMP can be found here.

How to contribute to this snap

Thanks for your interest! Below you find instructions to help you contribute to this snap.

The general workflow is to submit pull requests that merges your changes into the candidate branch here on GitHub. Once the pull request has been merged, a GitHub action will automatically build the snap and publish it to the candidate channel in the Snap Store. Once the snap has been tested thoroughly, we promote it to the stable channel so all our users get it!

Initial setup

If this is your first time contributing to this snap, you first need to set up your own fork of this repository.

1. Fork the repository into your own GitHub namespace.

2. Clone your fork, so that you have it on your local computer.

3. Configure your local repo. To make things a bit more intuitive, we will rename your fork's remote to myfork, and add the snapcrafters repo as snapcrafters.

   git remote rename origin myfork
   git remote add snapcrafters https://github.com/snapcrafters/gimp.git
   git fetch --all

Submitting changes in a pull request

Once you're all setup for contributing, keep in mind that you want the git information to be all up-to-date. So if you haven't "fetched" all changes in a while, start with that:

git fetch --all -p

Now that your git metadata has been updated you are ready to create a bugfix branch, make your changes, and open a pull request.

1. All pull requests should go to the stable branch so create your branch as a copy of the stable branch:

   git checkout -b my-bugfix-branch snapcrafters/candidate

2. Make your desired changes and build a snap locally for testing:

   snapcraft --use-lxd

3. After you are happy with your changes, commit them and push them to your fork so they are available on GitHub:

   git commit -a
   git push -u myfork my-bugfix-branch

4. Then, open up a pull request from your my-bugfix-branch to the snapcrafters/candidate branch.

5. Once you've opened the pull request, it will automatically trigger the build-test action that will launch a build of the snap. You can watch the progress of the snap build from your pull request (Show all checks -> Details). Once the snap build has completed, you can find the built snap (to test with) under "Artifacts".

6. Someone from the team will review the open pull request and either merge it or start a discussion with you with additional changes or clarification needed.

7. Once the pull request has been merged into the stable branch, a GitHub action will rebuild the snap using your changes and publish it to the Snap Store into the candidate channel. After sufficient testing of the snap from the candidate channel, one of the maintainers or administrators will promote the snap to the stable branch in the Snap Store.

Maintainers

• @lucyllewy
• @frenchwr

License

• The license of both the build files in this repository is MIT