X3F to MOV Converter

How to Convert X3F to MOV Online

1. Upload Your X3F Files: Drag and drop or click "+ Add Files" to load Sigma Foveon RAW files from your computer. Batch upload is supported — drop an entire shoot in at once. Files stay in your browser session; nothing is mailed off to a third-party processor.
2. Pick a Merge Strategy and Frame Duration: Choose Merge images to stitch every X3F into a single MOV slideshow, or Video per image to render one MOV per source frame. Set Duration to anything from 1/60 second (60 fps timelapse) up to 10 seconds per frame for a contemplative slideshow.
3. Set Background Color and Resolution (Optional): Pick a Background Color (Black is the default — useful when a portrait X3F is letterboxed into a landscape MOV) and a Video Resolution — keep the source pixel dimensions, choose a Preset Resolution (1080p, 1440p, 2160p, vertical 1080×1920 for Reels, square 1080×1080), or enter a custom Width × Height with aspect ratio locked.
4. Tune Quality and Download: Under File Compression, pick Constant Quality or Constraint Quality, then a Preset (Low / Medium / High / Very High). Click Convert and download the MOV — drop it straight into Final Cut Pro, iMovie, Premiere, DaVinci Resolve, or QuickTime Player.

Why Convert X3F to MOV?

The Sigma X3F format stores Foveon X3 RAW data — a three-layer stack that captures red, green, and blue at every pixel rather than interpolating from a Bayer mosaic. That detail is invaluable for stills, but X3F has no native motion variant and is unsupported by Apple's QuickTime stack, Final Cut Pro, iMovie, Premiere, DaVinci Resolve, and every web browser. Wrapping the frames in a MOV container (Apple's QuickTime File Format — the same structure the ISO base media MP4 spec was derived from) makes them universally editable.

• Timelapse from a Sigma DP Quattro or sd Quattro shoot — A 240-frame X3F timelapse at 1/24 second per frame becomes a 10-second 24 fps MOV ready for Final Cut Pro's timeline without any intermediate DNG export pipeline.
• Client slideshow / proofing reel — Render a single MOV at 5 seconds per frame and email or AirDrop it; clients on macOS open MOV in QuickTime Player without any plugin, while X3F throws "unsupported format" everywhere except Sigma Photo Pro.
• Final Cut Pro and iMovie compatibility — Apple's Final Cut Pro does not list X3F among supported RAW still formats (only generic "RAW" via macOS Media Extensions, which excludes Foveon). MOV at H.264 or ProRes drops in natively.
• Logic Pro / Motion / Compressor projects — All three Apple pro apps consume MOV as their native still-from-image and slideshow ingest path; X3F has no codec component on macOS.
• Instagram Reels and TikTok exports — Pick 1080×1920 vertical at 3 seconds per frame to turn a Sigma Merrill street-photography series into a swipeable Reel, then upload the MOV directly (Instagram re-encodes to H.264 on its end).
• Archival viewing copies — Keep your X3F masters, but bake a MOV proof so non-Sigma users (and your future self on a machine without Sigma Photo Pro installed) can browse the shoot without specialised tooling.

If you only need stills, convert X3F to JPG, X3F to PNG, or X3F to TIFF first; for MP4 instead of MOV use X3F to MP4. For other RAW slideshow pipelines see ARW to MOV (Sony) or general JPG to MOV.

X3F vs MOV — Format Comparison

Codec and Quality Preset Guide

The converter wraps the slideshow in MOV using H.264 by default — the most universally compatible codec for the container. Pick your preset based on where the MOV is going:

Constant Quality locks a perceptual quality target and lets bitrate float — ideal when you want consistent look across frames of varying complexity. Constraint Quality caps the bitrate ceiling, useful when you have a hard size budget (e.g., fitting under Slack's 1 GB free-tier upload or a 25 MB email cap).

Frequently Asked Questions

Why convert X3F to MOV instead of staying with the RAW files?

X3F is supported almost exclusively by Sigma Photo Pro and a handful of community tools (x3f_extract, X3Fuse, RawTherapee). It has no motion variant, no in-browser viewer, and Final Cut Pro, iMovie, Premiere, and DaVinci Resolve don't recognise the extension. MOV is the QuickTime container — Apple's native multimedia format and the parent spec that MP4 was forked from in 2001 — so the resulting file opens everywhere on macOS, in QuickTime Player on Windows, and (for H.264-encoded MOVs) in modern web browsers.

Which Sigma cameras produce the X3F files this tool accepts?

Every Sigma camera with a Foveon X3 sensor writes X3F: the DSLR line (SD9, SD10, SD14, SD15, SD1, SD1 Merrill), the DP fixed-lens compacts (DP1/DP2 and their s/x/Merrill revisions, plus DP0/DP1/DP2/DP3 Quattro), and the sd Quattro / sd Quattro H mirrorless bodies. The sd Quattro line can also write DNG via firmware update; if your camera shoots DNG you can use that path too, but this converter handles native X3F directly.

Should I pick H.264 MOV or ProRes for editing in Final Cut Pro?

This converter outputs H.264 MOV, which Final Cut Pro 11 imports natively and works for almost every workflow. Use ProRes only if you plan heavy colour grading or compositing — and in that case render H.264 MOV here, then transcode to ProRes 422 inside Final Cut Pro itself (File → Transcode → Create Optimized Media), which produces a higher-fidelity intermediate than any in-browser encoder can.

Does converting X3F to MOV preserve Foveon's three-layer colour accuracy?

Partially. The Foveon sensor's per-pixel RGB capture is debayered (or rather, de-stacked) during the X3F decode, and the result is rendered into the MOV at 8-bit YUV 4:2:0 — the colour-subsampled format H.264 uses for compatibility. Most of the visible Foveon "look" — micro-contrast and resolved detail in highlights — survives at the Very High preset, but if you need 10-bit or 4:2:2 chroma for grading, export X3F to 16-bit TIFF in Sigma Photo Pro first, then assemble those TIFFs into ProRes inside Final Cut Pro.

Can I make a timelapse from a sequence of X3F frames?

Yes — upload the whole sequence, leave Merge images selected, and set Duration to 1/24 second per frame for cinematic 24 fps, 1/30 second for 30 fps, or 1/60 second for 60 fps slow motion. 240 X3F frames at 1/24-second is exactly 10 seconds of footage. The output is a standard MOV ready to drop on any timeline.

What's the difference between MOV and MP4 here?

MP4 (ISO/IEC 14496-14) was published in 2001 and is structurally derived from the QuickTime File Format — same atom-based container, same codec support for H.264/H.265, broadly the same playback compatibility. Practical differences: MOV supports a few Apple-specific codecs (ProRes, ProRes RAW, ALAC) that MP4 cannot carry, and MOV is the native macOS choice. If you need maximum cross-platform compatibility (Windows Media Player, Android, smart TVs), pick X3F to MP4 instead.

Why is the background color option useful?

Foveon sensors produce a fixed aspect ratio (3:2 on Quattro, 3:2 / 16:9 on most DSLRs). If you render to a vertical 1080×1920 Reel or square 1080×1080 Instagram frame, the image is letterboxed and the empty area is filled with the Background Color you picked. Black matches most playback environments; choose a brand colour or white for client deliverables.

Will EXIF metadata (shutter speed, aperture, ISO, lens) survive the conversion?

X3F EXIF lives in the still-image header and is not carried into the MOV's track metadata — MOV stores its own track-level metadata (creation date, codec parameters, colour space) but doesn't have per-frame EXIF fields. If you need to preserve the shooting metadata, export X3F to a TIFF or JPG sidecar first via X3F to TIFF or X3F to JPG and archive those alongside the MOV.

Is anything uploaded to your servers?

Processing happens in your browser session and files are deleted after your session ends. No account is required and there are no watermarks, file-count limits, or hidden Pro tiers gating the conversion.