Less than two months after shipping GIMP 3.2.0 — itself the first major feature release built on the GTK3 toolkit — the GIMP development team has pushed out version 3.2.2, a maintenance update that squashes more than 70 bugs and polishes a product that spent the better part of a decade in gestation. The release landed on July 10, 2025, and it tells a story not just about bug fixes but about whether the world’s most prominent free image editor can finally keep pace with its commercial rivals.
For years, GIMP’s development cadence was the butt of jokes in creative-software circles. The gap between GIMP 2.10 and GIMP 3.0 stretched so long that many users assumed the project had quietly stalled. It hadn’t. But the transition from GTK2 to GTK3, the overhaul of the color pipeline to support high-bit-depth editing, and the introduction of a non-destructive workflow consumed enormous engineering effort from a volunteer-heavy team. Now, with two point releases in rapid succession, the project appears to be operating under a fundamentally different rhythm.
What 3.2.2 Actually Fixes — and Why It Matters
According to Phoronix, GIMP 3.2.2 addresses 71 bugs, adds six new features, and incorporates 11 translation updates. The bug fixes span the application’s core editing tools, its scripting interfaces, and platform-specific quirks on Windows, macOS, and Linux alike. That breadth matters. GIMP’s cross-platform promise has always been one of its strongest selling points against Adobe Photoshop, but inconsistent behavior across operating systems has historically undermined that promise.
Among the more notable changes: improvements to how GIMP handles color management on displays, refinements to the text tool (long a source of frustration), and fixes to Script-Fu and Python-Fu — the two primary scripting environments that power automation and plugin development. Script-Fu, GIMP’s built-in Scheme-based scripting language, received particular attention. Several crashes tied to malformed scripts have been resolved, and the console’s error reporting has been tightened.
There are also fixes targeting the paint dynamics engine, the gradient tool, and layer group handling. Not glamorous. But these are the kinds of paper-cut issues that drive working professionals away from a tool. A gradient that renders incorrectly or a layer group that corrupts on save doesn’t just waste time — it destroys trust.
The six new features are modest in scope. They include quality-of-life improvements like better drag-and-drop behavior for layers and enhanced metadata handling for exported files. No headline-grabbing additions. That’s by design. The GIMP team has signaled that the 3.2.x series is about stabilization, not spectacle.
And stabilization is exactly what GIMP 3 needs right now.
The 3.0 release in March and the 3.2.0 release in May introduced sweeping architectural changes. Non-destructive editing — the ability to apply filters and adjustments as reversible layers rather than permanent pixel modifications — was the marquee addition. It’s a feature Photoshop has offered since the late 2000s, and its absence from GIMP was arguably the single biggest technical objection professionals raised against adopting the software. With it now in place, the question shifts from capability to reliability.
The Competitive Context: Photoshop, Krita, and the Subscription Economy
GIMP doesn’t exist in a vacuum. Adobe’s Photoshop remains the dominant force in raster image editing, and its subscription model — currently $22.99 per month for the Photography plan — continues to generate friction among users who resent paying indefinitely for software they once bought outright. That friction is real, but it hasn’t translated into mass defections. Adobe’s installed base, its integration with Lightroom and other Creative Cloud applications, and its AI-powered generative fill features keep most professionals locked in.
Then there’s Krita. Originally focused on digital painting rather than photo manipulation, Krita has steadily expanded its feature set and now overlaps significantly with GIMP’s territory. It ships with a more modern-feeling interface out of the box, supports non-destructive layer effects, and has cultivated a passionate community of illustrators and concept artists. For certain workflows, Krita is simply a better tool than GIMP — and it’s also free.
GIMP’s response has been to lean into its identity as a general-purpose image editor with deep scripting support, extensive file format compatibility, and a plugin architecture that allows third-party developers to extend the application in ways the core team never anticipated. The Script-Fu and Python-Fu improvements in 3.2.2 reinforce this strategy. Automation is where GIMP can differentiate itself from both Photoshop (which charges extra for batch processing features through Actions and scripting) and Krita (which has more limited automation support).
But let’s be honest. GIMP’s user interface remains its Achilles’ heel. The move to GTK3 improved things — high-DPI display support, better theming, more consistent widget behavior — but the application still feels like it was designed by engineers for engineers. Dialog boxes proliferate. Tool options aren’t always where you’d expect them. The learning curve is steep, and the defaults are unfriendly to newcomers. These are design problems, not engineering problems, and they won’t be solved by bug-fix releases alone.
The GIMP team knows this. In their development roadmap, interface overhauls are earmarked for future releases, potentially including a move to GTK4 in the longer term. But that’s a multi-year effort, and the project’s resource constraints are real. GIMP is developed primarily by volunteers, with some sponsorship from organizations like the GNOME Foundation. There is no venture capital. No corporate parent. No marketing department.
What there is, however, is momentum. Two releases in two months. Over 70 bugs fixed in a single point release. Active translation work across 11 languages. These are signs of a project that has found its stride after a long period of architectural upheaval.
What Comes Next
The GIMP team has indicated that 3.2.4 is already in the pipeline, with further stabilization work and potentially some additional non-destructive filter support. The project’s GitLab repository shows active development on CMYK soft-proofing improvements — a feature critical for print professionals — and continued work on the GEGL (Generic Graphics Library) backend that powers GIMP’s modern processing pipeline.
GEGL deserves a mention here because it’s the unsung engine behind everything that makes GIMP 3 feel different from GIMP 2. High-bit-depth color. Non-destructive editing. Hardware-accelerated rendering on supported GPUs. All of it flows through GEGL. Improvements to GEGL propagate directly into GIMP’s capabilities, and the library has been receiving steady updates alongside the main application.
For Linux users, GIMP 3.2.2 is already available through Flathub and most major distribution repositories. Windows and macOS installers are available from the official GIMP website. The Flatpak distribution method has become increasingly important for the project, as it allows the team to ship consistent builds across Linux distributions without worrying about dependency conflicts — a persistent headache in the Linux software world.
So where does this leave GIMP in mid-2025? In a stronger position than it’s been in years. Not because of any single feature or release, but because the project has demonstrated that it can ship regularly, fix problems quickly, and build on the massive architectural investment it made during the long 2.x-to-3.x transition. The software still isn’t Photoshop. It may never be. But for the millions of users who need a capable, free, cross-platform image editor — and for the developers who build workflows on top of its scripting infrastructure — GIMP 3.2.2 is a quiet but meaningful step forward.
The real test comes next. Can this pace hold?
WebProNews is an iEntry Publication