Initializing... drag & drop files here
Supports: XCF
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.
| Property | XCF (GIMP) | MOV (QuickTime) |
|---|---|---|
| Type | Layered raster project | Video container |
| Owner | GIMP / GNOME (free, open) | Apple (since 1991) |
| Stores | Layers, masks, channels, paths, guides, selections | Video, audio, subtitle tracks |
| Bit depth | Up to 64-bit float per channel | Codec-dependent (8-, 10-, 12-bit) |
| Animation | No native frames; one composited image | Yes, full motion video |
| Best editor | GIMP (2.10+ / 3.x) | Final Cut Pro, iMovie, DaVinci Resolve, Premiere Pro |
| Plays in browsers | No | Safari only (Chrome/Firefox limited; depends on inner codec) |
| Portability | Low — GIMP-specific | High on Apple devices, good elsewhere |
| Typical use | Active design project | Final delivery, editing source |
| Use case | Recommended setting | Why |
|---|---|---|
| Final Cut Pro / iMovie import | Quality Preset: Very High | FCP and iMovie accept H.264-in-MOV without transcoding; very high keeps detail in flat colors and gradients common in GIMP comps |
| Keynote / QuickTime playback | Quality Preset: High at 1080p | Plenty of headroom for projected slideshows without bloated file size |
| Time-lapse from GIMP frames | Image Duration: 1/24 sec, Merge images | Produces 24 fps motion; matches film cadence for pencil tests |
| Long presentation slideshow | Image Duration: 5-10 sec, Quality: High | Comfortable read time for text-heavy slides without quality loss |
| Smallest shareable MOV | Target file size (%) at 25-50% | Constrains output to a percentage of estimated full-quality size — easiest one-shot compression |
| Archival master | Constant Quality (CRF), low CRF value | CRF preserves visual quality at the cost of file size; better than fixed bitrate for stills-based video |
No — and they can't be. MOV is a video container with frame-based codecs; it has no concept of editable raster layers. Each XCF is flattened (composited top-to-bottom with current visibility, opacity, and blend modes) into a single image before it becomes a frame in the MOV. If you need layer access later, keep the XCF source files separately; this converter never modifies your input files.
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.
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.
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.
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.
The image is letterboxed or pillarboxed against the Background Color (default Black). Pick a Background Color that matches your design's edge tone if black 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).
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.
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 before export (File > Export As in GIMP) can shrink an unwieldy XCF before you upload — the MOV result is identical either way, since the converter flattens internally.
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.