The longstanding friction between GIMP and Photoshop’s native file format has always been practical rather than philosophical. GIMP has read and written PSD files for years, but “reads PSD” and “faithfully round-trips a PSD” are not the same claim. Layer modes translated incorrectly, adjustment layers collapsed to pixels, smart objects lost their editability, and text layers sometimes arrived looking nothing like their source. GIMP 3.4 is positioned to close much of that gap — and for anyone maintaining a mixed workflow where some collaborators are in Photoshop and others aren’t, the specifics matter.
What the PSD Format Actually Requires
PSD files are more structurally complex than most raster formats. Where a TIFF or PNG stores pixels in a relatively flat hierarchy, a PSD encodes layers, layer groups, blend modes, channel data, masks, adjustment layers, smart objects (which store embedded sub-documents), and a composite flattened image — all in the same file. Adobe has documented portions of the spec publicly, but the format also carries a substantial amount of undocumented or implementation-specific behavior, which is part of why open-source implementations have historically struggled.
Blend modes are a particularly concrete example. Photoshop’s blend mode list includes modes like Vivid Light, Hard Mix, and Linear Burn whose exact pixel math differs subtly from what other applications implement under identical names. A layer set to Vivid Light in Photoshop blends each channel by applying either Color Dodge or Color Burn depending on whether the blend layer’s value is above or below the midpoint — the exact arithmetic is specified, but minor floating-point differences in implementation still produce visible deviations. When GIMP renders a PSD that was built in Photoshop, any mode mismatch shows up immediately as a color or luminosity shift in the composite.
Adjustment layers are the other structural minefield. In Photoshop, a Curves adjustment layer stores a set of curve node coordinates and applies the transformation non-destructively to everything below it in the stack. Historically, GIMP had no equivalent non-destructive adjustment layer system, so when importing a PSD it would rasterize those adjustments — permanently baking the tonal changes into the pixels below. You got a flat representation of what the file looked like, not an editable version of how it was built.
What GIMP 3.4 Changes in Practice
GIMP 3.4’s PSD improvements are centered on two areas: more accurate blend mode translation and better preservation of layer structure during import. The development notes reference expanded support for Photoshop-specific layer blend modes, meaning more modes now map to GIMP’s own rendering pipeline rather than falling back to a “Normal” or collapsed approximation. For files where blend modes were the primary source of visual drift between applications, this is a direct improvement.
Layer group handling also received attention. Photoshop uses nested layer groups extensively for organizational and masking purposes — a group with a layer mask applied at the group level clips all layers inside it, which is a structurally distinct behavior from applying a mask to individual layers. Prior GIMP versions sometimes flattened these groups on import, discarding the hierarchical structure. Version 3.4 aims to preserve that nesting, which matters if your intention is to continue editing the file rather than simply viewing its final output.
Text layer handling is a related improvement worth understanding carefully. A PSD text layer stores the text string, font name, size, tracking, leading, and other typographic attributes alongside the rasterized pixel preview that Photoshop embeds for quick rendering. GIMP can now read more of those text attributes and reconstruct an editable text layer, but font substitution is an unavoidable reality whenever the editing system doesn’t have the same fonts installed. The text may reflow or the letterforms change if the original font is absent — that limitation is architectural, not a GIMP-specific failure.
The Adjustment Layer Situation — Still the Core Caveat
One honest caveat is worth stating clearly: GIMP’s non-destructive editing architecture differs from Photoshop’s in ways that affect adjustment layer round-tripping. GIMP 3.0 introduced a non-destructive editing layer (GEGL operations as layer effects), but its adjustment layer model and Photoshop’s are not equivalent systems. Importing a PSD with a complex Curves, Selective Color, or Channel Mixer adjustment layer and expecting to export a PSD that Photoshop then reads back as a live Photoshop adjustment layer is still not a realistic expectation with GIMP 3.4. Some adjustment layers will import as editable in GIMP’s own terms but will not round-trip back to Photoshop as parametric adjustments.
This distinction matters most for collaborative workflows where the same PSD moves back and forth between a GIMP editor and a Photoshop editor. For workflows where GIMP is at one end — importing a Photoshop-built PSD to make specific targeted changes, then exporting a flattened or partially-merged result — the improvements are more practically useful.
Where This Fits in a Real Editing Workflow
Consider a scenario that comes up frequently in small editorial or design teams: one member works in Photoshop and builds layered comps for review; another edits on a system without a Creative Cloud subscription. Previously, that second editor had to work from a flattened export (a JPEG or a TIFF with merged layers) because the PSD handed to them in GIMP would arrive with enough structural damage to make non-destructive editing pointless. With 3.4’s improvements, more of the original structure survives import, meaning that second editor can now adjust individual layers and return something closer to a live document.
For single-user workflows, the calculus is slightly different. If you’re building files in GIMP with the intention of exporting to PSD for delivery, the export side of GIMP’s PSD support is also relevant — specifically whether the PSD file it produces is interpretable by the receiving application without visual surprises. Checking the result in a second application before final delivery remains good practice, as the PSD format’s complexity means edge cases persist even as implementation quality improves.
Our photo editing coverage has addressed several adjacent situations: how non-destructive features behave differently across tools, what actually changes when an AI masking system modifies a layer’s structure, and where free and subscription tools diverge in ways that affect round-trip file fidelity. The GIMP 3.4 PSD improvements slot into that broader conversation about what “compatible” actually means across editing environments.
Practical Next Steps
If you work with PSD files in GIMP, the most useful thing you can do after updating to 3.4 is run a deliberate compatibility check on files that previously imported with problems. Open a PSD that you know well — ideally one whose Photoshop output you have for comparison — and inspect the layer stack carefully: blend mode labels, group nesting, mask boundaries, and text editability. Export it back to PSD, open that export in Photoshop or Photopea (which reads PSD with relatively high fidelity), and compare the composite output to the original. That manual audit will tell you far more about how your specific files interact with the updated import/export code than any general compatibility statement can.
Pay particular attention to any layers using Photoshop-specific blend modes and any adjustment layers that sit above complex composites. Those remain the most likely failure points, and knowing exactly where the translation breaks down in your specific files is the prerequisite for deciding whether the workflow is now reliable enough to depend on.