Install GIMP on Mac: Apple Silicon, Intel and first launch

Choose the correct Mac build, install it in Applications and keep your editable project separate from its exported image.

A pear and closed silver laptop appear on the front of five thin matte prints, with window and garden photos behind on cream.

To install GIMP on a Mac, download the official stable DMG for your chip, open it and drag GIMP.app into Applications. Choose Apple Silicon / ARM64 for an Apple chip or Intel / x86_64 for an Intel processor; the current GIMP 3.2 package needs macOS 11 Big Sur or newer. I'd use the direct DMG for a first installation because it keeps the download, installed app and update route easy to identify.

After copying, launch GIMP from Applications. The installation is ready for image work when that copy opens a picture, saves an editable XCF and exports a separate image you can reopen.

About This Mac shows Chip: Apple M2 Pro and macOS: Ventura 13.3.1 (a), with both rows highlighted.
This Apple M2 Pro example needs the ARM64 download; read your own Chip or Processor entry and macOS version before choosing a package. Open the Mac chip and macOS fields at full size.

Check the chip and macOS version before downloading

Open Apple menu → About This Mac. Read both the chip or processor entry and the macOS version. Apple explains that Apple Silicon Macs show Chip, while Intel Macs show Processor; the age or size of the computer isn't a reliable substitute.

What About This Mac showsWhat to chooseCheck before continuing
Chip: Apple M…Apple Silicon / ARM64 DMGThe filename ends in -arm64.dmg.
Processor: Intel…Intel / x86_64 DMGThe filename ends in -x86_64.dmg.
macOS earlier than 11Pause the current GIMP 3.2 installation.Changing the chip download won't remove the macOS requirement.

The official GIMP download page lists the stable release, separate Mac builds and macOS 11 minimum. Select its macOS section if the page detects another operating system. Use the stable release offered there rather than a version number in an old tutorial or a search advert. GIMP 3.2.8 is the stable package used for the version-specific advice below.

If your Mac runs an older macOS release, check Software Update for the macOS versions compatible with your Mac. An archive download is a different decision: older GIMP packages have their own requirements and lack later fixes. Don't treat an old Intel download as a way to make the current release support an incompatible system.

Use the official stable download

Choose the direct Mac download unless you already use BitTorrent. Both routes on GIMP's page are distribution choices; you don't need a separate downloader, browser extension or paid activation key. GIMP is free software that can also be used commercially.

There are two common wrong turns. The GIMP team doesn't supply a package on Apple's App Store, so an App Store listing isn't the team's official Mac distribution. Its development downloads are experimental builds intended for testing; their troubleshooting instructions aren't the normal stable installation procedure.

The stable page also publishes a SHA-256 checksum for each DMG. If you verify a download, compare it with the entry for the same version and architecture: an Intel file and an Apple Silicon file have different hashes. A matching checksum confirms a match with the published file; it doesn't replace reading a security alert or checking where you obtained the download.

For an optional file check, open Terminal and type shasum -a 256 followed by a space. Drag the downloaded DMG from Finder into Terminal to insert its path, then press Return. The shasum tool's -a 256 option calculates SHA-256. Compare the full hash at the start of the output with the matching file on GIMP's page. If it differs, don't open that copy; check that you compared the correct file, then download it again from the official page.

Open the DMG, copy GIMP, then launch the installed app

A DMG is a disk image containing the application. Opening it makes that image available in Finder; it doesn't mean you've copied GIMP into Applications yet.

  1. Finish the download. Find the .dmg in your browser's downloads or Finder's Downloads folder. Check the arm64 or x86_64 part before opening it.
  2. Open the disk image. Double-click the DMG. Wait for its Finder window to appear.
  3. Copy GIMP into Applications. Drag GIMP.app onto the Applications folder in that window, or into Applications in Finder. Let the copy finish. If an existing GIMP.app is already there, follow the backup and update steps before replacing it.
  4. Open the installed copy. In Finder, select Applications and open GIMP from there. Respond to a first-launch confirmation only after checking the application and download you chose.
  5. Eject the mounted image. After copying and launching the Applications copy, use the eject control beside the mounted GIMP disk in Finder. Keep the DMG until you're satisfied the installed copy works.

Apple's Mac installation instructions start by opening the downloaded disk image and following its installation route. For GIMP, keep the source and installed copy distinct. If GIMP only seems available while the disk image is mounted, return to the copying step and launch it explicitly from Applications.

A managed work or school Mac can require an administrator's approved installation process. If copying or opening the app is blocked by that policy, contact the administrator with the exact message; repeated downloads won't change the device's permissions.

Read the launch message before choosing a fix

macOS uses different messages for an ordinary downloaded app, an unverified developer and damaged or malicious software. Apple's app-security guidance separates these cases. Treating every one as a prompt to force the app open is poor advice.

Message or symptomWhat to do next
Downloaded from the internet; asks whether to openCheck that it's the GIMP copy you downloaded from the official page. Confirm only if that's the app you intended to open.
Developer cannot be verified / Apple cannot check for malicious softwareCheck the source and install the current stable package first. If the warning remains, use Apple's guidance for that exact message. Its per-app Open Anyway route is conditional on being certain the app is trustworthy and unmodified.
“Is damaged” or “will damage your computer”Stop using that copy. Don't remove quarantine or disable Gatekeeper to force it open. Obtain a fresh official download; if the warning persists, contact the GIMP team or your device administrator.
Not supported on this MacRecheck both the macOS minimum and the Intel/Apple Silicon choice. A correct architecture can't compensate for an unsupported macOS version.
Blank or incomplete interface on an older GIMP buildSave and quit if possible, then update to the current stable build. If it continues, record the GIMP version, macOS version and chip when reporting the problem.

For Intel users in particular, the GIMP 3.2.8 release notes report consistent Python notarisation to address Gatekeeper warnings, along with a fix for the Mac blank-interface startup bug. I'd update an affected older installation before adopting a workaround from a forum. That release note is a reason to try the corrected package, not a guarantee that every launch failure has the same cause.

Don't use a global Gatekeeper-disable command, a quarantine-removal command or broad security permissions as routine installation steps. They don't establish that a file is the right build or that it hasn't been modified.

Confirm the installed version and open a simple image

With GIMP active, choose GIMP → About and read the version. The About dialog identifies the running GIMP version and provides Check for updates; on macOS the application menu holds commands that cross-platform instructions may place under Help or Edit. If the version is unexpected, quit GIMP and launch the Applications copy explicitly.

The Mac menu bar is at the top of the screen. Click GIMP's window first so you're reading its menus rather than Finder's. For preferences steps, use Settings or Preferences in the GIMP menu; the Mac application-menu definition includes the preferences and About commands.

  1. Make a working copy of an ordinary JPEG or PNG in a folder you can find again.
  2. Choose File → Open in GIMP and select that copy. This opens the image as a project; Open as Layers serves a different task, adding an image to a project that's already open.
  3. Check that the picture appears and that you can select its layer. For a useful first operation, follow the crop walkthrough or resize the whole image.

Starting with a JPEG or PNG keeps the installation check simple. A camera RAW file may need a separate loader: GIMP's RAW explanation describes the role of darktable or RawTherapee. Failure to import that format doesn't by itself prove the application was installed incorrectly.

If GIMP can't reach Desktop, Documents or Downloads

On macOS Ventura 13 or newer, check System Settings → Privacy & Security → Files & Folders. Apple's folder-access controls let you enable access to specific locations for an app. On Big Sur 11 or Monterey 12, use System Preferences → Security & Privacy → Privacy → Files and Folders, as shown in Apple's Monterey instructions. Allow the working folder you need, then retry opening or exporting there.

A folder-access problem doesn't automatically call for Full Disk Access. Keep the permission change tied to the location that's failing. If GIMP opens a local JPEG but cannot reach one protected folder, solve that location's access rather than reinstalling the whole application.

Save the editable project and export a separate image

Choose File → Save As, give the project a clear name such as first-edit.xcf and select your working folder. XCF keeps the layer structure for later edits. It doesn't preserve Undo history, so saving the master isn't a way to retain every earlier step.

Next choose File → Export As. Give the output a different name and a suitable extension, then complete the format's export dialog. GIMP uses Export As for delivery formats and asks before overwriting an existing file.

File you needUseCheck after saving
An editable GIMP masterSave As → .xcfReopen in GIMP and confirm the expected layers remain.
An image with transparencyExport As → .pngThe intended areas are transparent; the exported image has the right dimensions.
An ordinary opaque photographExport As → .jpgCheck the chosen background, visual quality and file destination.

Keep the original, XCF and export as distinct files. Reopen the export in Preview and check the image you would send. An export alone doesn't save your layered working project, and a recipient expecting a JPEG won't gain editable layers from receiving an XCF they can't open.

Use Homebrew if it's already your app-management route

If you already maintain a working Homebrew installation, the GIMP cask installs the app into Applications. You don't need to add Homebrew just to follow this guide. It has its own macOS and hardware support requirements, separate from the GIMP DMG's minimum.

In Terminal, inspect the cask and then install it:

brew info --cask gimp
brew install --cask gimp

Homebrew's GIMP cask selects the architecture-specific DMG from GIMP's official download server. Open GIMP from Applications afterwards and confirm the running version just as you would with the direct download.

If Homebrew reports an existing /Applications/GIMP.app, stop before forcing an overwrite. Save your projects and identify whether the existing app came from a direct DMG or Homebrew. Back up its personal resources, then choose one route to manage that application. Mixing a manual replacement with a package-manager record makes the next update harder to understand.

The stable cask also conflicts with gimp@dev. If you previously installed the development cask, identify and back up that setup before switching; don't solve the conflict by adding force flags.

Update without losing projects, brushes or settings

Before an update, save every open project. Keep project backups in their normal working location, then back up personal GIMP resources separately. The application bundle, an XCF document and your personal brushes are different things.

The GIMP manual places the usual Mac 3.2 configuration folder at ~/Library/Application Support/GIMP/3.2/. In the running app, check GIMP → Settings/Preferences → Folders for personal brushes, patterns and other resources. The resource-folder documentation distinguishes personal folders from the bundled system folders. Copy the identified personal folder to a backup after quitting; preserve any custom resource folders you added elsewhere too.

For a direct DMG installation, download the current stable build for the same Mac architecture, open its image and copy GIMP.app into Applications, replacing the existing application only after those backups. Launch from Applications and check the version and a copied XCF. The About dialog's update check helps locate a newer download; it isn't a reason to assume the application has already replaced itself.

For a Homebrew-managed installation, update Homebrew's package information and then request the GIMP cask upgrade:

brew update
brew upgrade --cask gimp

The Homebrew command reference distinguishes update, which refreshes package information, from upgrade, which upgrades an installed package. Check the app afterwards. When moving from GIMP 2 to GIMP 3, restore extra plug-ins selectively: the plug-in installation guide covers version compatibility. On an Apple Silicon Mac, also check whether extra plug-ins need their own Apple Silicon update.

Remove GIMP while keeping the work you made

Save your projects, quit GIMP and keep the resource backup. For a manually installed DMG copy, remove GIMP.app from Applications using Apple's app-removal route. If Homebrew manages it, use brew uninstall --cask gimp so its installation record is updated too.

Don't add Homebrew's --zap option when your aim is only to remove the application: zap also removes associated files, which can include settings and resources. Leave your original images and XCF projects alone. If you reinstall later, use the same chip and macOS checks rather than restoring an old app bundle simply because it's already on a backup drive.

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.