Initializing... drag & drop files here
Supports: XCF
XCF is GIMP's native working format — it stores every layer, channel, path, mask, and guide so the design stays editable. That same richness makes XCF unusable outside GIMP: no browser, phone gallery, image viewer, or messaging app reads it. HEIF (High Efficiency Image File Format, ISO/IEC 23008-12) is a modern delivery container that flattens a finished design into a single, well-compressed image with optional 10-bit color and HDR. Typical reasons to export from XCF to HEIF:
| Property | XCF (GIMP) | HEIF |
|---|---|---|
| Maintainer | GIMP Project | MPEG / ISO/IEC 23008-12 (2015) |
| File role | Editable working file | Delivery / archival image |
| Layers, masks, paths, guides | Preserved | Flattened to a single image |
| Default codec | RLE-compressed pixel data | HEVC (H.265); also AV1, AVC, JPEG variants |
| Color depth | Up to 32-bit float per channel | 8 / 10 / 12 / 16-bit per channel |
| Transparency / alpha | Yes (per layer) | Yes (single alpha channel) |
| Animation / sequences | No | Yes (.heifs /.heics) |
| Native preview on iOS / macOS | None | Yes (iOS 11+ / macOS 10.13+) |
| Native preview on Windows / Android | None | Windows 10/11 (HEIF + HEVC extensions); Android 10+ |
Browser support in <img> |
None | Safari 17+ only (caniuse) |
| Typical size vs JPEG (same quality) | Much larger (carries layers) | About 50% smaller |
| Ideal use | Continued editing in GIMP | Sharing, phone galleries, archival |
| Aspect | HEIF (.heif) | HEIC (.heic) |
|---|---|---|
| Definition | Container spec (ISO/IEC 23008-12) | HEIF container holding HEVC-encoded image data |
| Codec inside | Any approved codec — HEVC, AV1, AVC, JPEG | HEVC only |
| Mandated extension | .heif, .heifs for non-HEVC payloads |
.heic, .heics (mandatory for HEVC payloads) |
| Apple usage | Generic term in docs | Default extension iPhones write since iOS 11 |
| When you'd choose it | Need AV1 or AVC payload, broader codec future-proofing | Maximum compatibility with Apple devices and existing HEIF readers |
If your recipients are mostly on iPhones or Macs, convert XCF to HEIC directly so the file is named with the extension Apple's tooling expects.
| Setting | What it controls | When to use |
|---|---|---|
| Very High (Recommended) | Near-visually-lossless HEVC quality | Portfolio output, print prep, archival |
| High | Strong visual quality, ~30-50% smaller than Very High | General sharing, social, web previews |
| Medium / Low | Aggressive compression for size | Email attachments, low-bandwidth previews |
| Image Quality (%) | Manual 0-100 slider | Precise control when matching another asset |
| Target file size (%) | Encoder targets a percentage of source size | Bulk batch with predictable shrinkage |
| Specific file size (KB/MB) | Encoder auto-scales to a hard cap | Hitting upload limits (e.g., a 2 MB CMS cap) |
No. HEIF is a single-image delivery format, so the converter flattens every visible layer, group, and mask into the final raster. Keep the original.xcf if you'll need to edit again — HEIF is for sharing, not source-of-truth. To preserve layer-like structure for non-GIMP editors, export to PSD instead, or keep the.xcf alongside the.heif.
Only Safari 17 and later (macOS Sonoma, iOS 17, iPadOS 17) decode HEIF or HEIC inside an <img> tag. Chrome, Firefox, and Edge do not — neither current nor any prior version (verified on caniuse.com/heif). If the file needs to render in any browser, export to WebP, AVIF, JPG, or PNG instead. HEIF is best treated as a phone-and-Apple delivery format, not a web one.
They're related but not identical. HEIF is the container spec defined in ISO/IEC 23008-12; HEIC is specifically a HEIF container holding HEVC-encoded image data. The standard mandates .heic for HEVC payloads and .heif for the generic case. iPhones write .heic by default, but the underlying structure is HEIF — that's why the two terms get used interchangeably in casual usage.
HEIF using HEVC compression typically produces files about 50% the size of JPEG at equivalent perceived quality, per Apple's HEIF/HEVC documentation and independent comparisons. Real-world savings depend on image content — flat illustrations and digital paintings (common XCF output) often see larger savings than noisy photographs.
Yes. HEIF supports an alpha channel, so transparent backgrounds in the flattened XCF are preserved in the.heif output. Note that not every HEIF reader displays alpha correctly — Apple's Preview and Photos handle it well; some Windows tools render the alpha as black until the HEIF Image Extensions are installed.
HEIF supports up to 16-bit per channel, which makes it a strong option for designs with smooth gradients, HDR composites, or wide-gamut color. The output bit depth depends on encoder settings on the back end. If you're exporting from GIMP at high bit depth and need to keep that fidelity, HEIF outperforms 8-bit JPEG on banding-prone content.
HEVC is patent-encumbered and licensing for browser use is complex, which is why Chrome, Firefox, and Edge skipped native HEIF support and instead invested in royalty-free AVIF. For Apple-internal pipelines HEIF dominates; for cross-browser web pages, AVIF (AV1-based) is the modern equivalent.
HEIF natively carries ICC color profile, EXIF, and XMP metadata, and the converter preserves embedded profile and metadata blocks where present in the XCF. If you've assigned an sRGB or Display P3 profile in GIMP, that tag travels with the.heif so color-managed apps render the result correctly.
If you only need a smaller delivery copy of a HEIF you already have, compress HEIF skips a re-encode of the original raster math and lets you target a size or quality directly. Convert from XCF when you've made fresh edits in GIMP that need to land in a HEIF.