X3F
X3F camera raw imageUsed for carrying minimally processed sensor output for a raw workflow.
- Family
- Images
- MIME
- image/x-sigma-x3f
Convert X3F to BMP online and see exactly what camera-raw development and image encoding changes, what BMP still can't promise, and how to verify the result.
The sensor-oriented X3F data is developed into display pixels using demosaicing, white balance, tone, orientation, and color interpretation before BMP encoding. That makes the result a rendered photograph, not another untouched camera negative. The Sigma X3F path develops layered Foveon sensor information rather than applying a conventional color-filter-array demosaic used by most camera raws. BMP output writes a single flat pixel surface with an explicit row order and color depth, built for simple bitmap interchange rather than layers or multiple resolutions.
Decoded canvas - Sigma camera raw data built around Foveon layered-sensor samples and Sigma metadata. Written image - A plainly structured bitmap with minimal compression that most software can read.
Used for carrying minimally processed sensor output for a raw workflow.
Designed for pixel-based artwork, scans, and photographs.
BMP wins this route whenever its specific mix of compatibility, alpha, animation, and file size fits the destination better than X3F does.
Conventional Bayer-oriented development does not reproduce every Foveon color and detail decision.
A BMP derivative is typically far larger than a web-oriented image, and row order or alpha handling can differ between the apps that read it.
a plainly structured bitmap with minimal compression that most software can read is what gets written, labeled as image/bmp. Whether that actually opens depends on the receiving application, not on the file extension.
Compare with Sigma Photo Pro and inspect color, fine detail, highlights, crop, noise, and metadata.
Check the dimensions, color depth, and orientation, and confirm whether the app you're using actually reads BMP transparency.