CONVERSION GUIDE:
RAW to X3F Conversion Guide
This guide explains RAW to X3F. RAW to X3F is not available as a browser conversion yet. This guide explains the workflow, what changes in the file, and what must be preserved before upload is enabled.
Conversion guide. This RAW to X3F route is not available in the browser yet. This guide explains what must be preserved and links to safer alternatives that work now.
RAW to X3F is not available yet
No upload box is shown until the RAW reader and X3F export path can preserve the file safely.
- No upload prompt is shown until the conversion is actually supported.
- Downloads must match the real output format before this page becomes available.
- No hidden loss of layers, animation, image structure or color data.
What changes before converting RAW to X3F
Input format details: RAW is part of camera RAW workflows, so conversion normally needs decoding, color processing and tone mapping before export.
Output format details: X3F is part of camera RAW workflows, so conversion normally needs decoding, color processing and tone mapping before export.
Source input: RAW input: Develop supported camera RAW to 29 rendered outputs using temporary server processing. Genuine single-image camera RAW only, up to 64 MiB and 24 MP. Unsupported camera variants, renamed raster files and rendered Linear DNG are refused. Your original file is uploaded unchanged for isolated server processing and deleted after the request. No browser RAW decoding or embedded JPEG fallback. Output is rendered sRGB RGB8 with camera white balance; sensor data and source metadata are not retained. PNG and WEBP use lossless encoding; JPG/JPEG use fixed quality 90 with 4:4:4 sampling. No proprietary RAW output is created. Advanced rendered outputs are resized only when needed to at most 2,073,600 pixels (about 2 MP); ICO/CUR are bounded to a 256 px largest dimension. Fixed output profiles; no reconstructed layers, vectors, animation, HDR or sensor data.
Target output: X3F output: Sigma DP1 X3F TRUE input has four named server exports: JPG, JPEG, PNG and WEBP. Sigma DP1 only: FOVb 2.2, HI, TRUE type 3 format 30, three-plane 2688 × 1792 sensor; sRGB8 render 2651 × 1767. Complete Python prevalidation and isolated non-root LibRaw 0.21.4 DP1 fork; up to 64 MiB per file and 24 MP. Merrill, Quattro, other Sigma models/variants and proprietary RAW output are not supported. No embedded JPEG or CAMF decoding.
This page focuses on the exact RAW to X3F task: compatibility, compression, transparency, animation, metadata, color profile and output-quality trade-offs for this pair.
Transparency and layers
- RAW conversion should apply RAW decoding, white balance, demosaicing and color processing before writing X3F.
- Metadata, EXIF orientation and color profiles should be handled deliberately rather than silently copied or dropped.
Best use cases for RAW to X3F
- A certified RAW engine must support RAW before any X3F export or upload can be offered.
- Make RAW files easier to open in software that expects X3F.
- Prepare X3F output for upload forms, websites, archives or sharing.
- Create a predictable X3F copy while keeping the original RAW file untouched.
Quality, file size and compatibility
X3F output should be chosen for the actual destination: web pages need small files, archives need predictable compatibility, design handoff may need transparency, and camera workflows may need color accuracy. ImageConvert separates available routes from guide-only routes so visitors do not get mislabeled downloads or silent animation/layer loss.
For lossy outputs such as JPG, JPEG, JFIF and many WEBP settings, quality can reduce file size but permanently changes pixels. For lossless or alpha-friendly outputs such as PNG and some WEBP settings, transparency and sharp graphics can be preserved when the source data supports it. Professional formats require explicit color management and metadata handling.
What this conversion must preserve
A safe RAW to X3F workflow must decode the source format, preserve the parts users care about, and explain any unavoidable changes before download.
- File structure, layers, animation, pages or RAW sensor data should not be silently discarded.
- Transparency, metadata, EXIF orientation and color profiles need explicit handling.
- The page should offer upload only after downloaded X3F files are verified as real X3F output.
FAQ
Is RAW to X3F available now?
Not yet. ImageConvert explains the workflow and keeps upload disabled until this conversion is reliable.
What changes when I convert RAW to X3F?
RAW conversion should apply RAW decoding, white balance, demosaicing and color processing before writing X3F. Metadata, EXIF orientation and color profiles should be handled deliberately rather than silently copied or dropped.
Will RAW to X3F keep transparency, animation or layers?
It depends on the source and target. X3F output follows X3F format limits, so transparency, animation, editable layers, metadata and color profiles must be handled explicitly by the conversion engine.
Can I keep the original RAW file after converting to X3F?
Yes. ImageConvert is designed to create a new X3F output and leave the original RAW file unchanged.
When this page should become a live converter
This page can become a live converter after ImageConvert has a proven RAW decoder, a real X3F export path, artifact-byte tests and clear limits for file size, metadata and visual fidelity.