After more than two decades of development under the GIMP 2.x series, the open-source image editor that has long served as the free alternative to Adobe Photoshop is nearing the finish line for its next major release. GIMP 3.2 Release Candidate 3 (RC3) landed on July 14, 2025, bringing with it more than 70 bug fixes and a handful of refinements that signal the development team is in the final stretch of polishing before a stable release.
The announcement, first reported by Phoronix, marks the third release candidate since the GIMP project shifted its focus to the 3.2 branch — a version that builds on the foundational overhaul introduced with GIMP 3.0 earlier this year. For industry professionals who have watched the GIMP project’s glacial but deliberate pace of development, this RC3 build represents a significant confidence signal that the stable 3.2 release could arrive within weeks rather than months.
A Long Road From GIMP 3.0 to 3.2
To understand the significance of GIMP 3.2, one must first appreciate what GIMP 3.0 represented. Released in early 2025 after years of development, GIMP 3.0 was the project’s first major version bump since GIMP 2.0 arrived in 2004. The 3.0 release brought a complete migration from the GTK2 toolkit to GTK3, a modernized user interface, non-destructive editing capabilities, improved color management, and a rewritten scripting API based on GObject Introspection. It was, by any measure, a generational leap for the software.
But as is common with major open-source releases that carry years of accumulated architectural changes, GIMP 3.0 shipped with rough edges. The development team acknowledged as much, positioning the 3.2 release as the version that would sand down those edges and deliver a more refined experience. According to the official GIMP release notes referenced by Phoronix, RC3 addresses over 70 bugs that were identified during the RC1 and RC2 testing cycles, alongside contributions from the broader open-source community.
What RC3 Brings to the Table
The GIMP 3.2 RC3 release is primarily a stability and bug-fix release, which is exactly what one would expect from a third release candidate. The development team has been focused on squashing regressions, fixing crashes, and addressing usability issues reported by testers. Among the areas of improvement are canvas rendering fixes, better handling of certain file formats, and corrections to tool behavior that had been inconsistent since the 3.0 release.
One area that has received particular attention is the scripting and plug-in infrastructure. GIMP 3.0’s migration to a new API broke compatibility with many older Script-Fu and Python-Fu scripts, and the 3.2 cycle has involved significant work to improve the stability and documentation of the new scripting system. For professional users and studios that rely on automated workflows — batch processing, custom export pipelines, or integration with other tools — the maturity of this scripting layer is a deciding factor in whether GIMP can serve as a viable production tool.
The GTK3 Migration: Still Paying Dividends
The move from GTK2 to GTK3, which was the single largest technical undertaking in the GIMP 3.x development cycle, continues to yield improvements in RC3. The GTK3 toolkit provides better support for modern display technologies, including HiDPI screens, Wayland on Linux, and improved color rendering. For photographers and digital artists working on high-resolution displays — now standard in professional environments — this is a meaningful quality-of-life improvement over the GIMP 2.x series, which looked increasingly dated on modern hardware.
The GTK3 migration also opens the door to future possibilities. The GTK project itself has moved on to GTK4, and while GIMP 3.x will remain on GTK3, the architectural work done during the 3.0 cycle makes a future GTK4 migration far less painful than the GTK2-to-GTK3 transition proved to be. The GIMP development team has indicated that GTK4 is on their radar for a future major version, though no timeline has been committed.
Non-Destructive Editing: The Feature Professionals Have Been Waiting For
Perhaps the most consequential feature introduced in the GIMP 3.0 cycle — and further refined in 3.2 — is non-destructive editing. This capability, which allows users to apply filters and adjustments as editable layers rather than permanently altering pixel data, has been a standard feature in Adobe Photoshop for years. Its absence from GIMP was frequently cited as the primary reason professional users could not adopt the open-source editor for serious work.
GIMP 3.0 introduced the initial implementation of non-destructive filters, and the 3.2 release candidates have been expanding and stabilizing this feature. While the implementation is not yet as comprehensive as Photoshop’s — not all filters support non-destructive application — the foundation is now in place, and the development team has indicated that expanding non-destructive support will be a priority in future releases. For studios and freelancers evaluating open-source alternatives to the Adobe Creative Cloud subscription model, this feature alone changes the calculus significantly.
The Competitive Context: Krita, Photopea, and Adobe’s Dominance
GIMP does not exist in a vacuum. The open-source and free image editing space has grown considerably in recent years. Krita, which began as a digital painting application, has expanded its feature set and now overlaps with GIMP in several areas. Photopea, a browser-based editor that closely mimics Photoshop’s interface and supports PSD files natively, has gained a substantial user base among casual and semi-professional users. And Adobe itself has introduced a web-based version of Photoshop, further raising the bar for what users expect from an image editor in 2025.
Against this backdrop, GIMP’s 3.2 release is not just a technical milestone — it is a statement of relevance. The project’s development pace has historically been a source of frustration for its community. The gap between GIMP 2.8 (released in 2012) and GIMP 2.10 (released in 2018) was six years. The gap between 2.10 and 3.0 was another seven years. The relatively rapid cadence of the 3.0-to-3.2 cycle, with multiple release candidates arriving in quick succession, suggests the project has found a more sustainable development rhythm.
Community Contributions and the Open-Source Development Model
The GIMP project remains an all-volunteer effort, funded primarily through donations and supported by the GNOME Foundation. Unlike Blender, which has attracted significant corporate sponsorship and now employs a full-time development team, GIMP relies on a smaller core of dedicated contributors. This reality shapes both the pace and priorities of development.
As reported by Phoronix, the RC3 release includes contributions from community members beyond the core team, a healthy sign for the project’s long-term sustainability. The new GObject Introspection-based API has also made it easier for third-party developers to write plug-ins in languages like Python 3, JavaScript, and Lua, potentially broadening the contributor base over time.
What Comes Next: The Path to Stable and Beyond
The release of RC3 suggests that GIMP 3.2 stable is imminent, though the development team has not committed to a specific date. In open-source development, the convention is to continue releasing candidates until no release-critical bugs remain, at which point the final RC is re-tagged as the stable release. If RC3 proves sufficiently stable based on community testing, it could be the last candidate before the official 3.2.0 release.
Looking further ahead, the GIMP project has outlined ambitions for the 3.4 and subsequent releases, including expanded non-destructive editing support, CMYK workflow improvements for print professionals, and continued performance optimization. The project’s roadmap also acknowledges the eventual need to address GTK4 migration, though this is considered a longer-term effort.
For the millions of users worldwide who depend on GIMP — from Linux desktop users who have no access to Photoshop, to educators teaching image editing without software licensing costs, to professional photographers seeking to reduce their Adobe dependency — the 3.2 release represents a tangible step forward. It may not grab headlines the way an AI-powered feature announcement from Adobe would, but for those who value software freedom and open standards, the steady progress of GIMP 3.2 is exactly the kind of news that matters.
from WebProNews https://ift.tt/IlncCGe
No comments:
Post a Comment