Drag files or click to select
Convert files online
Drag files or click to select
Convert files online
What is X3F to BMP conversion?
X3F to BMP conversion transforms Sigma's proprietary RAW format into the classic Windows Bitmap format. X3F is the container used by Sigma digital cameras, identified by the FOVb magic signature. It stores unprocessed Foveon X3 sensor data on most Sigma bodies (sd Quattro, sd Quattro H, dp Quattro series, dp Merrill series, earlier sd-series) or Bayer sensor data on the full-frame Sigma fp and fp L. X3F is a format for professional photo processing in specialized software, primarily Sigma's own Sigma Photo Pro. Most third-party applications either do not open X3F or process it in a simplified way.
BMP (Bitmap Image File) is one of the oldest raster image formats, introduced by Microsoft for Windows in 1990. Its defining feature is uncompressed pixel storage. Each pixel is recorded directly with its exact RGB values at 8 bits per channel, making BMP a completely lossless format that preserves every color value with absolute fidelity. The file structure is exceptionally simple: a fixed header followed by a pixel array stored row by row.
X3F to BMP conversion is useful in specific areas: scientific image processing, image processing software development, machine vision, medical visualization, industrial quality control. Anywhere algorithms analyze images pixel by pixel, uncompressed BMP provides predictable, deterministic behavior without compression artifacts.
During X3F to BMP conversion several operations happen in sequence. For Foveon-based cameras the decoder separates the three-layer sensor signal into RGB channels using the Foveon color matrix. For Sigma fp with a Bayer sensor, standard demosaicing is applied. After that, white balance, sRGB gamma correction, and the result is written into the BMP container without any compression. The absence of an encoding stage guarantees the resulting image contains no compression-related distortion.
Technical comparison: X3F vs BMP
X3F and BMP serve fundamentally different purposes. X3F preserves maximum sensor information from Sigma cameras, while BMP stores rendered raster images in the simplest accessible form.
| Characteristic | X3F | BMP |
|---|---|---|
| Developer | Sigma Corporation | Microsoft |
| Data type | Unprocessed sensor data | Rendered raster image |
| Color depth | 12-14 bits per channel | 1, 4, 8, 16, 24, 32 bits per pixel |
| Compression | Lossless (HUFF/TRUE) | Usually none |
| File signature | FOVb | BM (0x42 0x4D) |
| Source sensor | Foveon X3 (3 layers) or Bayer (Sigma fp) | Not applicable |
| Dynamic range | 10-13 EV | ~8 EV (at 24 bits per pixel) |
| Transparency | Not supported | Supported (32-bit BGRA, rarely used) |
| EXIF metadata | Full plus Sigma Maker Notes | Not supported |
| Universal viewing | Narrow (Sigma ecosystem) | Opens on any Windows system |
| File size (24 MP) | 30-50 MB | 70-150 MB |
| Color space | Linear RGB (no gamma correction) | sRGB with gamma correction |
| Primary use | Professional Sigma photography | System programming, image analysis |
| Reference decoder | Sigma Photo Pro | Not applicable (open specification) |
BMP supports various color depths: from monochrome (1 bit per pixel) to full-color with alpha channel (32 bits per pixel). For X3F conversion, 24-bit per pixel (True Color) is the most common mode, where each pixel uses three bytes - one each for red, green, and blue channels.
The BMP file structure is straightforward: a fixed-size header (54 bytes for standard BITMAPINFOHEADER), followed by a pixel array stored row by row from bottom to top. Each row is padded to a multiple of 4 bytes. This transparent organization makes BMP convenient for software processing.
X3F is much more complex - a multi-section container. Reading X3F correctly requires understanding Sigma's proprietary specification and the Foveon layer decoding algorithms. Reference-quality decoding is provided only by Sigma's own Sigma Photo Pro.
BMP file size significantly exceeds X3F: an uncompressed 24-megapixel image at 24-bit depth occupies about 72 MB of pixel data plus headers. For Foveon sensors with declared resolution up to 49 MP effective on sd Quattro, BMP can reach 140-150 MB. By comparison, the same image in X3F takes 30-50 MB.
File size by image content
| Scene type | X3F (Sigma sd Quattro) | BMP (24 MP, converted) |
|---|---|---|
| Detailed landscape | 40-50 MB | 75-150 MB |
| Portrait with soft background | 35-45 MB | 75-150 MB |
| Studio shot on white background | 30-40 MB | 75-150 MB |
| Night scene with high ISO | 45-55 MB | 75-150 MB |
Unlike compressed formats where file size varies with image complexity, BMP file size is determined almost entirely by resolution alone. The same Sigma sd Quattro frame produces a similar-sized BMP regardless of whether it depicts a uniform white wall or an intricate forest scene.
X3F file sizes vary because their lossless compression is more effective on smooth, low-noise images and less effective on noisy, detailed content. BMP eliminates this variability entirely.
When to choose BMP over other formats
BMP is not the most popular format for everyday photo sharing. However, several professional and technical scenarios make uncompressed BMP the optimal choice.
Scientific and engineering work
In scientific environments BMP is valued for absolute predictability. When a researcher processes microscope shots, satellite images, or medical scanner data, it is critical that pixel values are not distorted by compression algorithms. BMP guarantees that a value of (128, 64, 200) stays exactly that - no interpolation, rounding, or redistribution.
This matters in spectral analysis where pixel color carries quantitative information. In astrophotography, defectoscopy, metallography, and biological microscopy, researchers sometimes photograph specimens on Sigma cameras and convert X3F to BMP for automated analysis. The Foveon sensor is especially interesting for scientific tasks requiring accurate color rendering without Bayer demosaicing artifacts.
Software development
Programmers building image processing tools often work with BMP as a debugging and intermediate format. The simple structure means writing a BMP parser takes about an hour, while properly reading PNG or JPEG requires third-party libraries. When developing filters, detectors, classifiers, and neural networks it is convenient to work with data in the most transparent form possible.
Foveon photographs in BMP make useful test material: the specific properties of the three-layer sensor (no demosaicing artifacts, accurate color at every point) make them interesting for testing color processing algorithms.
Industrial automation and machine vision
Quality control systems on production lines analyze part images looking for defects: cracks, chips, deformations. Many embedded machine vision systems treat BMP as their native format because reading uncompressed pixel arrays requires minimal compute and runs in predictable time.
Sigma cameras with Foveon sensors are used in specialized industrial control tasks thanks to accurate color rendering without Bayer mosaic effects. Converting calibration reference shots and specimens from X3F to BMP integrates high-quality photographs into the industrial control pipeline.
Legacy software compatibility
Some enterprise and government systems built in the 1990s and 2000s support only a limited set of formats: BMP and sometimes TIFF. This shows up in medical information systems, geographic information systems, archival storage, and specialized vertical software.
If a procedure or specification requires submitting images in BMP, X3F conversion lets you use professional Sigma photographs while maintaining system compatibility.
Texture creation for older game engines
Some game engines and modding tools accept textures only in BMP. Designers shooting real surface textures (brick, wood, metal, fabric) on Sigma cameras convert X3F to BMP for import into level editors. The accurate color rendering of the Foveon sensor is especially valuable for creating realistic textures.
Technical aspects of X3F to BMP conversion
Foveon decoding
Each point on the Foveon X3 sensor records three color channels at once thanks to three vertically stacked photodiode layers. The top layer responds mostly to blue, the middle layer to green, and the bottom layer to red, based on wavelength penetration depth. The decoder applies the Foveon color matrix to separate the layered signal into RGB channels. On Quattro sensors the top layer has higher resolution than the lower ones, so the decoder performs hierarchical scaling.
Unlike Bayer sensors, Foveon does not require traditional demosaicing - each spatial position already contains all three color channels. This eliminates moire and false color artifacts. In BMP the result is saved as a standard 24-bit RGB image.
Sigma fp X3F decoding
X3F files from Sigma fp and fp L contain Bayer sensor data. The decoder runs standard demosaicing: each pixel records one color channel through the color filter, and the other two are interpolated from neighbors. The result is saved to BMP in standard RGB format.
Bit depth reduction
X3F stores data at 12-14 bits per channel - that is 4,096-16,384 discrete brightness levels. Standard BMP works with 8 bits per channel (256 levels). During conversion tone mapping translates the wider dynamic range to 8-bit using a gamma curve and tonal compression.
This operation is irreversible. Subtle gradients in shadows and highlights, distinguishable in 12-14 bit X3F, are quantized to fewer discrete levels in BMP. For most practical tasks 8-bit is sufficient, but for scientific measurements the precision loss can be material.
Lack of EXIF metadata in BMP
A key difference between BMP and formats like JPEG, PNG, and TIFF is complete absence of EXIF metadata support. During X3F to BMP conversion all shooting parameters (shutter speed, aperture, ISO, Sigma camera model, date, GPS coordinates) are permanently lost. Sigma-specific Maker Notes data (X3 Fill Light, Sigma color modes, Foveon processing parameters) is also lost.
If metadata is important - for cataloging, copyright proof, or legal purposes - keep the original X3F files in parallel or export metadata to a separate sidecar file before conversion.
Pixel storage details in BMP
BMP stores pixel rows bottom-up - the first data row corresponds to the bottom row of the image. Each row is padded with zero bytes to a length divisible by 4. The color component order is BGR (blue, green, red) rather than the conventional RGB.
These details are transparent to users: any viewer displays BMP correctly. However when processing converted files programmatically, it is important to account for the inverted row order and BGR format to avoid bugs in analysis algorithms.
What works well in BMP
Not every photograph makes sense in BMP. Without compression file sizes are much larger than JPEG or PNG. Conversion to BMP is justified in these cases:
- Reference Foveon shots for calibration - color target photos (ColorChecker), rulers, scales used to calibrate equipment. Foveon's color accuracy makes them especially valuable.
- Test images for development - Foveon photographs with varied content serving as input for color processing algorithms.
- Cropped regions for analysis - cut-out portions where a specific area is analyzed: material texture, surface defect, biological subject.
- Intermediate processing results - if the pipeline has multiple stages, BMP between stages guarantees no accumulating compression artifacts.
- Images for embedded systems - if the target device lacks PNG/JPEG decompression libraries, BMP is the only option.
For everyday photo sharing, web publication, and social media, BMP is not recommended: files are too large, and most platforms do not accept BMP. JPEG, WebP, or AVIF are more appropriate.
Advantages of the BMP format
Absolute pixel-level accuracy
BMP does not modify image data during read or write. Every pixel is stored and retrieved with bit-exact precision. This guarantees reproducibility: if two different applications read the same BMP file, they get identical pixel arrays.
For scientific measurements and automated quality control this property is irreplaceable. Analysis results do not depend on decoder implementation, library version, or platform.
Minimal compute requirements
Reading BMP requires no decompression: the CPU does not spend time unpacking data. This matters for embedded systems with limited compute and for real-time tasks where predictable pixel access time is critical.
Loading a BMP file into memory is essentially a simple block copy from disk to RAM with row alignment. No intermediate buffers, compression dictionaries, or inverse transforms.
Maximum Windows compatibility
BMP is the native Windows format, supported at the OS level since Windows 3.0 (1990). Any Windows application that works with graphics can open BMP without installing additional codecs or libraries. This includes built-in tools: Paint, Photos, image viewers, and all versions of Microsoft Office.
In enterprise environments where third-party software installation is restricted by security policy, BMP guarantees image accessibility from any workstation.
Simple software processing
The BMP format is documented by Microsoft and has an open specification. Header structure and data layout are unambiguously described and have not changed in decades. A read/write BMP program can be written in any language with minimal effort - no external library dependencies.
For educational projects, prototypes, and demo applications BMP remains popular thanks to its transparency.
Limitations and recommendations
Large file sizes
The main BMP limitation is the lack of compression. A 6192x4128 pixel image at 24-bit takes about 73 MB. For the Foveon sensor on Sigma sd Quattro with 49 MP effective resolution it can reach 150 MB. By comparison the same photo in JPEG at visually identical quality is about 5-10 MB, in PNG about 80-110 MB.
For storing many files this becomes critical. A thousand Foveon photographs in BMP would occupy about 100 GB versus 8-12 GB in JPEG. Convert to BMP only the shots that really need the uncompressed format.
Not suitable for web or social media
Web browsers can technically display BMP, but the huge file size makes it impractical. No social media platform or image-sharing service accepts BMP: Instagram, Facebook, VKontakte, Twitter, Pinterest require JPEG, PNG, or WebP.
For publishing Foveon photos online convert X3F to JPEG, WebP, or AVIF.
No metadata
BMP does not store shooting parameters, copyright, color profiles, or geolocation. Converting from X3F loses all of this. If you need to preserve EXIF, choose JPEG, PNG, or TIFF.
No return to RAW
X3F to BMP conversion is irreversible. While BMP preserves pixels without distortion, the original Foveon layer data or Bayer mosaic is already decoded. Re-processing with different RAW parameters is impossible.
Always keep your X3F originals. Convert copies to BMP, leaving the RAW archive for potential re-processing.
Basic decoding only
This service performs basic X3F decoding with default processing parameters: white balance is taken from the camera metadata as recorded at capture time, standard sRGB gamma correction is applied, and Foveon layer combination or Bayer demosaicing runs automatically. White balance adjustment, exposure compensation, highlight and shadow recovery, tone curves and noise reduction are not available. For reference-quality Foveon rendering use Sigma Photo Pro before BMP conversion. Universal converters (Adobe Lightroom, Capture One, RawTherapee) open X3F but process Foveon data simplistically.
What is X3F to BMP conversion used for
Scientific processing and analysis of Foveon images
Researchers photograph subjects with Sigma cameras and Foveon sensor (microscope specimens, material samples, astronomical objects) and convert X3F to BMP for pixel-by-pixel analysis. The accurate Foveon color rendering without Bayer demosaicing artifacts makes these images especially valuable for scientific measurement.
Developing and testing graphics software
Programmers use Foveon photographs converted from X3F to BMP as test data for image processing algorithms: filters, object detectors, neural networks. The simple BMP structure allows reading files without third-party libraries, and the distinctive Foveon color provides interesting test cases for color algorithms.
Integration with legacy enterprise systems
Some specialized software complexes in medicine, government, and industry accept images only in BMP. Converting from X3F lets you load high-resolution professional Foveon photographs into such systems without compatibility loss.
Industrial quality control with Foveon
Machine vision systems on production lines use BMP as their native format for image analysis. Foveon reference and calibration target photos shot on Sigma in X3F are converted to BMP for integration into the inspection pipeline. The accurate Foveon color is valuable for tasks where color attributes matter.
Creating textures for game engines and 3D modeling
Artists and designers photograph real surfaces (stone, wood, metal) on Sigma cameras for texture creation. Some engines and modding tools require BMP input, so X3F conversion is needed. Foveon provides accurate color without demosaicing artifacts, important for realistic textures.
Tips for converting X3F to BMP
Preserve your X3F originals
BMP conversion is irreversible: the original Foveon sensor data is gone after decoding and bit depth reduction. Keep the X3F files for possible re-processing with different parameters. Foveon decoding algorithms continue to improve, and older shots can be processed better later.
Plan for storage space
BMP files from 24 MP Foveon photos weigh 70-150 MB each depending on the Sigma model. Batch-converting hundreds of shots takes tens of gigabytes. Make sure you have enough disk space, and convert only the files that actually need the uncompressed format.
Choose BMP only for specialized tasks
For web publication and photo sharing use JPEG, WebP, or AVIF - they are much smaller and universally supported. BMP is justified for scientific analysis, software processing, machine vision, and legacy software compatibility where bit-exact accuracy or the absence of decompression matters.
Export EXIF separately when needed
If shooting parameters and Sigma Maker Notes matter for your work, save the metadata from X3F to a separate file before BMP conversion. BMP does not support EXIF, so camera, shutter speed, aperture, ISO, and GPS information is lost during conversion.