Initializing... drag & drop files here
Supports: XCF
XCF is GIMP's native format — released December 15, 1997 and named for the eXperimental Computing Facility at UC Berkeley where GIMP was started. It stores everything: layers, masks, channels, paths, selections, guides, and text objects, which is exactly why it's unusable on the web. Browsers, social platforms, and presentation tools cannot decode XCF. Converting to WebM produces a Matroska-based video file (WebM is a constrained Matroska profile, launched by Google at I/O on May 18, 2010) that plays inline in HTML5 <video> and embeds in any modern site without plugins.
<video autoplay loop muted playsinline> and a poster fallback.| Property | XCF | WebM |
|---|---|---|
| Type | Layered raster image (GIMP project) | Web video container |
| Container / structure | Native GIMP binary (versioned) | Matroska profile |
| Stores | Layers, masks, channels, paths, selections, guides | Video + audio + text tracks |
| Codecs | N/A (raster pixels per layer) | Video: VP8, VP9, AV1. Audio: Vorbis, Opus |
| Browser playback | None | Chrome 25+, Firefox 28+, Edge 79+, Opera 16+, Safari 16+ desktop, iOS 17.4+ |
| Color depth | Up to 32-bit float per channel (GIMP 2.10+) | 8/10/12-bit (codec dependent) |
| Animation | Frames as layers (GIF/WebP via export) | Native video, any frame rate |
| Typical use | GIMP working files, intermediate edits | Web embeds, hero loops, social uploads |
| First release | 1997 | 2010 |
| Setting | Use case | Trade-off |
|---|---|---|
| Quality Preset: Highest | Master/archival slideshow | Largest file; near-lossless |
| Quality Preset: Very High (default) | Site hero, portfolio | Excellent perceived quality, moderate size |
| Quality Preset: High | Standard web embed, YouTube source | Good balance — recommended for most uploads |
| Quality Preset: Medium / Low | Forum or chat embeds, fast LCP | Visible artifacts in flat color regions |
| Constant Quality (CRF) | When you want consistent visual quality regardless of motion | Variable file size; CRF 30–35 typical for VP9 web slideshows |
| Target file size (%) | Hitting a hard upload cap (e.g., a 10 MB Discord limit) | Quality scales to fit |
| Specific file size | Producing exactly N MB | Same as above with a hard ceiling |
| Scenario | Resolution | Duration per frame | Merge strategy |
|---|---|---|---|
| Website hero loop | 1920×1080 or 1280×720 | 3–5 seconds | Merge images |
| Vertical social (Reels, Shorts, TikTok) | 1080×1920 | 3 seconds | Merge images |
| Square feed post (Instagram) | 1080×1080 | 4 seconds | Merge images |
| 4K design reel | 3840×2160 | 5 seconds | Merge images |
| Per-mockup standalone clips | Keep original | 6–10 seconds | Video per image |
Yes — each XCF is rendered through GIMP's compositor with current layer visibility, opacity, and blend modes applied, then handed to the video encoder as a single image per frame. If you want a specific layer hidden, toggle its visibility off in GIMP and resave the.xcf before uploading.
VP9 is the safer default in 2026. It plays in every browser that supports WebM and has been hardware-accelerated on most chips since around 2017. AV1 compresses ~30–50% smaller than VP9 at the same quality but its hardware decode is limited to recent silicon — Apple only added AV1 hardware decode on M3 Macs and iPhone 15 Pro / iPhone 16 generation. For a public website where visitors might be on older phones or Intel laptops, ship VP9.
VP9 and AV1 are tuned for natural video, not still images that hold for seconds. When a frame doesn't change at all, the encoder still encodes timing and minimal residuals every keyframe. Drop the frame rate (the encoder targets 30 fps internally even for slideshows) by extending each image's duration, or use Constant Quality (CRF) at a higher value (35–40) — for static slideshows that's near-invisible quality loss with much smaller files.
Not in this single XCF→WebM step — the input is purely images. Convert first, then if you need audio, run the WebM back through a video editor or use Compress WebM for re-encoding. WebM supports Vorbis and Opus audio when present; Opus is the modern choice and is also royalty-free.
Yes, on iOS 17.4 (released March 2024) and later for Safari. Older iOS versions had only partial WebM support — VP8 worked on some, VP9 on others. If your audience includes pre-iOS 17 devices, also publish an MP4 fallback. After conversion you can run WebM to MP4 to produce that fallback from the same source.
Yes. Under "Background Color," pick from the named palette (Black, White, Gray, plus full color options including Crimson, Navy, Teal, etc.). This fills any padding when your XCF aspect ratio doesn't match the chosen output resolution. Default is Black, which matches <video> element default backgrounds in most browsers.
GIF is capped at a 256-color palette and always lossless (no temporal compression), which makes file sizes huge. WebP animation is much better — true 24-bit color, smaller files — and GIMP exports it natively. WebM goes further with proper interframe compression (VP9 or AV1), making it the right choice when total run time exceeds a few seconds. For a 2-second 5-frame logo reveal, WebP is fine; for a 30-second design reel, WebM is dramatically smaller.
Beyond video, you can flatten to a still image: XCF to PNG for lossless web-ready stills (preserves transparency), XCF to JPG for photographs and smaller hero images, or XCF to GIF when you need the legacy animated-GIF compatibility. For a non-WebM video container, XCF to MP4 uses H.264 by default for broader legacy device coverage.
Files process for the duration of your conversion session and are not used for any other purpose. There's no account requirement, no watermark on output, and no sign-up wall — drop the XCF, get the WebM, leave.