📖 What is an XCF File?
An XCF file is the working document of GIMP, the free image editor. When you save a picture in GIMP, you get an .xcf file that keeps every layer, mask and adjustment intact, so you can come back to the project another day and pick up your editing right where it stopped.
The name is an old one, short for eXperimental Computing Facility, but what matters is its role. An XCF file is not the finished picture you send to someone. It is the editable master behind it, holding all the moving parts of your work rather than a single flattened image. Think of it as the project, while a PNG or JPG is the snapshot you hand out when the project is done.
Because it stores all of that structure, an XCF file is read properly only by GIMP and a small number of related tools. Most image viewers and web browsers cannot show it, which surprises people who expect any image file to open anywhere. Once you know it is a working file rather than a share-ready picture, that behaviour makes sense.
Key Characteristics
- GIMP's native format for saved work
- Keeps layers editable, not flattened
- A working master, not a delivery image
- Free and open, tied to GIMP
Good to Know
- Opens fully in GIMP, which is free
- Not shown by browsers or most viewers
- Export to PNG or JPG to share it
- The open-source answer to Photoshop's PSD
⚡ Quick Facts
| File Extension | .xcf |
| Full Name | eXperimental Computing Facility |
| Belongs To | GIMP (GNU Image Manipulation Program) |
| First Released | 1997 |
| Opens In | GIMP, and a few related tools |
| Kind of File | Layered raster image project |
| Media Type | image/x-xcf |
| Share As | PNG, JPG or other exported formats |
🎨 A Working File, Not a Picture
The single most useful idea about an XCF file is that it is a work in progress saved to disk. It exists so you do not lose your editable structure between sessions, and that purpose shapes everything else about it.
When you build an image in GIMP, you rarely work on one flat picture. You stack layers, add masks that hide or reveal parts of them, keep selections and paths, and type text that stays editable. A finished JPG throws all of that away and keeps only the final pixels. An XCF keeps it all, so tomorrow you can move a layer, soften a mask or fix a typo without starting over. That is why an XCF is best thought of as the source you keep and a PNG or JPG as the copy you publish.
🗂️ What an XCF File Holds
Inside an XCF file is the full state of your GIMP project. Rather than a single grid of pixels, it stores the separate pieces that make up your work and the way they are arranged.
Layers and Masks
Each layer stays separate, along with the masks that control what shows through.
Channels and Paths
Colour channels, saved selections and the vector paths you drew are all preserved.
Text and Guides
Editable text stays as text, and the guides you placed for alignment stay put.
One thing an XCF does not save is your undo history. The list of steps you can undo lasts only for the current session, so once you close GIMP that history is gone even though the layers and everything else remain. It is worth knowing before you rely on undoing your way back through a reopened file.
💾 Save vs Export
This is the part that trips up almost everyone new to GIMP, and it is worth getting straight. In GIMP, saving and exporting are two different actions that produce two different kinds of file.
When you choose Save, GIMP writes an .xcf file, keeping all your layers and edits. It deliberately does not offer to save a JPG or PNG here, because those formats cannot hold the editable structure. To produce a shareable image you use File then Export As, which flattens the project into a PNG, JPG or another common format. Since GIMP version 2.8 this split has been explicit, with Save reserved for the working XCF and Export used for everything you send out. So if you saved your work and cannot find a JPG, the reason is simply that Save made an XCF, and the JPG comes from Export instead.
⚖️ XCF vs PSD
People who know Photoshop often ask how XCF compares to PSD, and the two really are close cousins. Each is the native, layered working format of its own editor.
A PSD is Photoshop's project file and an XCF is GIMP's, and both keep layers, masks and other editable pieces rather than a flattened image. The main practical difference is the software around them. Photoshop is paid and its PSD is a de facto industry standard, while GIMP is free and open and its XCF is tied mainly to GIMP. The two are not fully interchangeable, though GIMP can open many PSD files and export to PSD, which helps when moving work between the two. If you understand what a PSD is, you already understand what an XCF is, just in the open-source world.
| Trait | XCF | PSD |
|---|---|---|
| Editor | GIMP | Adobe Photoshop |
| Cost | Free and open | Paid |
| Keeps layers | ✓ Yes | ✓ Yes |
| Role | Editable master | Editable master |
| Cross-support | GIMP can open and export many PSD files | |
📂 How to Open an XCF File
To open an XCF file with everything intact, the tool you want is GIMP itself, which is free and runs on Windows, macOS and Linux. A few other options exist when you only need a quick look.
GIMP
The native editor. Install it free, then open the file to reach every layer, mask and path.
Photopea
A browser-based editor that reads XCF with layers, handy when you cannot install anything.
A GIMP-based viewer
Tools such as Seashore on Mac open XCF, and some viewers show a flattened preview only.
For real editing, GIMP is the reliable choice, since it is the program the format was built for and nothing else matches it for fidelity. When you just want to see what an XCF contains, a browser editor like Photopea or a lightweight viewer can give you a preview without a full install. What you will not find is broad support in ordinary photo apps, because they are built for finished images rather than layered projects.
👁️ Opening It Without GIMP
If you cannot or would rather not install GIMP, you still have options, but it helps to know they fall into two groups. Some tools give you the real layered project, and others show only a flattened preview.
For layers, the standout is Photopea, a free editor that runs in your browser and reads XCF with its layers intact, which makes it the closest thing to GIMP without an install. For a quick look, lightweight viewers such as IrfanView and XnView MP open an XCF as a single flattened picture, letting you see and even batch-export the result but not touch the separate layers. The trade is clear. Layer-aware tools let you edit or inspect the structure, while preview tools are faster but show only the merged image. Ordinary web browsers sit outside both groups, since they do not read XCF at all, so viewing one online means using a browser editor like Photopea rather than opening the file directly.
| Tool | Reads layers | Best for |
|---|---|---|
| GIMP | ✓ Yes | Full editing, native fidelity |
| Photopea | ✓ Yes | Layer access in a browser, no install |
| IrfanView, XnView MP | ✗ Flattened only | Quick preview or batch export |
| Web browser | ✗ No | Nothing, export an image first |
🔄 Converting to PNG or JPG
When your image is finished and you want to share it, you convert the XCF into an ordinary picture format. In practice this means exporting from GIMP, which flattens the layered project into a single image.
Open the file in GIMP, choose File then Export As, and pick a format such as PNG when you need transparency or JPG when you want a small photo-style file. This choice matters, because PNG keeps any transparent areas from your XCF while JPG has no transparency and fills those areas with a solid colour, so a logo or cut-out is almost always better exported as PNG. GIMP merges the layers into one image and writes the result, leaving your original .xcf untouched so you can keep editing it. If you have many files or no GIMP to hand, command-line tools like ImageMagick and some online converters can flatten an XCF to PNG or JPG as well, though anything with unusual layers is safest handled in GIMP. Whichever route you take, remember the export is a one-way snapshot, so the editable layers live on only in the XCF.
📦 Why XCF Files Are Large
An XCF file is often much bigger than the JPG or PNG you export from it, sometimes many times the size, and there is a simple reason for that.
A flattened image stores only the final pixels, but an XCF stores every layer, mask, channel and path separately so they stay editable. All of that extra structure takes space, and a project with a high-resolution canvas and lots of layers can grow to a hefty file. This is normal and not a fault. A practical habit is to keep the XCF while a project is active and, once you have exported the finished image and no longer expect to re-edit, to archive or remove the large working file to reclaim space.
🏛️ A Short History
The XCF format first appeared in 1997 as the saving format of GIMP, which was created as a free alternative to expensive image editors. The odd name, eXperimental Computing Facility, comes from the university lab where GIMP's authors did early work.
Early XCF files stored their image data with a simple run-length scheme, though GIMP has long been able to write compressed XCF files using tools like gzip, and from the format's version four, shipped with GIMP 2.10 in 2018, the image data can be compressed with zlib and newer features are supported. Because XCF is tied so closely to GIMP rather than being a shared standard, the GIMP and Krita projects have also worked on an open, cross-application format called OpenRaster, meant to move layered images between different editors. Even so, XCF remains the everyday working format for GIMP users and shows no sign of going away.
🛠️ Common Issues
Most trouble with XCF files comes from expecting them to behave like ordinary pictures. Each common problem has a clear cause.
| It will not open in my photo app | Most viewers cannot read XCF. Open it in GIMP, or export a PNG or JPG for other apps. |
| The browser will not show it | Browsers do not display XCF. It is a working file, not a web image, so export one to view online. |
| I saved but cannot find a JPG | Save makes an .xcf. Use File then Export As in GIMP to produce a JPG or PNG. |
| The file is very large | Normal for a layered project. Export the finished image, then archive the XCF if you are done. |
❓ Frequently Asked Questions
An XCF file is the native working format of GIMP, the free image editor. When you save a picture in GIMP, you get an .xcf file that keeps every layer, mask, channel and path editable, so you can return to the project and keep editing from the point you stopped. The name is short for eXperimental Computing Facility. The key point is that an XCF is the editable master behind an image, not the finished picture you share, which is why you export a PNG or JPG from it when the work is done. It is the open-source equivalent of Photoshop's PSD.
The reliable way to open an XCF file with everything intact is GIMP, which is free and runs on Windows, macOS and Linux. Install GIMP, then open the file to reach every layer, mask and path. If you cannot install anything, a browser-based editor such as Photopea reads XCF with its layers, and some lightweight viewers show a flattened preview only. Ordinary photo apps and web browsers generally cannot open an XCF, because it is a layered working file rather than a finished image, so GIMP remains the dependable choice for real editing.
Open the file in GIMP, choose File then Export As, and pick PNG when you need transparency or JPG for a smaller photo-style file. GIMP flattens the layers into one image and writes it, leaving your original .xcf untouched so you can keep editing. For batches or when GIMP is not available, command-line tools like ImageMagick and some online converters can flatten an XCF as well, though files with unusual layers are safest in GIMP. Remember the exported image is a one-way snapshot, so keep the XCF as your editable original.
Because an XCF is a layered project file, not a ready-to-share image. It stores all the editable structure of a GIMP project, which browsers and most photo viewers are not built to read, so they simply cannot display it. This catches people out, since almost any other image opens anywhere. The fix is to open the XCF in GIMP for editing, or to export a PNG or JPG from it when you need a file that opens in a browser, on a phone or in an ordinary image viewer.
XCF and PSD are close cousins. Each is the native, layered working format of its own editor, keeping layers, masks and other editable pieces rather than a flattened image. XCF belongs to GIMP, which is free and open, while PSD belongs to Adobe Photoshop, which is paid and treated as an industry standard. They are not fully interchangeable, but GIMP can open many PSD files and export to PSD, which helps when moving work between the two. If you understand what a PSD is, you already understand what an XCF is, just in the open-source world.
That is how GIMP is designed. The Save command writes an .xcf file, which keeps all your layers and edits, and it deliberately does not offer JPG or PNG there, because those formats cannot hold the editable structure. To produce a shareable image you use File then Export As instead, which flattens the project into a PNG, JPG or another format. Since GIMP version 2.8 this split has been explicit, with Save reserved for the working XCF and Export used for anything you send out. So the JPG comes from Export, not Save.
An XCF file is often much bigger than the JPG or PNG you export from it because it stores far more. A flattened image keeps only the final pixels, while an XCF keeps every layer, mask, channel and path separately so they stay editable, and all that structure takes space. A project with a high-resolution canvas and many layers can grow to a hefty size, which is normal rather than a fault. A good habit is to keep the XCF while the project is active, then archive or delete the large working file once you have exported the finished image and no longer need to edit it.
Yes, with a couple of routes. For the layers intact, Photopea is a free editor that runs in your browser and reads XCF, which is the nearest thing to GIMP with nothing to install. For just a look, lightweight viewers such as IrfanView and XnView MP open an XCF as a single flattened image, so you can see or batch-export it but not edit the separate layers. Ordinary web browsers cannot open an XCF at all. So if you need the structure use Photopea, and if you only need to see or convert the picture a flattening viewer is quicker.
An XCF file itself keeps transparency, but whether the exported copy does depends on the format you pick. Export to PNG and any transparent areas are preserved, which is why PNG suits logos, icons and cut-out images. Export to JPG and the transparency is lost, because JPG has no transparent channel and fills those areas with a solid colour, usually white. So when your image has see-through parts you want to keep, choose PNG in GIMP's Export As dialog rather than JPG. The XCF always holds the original transparency for you to export again later.
XCF is GIMP's own layered format, tied mainly to GIMP, while OpenRaster, using the .ora extension, is an open standard for layered images meant to be shared across different editors. The GIMP and Krita projects worked together on OpenRaster precisely so a layered image could move between applications more freely than XCF allows. In practice XCF preserves the fullest detail of a GIMP project, whereas .ora trades some of that for portability between programs. If you work only in GIMP, XCF is the natural choice, and if you need to hand a layered file to another editor, OpenRaster is worth considering.
For a whole folder of files, a command-line tool such as ImageMagick can flatten each XCF to a standard image, with a simple command that reads an XCF and writes a PNG. This is quick and needs no clicking through menus. The one caution is fidelity, since flattening outside GIMP can occasionally drop layer blend modes or shift colours, so files with complex layers are safest exported from GIMP itself. For straightforward images a batch tool is fine, and for anything you care about visually, a check in GIMP is worthwhile. Either way the original XCF files stay untouched.
Usually yes, because the XCF format is largely backward compatible, so newer versions of GIMP open files made by older ones. The reverse is less certain. A file that uses a feature added in a newer release may not open cleanly in an older GIMP, and layer groups, introduced in GIMP 2.7, are a known example that earlier versions such as 2.6 cannot read. In some cases the file still opens but a newer feature is simplified, such as editable text becoming an ordinary layer. To avoid surprises, it is best to open an XCF in the same or a newer version of GIMP than the one that made it.
Yes, and the simplest way is in GIMP. Open the XCF, hide the layers you do not want by clicking their visibility icons, then use File and Export As to save just what remains as a PNG, which keeps the transparency around the layer you kept. You can repeat this for each layer you need. GIMP also lets you export layers individually through its layer menu and add-ons. Because an XCF stores every layer separately, pulling one out is a matter of choosing what to show and exporting, rather than any special conversion, and the original file stays intact throughout.
📝 Summary
An XCF file is the native working format of GIMP, the free and open image editor, and the name is short for eXperimental Computing Facility. The single idea to hold on to is that an XCF is an editable project, not a finished picture. It saves the full state of your work, every layer, layer mask, channel, path, saved selection and editable text, so you can reopen it in GIMP and keep going rather than starting over. This makes it the open-source equivalent of Photoshop's PSD, and the two are close cousins that GIMP can even move work between, since it opens and exports many PSD files. Because it stores all that structure, an XCF is read fully only by GIMP and a few related tools such as the browser editor Photopea, while ordinary photo viewers and web browsers cannot show it, and it is usually far larger than the flattened image you make from it. The point that confuses most newcomers is the difference between Save and Export in GIMP. Save writes the editable .xcf, while File then Export As flattens the project into a PNG, JPG or other common format for sharing, a split that has been explicit since GIMP version 2.8. So the workflow is to keep the XCF as your editable master and export a picture from it when the image is done, remembering that the export is a one-way snapshot and the layers live on only in the XCF. Once a project is finished and you no longer expect to re-edit, the large XCF can be archived or removed to reclaim space. In short, treat the XCF as the source you keep and the PNG or JPG as the copy you publish.