X3F to PPM Converter

How to Convert X3F to PPM Online

1. Upload Your X3F File: Drag and drop or click "+ Add Files" to select X3F RAW files from a Sigma SD or DP camera. Batch upload is supported — drop a folder export from SIGMA Photo Pro and convert them all in one pass.
2. Pick Bit Depth: Default is 8-bit (Recommended), which produces a standard P6 binary PPM with one byte per channel (0–255). Choose 16-bit (High Precision) when you need the full Foveon tonal range for scientific or post-processing pipelines, or 1-bit (Black & White) for thresholded mask output.
3. Set Image Resolution (Optional): Keep the source dimensions, pick a Preset Resolution, scale by Resolution Percentage, or enter a custom Width × Height. Aspect ratio is preserved when you only set one dimension.
4. Convert and Download: Click "Convert" and download the PPM file. processing happens on our servers — no sign-up, no watermark, no daily file limit.

Why Convert X3F to PPM?

X3F is Sigma's proprietary RAW container for cameras using Foveon X3 sensors — first shipped in the Sigma SD9 in 2002, and used through the SD10, SD14, SD15, SD1/SD1 Merrill DSLRs, the DP1/DP2/DP3 Merrill compacts, and the Quattro line (dp Quattro from 2014, SD Quattro from 2016). The Foveon design stacks three photodiode layers and captures red, green, and blue at every pixel location instead of interpolating from a Bayer filter, so there is no demosaicing step in the rendering pipeline. PPM (Portable Pixmap, part of the Netpbm family since 1988) is the natural target when you want that raw RGB intact and trivially parseable — a short ASCII header followed by R/G/B samples, nothing else to decode.

• Feed image-processing pipelines — OpenCV, ImageMagick, GraphicsMagick, scikit-image, MATLAB, and most Unix CLI tools read PPM with zero codec dependencies. Drop the file into a pipe(1) chain (pnmscale, pnmtopng, pamcut) without touching libraw.
• Computer-vision and ML preprocessing — PPM has no compression artifacts and no metadata parsing tax, which keeps training-pipeline I/O deterministic. Many academic vision datasets ship in PPM/PGM for exactly that reason.
• Long-term scientific archives — the format is fully specified in a single page on netpbm.sourceforge.net, byte-order is fixed (big-endian for 16-bit), and there is no patent encumbrance. A PPM written today will still be parseable in 30 years by a 50-line Python script.
• Print and color-science workflows — 16-bit PPM (P6 with maxval 65535) preserves the Foveon's full tonal range when you intend to apply ICC profiling or precision tone curves downstream in tools like darktable or RawTherapee that accept Netpbm input.
• Teaching and reproducible research — undergraduate graphics courses (Clemson, Wooster, Utah, UW CSE 576) use PPM because the entire format fits on a single slide and students can write a parser in an afternoon. Foveon source data plus PPM output is a common assignment baseline.
• Universal interop — when Adobe Camera Raw or Lightroom won't open older X3F files (Foveon support is incomplete in many editors), a PPM export through xconvert sidesteps the problem entirely. Open the PPM in Photoshop, GIMP, IrfanView, or any image viewer.

X3F vs PPM — Format Comparison

PPM Bit-Depth Quick Guide

Frequently Asked Questions

Why convert X3F to PPM instead of TIFF or DNG?

PPM is the lightest possible target when a downstream tool needs raw RGB samples and nothing else. TIFF carries tags, ICC profiles, compression options, and tiling — useful, but extra parsing surface. DNG is still a RAW container and requires a Foveon-aware decoder. PPM is a 4-line ASCII header followed by sample bytes, so a scikit-image or OpenCV reader handles it with zero configuration. If you need EXIF preserved or LZW compression, use X3F to TIFF instead.

Will the PPM preserve Foveon's full color depth?

At 16-bit (High Precision) you get a P6 PPM with maxval 65535, which carries 16 bits per channel — enough headroom for the Foveon's three stacked photodiode layers without quantization loss on a normal exposure. At 8-bit (Recommended) the sensor data is rounded to 0–255 per channel, which is fine for display but discards precision you may want for grading. Use 16-bit when the PPM is an intermediate and the final output will go through tone curves.

Why is my PPM so much larger than the X3F?

PPM is fully uncompressed. A 24 MP Foveon image at 8-bit/channel works out to 24,000,000 × 3 = ~72 MB of pixel data, plus a tiny ASCII header — typically ~145 MB once you include row padding and the realistic 4936 × 3296 × 3 sensor resolution of an SD Quattro. At 16-bit that doubles to ~290 MB. The source X3F is ~50–60 MB because it stores the packed sensor signal, not interpolated RGB.

Which Sigma cameras produce X3F files?

The Foveon X3 sensor shipped first in the SD9 (2002), then the SD10 (2003), SD14 (2006), SD15 (June 2010), SD1 and SD1 Merrill (2011/2012), the DP1/DP2/DP3 Merrill compacts (2008–2013), and the Quattro line — dp Quattro from 2014 and SD Quattro from 2016. As of 2025 Sigma has not shipped a new Foveon-sensor camera since the Quattro generation, so X3F files in circulation come from those bodies.

Can I open the resulting PPM in Photoshop or GIMP?

Yes — GIMP reads and writes PPM natively (File → Open works on .ppm, .pgm, .pbm). Photoshop supports PPM through the built-in "Portable Bit Map" plug-in; if you do not see it, install the optional file format plug-ins from Adobe's "Optional plug-ins" download. IrfanView, XnView, ImageMagick's display, macOS Preview (limited), and any Netpbm-aware viewer also open PPM directly.

What is the difference between P3 and P6 PPM?

P3 is the "plain" ASCII variant — each sample is a decimal number separated by whitespace, which is human-readable but roughly 3× larger and slow to parse. P6 is the "raw" binary variant — each sample is one byte (maxval ≤ 255) or two bytes (maxval > 255, big-endian) of pure binary data after the ASCII header. xconvert writes P6 for both 8-bit and 16-bit output because every Netpbm-compatible reader handles P6 and the file size is far smaller.

Does PPM support transparency?

No. The PPM specification has no alpha channel; the format only stores RGB triplets. If you need transparency you want PNG, TIFF (with alpha), or PAM (a Netpbm extension that supports arbitrary channels including alpha). Convert via X3F to PNG when you need an alpha mask or a smaller compressed output.

Will the EXIF and white-balance metadata survive the conversion?

No — PPM has no metadata section at all. Camera model, lens, exposure, shutter speed, white-balance tag, and capture timestamp from the X3F are dropped. If you need that metadata downstream, export an EXIF sidecar from SIGMA Photo Pro first, or use X3F to JPG (preserves EXIF) for an inspection copy alongside the PPM for processing.

Is X3F to PPM a good fit for batch scientific workflows?

Yes — that is the classic Netpbm use case. Drop a folder of X3F captures, set 16-bit High Precision, and pipe the resulting PPMs straight into pnm* tools, OpenCV imread, MATLAB imread, or a NumPy memmap reader. No codec licensing, no EXIF parsing, no Foveon decoder dependency on the consuming machine. Pair with DNG to PPM or CR2 to PPM when your dataset mixes Sigma with Adobe DNG or Canon RAW captures.