Initializing... drag & drop files here
Supports: X3F
X3F is Sigma's proprietary RAW container for Foveon X3 sensors, which capture full red, green, and blue at every photosite by stacking three photodiodes vertically instead of using a Bayer color filter (Foveon, Inc., now owned by Sigma). The format is rich but heavy — a single sd Quattro H file can exceed 50 MB — and outside Sigma Photo Pro, Adobe Camera Raw, or libopenraw, almost nothing opens it natively. AVIF (AV1 Image File Format, AOMedia v1.0.0 released February 2019) is the modern destination: roughly half the size of JPEG at equivalent visual quality, 10/12-bit color, HDR via BT.2100 PQ/HLG, and native rendering in every current desktop and mobile browser.
| Property | X3F (Sigma RAW) | AVIF |
|---|---|---|
| Type | Camera RAW container | Compressed image (AV1 intra-frame) |
| Maintainer | Sigma Corporation (Foveon, Inc.) | Alliance for Open Media |
| First release | 2002 (Sigma SD9) | Feb 2019 (v1.0.0) |
| Color capture | 3 stacked photodiodes per pixel (no demosaic) | Standard RGB / YUV after encode |
| Bit depth | 12-14 bit sensor data | 8 / 10 / 12-bit |
| Compression | Mostly lossless, proprietary | Lossy and lossless |
| Typical file size | 20-60 MB | 100 KB - 2 MB at web quality |
| HDR | Stored as raw sensor values | Yes (BT.2100 PQ/HLG) |
| Animation | No | Yes (image sequences) |
| Browser support | None native | Chrome 85+, FF 93+, Safari 16.4+, Edge 121+ |
| Best for | Editing, archival of Foveon shots | Delivery, web, sharing |
| Preset | Typical AVIF size (from 20 MB X3F) | When to use |
|---|---|---|
| Highest | 1.5 - 3 MB | Print drafts, client review, archive copies |
| Very High (default) | 600 KB - 1.5 MB | Portfolio sites, fine-art prints to screen |
| High | 250 - 600 KB | Blogs, news, general web delivery |
| Medium | 100 - 250 KB | Thumbnails, fast-loading galleries, mobile-first |
| Low / Lowest | 30 - 100 KB | Placeholders, contact sheets |
Use the Specific file size option when you need a hard cap (e.g., a 500 KB CMS limit). The encoder will iterate to land within the target.
Foveon sensors record full red, green, and blue at every photosite via three stacked photodiodes, so a 15 MP Sigma SD1 Merrill file effectively stores 45 million color samples instead of the ~15 million a Bayer sensor records before demosaic. That triple data plus minimal RAW compression is why a single sd Quattro H frame can run 50+ MB. AVIF discards what your eye cannot perceive and routinely compresses the same image into the 1-2 MB range with no visible difference at normal viewing distances.
For viewing, yes — at the Very High or Highest preset, AVIF 10-bit preserves the smooth color transitions and resolved fine detail that make Foveon distinctive. What you lose is the ability to re-develop the file (white balance, exposure recovery, demosaic algorithm choice). If you still want to edit, keep the X3F as your master and treat AVIF as the delivery export. See X3F to TIFF for a 16-bit editable intermediate.
Yes. We handle the older SD9/SD10/SD14/SD15 X3F variants and the newer Quattro architecture (where the top layer carries 4x the resolution of the lower two). The Sigma X3F plug-in for Photoshop is otherwise the only way to open Quattro files in Adobe — you can skip that step entirely if you only need a deliverable image.
Very High is the sweet spot — it typically compresses a 20 MB X3F to under 1.5 MB with no perceptible artifacts on retina displays, and it preserves the subtle tonal gradations Foveon owners care about. Step up to Highest only for files you'll zoom into (large prints, pixel-peep reviews). Drop to High or Medium for thumbnail grids or above-the-fold hero images where load time matters more than 100% pixel fidelity.
The encoder writes 10-bit AVIF by default when the source is high-bit-depth RAW, which is the right call for Foveon — 12-bit sensor data downsampled to 8-bit JPEG visibly bands in skies and skin. Browsers that don't yet handle 10-bit AVIF (a small minority) downconvert gracefully on display.
At matched visual quality, AVIF files are typically 20-30% smaller than WebP and 40-50% smaller than JPEG (Netflix and Cloudinary studies). AVIF also supports 10/12-bit color, HDR (PQ and HLG transfer functions per BT.2100), and lossless mode — none of which JPEG offers. WebP is still useful when you need Internet Explorer (which AVIF dropped entirely) or pre-2022 Safari support; otherwise AVIF wins on every axis. If you want JPEG for legacy compatibility, see X3F to JPG.
Yes. The format has been remarkably stable since its 2002 debut on the SD9 — header layout and Foveon raw sensor data block are similar across the Sigma lineup, with format variations introduced for DP1 (2008) and the Quattro architecture (2014). The converter recognizes all common variants.
Standard EXIF (make, model, focal length, shutter, ISO, GPS if your camera tagged it) is preserved into the AVIF output. Sigma-specific MakerNotes (X3 Fill Light, Foveon-specific white balance presets) may not survive since AVIF metadata containers don't carry vendor-proprietary RAW blocks — keep the original X3F if you need round-trip editing in Sigma Photo Pro later.
Sigma Photo Pro and Adobe Camera Raw are full RAW developers — they demosaic, apply tone curves, and let you edit exposure / white balance / sharpening before export. This tool is for the "I already like the image as-shot, just give me a web-ready file" case. For creative edits, develop in Sigma Photo Pro to 16-bit TIFF first, then drop that into a JPG to AVIF or PNG to AVIF conversion. If you only need the AVIF to be smaller, Compress AVIF trims further.