Image format
Sigma raw capture for compatible Foveon-camera workflows, developed with sensor-aware software.
Explore the format
Choose a target format for your Sigma X3F images.
Marked paths may need steps such as flattening, rasterization, tone mapping or animation loss.
Choose a source format to convert to Sigma X3F.
Sigma X3F Raw
X3F is Sigma’s raw image representation used by compatible Foveon cameras. It stores capture data for later development rather than only a finished JPEG. Sensor-aware processing is important: different sensor designs and camera generations should not be treated as if they all used the same Bayer-mosaic interpretation.
Sigma documents X3F development through Photo Pro and in-camera JPEG processing on supported models. The related X3I format is a different multi-capture representation in the sd Quattro workflow. Neither the layered sensor concept nor several captures imply a Photoshop layer stack in every X3F.
Use the raw original for repeated photographic development when exposure interpretation and colour decisions need to remain flexible. Export JPEG for an opaque delivery image or a suitable high-precision raster for further editing. Those exports bake in processing choices and cannot recreate the original sensor data, calibration or all vendor metadata.
Raw development interprets capture values using colour calibration, white balance and a tone curve; mosaiced data also needs demosaicing. A built-in preview is already rendered and can look different from a fresh raw development. More bit depth does not recover clipped exposure or establish a ready-to-display HDR image.
Sigma documents X3F development through Photo Pro and in-camera JPEG processing on supported models. The related X3I format is a different multi-capture representation in the sd Quattro workflow. Neither the layered sensor concept nor several captures imply a Photoshop layer stack in every X3F.
Raw formats evolve alongside camera sensors, recording modes and development software. These milestones connect this format family to the camera and processing workflows that use it.
Different formats, different trade-offs. Choose for the image and the workflow.
DNG provides a published container for camera raw data and calibration information. It can simplify supported raw interchange, but conversion does not guarantee that every proprietary maker note or processing feature will remain usable.
JPEG makes a compact photographic delivery file, but ordinary JPEG discards detail and has no alpha. Keep the richer source for editing and use JPEG when the receiving workflow expects an opaque photo.
TIFF provides tagged raster storage with multiple images and several sample types and compression schemes. It is a useful interchange choice for scanning and high-precision editing, but the receiving tool must support the particular TIFF variant.
PNG preserves decoded pixels losslessly and can carry alpha. It is useful for transparent graphics and screenshots; it does not preserve editable document layers or camera sensor data, and photographic files can be large.
X3F is Sigma’s raw image representation used by compatible Foveon cameras. It stores capture data for later development rather than only a finished JPEG. Sensor-aware processing is important: different sensor designs and camera generations should not be treated as if they all used the same Bayer-mosaic interpretation.
Sigma documents X3F development through Photo Pro and in-camera JPEG processing on supported models. The related X3I format is a different multi-capture representation in the sd Quattro workflow. Neither the layered sensor concept nor several captures imply a Photoshop layer stack in every X3F.
No. Sigma describes individual X3F raw images and X3I multi-capture files in the sd Quattro workflow. Support for one should not be assumed to include the other.
Check the exact camera model and recording mode in the processor’s support list. Raw support is model-specific, even when the extension is recognised. Viewing an embedded JPEG preview does not prove the sensor data has been decoded.
Raw-to-image export develops the data: white balance, colour mapping and tone become part of the pixels. Grayscale, palette and SDR targets can discard additional information. Keep the original; converting a rendered image back into a raw container cannot reconstruct the capture.
Use the raw original for repeated photographic development when exposure interpretation and colour decisions need to remain flexible. Export JPEG for an opaque delivery image or a suitable high-precision raster for further editing. Those exports bake in processing choices and cannot recreate the original sensor data, calibration or all vendor metadata.