XCF to AV1

How to Convert XCF to AV1 Online

1. Upload Your XCF Files: Drag and drop or click "+ Add Files" to select GIMP project files (.xcf). Layered images are flattened to a single rendered frame before encoding. Batch is supported — upload an entire portfolio in one pass.
2. Pick Merge Strategy and Image Duration: Under "Merge strategy," choose "Merge images" to stitch every XCF into one AV1 slideshow, or "Video per image" to output one AV1 file per upload. Set "Image Duration" between 1/60 second and 10 seconds per frame — 3-5 seconds suits portfolio reveals; 1/24 second turns a frame sequence into 24fps animation.
3. Tune Compression and Resolution (Optional): Under "File Compression," pick one of seven modes — Quality Preset (Lowest to Highest), Target file size (%), Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality (CRF), or Constraint Quality. Constant Quality with a CRF around 30 is the sweet spot for AV1 (the 0-63 range works inversely to H.264's 0-51). Under "Video resolution," keep original, choose a preset (4K, 1440p, 1080p, 720p, social presets like 1080×1350 and 1080×1920), or enter exact width and height.
4. Convert and Download: Click "Convert." Files process in your browser session — no sign-up, no watermark, no upload to a third party.

Why Convert XCF to AV1?

XCF is GIMP's native project format — released December 1997, currently at version 4 (GIMP 2.10) — and it stores layers, channels, paths, selections, and guides that no video tool understands directly. AV1, the Alliance for Open Media codec finalized March 2018, is the most efficient royalty-free video codec available: roughly 30% smaller than HEVC and 50% smaller than H.264 at matched quality (per Facebook and Moscow State University comparisons). Flattening XCF to AV1 turns design comps and digital paintings into ultra-compact video that streams cleanly on the modern web.

• Portfolio reveals on personal sites — A 1080p AV1 slideshow at CRF 32 typically fits in 2-4 MB per minute, a fraction of an equivalent MP4. Pages stay under Core Web Vitals budgets even with multiple embedded reveals.
• YouTube and social uploads — YouTube re-encodes more than 75% of its catalog to AV1; uploading AV1 directly avoids one transcode generation and preserves your encode decisions. 1080×1920 (Shorts/Reels) and 1080×1350 (feed) presets are built in.
• GIMP frame sequences exported as a project series — Animators who keep each frame as a separate XCF can pick "Merge images" with 1/24 second duration to render a 24fps AV1 directly, skipping the intermediate PNG sequence step.
• Embedded marketing reels in modern browsers — Chrome 70+, Firefox 67+, Edge 121+, Opera 57+, and Samsung Internet 12+ play AV1 in MP4 or WebM containers without a polyfill. Safari 17 added decode on M3 Macs, M4 iPad Pro, iPhone 15 Pro, and iPhone 16 hardware (older Apple devices on Safari 17 fall back).
• Long-form archival of design history — A multi-year XCF archive merged into a single low-bitrate AV1 (CRF 40, 1280×720) compresses thousands of comps into a watchable timelapse at a fraction of the original disk footprint.

XCF Layer Source vs AV1 Video Output — What Changes

AV1 Compression Modes — Pick the Right One

Frequently Asked Questions

Why convert a still image format like XCF to a video codec like AV1?

Most XCF→AV1 use cases are slideshow or animation workflows: you have multiple XCF frames and want a single small video file you can embed or upload. Other XCF converters (CloudConvert, Convertio) only output to image formats — they can't produce AV1 video. If you need a still image with AV1-style compression, convert XCF to AVIF instead, since AVIF is the still-image format derived from AV1.

Are GIMP layers, paths, and channels preserved?

No. AV1 is a video codec and only sees rendered frames. Each XCF is flattened with its current layer visibility before encoding — hide layers you don't want before exporting from GIMP, or use "Image > Flatten Image" first if you want the saved state to match what's encoded.

Why is AV1 encoding so much slower than H.264 or HEVC?

AV1 trades encode time for bitrate efficiency. The reference libaom encoder is computationally heavier than libx264 by an order of magnitude or more — that's the cost of the ~50% bitrate savings. For a 30-second 1080p slideshow this is rarely noticeable, but a 4K timelapse can take meaningful time. If speed is more important than size, convert XCF to MP4 for an H.264 output, or convert XCF to HEVC for a middle ground.

Which devices can actually play AV1 with hardware acceleration?

Hardware decode is widespread on 2022+ silicon: Intel 11th-gen (Tiger Lake) and newer, AMD RDNA 2+ GPUs and Ryzen 6000+, Nvidia RTX 30 series and newer, Apple M3 and newer, and most flagship Android SoCs (Snapdragon 8 Gen 1+, Tensor G1+, Dimensity 1000+). Older devices fall back to software decode, which works but uses more battery. ScientiaMobile's certification data shows roughly 88% of large-screen devices certified 2021-2025 ship hardware AV1 decode.

What CRF value should I use for an XCF slideshow?

For 1080p with mostly static frames (the typical XCF slideshow case), CRF 28-32 produces visually transparent results at very small file sizes — often a few MB per minute. Drop to CRF 24-28 if your XCF artwork has subtle gradients or fine texture you want preserved. Note the AV1 CRF range is 0-63 (lower is higher quality), wider than H.264's 0-51 — equivalent quality numbers are roughly +5 to +6 above H.264.

What container does the output use — MP4 or WebM?

XConvert wraps AV1 in MP4 (.av1/.mp4) by default for the broadest player compatibility. Both MP4 and WebM containers carry AV1 cleanly across Chromium browsers, Firefox, and recent Safari. If you specifically need WebM, convert XCF to WebM instead, which uses the WebM container with VP9 or AV1.

Can I add a background color for transparent areas of my XCF?

Yes. Under "Background Color," choose from 24 named colors (black, white, gray, red, blue, etc.) — AV1's Main profile doesn't carry an alpha channel, so transparent XCF pixels need a fill. Pick a color that matches your site or platform background.

Will the output play on iPhone and iPad?

Only on AV1-capable Apple hardware: M3 Macs and later, M4 iPad Pro, iPhone 15 Pro, iPhone 15 Pro Max, and the entire iPhone 16 family running Safari 17 or newer. Older iPhones and iPads do not have AV1 decode and Apple ships no software fallback. For universal Apple compatibility, convert XCF to MOV (H.264) or use XCF to MP4.

How small can an XCF-to-AV1 slideshow get?

Surprisingly small. A 30-second 1080p slideshow of mostly static design comps at CRF 35 often lands in the 1-2 MB range — AV1's intra-frame prediction is exceptional for slow-changing content. Use Constant Quality (CRF) rather than Constant Bitrate for slideshows, since CBR wastes bits on still frames. For extreme size targets, compress AV1 the output further.