XCF to MJPEG Converter

How to Convert XCF to MJPEG Online

1. Upload Your XCF Files: Drag and drop or click "+ Add Files" to load XCF files exported from GIMP. Batch is supported — drop in a numbered sequence (frame_001.xcf, frame_002.xcf,...) and they're treated as ordered frames. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours.
2. Pick Merge Strategy and Image Duration: Default Merge strategy is Merge images (every XCF becomes one frame in a single MJPEG file). Switch to Video per image if you want one short MJPEG per XCF instead. Set Image Duration to how long each frame is on screen — 1/24 second for cinema-style 24 fps, 1/30 for video-standard 30 fps, 1/60 for high-frame-rate, or longer (1–10 seconds) for slideshow-style sequences.
3. Tune Quality, Background, and Resolution (Optional): Under File Compression, pick a Quality Preset — Highest, Very High (Recommended), High, Medium, Low, Lowest — which maps to the MJPEG qscale parameter (lower number = higher quality, range 1–31 per FFmpeg). Set Background Color (default Black) to fill any transparent XCF regions, since MJPEG has no alpha channel. Under Video resolution, keep original or pick a Preset Resolution (2160p / 1440p / 1080p / 720p / 480p / 360p / 240p), scale by percentage, or enter custom Width × Height.
4. Convert and Download: Click Convert. Each XCF is flattened to RGB, JPEG-encoded as one frame, and wrapped into the MJPEG stream. Download individually or as a ZIP. No sign-up, no watermark, no email required.

Why Convert XCF to MJPEG?

XCF (eXperimental Computing Facility, named after GIMP's birthplace at UC Berkeley) is GIMP's native layered project format — it stores every layer, mask, channel, path, guide, and selection state, which makes it indispensable for editing but useless for direct video playback. MJPEG (Motion JPEG) takes the opposite approach to modern codecs: each frame is an independent JPEG image with no inter-frame prediction, so any single frame can be decoded and cut without touching its neighbours. Converting a sequence of XCF frames to MJPEG produces a frame-accurate video stream that opens cleanly in non-linear editors, surveillance recorders, and animation pipelines. Common reasons to do this:

• Frame-accurate cut-and-splice editing — Because every MJPEG frame is a standalone JPEG, you can cut at any frame with no GOP-boundary penalty. DaVinci Resolve, Premiere, Vegas, and Avid all handle MJPEG as a low-CPU intermediate during rough-cut and assembly.
• GIMP animation export pipeline — GIMP can render each layer of an XCF (or each XCF in a numbered batch) as a still, but its native video export is limited. Exporting frames as XCF and converting the sequence to MJPEG keeps full per-frame quality without lossy re-encoding between stages.
• Dashcam, IP-camera, and CCTV workflows — MJPEG is still the default codec on many embedded surveillance devices because it tolerates dropped frames gracefully (per Wikipedia: "even if one is dropped, the rest of the video is unaffected") and decodes on low-power ARM/SoC hardware that struggles with H.264 motion-compensation.
• Medical and scientific imaging — Microscopy, ultrasound, and slow-motion capture rigs frequently store sequences as MJPEG because each frame can be archived, re-encoded, or extracted losslessly without depending on a reference frame.
• Older AVI / QuickTime pipelines — Legacy non-linear editors (Sony Vegas pre-12, older Premiere builds, Avid Media Composer pre-DNxHD) opened MJPEG-in-AVI faster than long-GOP MPEG-4 because no motion compensation is needed at decode time.
• Predictable bitrate for fixed-rate storage — Each frame has roughly the same byte budget, so disk-write rate is constant. Useful for embedded recorders sizing flash partitions, or for situations where a steady I/O profile matters more than absolute size.

If you actually need a smaller, web-friendly output instead, convert XCF straight to XCF to MP4 for H.264-in-MP4. For single-image exports use XCF to PNG (preserves alpha) or XCF to JPG (flattened). For looping animation see XCF to GIF.

MJPEG vs Modern Codecs at a Glance

Quality Preset → qscale Quick Guide

XConvert's Quality Preset maps to FFmpeg's MJPEG qscale parameter (range 1–31; 1 = best). Lower qscale means higher quality and bigger files.

Frequently Asked Questions

What's the difference between XCF and a flat image like PNG when converting to video?

XCF is GIMP's project file — it preserves every layer, mask, channel, path, guide, and selection separately, plus the canvas size and colour mode. When you convert XCF to MJPEG the converter must first flatten every layer into one composite raster image per frame, then JPEG-encode that composite. Transparent regions fall through to whatever you set in Background Color (default Black) because JPEG has no alpha channel. If you want to keep alpha through to a per-frame still, export each XCF to PNG instead via XCF to PNG.

Will my GIMP layers, masks, or paths be preserved in the MJPEG output?

No — and they can't be. MJPEG, like any video format, stores a sequence of flat raster frames. Layer structure, masks, layer groups (GIMP 2.7+), paths, guides, and channels are flattened into the rendered pixels during conversion. If you need to keep the layered project intact, hold on to the original .xcf and use the MJPEG only for playback or editing-intermediate use.

Why is my MJPEG file so much larger than an MP4 of the same footage?

MJPEG stores every frame as an independent JPEG with no inter-frame prediction. H.264/H.265 in MP4 only stores full keyframes every 1–10 seconds and describes the in-between frames as deltas. For typical footage MJPEG runs 5–20× larger than H.264 at comparable per-frame quality, per surveillance-industry benchmarks. That's the cost of frame independence. If size matters more than frame-accurate editing, convert to MP4 instead via XCF to MP4.

What frame rate should I pick for Image Duration?

For cinema-style motion use 1/24 second per frame (24 fps); for standard video use 1/30 (30 fps NTSC) or 1/25 (25 fps PAL); for high-frame-rate web video use 1/60 (60 fps). Pick longer durations (1, 2, 5, 10 seconds per frame) when each XCF is a slideshow image rather than an animation frame. The selector exposes 1/60, 1/30, 1/24, 1/10, 1/5, 1/3, 1/2 second and 1–10 second whole-second options.

My XCF has transparent regions — what happens to them?

JPEG (and therefore MJPEG) does not support alpha channels. Any transparent or partially transparent pixels in the XCF are composited against the Background Color you set during the convert step (default Black). If you have soft edges (anti-aliased masks against transparency) and the background colour doesn't match your intended scene, you'll see a coloured halo on the rendered frame. Choose a background that matches your destination (white for documents, black for cinema, chroma green for keying workflows).

Can MJPEG be played in browsers and on phones?

Yes — Motion JPEG decodes natively in Safari, Chrome, Firefox, and Edge, and on QuickTime, VLC, and most PlayStation generations. Mobile Safari and Chrome on Android also handle it. The catch is the wrapping container: a raw .mjpeg stream is video-only with no audio support, and some players prefer MJPEG wrapped inside an AVI or MOV container. If a recipient's player won't open it, try VLC (brew install --cask vlc) — its MJPEG demuxer is the most permissive.

How does XConvert preserve quality compared to GIMP's built-in video export?

GIMP's animation export (File → Export As → ".mp4" or ".webm") goes through FFmpeg as a long-GOP encode with motion compensation, which discards detail that doesn't survive inter-frame prediction. Exporting frames as XCF first and converting the sequence to MJPEG keeps each frame intra-coded — every frame is JPEG-encoded independently at the qscale you pick, with no temporal compression. At Highest / Very High presets the result is visually identical to the per-frame composite GIMP produces internally.

Does MJPEG support audio?

No — MJPEG is a video-only codec by definition (it's literally a stream of JPEG images). To attach audio you need to wrap the MJPEG video in a container that supports separate audio tracks (AVI, MOV, or MKV), then mux an audio stream alongside. If you need audio plus video in one file, convert to MP4 instead via XCF to MP4; the H.264 + AAC combination is universally supported and an order of magnitude smaller.

What's the file size limit?

XConvert processes XCF files in the browser, so the practical limit is upload size and connection speed plus willingness to wait on the upload. Large multi-layer XCFs (4K, 30+ layers) can run hundreds of MB each, and a 1000-frame MJPEG sequence at 1080p Very High preset typically lands at 1–3 GB. There's no fixed per-file cap and no quantity limit on batch jobs.