GIMP 3.1.2 is the first development build on the road to GIMP 3.2, and it doesn’t waste time proving the project’s new ambitions. Released on June 23, 2025, this snapshot stacks a purpose-built Overwrite paint mode for pixel art, deepens its non-destructive editing stack, and takes the most aggressive step yet toward real interoperability with Adobe Photoshop and other creative tools. For Windows users who juggle GIMP alongside commercial suites or who need predictable behavior across high-DPI and ARM devices, the 3.1.2 build plants a flag: GIMP now treats format compatibility and desktop integration as first-class design goals.

The release is not meant for production work. As an early 3.1-series dev build, stability is not guaranteed, and the team warns that regressions are part of the development bargain. Still, the feature set is surprisingly polished for a mid-cycle snapshot, and many of the additions directly address long-standing pain points voiced by Windows creatives.

Overwrite paint mode: pixel art gets its own brush logic

Pixel artists have always needed a tool that paints exactly what they click—no blending, no opacity buildup, no surprises. GIMP 3.1.2 introduces the Overwrite paint blend mode, which does precisely that: it replaces the underlying color and opacity in the painted area instead of blending with existing pixels.

  • The mode is tuned primarily for the Pencil tool, where hard edges and exact coverage are the expectation.
  • With softer tools like the Brush, some interpolation still occurs to maintain anti-aliasing and gradient smoothness.
  • Overwrite is strictly a paint mode; it does not appear in layer or effect blend modes, so you won’t accidentally apply it where it doesn’t belong.

Before Overwrite, pixel workflows forced artists to toggle alpha locks, switch to hard-edged brushes, or use selection stamps — friction that broke creative flow. Now, a single mode delivers the predictable coverage pixel art demands, and the Pencil tool becomes a much more precise instrument.

Non-destructive editing widens its reach

GIMP 3.0’s layer filters brought non-destructive editing into the core, but they were confined to layers. The 3.1.2 build extends that same filter system to channels. The Channels dockable now sports an Fx column, identical to the Layers panel, enabling users to attach, reorder, merge, and edit filters on channel data.

For compositors and colorists, this is a major unlock. Masks and alpha channels can now be tweaked non-destructively — a sharpening filter on a mask to refine a selection edge, or a levels adjustment on the alpha to punch up transparency, all fully reversible. Meanwhile, the underlying GEGL filter pipeline receives internal refactoring that won’t affect day-to-day use but promises fewer bugs and smoother expansion in future releases.

Typography gets outline direction controls

Text tools gained outline styles in 3.0; 3.1.2 adds precision. A new Outline Direction option lets users control whether the outline grows inward, outward, or in both directions. For UI mockups, logo drafts, or any design where the halo effect of an outline changes the composition’s feel, this granularity is a small but meaningful ergonomic improvement.

Color management: Total Ink Coverage enters the CMYK selector

Designers preparing files for print now see a Total Ink Coverage (TIC) readout directly inside the CMYK Color Selector. Different presses and paper stocks have strict limits on how much ink a substrate can accept before smearing or drying problems occur. Having the TIC value visible while picking colors reduces guesswork and helps keep jobs within printer tolerances—a small addition with outsized importance for production work.

Windows theme parity arrives via System Colors

GIMP’s new System Colors scheme automatically matches the host operating system’s light or dark theme preference on Windows and Linux (macOS support awaits platform contributors). The interface no longer stands out as a jarringly different visual environment when you switch between apps.

  • Brush, Font, and Palette previews now use theme-aware background colors, eliminating the harsh white backdrops that caused eye strain in dark modes.
  • The Palette dockable automatically selects the next swatch after deleting one, speeding up library cleanup.
  • Toggling Lock pixels now creates its own undo step, so history stays consistent.
  • The Foreground Selection algorithm no longer fires when no selection is active, cutting unnecessary lag when switching tools.
  • The Merge Filter checkbox for non-destructive filters retains user-set state instead of being flipped unexpectedly.

These are papercut fixes, but they add up. Long editing sessions on Windows feel less like fighting the UI and more like uninterrupted work.

Interoperability becomes a headline feature

GIMP 3.1.2 positions itself as the most Photoshop-friendly and cross-app release the project has ever shipped. The goal is explicit: minimize the friction of moving assets between GIMP, Photoshop, Krita, and other tools in a mixed pipeline.

Direct Photoshop imports and exports

  • Photoshop Patterns (.pat) import: Place Adobe pattern files in GIMP’s patterns folder and they load alongside native patterns. RGB and grayscale patterns are known-good; wider coverage will benefit from community testing.
  • Curves and Levels presets (.acv, .alv): GIMP can now import Photoshop adjustment presets, enabling consistent tone shaping across apps for studios that use both tools.
  • Initial PSB export: GIMP adds first-cut support for exporting Photoshop Large Document (PSB) files. PSB extends the 30,000-pixel dimension limit of PSD up to 300,000 pixels, meeting the needs of large-format print and VFX matte painting. As initial support, complex layered files should be validated in Photoshop before relying on this path.

Krita and OpenRaster collaboration

  • A new Krita palette export (.kpl) option in the Palette dockable lets teams keep swatch libraries aligned between GIMP and Krita.
  • OpenRaster extensions now preserve selected and content-locked layer states when reading and writing ORA files, making cross-app layer fidelity much less lossy.

High dynamic range and VFX formats

  • OpenEXR multi-layer loading: GIMP can open multi-layer or multi-view EXR files as layered compositions. Multi-view renders from Blender arrive with layers intact, preserving compositing structure.
  • JPEG 2000 export: previously import-only, GIMP can now write JP2 files, catering to archival and broadcast workflows where visually lossless compression is prized.
  • HEJ2 export: an HEIF container carrying JPEG 2000 data, bridging ecosystems experimenting with HEIF beyond AVIF and H.265.

Animation and retro game assets

  • APNG import: Animated PNGs can be brought directly into GIMP. APNG is common for web UI, stickers, and game HUDs where alpha-friendly animation is needed without GIF’s palette limitations. (Export is not yet supported; round-tripping requires external tools.)
  • PlayStation 1 TIM load/export: The classic TIM format returns as an updated GIMP 3 plug-in, a direct benefit for retro game modders and preservationists.

RAW photography and unusual formats

  • ART (AnotherRawTherapee) joins darktable and RawTherapee as a Camera Raw loader, giving photographers more choice in raw development before handing off to GIMP.
  • Over-the-Air Bitmap (Nokia’s monochrome mobile format), Jeff’s Image Format (.jif), and AVCI stills import further widen compatibility with historical and broadcast media.

Windows-specific build and packaging improvements

The build system now auto-generates a list of image formats GIMP can handle, and the Windows installer and MSIX package use that list to associate file types with the application. This ends the long-standing problem where new importers shipped but file associations lagged behind, forcing users to manually set defaults.

Universal installers for x86 (32-bit and 64-bit) and ARM64 are now standard, alongside a Microsoft Store package. Native ARM64 support means GIMP runs without emulation overhead on Windows on ARM devices — critical for brush-heavy painting or filter-stacked projects on ultraportables and tablets.

Build scripts have been made POSIX-compliant with CI guarding against regressions. On Windows, the result is fewer platform-specific surprises after updates and a more predictable install footprint.

Developer-facing improvements that matter

Plug-in authors gain a new API to create GimpCoordinates widgets in auto-generated dialogs — two linked numeric fields with a chain toggle and unit dropdown. This replaces ad-hoc, inconsistent implementations with a standard control. Unsigned integer parameters now generate correct widgets, and the GimpChoice type defaults to radio buttons for two-option cases, reducing boilerplate.

Under-the-hood fixes include automatic alpha channel addition when a transformation or filter requires transparency on a layer without one, a DDS-loading fix for 32-bit systems, and restored transparency support for the legacy Jigsaw filter. These changes reduce support load and smooth the experience for both users and developers.

The 3.2 roadmap: vector and linked layers on deck

Two high-impact features are under active development for GIMP 3.2, and both address capability gaps that have long frustrated Windows-based designers.

  • Linked layers: Likely modeled after smart-object-like behavior, where a source asset updates across multiple compositions non-destructively. This would streamline mockup work and template-driven design.
  • Vector layers: Bringing vector-native layers into GIMP’s non-destructive stack would elevate its utility for logo creation, UI design, and brand work without forcing a switch to a separate vector application.

Exact implementations are not yet detailed, but the direction is clear: GIMP intends to blend raster and vector inside a single, non-destructive editing environment.

Practical considerations and risks

Developers emphasize that 3.1.2 is a development snapshot, not a release candidate. Regressions, incomplete features, and instability are part of the deal. Specific caveats include:

  • Overwrite mode’s behavior with non-Pencil tools is still being tuned; brush strokes may not feel final.
  • APNG is import-only; PSB export is labeled “initial” and complex documents may not round-trip perfectly.
  • Auto theme matching depends on OS-level support and may behave differently on customized Windows setups.
  • Non-destructive filters only apply to GEGL-based effects; many legacy filters remain destructive.

Production teams considering GIMP 3.1.2 for daily work should isolate it in test environments. For interoperability tests — especially PSB export and Photoshop preset imports — build smoke tests that mirror real assets: layered comps with text, masks, and curve adjustments. Where APNG or TIM appear in pipelines, set up round-trip validation with external tools until GIMP supports full write cycles for those formats.

GIMP’s Windows trajectory: cohesive, capable, and increasingly cross-tool

GIMP 3.0 proved that a modernized, non-destructive core was possible. GIMP 3.1.2 shows the project applying that foundation to the pragmatic problems Windows users actually face: jarring theme differences, limited file interchange with Photoshop and Krita, and install experiences that felt unfinished. The roadmap for linked layers and vector layers promises to close long-standing gaps for designers who prefer or require FOSS tooling.

The development build’s eclectic surface — EXR views and PS1 textures in a single release — reflects GIMP’s community-driven nature. But for Windows creatives who work across tools and formats daily, 3.1.2 points to an editor that is steadily becoming more cohesive, more interoperable, and far better adapted to real-world workflows.

Source: 9to5Linux