Initializing... drag & drop files here
Supports: XCF
XCF is GIMP's native project format — it preserves layers, channels, paths, selections, transparency, and guides, but only GIMP, Krita, Photopea, and a handful of other editors can open it. HEIC (High Efficiency Image Container, ISO/IEC 23008-12) is Apple's image format — the default photo format on every iPhone with an A10 Fusion chip or newer (iPhone 7 and later) since iOS 11 shipped on September 19, 2017. HEIC stores roughly twice as much image data as a same-quality JPEG by using HEVC compression, so a 1.18 MB JPEG drops to about 756 KB as HEIC at the same visible quality.
libheif is installed separately. Converting online avoids the package-management detour.| Property | XCF | HEIC |
|---|---|---|
| Origin | GIMP, released December 15, 1997 (UC Berkeley XCF — eXperimental Computing Facility) | Apple adoption of HEIF (ISO/IEC 23008-12), iOS 11, September 2017 |
| Compression | RLE (legacy) or zlib (GIMP 2.10+) — lossless | HEVC, lossy by default; lossless option supported |
| Layers / channels / paths | Preserved | One raster layer only — flatten in GIMP before converting |
| Transparency / alpha | Yes | Yes |
| Bit depth | 8 / 16 / 32-bit per channel | 8 / 10 / 12-bit per channel |
| Typical file size for the same image | Large (uncompressed-ish) | Roughly 50% of an equivalent-quality JPEG |
| Native support | GIMP, Krita, Photopea, Seashore | iOS 11+, macOS High Sierra+, Windows 10 1803+ (HEIF Image Extensions), Windows 11 22H2+ (built-in), Android 10+ |
| Edit-in-place after export | No (you keep editing the.xcf) | No (HEIC is a delivery format) |
| Best for | Active editing, source-of-truth project file | Sharing, archiving, Apple ecosystem delivery |
| Preset | Image Quality (%) range | Use it for |
|---|---|---|
| Highest | ~95-100 | Archival exports, print-ready master HEIC |
| Very High (default) | ~85-90 | General-purpose sharing — visually indistinguishable from the source |
| High | ~75-80 | Web posts, social media, large-batch exports |
| Medium | ~60-70 | Email attachments, lightweight previews |
| Low / Lowest | ~30-50 | Thumbnails, drafts, smallest possible file |
No, and the merge is not performed here either. HEIC is a delivery format, not an editing format, and a multi-layer XCF is read as a multi-page image from which a single layer is written rather than the composite GIMP shows on canvas — so the other layers' artwork is missing and the regions they covered arrive transparent. Flatten in GIMP before uploading (Image → Flatten Image, then re-save the .xcf) and the HEIC matches your canvas exactly; a single-layer XCF is already fine. Keep the original .xcf as your editable source of truth, and if you need a layered file other apps can edit, export PSD or layered TIFF from GIMP directly — that is a GIMP export, not a conversion this page performs.
Yes — every iPhone with iOS 11 or newer (iPhone 5s and later run iOS 11; iPhone 7 with the A10 Fusion chip and later can both display and capture HEIC). AirDrop the file or save it to iCloud Drive and the Photos app opens it natively, no plugin required.
On Windows 10 version 1803 and later, install the free "HEIF Image Extensions" from the Microsoft Store and HEIC opens in Photos and File Explorer. Windows 11 22H2 and later ship HEIF support built-in. If a colleague on older Windows can't open the file, send them a HEIC to JPG link instead.
HEIC supports an alpha channel, so transparent areas in the XCF are preserved in the HEIC. If the result looks far more transparent than expected, the cause is an unflattened stack rather than the encoder — the areas the missing layers covered are simply empty. Flatten in GIMP and re-convert. If you need maximum transparency compatibility (some older HEIC viewers ignore alpha), convert to XCF to PNG instead — PNG transparency works everywhere.
Two reasons. First, XCF stores every layer, channel, and path uncompressed-ish (RLE or zlib) — a five-layer 4000×3000 XCF can hit 80-200 MB. HEIC stores a single rendered image. Second, HEVC is far more aggressive than the lossless schemes in XCF: at "Very High" quality the visible image is virtually identical, but the file is roughly half the size of a JPEG export and a fraction of the original XCF.
HEIC itself supports up to 12-bit per channel and the converter writes 8-bit by default for maximum compatibility. If your downstream tool (Photoshop, iOS Photos) expects 8-bit, leave it. Note that Photoshop currently reads only 8-bit HEIC, so 10- and 12-bit files are best opened in Apple Preview, GIMP 2.10.22+, or Affinity Photo.
Only if file size doesn't matter and you're archiving the master. Lossless HEIC is roughly 4-8× larger than the default lossy preset and is rarely necessary — at "Very High" quality (~90%) virtually no one can spot artifacts. For true archival, keep your.xcf and export an additional lossless XCF to TIFF instead — TIFF has decades-deep tooling support.
Yes. Upload as many XCF files as you want, apply the same Quality Preset and Resolution settings to all of them, or override per-file. Each file converts in parallel on our servers and downloads individually or as a ZIP archive.
They're nearly the same thing. HEIF is the umbrella ISO/IEC 23008-12 container; HEIC is HEIF specifically encoded with HEVC, which is what Apple uses and what the.heic extension implies. If a downstream tool wants the more generic extension, use XCF to HEIF — the bytes are functionally identical for HEVC content.