XCF

Almost nothing outside GIMP renders XCF reliably enough to generate a trustworthy thumbnail or preview. XCF stores layers as compressed 64×64-pixel tiles with GIMP-specific blend modes and compositing rules that most third-party decoders don't replicate correctly, so a generic image library can produce a preview that doesn't match what GIMP actually renders. The dependable route for a DAM is invoking GIMP itself in headless batch mode to flatten the file and export a standard preview, rather than trusting a generic reader.

A flattened TIFF or PSD-equivalent derivative should accompany every XCF working file, since XCF is a project format incompatible with most non-GIMP software and can't be opened or previewed reliably elsewhere. Also worth capturing: the GIMP version used to save the file, since layer groups, GEGL-based high-bit-depth data, and embedded color profiles were introduced in different GIMP releases, so older files may lack structure newer ones assume. This lets a DAM reconstruct or re-export the asset later without the original GIMP install.

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.

No. GIMP itself treats XCF strictly as a project file: its own workflow expects users to export to TIFF, PNG, or JPEG for anything leaving the application, and XCF is never the intended target for sharing or publishing. Compressed variants such as .xcf.gz and .xcf.bz2 shrink the file on disk but still require GIMP to open, so compression doesn't solve distribution either. For a DAM, this means XCF should be treated as a source/working asset only, always paired with an exported derivative for viewing or downstream use.

No, Photoshop has no native XCF support. A handful of third-party plugins and conversion utilities claim import capability, but reliability varies by release, and GIMP-specific constructs such as layer groups, GEGL-based high-bit-depth data, and parasite metadata may not translate cleanly through them. The more dependable route is exporting to PSD or TIFF from GIMP itself, manually or via a scripted headless batch job, before the asset enters a Photoshop-based workflow. Browser tools such as Photopea can also open XCF directly for a quick look.

GIMP can run in headless batch mode from its command-line binary, invoked as gimp-console with flags like --no-interface and --batch-interpreter=plug-in-script-fu-eval, executing Script-Fu (GIMP's Scheme-based scripting language) or Python-Fu commands without drawing a window. This lets a DAM script bulk operations across large XCF batches on a server — flattening layers, exporting thumbnails or PSD/TIFF derivatives, reading metadata — which is the practical route for automated proxy generation at scale rather than opening each file interactively.

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.

XCF is GIMP's equivalent of Adobe Photoshop's native PSD format: both are project files that preserve full editability — layers, channels, paths, and selections — rather than a finished, portable image. Neither is intended for general exchange, and both effectively require their originating application, or a capable emulator like Photopea, for full-fidelity access. The practical difference for a DAM is ecosystem size: PSD has far broader third-party read support than XCF, making flattened derivatives even more essential when handling XCF assets.