XCF to MOV

How to Convert XCF to MOV Online

1. Upload Your XCF Files: Drag and drop one or more GIMP project files (.xcf), or click "+ Add Files" to select them. Flatten layered projects in GIMP first (Image → Flatten Image, then re-save the .xcf) — the converter encodes a single layer rather than the merged canvas, so unflattened stacks come out missing content. Batch upload is supported, so you can build a multi-image slideshow in a single pass.
2. Pick Merge Strategy: Choose "Merge images" to combine all uploaded XCFs into one MOV, or "Video per image" to render each XCF as its own MOV clip. The merge default is the right pick for slideshows; per-image is right when you need separately editable clips for Final Cut Pro or iMovie.
3. Set Image Duration and Background Color (Optional): Default is 5 seconds per frame. Pick anything from 1/60 of a second up to 10 seconds, or any preset in between for time-lapse vs. presentation pacing. Set Background Color (default White) for letterboxed areas when an XCF's aspect ratio doesn't match the output frame.
4. Adjust File Compression and Video Resolution (Optional): Under File Compression pick a Quality Preset (Very High to Lowest), Target file size (%), Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality (CRF), or Constraint Quality. Under Video resolution keep original, choose a Fixed Resolution preset (720p, 1080p, 1440p, 2160p, 4320p, plus social-square and vertical presets), or enter custom Width and Height. Click "Convert" and download — files are processed on our servers and deleted automatically after a few hours, no sign-up, no watermark.

Why Convert XCF to MOV?

XCF is GIMP's native project format — it preserves every layer, mask, channel, path, guide, and selection at up to 64-bit precision per channel, which is exactly what you want while editing and exactly what no video editor on earth can read. To use GIMP artwork in a Mac-side editing pipeline, you have to flatten and re-encode into a video container. MOV is the natural target on macOS: it is Apple's QuickTime container (released 1991, with the.mov extension formalized in 1998) and is the default native format that Final Cut Pro and iMovie read without transcoding when the inner codec is supported.

• Final Cut Pro and iMovie slideshows from GIMP boards. Designers laying out title cards, comic panels, or storyboard frames in GIMP can flatten each board (Image → Flatten Image) and turn the set into a MOV slideshow that drops straight into a Mac timeline, instead of exporting PNG sequences and importing image-by-image.
• macOS Keynote and QuickTime Player presentations. Keynote and QuickTime Player both play MOV natively, so a single MOV slideshow plays back identically across every Mac without bundling assets.
• Client deliverables for Mac-first studios. Many ad agencies, post houses, and motion-design studios are Mac-only and prefer MOV (specifically ProRes-wrapped MOV) for archival; a flattened MOV slideshow preserves color and timing without GIMP installed at the receiving end.
• Animation roughs from layered GIMP files. When each XCF in a batch is one frame of a hand-drawn animation, "Merge images" with a 1/24-second duration produces a 24 fps MOV — useful for pencil tests before moving to a dedicated 2D animation app.
• AirDrop-friendly review reels. MOV is the format every iPhone, iPad, and Mac plays in the share sheet preview; sending a flattened MOV to a stakeholder is a one-tap action where XCF would require GIMP just to open.
• Archive of design iterations. Pairing each version of a GIMP comp with a 3-second slot in a MOV gives clients a scrub-through history they can review in QuickTime Player without any imaging software.

XCF vs MOV — Format Comparison

MOV Codec and Quality Quick Guide

Frequently Asked Questions

Are GIMP layers preserved in the MOV?

No — and they can't be. MOV is a video container with frame-based codecs; it has no concept of editable raster layers. What matters in practice is that the converter does not merge the stack for you: a multi-layer XCF is read as a multi-page image and one layer is encoded rather than the composite GIMP shows on canvas, so the remaining layers' content is missing and the areas they covered arrive transparent — which in a video frame means they fall back to the Background Color. Flatten in GIMP before uploading (Image → Flatten Image, then re-save the .xcf) and the MOV frame matches your canvas. A single-layer XCF converts as-is. Either way, keep the layered source files separately; this converter never modifies your input files.

Why isn't there a codec dropdown like other converters show?

The XCF-to-MOV pipeline picks a sensible default codec (H.264-in-MOV) so the output plays in QuickTime Player, Final Cut Pro, iMovie, and on every modern Mac without intervention. The Quality Preset, Bitrate, and CRF controls under File Compression give you the encoder knobs that actually affect output — codec choice would only matter if you were targeting a non-Apple workflow, and in that case convert XCF to MP4 is the better starting point.

Will the MOV play on Windows or Linux?

Yes. Windows 10 and 11 play H.264-in-MOV through the built-in Media Player; on older Windows, VLC plays it on every version since XP. Linux plays it through VLC, mpv, or any GStreamer-based player. The MOV container is older than MP4, but its H.264 payload is universally supported.

Can Final Cut Pro import the output directly?

Yes. Final Cut Pro accepts MOV files whose video track uses a supported codec, which includes H.264 and HEVC (H.265) per Apple's Final Cut Pro media-formats documentation. The default output here is H.264-in-MOV. If FCP optimizes media on import, it may transcode to ProRes 422 in the background — that is FCP's standard behavior, not a conversion problem.

How do I make a 24 fps animation from frame XCFs?

Set Merge strategy to "Merge images" and Image Duration to "1/24 second per frame" (the 1_24_SECOND preset). Order your XCF files so they upload in frame order — the converter renders them in the upload sequence. The output MOV plays back at 24 fps exactly. For 30 fps use 1/30 second; for 60 fps use 1/60 second.

My XCF aspect ratio doesn't match 1080p — what happens?

The image is letterboxed or pillarboxed against the Background Color (default White). Pick a Background Color that matches your design's edge tone if white bars look out of place. Alternatively, choose "Keep original" under Video resolution — the MOV will use the XCF's exact pixel dimensions, which avoids letterboxing entirely (note that some editors prefer standard 1080p/4K timelines).

Is XCF the same as a PSD?

No. XCF is GIMP's native format; PSD is Adobe Photoshop's native format. They overlap conceptually (both store layers, masks, paths, channels) but the byte-level structure is completely different. GIMP can open most PSDs and Photoshop can open some XCFs through plugins, but neither is a perfect round-trip. If you only need a still image, convert XCF to PNG or convert XCF to JPG keeps things simple.

What is the file size limit?

xconvert's free tier accepts files up to the limit shown next to the upload button on the live page; the size that matters is your XCF input, not the MOV output. GIMP project files with many high-bit-depth layers can grow into hundreds of megabytes, so flattening in GIMP (Image → Flatten Image) before you upload both shrinks an unwieldy XCF and is the step that makes the MOV frame match your canvas — it is worth doing for accuracy, not just for size.

What if I want the reverse — MOV to a still or to MP4?

For MOV-to-MP4 (the most common follow-up, e.g. to share on platforms that prefer MP4), use convert MOV to MP4. For pulling a still frame back into GIMP, export a single frame from the MOV as PNG in any video tool, then open it in GIMP — there's no direct MOV-to-XCF conversion because MOV doesn't carry layer data to recover.