XCF to AVIF

How to Convert XCF to AVIF Online

1. Upload Your XCF File: Drag and drop or click "+ Add Files" to select your GIMP project. Batch uploads are supported, so you can flatten and convert several .xcf source files in a single pass.
2. Pick a Quality Preset: Default is "Very High (Recommended)". Drop to "High" or "Medium" for typical web hero images, "Low" or "Lowest" for thumbnails where every kilobyte counts. If you want a hard ceiling, switch to "Specific file size" to target an exact size in KB or MB, or use "Image Quality (%)" to dial the AV1 encoder by percentage.
3. Set Resolution (Optional): Keep original to preserve the full XCF canvas, pick a "Preset Resolution" (4320p down to 144p), enter a custom "Width x Height" in pixels, or use "Resolution Percentage" to scale proportionally. The aspect-ratio lock keeps your composition intact when you only enter one dimension.
4. Convert and Download: Click "Convert". XCF layers are flattened, the result is encoded as AVIF, and a download button appears when each file is ready — no sign-up, no watermark.

Why Convert XCF to AVIF?

XCF is GIMP's native working format — short for "eXperimental Computing Facility" after the format's UC Berkeley origins — and it stores everything GIMP knows about a project: layers, layer groups, masks, channels, paths, guides, and selections. That's perfect for editing, but no browser, image viewer, or social platform reads .xcf directly. AVIF (AV1 Image File Format), released by the Alliance for Open Media in February 2019, is the modern web destination: AV1-based compression typically lands 50% smaller than JPEG and 20-30% smaller than WebP at the same perceived quality, with native support across Chrome 85+, Firefox 93+, Edge 121+, Safari 16.4+, and Opera 71+.

• Maximum-compression web hero images — A flattened JPEG export from GIMP at quality 80 is often 200-400 KB; the AVIF equivalent typically lands at 80-180 KB with no visible difference, helping Largest Contentful Paint stay under Google's 2.5-second Core Web Vitals threshold.
• High-bit-depth photo work without banding — AVIF supports 8-, 10-, and 12-bit color depth, so a photo edited in GIMP's high-precision linear-light mode keeps smooth gradients in skies and skin tones instead of posterizing the way 8-bit JPEG does.
• Transparency that survives the trip — Unlike JPEG, AVIF carries a real alpha channel, so transparent backgrounds, drop shadows, and feathered cutouts in your XCF flatten cleanly without a halo or matte color.
• HDR and wide-gamut exports — AVIF supports BT.2020 color primaries plus PQ and HLG transfer functions, letting GIMP HDR projects publish to web targets that can actually display them, instead of clipping to sRGB.
• CDN and Core Web Vitals savings — Cutting image weight by 30-50% directly reduces CDN bandwidth costs and pushes mobile pages further inside Google's "Good" Core Web Vitals band.
• Single-format, native-only delivery — Because AVIF support now covers ~94% of global traffic per caniuse.com, many teams ship AVIF as the primary format and only fall back to JPEG/WebP for older browsers.

XCF vs AVIF — Format Comparison

Quality Preset Guide

Frequently Asked Questions

Are GIMP layers, masks, and paths preserved when I convert to AVIF?

No — AVIF is a single-image delivery format, not an editing format, so the conversion flattens your XCF down to one composited bitmap. Keep the original .xcf as your editing source of truth and treat the AVIF as a derivative export. If you need to preserve layered structure for collaboration outside GIMP, export to PSD or OpenRaster instead, then convert that to AVIF only when you're ready to publish.

Why is the AVIF so much smaller than a JPEG export from GIMP?

Because AVIF uses AV1 intra-frame coding, which is roughly a generation ahead of JPEG's discrete cosine transform from 1992. Netflix's published AVIF tests showed cleaner detail, fewer blocking artifacts, and less color bleeding at the same bitrate. At equivalent perceptual quality, AVIF typically encodes at 50% of a JPEG's file size and 70-80% of a WebP's, which is why teams optimizing for Core Web Vitals are migrating image pipelines to AVIF.

Does AVIF preserve transparency from my XCF alpha channel?

Yes. AVIF supports a real alpha channel just like PNG and WebP, so transparent backgrounds, drop shadows, partially-transparent overlays, and feathered cutouts flatten and re-encode without picking up a matte color or visible halo. If your XCF has multiple transparent layers stacked together, GIMP's normal compositing rules are applied during flatten, then the resulting alpha mask is encoded into the AVIF.

Should I pick "Very High" preset or set "Image Quality (%)" manually?

"Very High" (the default) corresponds to roughly 90% quality and is a safe starting point for photography and hero images — visually indistinguishable from lossless on most monitors. Switch to manual "Image Quality (%)" only if you have a target — for example, q70 for a content-heavy article page where total page weight matters more than pixel-peeping, or q95 for an archival export. AVIF's quality curve is non-linear; values below 50 start to show flat-color blocking, while values above 95 give diminishing returns.

Will my XCF's HDR or 16-bit-per-channel data survive?

Partially. AVIF supports up to 12 bits per channel, so a 16-bit XCF is requantized to 10 or 12-bit on encode — that's still well above sRGB's 8-bit and avoids the visible banding you get from a JPEG export. True HDR transfer functions (PQ, HLG) and BT.2020 color primaries can be encoded into AVIF, but only if your source XCF was authored in a wide-gamut color space and exported through GIMP's color-managed pipeline before upload.

What browsers and operating systems can display AVIF?

Per caniuse.com, AVIF currently has ~94% global support: Chrome 85+ (Aug 2020), Firefox 93+ (Oct 2021), Opera 71+, Edge 121+ (Jan 2024), and Safari 16.4+ (March 2023, including iOS 16.4+). Older Edge versions from before the Chromium AVIF flip and Internet Explorer can't decode AVIF, so most teams keep a JPEG or WebP fallback in their <picture> element for the small remaining sliver.

What's the practical maximum dimension I should use?

AVIF's spec allows very large images, but in practice browsers cap decode at around 65,536x65,536 pixels and most CDNs limit stored AVIFs to several thousand pixels per side. If your XCF canvas is bigger than ~8000x8000, downscale via "Resolution Percentage" or "Width x Height" before convert — encode time grows roughly with pixel count, and few real screens benefit from images that large.

How does this differ from doing File > Export As > AVIF inside GIMP itself?

GIMP added AVIF export in version 2.10.22 (2020), so if you have a recent GIMP build you can absolutely export AVIF locally — that's the right path for one-off, full-control encodes. xconvert is for batch jobs (drop 50 XCFs at once), for cases where GIMP isn't installed (a Chromebook, a phone, a borrowed machine), and for predictable presets when you don't want to memorize libavif's encoder flags. The output AVIF is functionally the same; the workflow is faster.

What if I need a different output format instead?

We support the common GIMP export targets directly: XCF to PNG for lossless web/archival, XCF to JPG for legacy compatibility, XCF to WebP for a smaller fallback that still has near-universal browser support, and XCF to PDF if you're delivering print or document layouts. Going the other direction, PNG to AVIF and JPG to AVIF handle pre-flattened sources.