XCF vs PSD: GIMP versus Photoshop, compatibility, what to choose

Two projects, two ecosystems

In short, XCF is the native project format of GIMP, the free open-source editor, while PSD is the native format of Adobe Photoshop, the paid industry standard. In their role they are twins: both exist while you edit, and both save the entire working state of a project. The difference doesn't start inside the file — it starts around it, in which programs and people actually understand that file.

So the "XCF vs PSD" debate is really not about formats at all — it's about two ecosystems. On one side, free GIMP, where your project stays a private affair. On the other, Photoshop and the vast Adobe world that studios, agencies and freelancers have built their work around for years. If you've already worked out what XCF is, this article is the logical sequel: where XCF's boundary lies, and when PSD is the better pick instead.

What XCF and PSD share

Before pitting the formats against each other, let's be honest: they have far more in common than apart. Both are "projects," not "pictures." Where PNG or JPG hold a single flattened image, XCF and PSD keep the whole kitchen sorted onto separate shelves, so you can come back and redo any detail.

Specifically, both formats save:

• Layers — with opacity, blend modes and stacking order.
• Layer masks — stencils that hide parts of a layer without erasing them.
• Channels — including the alpha transparency channel and saved selections.
• Paths — editable vector curves.
• Transparency and the color profile — everything a project would fall apart without.

Both formats are also lossless: they don't throw away detail to save space the way JPG does. XCF compresses with RLE (and, since GIMP 2.10, the denser zlib). PSD has its own RLE/raw compression, plus a "big brother" PSB variant for huge files. The takeaway is simple: on pixels and on capabilities, XCF and PSD run almost neck and neck. All the intrigue is in compatibility.

The key difference: compatibility

This is the heart of the whole comparison. PSD is the de-facto interchange standard in the graphics world. It is opened not only by Adobe's own products (Photoshop, Illustrator, InDesign, After Effects, Premiere) but by third-party editors too: Affinity Photo, Sketch, Figma, the online Photopea — and yes, GIMP reads PSD as well. When a designer hands over "the source file," PSD is the default assumption.

XCF, by contrast, is essentially a loner. Only GIMP opens it fully. XnView MP and ImageMagick read the format partially, and Photoshop cannot open XCF at all — not in any version. This isn't an accident: GIMP's own developers say plainly that XCF is not meant for interchange — it mirrors the editor's internal data structures rather than serving as a universal container.

The table puts everything in its place: on raw capabilities the formats are nearly equal, but on the compatibility rows PSD wins by a landslide. That's exactly why, if a file has to reach anyone else, PSD is the default — even for people who paint in GIMP.

Cost: free vs subscription

The second big difference is money. GIMP and the XCF format are free forever: you download the editor, save projects as XCF, and never pay a cent — not today, not a year from now. Open source, no licenses, no subscriptions.

Photoshop and PSD live on an Adobe subscription. The PSD format itself, of course, "costs" nothing — but to work with it properly you need Photoshop, which you have to pay for. That's exactly why the "GIMP + XCF" pairing is so often called the free alternative to PSD: you get layers, masks and channels of the same class without opening your wallet.

Can GIMP open PSD (and vice versa)

Here's where it gets practically useful. GIMP opens PSD well — with its layers and masks — and, better still, it can export back to PSD via File ▸ Export As. In other words, a GIMP user can happily accept a PSD from a colleague, do the work, and hand the result back as PSD again. This is what makes GIMP a genuine free replacement for Photoshop on many jobs.

But it doesn't work the other way around: Photoshop simply does not open XCF. If your file needs to reach someone on Photoshop, sending them an XCF is pointless — they'll see an "unknown format." The fix is simple: don't send the XCF, export the project to PSD straight from GIMP. Your colleague opens a file they're used to, and you keep the original XCF for further work.

What gets lost in translation

Moving between formats is not magic, and a few things can get lost on the way. The basics travel reliably: ordinary layers, their opacity, masks and stacking order survive conversion in either direction. The trouble starts with signature features that have no exact counterpart on the other side.

For Photoshop those are adjustment layers, smart objects and layer styles — strictly "Photoshop things." When GIMP opens such a PSD, it often flattens those effects into ordinary pixel layers: the picture looks right, but the effect's editability is gone. The reverse direction has surprises too: GIMP-specific features can simplify when exported to PSD.

Hence the important caveat about the "round-trip" GIMP → PSD → Photoshop. For projects made of simple layers it usually goes smoothly. But if a project is packed with advanced, editor-specific effects, don't expect them to survive the full loop unscathed. The simpler the layer structure, the more reliable the transfer.

Which to choose for your task

Now the most important part — a simple rule for choosing. There is no "best" format in the abstract; there is the format that fits your situation.

• Choose XCF if you work solo in GIMP, want a free tool, and the project stays with you. It's your "full source."
• Choose PSD (or export to PSD) if you collaborate with Photoshop users, hand the file to a client or agency, or need the broadest possible app support.
• You need neither if the task is just to show the finished result. Then export to PNG or JPG: a file like that opens anywhere.

That last case is the most common of all: someone doesn't need to edit your project, they just want to see the picture or post it online. In that case neither XCF nor PSD is needed — a universal PNG is. You can flatten a GIMP project into PNG in a couple of seconds, right in your browser, without installing an editor.

Want the opposite — to build an editable GIMP project from a plain picture? There's a reverse conversion for that, PNG to XCF, and every supported conversion lives on the all formats page. And if someone sent you an XCF but GIMP isn't around, start with the hands-on guide on how to open XCF without GIMP.