GIMP 3.2.2 arrives with interface tweaks, bug fixes, and file format improvements
GIMP keeps moving at a fast pace in 2026. Just two weeks after the release of GIMP 3.2, the team has already shipped GIMP 3.2.2, a maintenance update that brings bug fixes, improvements to image format handling, plug-in updates, and a few targeted UI/UX tweaks that make a real difference in daily use.
Worth remembering that GIMP 3.0 only celebrated its first anniversary since its big debut, and the project hasn’t slowed down since. This version doesn’t bring a revolution, but it solves real problems users were already reporting over the past two weeks, and that alone is reason enough to update. 🛠️
What changed in the interface and user experience
Anyone who uses GIMP on a daily basis knows that small UI/UX details can be the difference between a smooth workflow and that annoying feeling of getting stuck on steps that should be simple. GIMP 3.2.2 delivers exactly that kind of adjustment: changes that don’t show up in big bold letters on the changelog, but that you feel the moment you open the program.
The team confirmed this version includes minor interface and user experience updates. These are visual and behavioral refinements that follow the philosophy of polishing what already exists without major structural overhauls. This is a smart approach to maintaining stability while progressively improving usability, something the project has been pursuing consistently since the launch of GIMP 3.0.
Among the interface improvements, the team fixed inconsistent behaviors in some dialogs and visual elements that affected the experience depending on the operating system configuration or desktop environment being used. Linux users running less conventional environments tend to notice this kind of fix more, but the truth is that anyone who spends hours in front of a screen editing images benefits from clearer, more predictable interface elements. 🎨
Bug fixes that impact real work
The bug fixes in this version cover a range of situations, from minor annoyances to problems that could significantly compromise editing work. The GIMP team addressed several reports that came in from the community in the two weeks since the launch of GIMP 3.2, and the fixes were deemed safe enough to land in the 3.2 series codebase.
Filter issue with layer groups
One of the most relevant bugs fixed in this version involved the behavior of filters applied to layer groups. In certain situations, when specific filters were added to layer groups, the layers would simply stop rendering. This meant users would see content disappear from the canvas with no clear indication of what had happened, which is particularly frustrating in complex compositions with multiple grouped layers.
This fix is especially important for designers and illustrators who work with elaborate layer structures and rely on non-destructive filters to maintain flexibility in their projects. With GIMP 3.2.2, this behavior has been resolved and rendering works reliably again when applying filters to layer groups.
Vector layer fixes
Another set of corrections addresses issues with vector layers. GIMP 3.2.2 resolves a series of inconsistencies that affected working with this layer type, which has gained more prominence in recent versions of the software. Vector layers are essential for anyone who needs to combine vector design elements with rasterized editing within the same project, and having stability in this feature makes a huge difference in GIMP‘s reliability as a professional tool.
The fixes ensure that vector layer behavior is more predictable and less prone to unexpected errors during editing, which represents an important step in solidifying this feature within the GIMP ecosystem.
More robust image format support
One of the areas that received considerable attention in this update was file format handling. GIMP deals with a massive number of image formats, and making sure all of them are handled correctly is an ongoing challenge. In GIMP 3.2.2, the team worked to make support more robust for several formats, including:
- FITS – a format widely used in astronomy and scientific imaging
- TIM – an image format associated with PlayStation
- PAA – a texture format used in games
- ICNS – the macOS icon format
- PVR – a compressed texture format for mobile devices
- SFW – the Seattle FilmWorks format
- JIF – a JPEG image format variation
These improvements ensure that GIMP can open, interpret, and export these formats with fewer errors and greater fidelity to the original content. For users who work with less common formats on a regular basis, like astronomy professionals using FITS or game developers dealing with PAA and PVR, these fixes eliminate friction that previously might have required manual conversions or the use of external tools.
Improved PSD file import
The Adobe PSD plug-in also received a significant improvement. Starting with GIMP 3.2.2, the plug-in now imports all channels in PSD images using multi-channel mode. Before this fix, PSD images that used multi-channel mode could lose channel information during import, which compromised the file’s fidelity when opened in GIMP.
This improvement is particularly relevant for professionals who receive PSD files from clients or collaborators working with Adobe Photoshop. Compatibility with the PSD format has always been a sensitive point for GIMP, and every advancement in this area brings the software closer to being an even more viable alternative for workflows that involve constantly swapping files between different image editing tools. 📁
Email functionality now works in AppImages
A fix that might seem minor but solves a real headache for many Linux users: the send by email functionality now works correctly from GIMP AppImages.
AppImages are a popular way to distribute software on Linux without depending on distribution-specific package managers. However, due to the sandboxed nature of this packaging format, some features that rely on operating system integration can run into problems. The ability to send images directly by email from GIMP was one of those that didn’t work properly when the software was running as an AppImage.
With GIMP 3.2.2, this issue has been resolved, meaning users who prefer the convenience of AppImages now have full access to this feature without needing to fall back on alternative installations. It’s the kind of fix that shows the GIMP team’s attention to different usage scenarios and distribution methods. 📧
End of support for 32-bit Windows builds
An important structural change that arrived with GIMP 3.2.2 is the discontinuation of 32-bit builds for Windows. This decision wasn’t made in a vacuum. 32-bit Windows systems represent an increasingly smaller share of users, and maintaining separate builds for that architecture consumes development resources and space in distribution packages.
By dropping 32-bit builds, the GIMP team can save space in Windows installation packages and simplify the compilation and testing process. This means the resources previously dedicated to maintaining compatibility with a declining architecture can now be redirected toward improvements that benefit the vast majority of users.
If you’re still running a 32-bit Windows system, you may need to consider alternatives or stick with an older version of GIMP. But for the overwhelming majority of users running 64-bit Windows, this change is transparent and only brings indirect benefits in the form of leaner packages and more focused development efforts.
Improvements to the plug-in ecosystem
Plug-in support is one of GIMP‘s greatest strengths, and GIMP 3.2.2 doesn’t neglect this area. The plug-in updates and file format handling improvements that came with this version reflect an ongoing effort to refine the extensibility ecosystem that was overhauled starting with GIMP 3.0.
For those who use third-party plug-ins, especially ones that were migrated from the GIMP 2.x era to the new extensibility model, this update brings more robust compatibility. The fixes implemented in file format handling and overall software stability directly benefit the experience of users who have a plug-in ecosystem set up and depend on it for their everyday work.
It’s worth noting that the GIMP team has been actively working on documentation and plug-in API stability, and each update like GIMP 3.2.2 contributes to a more mature and reliable ecosystem. A healthy plug-in ecosystem depends directly on a stable foundation to build on, and GIMP clearly sees this as a core part of its value proposition. 🔌
Is it worth updating now?
The short answer is yes, and for a simple reason: maintenance updates like GIMP 3.2.2 exist precisely to fix the issues that pop up after a major version lands in the hands of real users. GIMP 3.2 shipped with a series of noteworthy new features, but it’s natural that after heavy use by the community, bugs and inconsistencies start to surface. This version is a direct response to that process, and updating ensures you’re working with the most stable and reliable version currently available.
For users who rely on GIMP as their primary image editing tool, whether for graphic design, photography, digital illustration, or any other creative use, having a stable foundation is essential. The UI/UX fixes, the resolution of the filter issue with layer groups, the improvements to file format support, the complete PSD channel import, and the discontinuation of 32-bit Windows builds together form a set of changes that, while individually they might seem incremental, collectively deliver a noticeably more polished and reliable experience compared to the original GIMP 3.2.
The release pace the GIMP team has kept up in 2026 is encouraging. Two releases in less than a month shows commitment to quality and to the user community, and the project has clearly entered a phase of accelerated maturity following the historic milestone of GIMP 3.0. If this pace holds, there’s a lot of good stuff on the horizon. 🚀
