X3F to OGV Converter

How to Convert X3F to OGV Online

1. Upload Your X3F Files: Drag and drop or click "+ Add Files" to load Sigma X3F raws from your DP Merrill, dp Quattro, SD Quattro, SD1, or other Foveon body. Batch upload is supported — drop a whole shoot in one pass. files are processed on our servers and deleted automatically after a few hours; no Sigma Photo Pro or Lightroom plug-in needed first.
2. Choose Merge Strategy and Image Duration: Set Merge strategy to "Merge images" to chain every X3F into one slideshow OGV, or "Video per image" to emit one OGV per still. Pick an Image Duration (default 5 seconds per frame) — 3–5 seconds is typical for photo slideshows, 1–2 seconds for time-lapse playback of bracketed Foveon frames.
3. Pick Quality Preset and Resolution (Optional): Under File Compression, choose Constant Quality (recommended — fixed visual quality, variable bitrate) or Constraint Quality, then a Preset of Very High, High, Medium, Low, or Very Low. Default is Very High. Set Video resolution to Keep original, a Fixed resolution (1920×1080, 1280×720), or a Preset resolution (1080p, 720p, 480p). Pick a Background Color if your aspect ratios don't all match.
4. Convert and Download: Click "Convert" and grab the OGV file (or ZIP for per-image output). No sign-up, no watermark, no Sigma Photo Pro round-trip.

Why Convert X3F to OGV?

X3F is Sigma's proprietary RAW container for cameras using the Foveon X3 three-layer sensor — DP1/DP2/DP3 Merrill, the dp0–dp3 Quattro fixed-lens compacts, the SD Quattro and SD Quattro H mirrorless bodies, and older SD9 through SD1 Merrill DSLRs. Foveon stacks red, green, and blue photodiodes vertically at each pixel site instead of using a Bayer color filter array, so X3F files store three full color channels per location and read large (Merrill bodies write 46-megapixel-equivalent files; Quattro bodies write around 39 MP). That richness is unplayable as a video — encoders need a flat 2D frame stream, and X3F first has to be developed (Sigma Photo Pro, X3F SDK, or libraw via dcraw) before it can become a slideshow frame.

OGV (Ogg Theora video, container .ogv) is the open, royalty-free Xiph.Org format historically used as a free-software alternative to H.264. It's still useful in a narrow set of scenarios:

• Wikimedia Commons / Wikipedia uploads — Commons accepts WebM, Ogg Theora, and MPEG-1/2 only. WebM (VP9 + Opus) is now the official recommendation (about 92% of 2024 browsers play it natively, versus around 8% for Theora), but OGV is still accepted for legacy upload pipelines and bots that haven't migrated.
• Open-source / GPL projects with strict patent policies — Theora is unencumbered by codec royalties, which is why Debian, Fedora's default media stack, and some museum/library archival workflows still preferred OGV historically.
• GNU/Linux desktop slideshows — Older GNOME and KDE media apps shipped Theora playback out of the box without proprietary codec packs.
• MediaWiki self-hosted instances — Internal wikis that mirror Commons' policies still accept OGV uploads as a documented archive format.
• Legacy embed compatibility — Pre-2015 HTML5 <video> deployments used <source type="video/ogg"> as the Firefox fallback alongside MP4 for Safari.

For everything else in 2026 you almost certainly want WebM instead — Chrome 120+, Edge 122+, and Firefox 130+ have all disabled or removed Theora playback. If your destination isn't Wikimedia Commons or a Theora-mandated workflow, convert your Foveon frames with X3F to WebM or X3F to MP4 instead. To keep stills as stills, use X3F to JPG, X3F to PNG, or X3F to TIFF.

X3F vs WebM vs OGV — What You're Trading

OGV Quality Preset Cheat Sheet — Theora -q Settings

xconvert's "Constant Quality" preset maps to Theora's quality scale (-q 0 lowest to -q 10 highest, with subjective sweet spot around 6–8). Use this when you want consistent visual quality across slides regardless of how busy each Foveon image is.

"Constraint Quality" lets you cap the maximum and minimum quality bounds — useful when one or two ultra-detailed Foveon frames would otherwise blow up the file at the expense of simpler frames.

Frequently Asked Questions

Why are my Foveon X3F files so much bigger than the OGV output?

A single 46 MP Merrill X3F can run 50–60 MB on disk because it stores three full color channels per pixel location (no demosaicing). The OGV output is a heavily compressed Theora video at 8-bit 4:2:0 chroma subsampling, so each second of slideshow at 1080p Very High typically lands at 1–3 MB. A 30-slide sequence with 5-second durations (150 seconds total) will land around 150–450 MB depending on image complexity and quality preset — still dramatically smaller than the source X3Fs combined.

Will browsers actually play my OGV file in 2026?

Mostly not natively. Chrome 120+ disabled Theora by default in late 2023, Edge 122+ followed, and Firefox removed Theora support in version 130. Safari has never supported Theora. The only reliable native players today are VLC, MPV, mpv-based desktop apps, and older Linux media players (GNOME Videos, KDE Dragon Player). For browser playback, sites like Wikimedia Commons use the ogv.js JavaScript fallback to decode Theora in Safari and Chrome — your file works on Commons, just not in a vanilla <video> tag.

Should I use OGV or WebM for Wikimedia Commons uploads?

WebM with VP9 video and Opus audio is now Commons' official recommendation — about 92% of 2024 visitors can play it natively versus around 8% for Theora. OGV is still accepted as a documented format, but the upload wizard and Commons documentation actively steer you toward WebM. Use OGV only if your downstream tool, archive policy, or self-hosted MediaWiki instance specifically requires Theora.

Do I need to develop the X3F in Sigma Photo Pro first?

No. xconvert decodes the X3F bitstream server-side using the libraw / dcraw code path, applies the embedded Sigma color matrix, and emits a flat RGB frame to feed the Theora encoder. You won't get Sigma Photo Pro's signature Foveon "X3 Fill Light" or per-camera color science, so for portfolio-grade colour grading you may prefer to develop X3F to TIFF or PNG in Sigma Photo Pro first, then upload those instead.

What happens if my X3F files have different aspect ratios?

OGV needs a single fixed frame size, so xconvert letterboxes or pillarboxes each frame to match the chosen Video resolution. Pick a Background Color that suits your slideshow — black for photography portfolios, white for product reels, or a brand colour. If every X3F is from the same camera (always the case with Foveon bodies — Merrill is always 4704×3136, Quattro typically 5424×3616) you won't see any bars.

Can I add audio to the OGV slideshow?

The image-to-video converter emits silent OGV by default — there's no audio track to encode. To add music or narration, convert the silent OGV to your destination format first, then mux audio in a tool like FFmpeg, Audacity, or Shotcut. The Theora container pairs naturally with Vorbis or Opus audio inside the same .ogv file.

Why is the file size so large for a slideshow?

Theora is a 2008-era codec and its compression efficiency is roughly half that of VP9 at the same visual quality. A 30-second 1080p OGV at Very High typically lands around 60–150 MB, where the equivalent WebM (VP9) would be 25–60 MB and an MP4 (H.264) around 40–80 MB. If file size matters more than format purity, X3F to MP4 or X3F to WebM will produce a smaller, more compatible file from the same source frames.

Will Wikimedia Commons accept the file?

Yes, OGV is on Commons' accepted-formats list. The hard upload cap is 5 GiB total file size (with chunked upload via the Upload Wizard); the practical single-request cap is 100 MiB. A 1080p OGV slideshow at Very High runs roughly 2 MB/second, so you'd hit the 100 MiB limit somewhere around the 50-second mark — keep slideshows short or use chunked uploads for anything longer than a couple of minutes.

Is anything uploaded to your servers permanently?

files are processed on our servers and deleted automatically after a few hours and deleted after the session ends. No account is required, there are no watermarks, and there's no file-count limit or hidden Pro tier gating the converter.