SaaS Metrics
Gemini Executive Synthesis
Camera RAW file format support.
Technical Positioning
Developing a proprietary, pure-Rust, clean-room RAW decoder to achieve competitive feature parity with professional image editors, specifically addressing a critical market demand and competitor claims of lacking RAW support. The 'no LibRaw, no LGPL deps, no unsafe, wasm-safe' constraints define the architectural approach.
SaaS Insight & Market Implications
This issue addresses a critical market requirement for PhotoCraft: comprehensive Camera RAW file support. User feedback and competitor claims underscore this as a 'must-have' feature for professional image editing. The decision to build a 'clean-room, pure-Rust decoder' without external dependencies (LibRaw, LGPL) and unsafe code, while ensuring wasm-safety, defines a highly strategic and technically ambitious approach. The pain point is the current inability to process standard RAW formats, hindering adoption by photographers. For B2B SaaS in creative industries, robust RAW support is foundational. This initiative positions PhotoCraft to directly challenge established players by offering a performant, secure, and architecturally distinct solution, potentially appealing to enterprises with strict dependency or security policies. The detailed scope indicates a thorough understanding of the technical complexities involved.
Proprietary Technical Taxonomy
Raw Developer Origin & Technical Request
GitHub Issue
Oct 4, 2026
Repo: storytold/photocraft
Camera RAW support: clean-room Rust decoder (DNG, CR2, NEF, ARW, …)
Forum feedback: *"(Lossless) Compressed RAW support is a must"*, and a competitor's claim we have no raw support. Today TIFF-based raw files fail with a clear 'not supported' error (#25).
**Decision**: a clean-room, pure-Rust decoder (no LibRaw, no LGPL deps, no unsafe, wasm-safe), implemented from public specs.
**Scope (first cut)**
- DNG (uncompressed, lossless JPEG/LJ92, tiles, linearization, black/white levels, ColorMatrix/ForwardMatrix, AsShotNeutral)
- TIFF-based camera formats: CR2 (LJ92), NEF (lossless/compressed), ARW, PEF, ORF where feasible
- Demosaic (bilinear plus a higher-quality AHD/RCD-class option), white balance, camera → XYZ → working space, 16-bit output, embedded preview fallback
- Opens as a normal document; fuzzed and bounded against hostile input.
CR3 (ISO BMFF + CRX) and RAF/X-Trans are follow-ups.
🤖 Generated with [Claude Code](claude.com/claude-code
Developer Debate & Comments
Progress: landed the first cut of the clean-room `photocraft-raw` decoder: DNG (uncompressed and lossless JPEG, tiles, colour matrices, GainMap; phone DNGs included), Canon CR2, Sony lossless ARW, and uncompressed NEF/ARW/PEF, with bilinear, MHC and AHD demosaicing, opened as 16-bit ProPhoto documents. Still open here: - vendor-compressed NEF/ARW/PEF (Nikon's default lossless-compressed NEF in particular), CR3, RAF and ORF/RW2 currently open their embedded preview with a warning; - calibrated colour for non-DNG cameras (they're currently treated as sRGB primaries, so slightly undersaturated); - highlight reconstruction and a default tone curve.
Status after 0.2.0 + : DNG (incl. phone DNGs), Canon CR2, Sony ARW (lossless **and** the default compressed cRAW), Panasonic RW2 (RawFormat 5) and uncompressed Olympus ORF decode in the clean-room `photocraft-raw` crate. Still open, and why: - **Nikon compressed NEF** (Nikon's default): its decompression tables are only documented in GPL code (dcraw/LibRaw) or write-ups derived from it, so a clean-room implementation isn't possible without an independent specification. These files open their full-size embedded JPEG preview, with a warning. - **CR3, RAF (X-Trans), compressed ORF/PEF, RW2 RawFormat 4:** same situation or not yet investigated; they also open the embedded preview. - **Calibrated colour for non-DNG cameras:** needs per-camera matrices we can't take from third-party tables. Converting to DNG (Adobe DNG Converter) gives full-quality decoding for any camera today.
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from storytold/photocraft.
Extracted Positioning
Application stability and graphics backend compatibility on Windows.
Ensuring reliable application launch and operation on Windows, specifically addressing crashes related to the Intel Vulkan driver and seeking a robust graphics fallback mechanism (e.g., DirectX) for all launches. This aims for broad compatibility and stability.
Top Replies
Thanks for the thorough investigation and the DX12 workaround, @hambydustin-eng — that was really useful. 🙏 I believe your crash shares a root cause with : the GPU compositor rendered into an `Rgb...
Update, @hambydustin-eng: on top of the `Rgba16Float` fallback from , (now on `main`) hardens GPU start-up further: - if the GPU compositor's pipelines can't be built on an adapter (an unsupported ...
An update, @hambydustin-eng: (on main) makes startup survive driver crashes like yours. Before creating the GPU device, PhotoCraft now writes a small "starting" marker. If the previous launch died ...
Extracted Positioning
Eraser tool behavior on the Background layer.
Aligning the eraser tool's functionality with common expectations in professional paint applications, where erasing on a background layer typically reveals the background color rather than being 'locked out.' This aims for intuitive user experience and feature parity with industry standards.
Extracted Positioning
Stylus input (pressure/tilt) support for PhotoCraft on macOS and Linux.
Achieving feature parity with Windows and web platforms for professional-grade stylus input, crucial for a Photoshop reimplementation. The constraint of 'pure Rust' and forbidding 'unsafe code' dictates specific technical approaches.
Extracted Positioning
User Interface (UI) dropdown menu behavior.
Adherence to standard UI/UX expectations for desktop applications, specifically dynamic dropdown height based on content and screen real estate, avoiding unnecessary scrollbars. Aims for a 'clean-room reimplementation of Adobe Photoshop' implies matching professional application UI standards.
Frequently Asked Questions
Market intelligence mapped to Camera RAW file format support..
How is Camera RAW file format support. positioned in the market?
Based on our AI analysis of the original developer request, its primary technical positioning is: Developing a proprietary, pure-Rust, clean-room RAW decoder to achieve competitive feature parity with professional image editors, specifically addressing a critical market demand and competitor claims of lacking RAW support. The 'no LibRaw, no LGPL deps, no unsafe, wasm-safe' constraints define the architectural approach.
Are engineers actively discussing Camera RAW file format support.?
Yes, we have tracked 2 direct responses and active debates regarding this specific topic originating from GitHub Issue.
What are the foundational technologies related to Camera RAW file format support.?
Our proprietary extraction maps Camera RAW file format support. to adjacent architectural concepts including Camera RAW support, clean-room Rust decoder, Lossless Compressed RAW, TIFF-based raw files.
Are there startups building around Camera RAW file format support.?
Yes, market intelligence reveals commercial overlap. A product named 'RawToHEIC' focuses directly on this: Convert RAW to HEIC inside Apple Photos
Engagement Signals
Cross-Market Term Frequency
Quantifies the cross-market adoption of foundational terms like unsafe and DNG by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.