PicaJet

Reference Formats

XCF

GIMP's native project file format, preserving the full editable state of an image — layers, layer groups, channels, paths, guides, and selections — the open-source counterpart to Photoshop's PSD.

Extension

.xcf

Full name

eXperimental Computing Facility format (GIMP's native project format)

Introduced

December 15, 1997, with GIMP 0.99.16

Vendor

GIMP Development Team

What is inside the container

XCF stores everything GIMP's canvas holds: layers with blend modes and alpha, layer groups (added 2010), text layers, paths and guides, selection masks, and, since GIMP 2.10 (2018), high-bit-depth and GEGL-based image data plus embedded color profiles. It is explicitly a working/project format rather than a distribution format — GIMP itself expects you to export to TIFF, PNG, or JPEG for anything leaving the application.

How to open it

Cross-platform (native) GIMP opens and saves XCF natively
Adobe Photoshop no built-in support; requires a third-party plugin to import XCF
Command line/scripting GIMP's Script-Fu/Python-Fu console can batch-process XCF files headlessly
Viewers generic image viewers such as XnView offer only limited, flattened-preview support for XCF

For archives

Keep XCF only as the live working file for assets still being edited in GIMP; for DAM archival, store a flattened TIFF or PSD-equivalent derivative alongside it, because almost nothing outside GIMP can render XCF reliably enough to generate a trustworthy thumbnail or preview.

GIMP introduced XCF as its native format with version 0.99.16 on December 15, 1997, replacing earlier ad hoc saving with a structured file that could hold everything the editing session contained rather than just a flattened picture. The name traces back to the Experimental Computing Facility at UC Berkeley, where GIMP’s early development took place. The format grew with the application: layer modes arrived with XCF version 2 around 2002, layer groups with version 3 in 2010, and high-bit-depth GEGL-based image data with GIMP 2.10 in 2018.

For a DAM, XCF behaves much like PSD in spirit but with far thinner third-party support — Photoshop, browsers, and most asset-management preview engines cannot render an XCF file without a plugin or GIMP itself in the pipeline. That makes XCF a legitimate source/master format for teams standardized on GIMP, but a risky one to hand off across a mixed toolchain: a DAM ingesting XCF files should either run GIMP headlessly to generate flattened preview derivatives, or require contributors to export a TIFF/PNG alongside the XCF so the catalog always has something universally previewable.

Frequently asked

Can a DAM generate a reliable thumbnail directly from an XCF file?

Not easily. Almost nothing outside GIMP renders XCF reliably enough to generate a trustworthy thumbnail or preview, so a DAM should rely on a flattened derivative instead.

What should a DAM store alongside an XCF working file for archival purposes?

A flattened TIFF or PSD-equivalent derivative, since XCF is a live working format and most non-GIMP software cannot render it.

What editable state does XCF preserve?

Everything GIMP's canvas holds: layers with blend modes and alpha, layer groups added in 2010, text layers, paths and guides, selection masks, and since GIMP 2.10 in 2018 high-bit-depth GEGL-based image data plus embedded color profiles.

Is XCF intended as a distribution format?

No. GIMP itself expects users to export to TIFF, PNG, or JPEG for anything leaving the application; XCF is explicitly a working/project format only.

Can Adobe Photoshop open XCF files?

Not natively. Photoshop has no built-in XCF support and requires a third-party plugin to import it, which matters for DAM workflows that mix GIMP and Adobe users.

How can a DAM batch-process XCF files without opening GIMP's GUI?

GIMP's Script-Fu/Python-Fu console can process XCF files headlessly, which is the practical route for automated proxy generation at scale.

When was layer-group support added to XCF, and why does that matter for older files?

Layer groups were added in 2010, so XCF files created before that in earlier GIMP versions won't have that organizational structure, a detail worth knowing when auditing legacy XCF assets in a collection.

What is XCF the open-source counterpart to?

It is GIMP's equivalent of Adobe Photoshop's native PSD format, a project file that preserves full editability rather than a flattened, universally viewable image.

Sources