Initializing... drag & drop files here
Supports: X3F
.x3f) into the upload zone. Batch conversion is supported, so you can drop an entire shoot at once..jpeg or .jpg as the File extension — they are byte-identical.X3F is the RAW container Sigma cameras write when they use the Foveon X3 sensor — a three-layer stack that records red, green, and blue at every pixel position instead of interpolating colors from a Bayer mosaic. The file holds linear sensor data plus an embedded JPEG preview, and it can only be developed by Sigma Photo Pro (SPP) or a handful of third-party tools. Most websites, photo libraries, and editors cannot open it at all, which is why converting to JPEG (ISO/IEC 10918-1, standardized in 1992) is the fastest way to make the shot usable everywhere.
.x3f uploads. JPEG is the universal exchange format that browsers and apps have rendered since the mid-1990s.| Property | X3F (Sigma RAW) | JPEG |
|---|---|---|
| Type | Proprietary RAW container | Lossy compressed image |
| Origin | Sigma / Foveon (2002, with SD9) | ITU-T T.81 / ISO/IEC 10918-1 (1992) |
| Sensor data | Full linear, three-layer Foveon stack | Demosaiced, gamma-corrected 8-bit RGB |
| Color depth | 12-14 bit per layer (camera dependent) | 8 bit per channel (24-bit color) |
| Typical file size | 30-55 MB (15 MP SD1/Merrill) | 1-8 MB depending on quality |
| Editor support | SPP, dcraw, Iridient, X3Fuse, RawTherapee | Universal — every browser, OS, editor |
| Browser preview | Embedded JPEG thumbnail only | Native in Chrome, Safari, Firefox, Edge |
| Best for | Maximum-latitude editing in SPP | Sharing, web, email, print, archival |
| Preset | Approx. JPEG quality | Use case | Rough size for 15 MP source |
|---|---|---|---|
| Very High (default) | ~95 | Final delivery, prints, portfolio | 4-8 MB |
| High | ~85 | Client proofs, blog posts, full-res web | 1.5-3 MB |
| Medium | ~75 | Email, messaging, social uploads | 700 KB - 1.5 MB |
| Low | ~60 | Thumbnails, contact sheets, fast previews | 200-500 KB |
| Specific file size | Auto-calculated | When you need an exact KB/MB target | You set the cap |
None. Both extensions point to the same ISO/IEC 10918-1 / ITU-T T.81 bitstream. The three-letter .jpg form dates from MS-DOS / Windows 3.x, which limited extensions to three characters; modern systems accept the original four-letter .jpeg equally. Pick whichever your downstream workflow expects — the converter writes identical bytes either way. If you specifically need .jpg, our X3F to JPG converter produces the same output with that extension.
Some, yes. X3F stores 12-14 bit linear Foveon data; JPEG re-encodes to 8-bit gamma-corrected RGB with lossy DCT compression. At the Very High preset (around quality 95) the visual loss is usually invisible at print sizes. For maximum fidelity, develop the X3F in Sigma Photo Pro first, then export to TIFF — our X3F to TIFF converter keeps 16-bit data and lossless compression.
The Foveon X3 sensor shipped in the SD9 (2002), SD10, SD14, SD15, and SD1 / SD1 Merrill DSLRs, the DP1, DP2, DP3 and dp Merrill compacts, and the dp Quattro and sd Quattro lines. All write .x3f as their RAW container. Newer Sigma fp / fp L cameras use a Bayer sensor and write .dng instead, so they do not produce X3F.
X3F stores raw sensor readings from three stacked photodiodes per pixel site plus metadata and an embedded preview, often 30-55 MB on the 15 MP SD1 Merrill. JPEG throws away high-frequency information the human eye barely sees and packs the rest with DCT compression, typically achieving 10-20x size reduction at high quality. That is the design tradeoff: X3F preserves editing latitude, JPEG preserves bandwidth.
No. The converter reads X3F directly on our servers — no SPP, no plug-in, no Adobe Camera Raw, no command-line dcraw. This is useful on machines where SPP is not installed (Linux, Chromebooks, locked-down work laptops, mobile devices) or when SPP cannot open files from a newer Sigma body that your installed version predates.
The converter develops the actual raw Foveon data and re-renders a fresh JPEG, rather than extracting the small embedded preview (which is typically only a few hundred kilobytes and not full resolution). You get the full sensor resolution of your camera — 4800 x 3200 on the SD1 Merrill, for example — at the quality preset you chose.
Yes. Drag the entire folder of .x3f files into the upload zone. Each file processes with the same quality, resolution, and extension settings, then downloads as a ZIP when done. This is the fastest way to escape SPP's slow per-file workflow when you only need JPEGs for delivery.
If you only need viewable images, JPEG is fine and is the most universal format. For archival that preserves editing latitude, DNG (Adobe's open Digital Negative) is the photography-community standard because more editors can read DNG than X3F. Many photographers do both — JPEG for delivery and DNG for the master archive. Sigma's own X3F is the only format with full Foveon-aware development, so keep the originals if disk space allows.
Yes. Camera model, lens, shutter speed, aperture, ISO, capture date, and GPS (if recorded) are copied from the X3F's metadata block into the JPEG's EXIF segment. Lightroom, Photos, Bridge, and the operating-system file inspectors will show the same shooting data on the converted JPEG.