The Problem

Switching from Adobe Photoshop to GIMP means relearning tool positions, keyboard shortcuts, and workspace defaults. GIMP's default layout puts tools in different places than Photoshop, uses different shortcut keys for common operations like zoom and crop, and ships a generic icon and splash screen. PhotoGIMP removes that friction by shipping a pre-configured GIMP profile that mimics Photoshop's arrangement.

What This Does

PhotoGIMP is a configuration patch, not a GIMP plugin or extension. It replaces GIMP's user configuration files with Photoshop-style equivalents. The .config/GIMP/3.0/ directory contains the full set of GIMP settings: shortcutsrc remaps keyboard shortcuts to match Adobe's documented defaults, toolrc and the tool-options/ files reposition and pre-configure every tool (50+ tool-option files, from gimp-move-tool to gimp-warp-tool), and theme.css restyles the UI. The .local/share/ directory adds a custom icon set and desktop entry so the application appears as "PhotoGIMP" in the system menu.

The patch also includes a custom splash screen at .config/GIMP/3.0/splashes/splash-screen-2025-v2.png and a gimprc tuned for maximized canvas space. Documentation exists in English plus four translations (docs/README_it.md, README_pl.md, README_pt.md, README_ru.md).

How It Is Wired

There is no application code to trace. Execution begins when GIMP starts and reads its configuration from ~/.config/GIMP/3.0/. The patch works by overwriting those files: the user extracts the zip into their home directory, and GIMP's config loader picks up the new settings on next launch. The wiring is entirely declarative — no hooks, no scripts, no runtime logic.

The file with the widest blast radius is shortcutsrc, which changes every keyboard binding in one pass. The tool-options/ directory is the second-largest surface: each of the 50+ files sets defaults for a specific tool, and any GIMP update that changes a tool's options schema could break compatibility. The .desktop file in .local/share/applications/ is what makes the app appear as PhotoGIMP rather than GIMP in the launcher.

How To Use It

Setup: Requires GIMP 3.0 or newer. Run GIMP once and close it so the config directory exists. Download the release zip and extract it into your home directory, overwriting existing files.

Configuration: No environment variables or additional config files. The patch is the configuration.

Running it: Launch GIMP normally. The patch is applied at config-read time.

# Backup existing settings first
cp -r ~/.config/GIMP/3.0 ~/GIMP-3.0-backup

# Extract the patch into home (~)
unzip PhotoGIMP-linux.zip -d ~

# Launch GIMP
gimp

The README documents Flatpak installs explicitly; for distro-packaged GIMP the config path is the same (~/.config/GIMP/3.0).

Real-World Use

A designer migrating from Photoshop to GIMP on Linux installs GIMP via Flatpak, runs it once to generate configs, then extracts PhotoGIMP over ~/.config. On launch, the tool panel matches Photoshop's layout, the crop tool answers to C instead of Shift+C, and the workspace maximizes canvas area by default. The designer can work immediately without a relearning period.

Code Health & Issues

Static analysis found no CI/CD pipeline, no Dockerfile, no lockfile, and no committed secrets. Two test files are present, but the repo is configuration data — tests cannot meaningfully exercise it. There is a GPL v3 license. The lack of CI is a minor concern since there is no build step to validate; the real risk is version drift against GIMP's config schema.

Med - Configuration drift risk - GIMP 3.x updates may change tool-option schemas or shortcut names, silently breaking parts of the patch.

The Bottom Line

This is a well-documented, focused configuration package that does exactly one thing: makes GIMP 3 feel like Photoshop. It is not code you extend — it's a config set you apply and re-apply after GIMP updates. Suitable for Photoshop migrants and teams standardizing on GIMP; the main maintenance cost is keeping pace with GIMP's config schema changes.