Convert X3F to JXL

Why Convert X3F to JXL?

Converting X3F RAW files to JXL transforms Sigma's proprietary Foveon sensor data into a universally accessible, efficiently compressed format. X3F files are locked into Sigma's ecosystem — only Sigma Photo Pro provides complete X3F processing, and software support from third-party tools is limited. By developing your X3F files and storing the results as JXL, you preserve the exceptional color fidelity and sharpness of Foveon captures in a format that any modern application can read.

X3F files from Sigma cameras are typically 40–80 MB each, making large collections expensive to store and slow to transfer. JXL's lossless compression can reduce developed X3F output by 50–70% compared to TIFF, while its lossy mode achieves 90%+ reduction at visually transparent quality levels. For Sigma photographers with thousands of images, the storage savings and faster access justify the conversion effort.

The Foveon X3 sensor's unique three-layer architecture captures true RGB values at every pixel without Bayer interpolation, producing images with remarkable spatial resolution and color accuracy. JXL's high bit-depth support (up to 32-bit float) preserves this quality advantage completely, unlike 8-bit formats like JPEG or WebP that would flatten the tonal range. Converting to 16-bit JXL maintains the full dynamic range captured by the Foveon sensor.

Note that converting X3F to JXL is a one-way process in terms of RAW editing — the resulting JXL contains developed pixel data, not raw sensor values. Always keep original X3F files if you may need to re-process with different settings. JXL serves as the ideal format for your finalized, developed images: smaller than TIFF, higher quality than JPEG, and backed by an ISO international standard for long-term reliability.

Key Benefits of Converting X3F to JXL:

• Universal Accessibility: Open X3F-developed images in any JXL-capable application
• Efficient Compression: 50–70% smaller than TIFF for lossless developed output
• Foveon Quality Preserved: 16-bit JXL maintains Foveon's exceptional color and sharpness
• HDR Capability: Exploit Foveon's wide dynamic range in HDR JXL output
• Metadata Preservation: Camera settings and Exif data carried into JXL
• Progressive Decoding: Quick previews for browsing large photo collections
• ISO Standard: Long-term format viability backed by international standardization

Practical Examples

Example 1: Sigma DP2 Merrill Street Photography Archive

Scenario: A street photographer has 8,000 X3F files from their Sigma DP2 Merrill spanning five years. The files consume 450 GB and need to be developed and archived in an efficient, accessible format.

Source: street_tokyo_0247.x3f (52 MB, Foveon 14.8 MP, 14-bit RAW)
Conversion: X3F → develop → JXL (lossless, 16-bit)
Result: street_tokyo_0247.jxl (14 MB, 4704x3136, 16-bit lossless)

Archive results:
✓ 8,000 developed images: ~112 GB vs ~640 GB as TIFF
✓ Foveon's per-pixel sharpness fully preserved in 16-bit
✓ Exif data (camera, lens, ISO, date) embedded in JXL
✓ Progressive decoding enables fast gallery browsing
✓ No dependency on Sigma Photo Pro for viewing

Example 2: Landscape Photography Portfolio

Scenario: A landscape photographer uses a Sigma SD1 Merrill and wants to share developed Foveon images online with maximum quality while keeping file sizes manageable for web delivery.

Source: mountain_sunrise.x3f (68 MB, Foveon 46 MP, 14-bit RAW)
Conversion: X3F → develop → JXL (lossy, quality 95)
Result: mountain_sunrise.jxl (380 KB, 4800x3200, lossy q95)

Portfolio benefits:
✓ Web-ready file size with near-lossless visual quality
✓ Foveon color science preserved in the developed output
✓ Progressive loading shows preview within milliseconds
✓ HDR metadata for enhanced display on compatible screens
✓ Single file works for portfolio, prints, and social media

Example 3: Studio Product Photography Migration

Scenario: A product photography studio has been shooting with Sigma cameras for catalog work. They need to migrate X3F archives to a modern format that their design team can use directly in workflows.

Source: watch_macro_detail.x3f (45 MB, Foveon, 14-bit)
Conversion: X3F → develop (color-managed) → JXL (lossless)
Result: watch_macro_detail.jxl (8.6 MB, 4704x3136, lossless)

Studio workflow:
✓ Design team opens JXL directly — no Sigma software needed
✓ ICC profile embedded ensures accurate color on all monitors
✓ 81% smaller than equivalent TIFF for NAS storage
✓ Lossless quality for cropping, retouching, and compositing
✓ Batch conversion of entire X3F catalog to JXL archive

Frequently Asked Questions (FAQ)

Q: Does converting X3F to JXL preserve the Foveon color quality?

A: The conversion develops the X3F RAW data into a standard RGB image, then compresses it as JXL. In lossless mode, every pixel value from the developed output is preserved exactly. The unique color fidelity and sharpness of Foveon captures is maintained in the developed result. However, the raw sensor data itself is not stored — further RAW adjustments require the original X3F file.

Q: Can I still edit the JXL file after converting from X3F?

A: Yes — you can edit the JXL file in any supporting image editor (GIMP 2.99+, Krita, darktable). However, you lose the RAW editing flexibility that X3F provides (changing white balance, exposure recovery, noise reduction at the RAW level). The JXL contains a developed, "baked" image. For critical work, keep original X3F files and use JXL for distribution and archival of finalized images.

Q: How does the Foveon sensor differ from standard Bayer sensors?

A: Conventional Bayer sensors capture one color (R, G, or B) per pixel and interpolate the other two through demosaicing, which can introduce artifacts. The Foveon X3 sensor stacks three layers that each capture all of R, G, and B at every pixel position, producing true full-color data without interpolation. This results in superior per-pixel sharpness and color accuracy, which JXL preserves faithfully.

Q: What bit depth should I use for the JXL output?

A: For maximum quality preservation, develop your X3F at 16-bit and encode JXL in lossless mode. This captures the full tonal range from the 14-bit Foveon sensor data. For web delivery, 8-bit lossy JXL at quality 90–95 provides excellent visual results at dramatically smaller file sizes. The choice depends on whether the output is for archival (16-bit lossless) or distribution (8-bit lossy).

Q: Which Sigma cameras produce X3F files?

A: X3F is used by Sigma cameras with Foveon sensors, including the SD9, SD10, SD14, SD15, SD1/SD1 Merrill, DP1/DP1s/DP1x/DP1 Merrill, DP2/DP2s/DP2x/DP2 Merrill, DP3 Merrill, and dp Quattro series (dp0q, dp1q, dp2q, dp3q). Newer Sigma cameras (fp, fp L) use DNG instead of X3F with conventional Bayer sensors.

Q: Is the conversion process slow for X3F files?

A: X3F to JXL conversion involves two steps: RAW development (demosaicing the Foveon data) and JXL encoding. The RAW development step is the slower part, typically taking 5–15 seconds per image depending on resolution and processing settings. JXL encoding adds a few seconds more. Overall, expect 10–20 seconds per X3F file. Batch processing is recommended for large collections.

Q: Should I keep the original X3F files after conversion?

A: Yes — always keep original X3F files if possible. The RAW data provides flexibility to re-process with different white balance, exposure, and noise reduction settings that cannot be changed after conversion to JXL. Store X3F files on cold/archive storage and use JXL for active access, sharing, and display. Think of JXL as your developed prints and X3F as your negatives.

Q: Can JXL handle the high resolution of Foveon Quattro sensors?

A: Absolutely. JXL supports images up to billions of pixels, far exceeding any camera sensor. The Foveon Quattro's effective resolution (approximately 29 MP in the dp Quattro series) is easily handled by JXL. The format's progressive decoding is actually beneficial for these large files, allowing quick previews before the full resolution data loads.