X3F to M4V Converter

How to Convert X3F to M4V Online

1. Upload Your X3F Files: Drag and drop or click "+ Add Files" to load Sigma Foveon RAW shots straight from your camera card or local drive. Batch upload is supported — turn an entire SD9, SD Quattro, or DP Merrill shoot into a single Apple TV-ready slideshow in one pass. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.
2. Pick Merge Strategy and Image Duration: Set Merge strategy to Merge images to produce one M4V slideshow from all uploaded frames, or Video per image to render each X3F as a short standalone clip. Image Duration controls how long each photo holds on screen (default 5 seconds per frame; pick anywhere from 1/60 second for a fast-cut motion sequence to 10 seconds for a portfolio reel).
3. Tune Resolution and Compression (Optional): Video resolution offers Keep original, Fixed Resolutions (Width and Height fields, aspect ratio preserved), or Preset Resolutions (144p through 2160p / 4K UHD plus Instagram-style 1080×1080 and 1080×1920). Under File Compression, Quality Preset flips between Constant Quality (target a visual fidelity level — Very High is the recommended default) and Constraint Quality (cap the bitrate for a predictable file size). Background Color (default Black) fills the letterbox/pillarbox bars when source aspect ratio differs from output.
4. Convert and Download: Click "Convert" and grab the finished .m4v. No watermark, no sign-up, no email gate — files are deleted from your session when you close the tab.

Why Convert X3F to M4V?

X3F is the proprietary raw format Sigma writes from its Foveon X3 sensors — debuted in 2002 with the Sigma SD9 and used through the SD10, SD14, SD15, SD1, SD1 Merrill, the DP/DP Merrill compact line, and the SD Quattro/SD Quattro H mirrorless bodies. Foveon's three-layer stacked photodiode design captures full RGB at every photosite, which produces unusually crisp per-pixel detail but leaves you with a proprietary file no consumer playback device can read. M4V is Apple's MP4 variant — same MPEG-4 Part 14 container, but the .m4v extension is what Apple TV, the macOS/iOS TV app, iTunes, and QuickTime use to auto-route playback. (Apple's commercial M4V downloads carry FairPlay DRM; M4V files you create yourself are DRM-free and play anywhere MP4 plays.) Converting a sequence of X3F frames straight to M4V skips the "export each raw to JPEG, then assemble in iMovie" detour. Typical use cases:

• Apple TV slideshow from a Foveon shoot — Drop a wedding, landscape, or studio session onto an Apple TV 4K with native folder recognition; M4V is the format the TV app prefers and won't require re-encoding on import.
• Portfolio loop for gallery displays — Render a 30-frame DP Merrill series at 4K (3840×2160) and 5 seconds per frame for a 2.5-minute looping reel that plays cleanly on any HDMI display through an Apple TV or QuickTime kiosk.
• iMessage / Photos sharing — M4V plays inline in Messages and the Photos app on iPhone and iPad without prompting users to download a viewer the way .x3f would.
• Stop-motion and time-lapse from sd Quattro bursts — At 1/24 second per frame the converter cuts a cine-style 24 fps clip from a sequence of stills, useful for tripod-mounted golden-hour or astrophotography sets.
• Client review without sending raws — A 50-frame slideshow at 1080p averages 40-80 MB at the Very High preset, light enough to email or AirDrop while preserving Foveon's per-pixel sharpness in the rendered video.
• Archive playback after Sigma Photo Pro stops working — Apple no longer ships native X3F support in Preview or Photos, and third-party tools have struggled with macOS Sonoma compatibility; baking the shoot into M4V locks in a format the Apple ecosystem will read for the long haul.

If you only want stills, run X3F to JPG, X3F to PNG, X3F to TIFF, or X3F to HEIC instead. Need a non-Apple container? Try X3F to MP4 or X3F to MOV. To assemble already-rendered photos into video, use Image to Video.

X3F vs M4V — Format Comparison

M4V Resolution & Frame-Duration Guide

Image Duration: pick 5 seconds for a standard portfolio cadence, 2-3 seconds for a music-bed slideshow, 1/24 second for a 24 fps stop-motion / time-lapse render, and 10 seconds when each shot needs reading time (text-heavy or client-review reels).

Frequently Asked Questions

Why convert X3F to M4V instead of just MP4?

Container-wise they're nearly identical — both are MPEG-4 Part 14 with H.264/AAC inside. The difference is signalling: macOS, iOS, Apple TV, iTunes, and the Photos app treat .m4v as "this is meant for the TV app" and auto-import it accordingly, while .mp4 is more often opened in QuickTime or a third-party player. If you're feeding an Apple-ecosystem device, M4V is the more polite extension. If you want maximum cross-platform compatibility (Android, Windows Media Player, smart TVs), pick X3F to MP4 instead — the bytes are essentially the same but .mp4 plays without the second-guessing some non-Apple players do on .m4v.

Does the M4V file get FairPlay DRM?

No. FairPlay is applied by Apple's iTunes Store servers when they sell or rent a movie — it's not part of the M4V container itself. Files you create from your own X3F shots are DRM-free and play in VLC, on Android, in Chrome (with the right codec), and anywhere standard MP4 plays. If a player refuses, just rename the file to .mp4 and try again — the data is byte-compatible.

Why does Apple Preview show a generic icon instead of my X3F thumbnail?

Apple has never shipped native Sigma raw support in Finder/Preview/Photos for X3F. Sigma's older Sigma Photo Pro and third-party tools (Iridient X-Transformer, RawTherapee, Capture One via plug-in) handled this in the past, but several stopped working cleanly on macOS Sonoma. Rendering your shoot to M4V (or to a standard still format like JPG or TIFF, which Preview does read) bypasses the issue — the resulting video is recognised everywhere Apple recognises MP4.

Should I pick Constant Quality or Constraint Quality?

Use Constant Quality (Very High) for portfolio and client-review reels where visual fidelity matters most and you don't care about exact file size — the encoder spends whatever bits the scene needs. Use Constraint Quality when you need to hit a specific MB budget (e.g., fitting under an iMessage attachment limit or a streaming platform's per-file cap); it caps the bitrate so the size stays predictable, accepting some quality loss on busy frames.

What frame rate does the output run at?

Output frame rate is derived from your Image Duration choice. At 5 seconds per frame the video runs at 0.2 fps for slideshow pacing (the file is still encoded at a standard 24/25/30 fps internally, with each photo simply held for the chosen duration). For a true motion sequence — burst, stop-motion, or time-lapse — pick 1/24 second (24 fps cine), 1/30 second (30 fps standard video), or 1/60 second (60 fps smooth motion). Use 2-3 seconds for slideshows set to a music bed.

Will Foveon's per-pixel color detail survive the conversion?

You'll keep the visible per-pixel sharpness Foveon is known for, but you do lose the raw 14-bit RGB-per-photosite depth — M4V encodes to 8-bit YCbCr 4:2:0, which is the H.264 baseline that virtually every consumer playback device expects. For archival or further editing, keep the original X3F files; M4V is the delivery format, not the master.

Can I add a soundtrack or music bed?

The X3F-to-M4V renderer doesn't mix audio at conversion time — the output is silent video. To add music, render the slideshow here, then import into iMovie, CapCut, DaVinci Resolve, or any non-linear editor and lay an audio track underneath. If you already have a finished video that needs container changes, see MP4 to M4V.

Why are there black bars on my output?

Foveon sensor aspect ratios (typically 3:2 from DSLR bodies, sometimes 16:9 on newer Quattro cameras) often don't match the 16:9 or 1:1 output preset you picked. The converter pads the difference using your Background Color choice (default black). To avoid bars, pick a Preset Resolution that matches your source aspect ratio (e.g., a 3:2 custom Width/Height) or accept the letterbox/pillarbox for a clean cinematic frame.

How many X3F files can I batch in one render?

There's no fixed file-count cap. Practical limits come from browser memory — Foveon files are 15-50 MB each at full res, so a hundred frames is a 2-4 GB working set. For very large shoots, render in batches of 50-100 frames and concatenate the resulting M4V clips in iMovie or with ffmpeg -f concat. Sigma Photo Pro's typical export sessions follow the same rough chunking pattern.