Initializing... drag & drop files here
Supports: XCF
XCF is GIMP's native project format, named after the eXperimental Computing Facility at UC Berkeley where GIMP was first developed; it has stored layered raster work since December 1997. ASF (Advanced Systems Format) is Microsoft's container format, first released publicly in February 1998, and is the wrapper that holds WMV video and WMA audio. Converting layered XCF compositions into an ASF slideshow is useful when the playback target is a Windows-only environment that still expects Microsoft's media stack:
If your audience is on modern Windows 10/11, macOS, iOS, Android, or browsers, prefer XCF to MP4 — MP4 with H.264 has wider compatibility and better compression. Choose ASF only when the receiving environment specifically requires it.
| Property | XCF | ASF |
|---|---|---|
| Type | Layered raster image project | Audio/video streaming container |
| Owner / origin | GIMP (open source, 1997) | Microsoft (1998) |
| Spec status | Open, ad-hoc; documented by GIMP | Published spec, but proprietary license |
| What it stores | Layers, masks, paths, selections, channels, guides, color profiles | Encoded video (typically WMV) + audio (typically WMA) streams, metadata, indexing |
| Compression | RLE / zlib / gzip / bzip2 / xz (lossless) | Whatever codec is muxed in (lossy in practice) |
| Last spec update | Active (zlib added in v4) | Version 01.20.03, December 2004 |
| Native viewers | GIMP, Krita, Inkscape (export only), Photopea | Windows Media Player, VLC, MPC-HC |
| Typical use today | Working file for raster edits | Legacy Windows Media playback, some surveillance |
| Method | What it does | When to use |
|---|---|---|
| Quality Preset (Highest...Lowest) | Single-knob preset that maps to internal CRF + bitrate | Fastest path; pick "Very High" for review files, "Medium" for email |
| Target file size (%) | Outputs a file at N% of the input total size | When input is already close to your size budget |
| Specific file size | Targets an exact MB output via two-pass encoding | Hard caps (e.g., a 50 MB upload limit on a legacy intranet) |
| Constant Bitrate (CBR) | Fixed kbps regardless of scene complexity | Streaming over fixed-bandwidth pipes |
| Variable Bitrate (VBR) | Bitrate floats with scene complexity | Better quality-per-byte for VOD |
| Constant Quality (CRF) | Targets a perceptual quality level, file size varies | Highest quality at smallest size; default for most slideshows |
| Constraint Quality | CRF capped by a max bitrate ceiling | Quality target with a hard streaming cap |
Only when the target playback environment specifically requires ASF — Windows Media Services, an older Windows 7/8.1 corporate desktop, a legacy kiosk, or a Windows-only DVR review tool. Microsoft itself flagged the Windows Media Format 11 SDK as legacy and recommends Source Reader / Sink Writer (Media Foundation) for new code, so MP4 is the better default for general distribution. If you're sharing publicly, XCF to MP4 is the right call.
No — and they cannot be. ASF is a video container; each XCF is rendered to a single flattened RGB frame before being muxed. If you need the layers preserved for further editing, keep the XCF master and only export to ASF for distribution. To export a flat still without video wrapping, use XCF to PNG or XCF to JPG.
It's set by the Duration control under Image Duration. The default is 5 seconds per frame. Shorter values (1-2 seconds) work for stop-motion-style sequences; longer values (8-15 seconds) suit narrated photo essays. Each image gets the same hold time — there's no per-image override in this tool.
ASF is a container, not a codec. The output ASF wraps a WMV-compatible video stream so that Windows Media Player and other ASF-aware players can decode it without third-party packs. ASF can technically carry other codecs (the Microsoft spec does not mandate WMV), but standard ASF playback expects Windows Media-family content.
WMV is a video codec; ASF is the container that typically wraps WMV. Microsoft's own naming guidelines say a file should be called .wmv only when its ASF container holds Windows Media Video content, .wma for audio-only, and .asf for everything else. So a .wmv is an ASF with WMV video inside — they are not different file structures, just different extensions used to telegraph the contents.
Yes, with VLC or MPC-HC — both decode ASF/WMV cross-platform. Native Apple QuickTime and most macOS video tools do not. If your audience is on macOS without VLC, convert to MP4 instead. On Linux, mpv and VLC handle ASF; GNOME Videos / Totem usually needs the gstreamer-libav plugins installed.
Not in this XCF-to-ASF flow — input is image-only, so the resulting ASF has a video stream and no audio track. If you need a music bed, render the silent ASF here, then mux audio in a video editor (DaVinci Resolve, Shotcut, kdenlive) or use a dedicated audio-add tool. ASF accepts WMA audio as the matched audio codec.
Resolution is bounded by the largest preset offered (3840x2160 / 4K UHD), and you can also enter a custom Width x Height. There's no fixed cap on output file size — it's driven by your duration, resolution, and chosen compression method. For comfort with browser-side processing, keep total source XCF size under a couple of GB; very large inputs can be processed but will hold memory longer.
Re-run the file through Compress ASF and pick a Target file size (%) or a stricter CRF. You can also start over from XCF with a lower Quality Preset, a smaller resolution preset, or a shorter per-image duration. To switch container entirely, use ASF to MP4 — H.264 in MP4 typically gets you a 20-40% smaller file at equivalent perceptual quality.