LightCraft vs Lightroom: A Local-First Raw Editor Measured Against Adobe's

LightCraft vs Lightroom is a comparison between a local-first raw developer written in Rust and the photo workflow most photographers already know. LightCraft copies Lightroom's structure on purpose: a library with albums and ratings, a Develop-style set of sliders, masking, presets and export. It differs in how it is built and licensed, and in one weakness the README names without hedging: raw colour accuracy for many cameras is still unfinished.

What each one is

LightCraft is part of the ArtCraft family of open-source apps, described in the Crafting Apps guide. It is dual-licensed under MIT or Apache-2.0, runs natively on macOS, Windows and Linux and in the browser via WebAssembly, and has no account, cloud or telemetry. The README says it is young and moving fast.

Adobe Lightroom is a closed-source photo library and editor sold on subscription, with cloud sync and a large ecosystem of presets and profiles. Photographers use it for both the catalogue and the edit, and it is tightly tied to the rest of Adobe's apps.

How LightCraft edits

LightCraft is non-destructive, so original files are never touched, and its pipeline is scene-referred, wide-gamut and 32-bit float. The README describes edge-aware local tone mapping behind the Highlights and Shadows sliders, and says it computes colour work in OkLCh, a perceptual colour space.

The adjustment set mirrors what a Lightroom user expects:

• Light: Exposure, Contrast, Highlights, Shadows, Whites and Blacks.
• Color: white balance with an eyedropper, Vibrance that protects skin tones, Saturation, an 8-band Color Mixer and three-way Color Grading wheels.
• Effects: Texture, Clarity, Dehaze, Vignette and Grain.
• Tone curve: a parametric curve plus point curves for RGB and each channel.
• Detail, optics and geometry: sharpening, noise reduction, distortion and chromatic aberration controls, Upright, crop and straighten.
• Black and white: an 8-band mix.

Masking covers brush, linear and radial gradients, luminance and colour range, and Add, Subtract and Intersect combinations, with 15 local adjustments per mask. Subject and sky selection exist, but the README says they use classical heuristics for now rather than trained AI models.

Photo Merge for HDR and panoramas, spot removal with healing and cloning, and red-eye correction are also listed as working.

Library and workflow

The library covers albums nested in folders, smart albums, stacks, virtual copies, ratings, flags, colour labels, search, a filter bar, and Compare and Survey views for culling. Import can copy, move or add in place, with watched folders and duplicate detection. Export covers JPEG, PNG, TIFF, WebP, AVIF and DNG with batch naming, sharpening, watermarks and a metadata policy.

The README gives timing figures from a single machine, a 24-megapixel raw on an Apple M4 Pro, with sliders re-rendering in a few milliseconds. These are the project's own numbers on one system, so treat them as a design goal, not a benchmark you will see on every computer.

The raw colour problem

This is the most important limit. The README says DNG files use the matrices embedded in the file, so they look right. Sony ARW, Nikon NEF and Panasonic RW2 start from a look fitted to the camera's own JPEG, and other raws start from a neutral fallback, so colour looks muted. Canon CR3 and compressed Fujifilm and Olympus raws open as embedded previews only.

If you shoot Canon's current format, LightCraft cannot develop your files fully yet. Lightroom has years of camera-specific profiles behind it, and open-source raw developers such as darktable and RawTherapee have broad camera support too.

Speed, storage and interoperability

LightCraft's rendering pipeline runs on the GPU through wgpu compute and is checked against a CPU pipeline to within 1/255. When no suitable GPU is available, the same pipeline runs on all CPU cores and redoes only the stages a slider affects. The README adds timing figures from one machine, an Apple M4 Pro with a 24-megapixel raw: a slider update re-renders in a few milliseconds, and opening a raw shows its embedded camera preview within about a tenth of a second while the full render follows. Those are the maintainers' measurements on one system, so expect different numbers on other hardware.

Culling is designed for speed. The next and previous photos are prepared in the background, so stepping through a shoot stays quick, and a worker pool renders the loupe, the before and after view and every visible thumbnail off the interface thread, using drafts during drags and full quality on release.

The catalogue is a crash-safe, append-only log of human-readable operations with snapshots and background compaction, and failed saves are reported instead of hidden. Because it is a log, you can diff it, back it up or replay it. That is a different philosophy from a single opaque database file, and it suits people who care about long-term ownership of their edits.

For interoperability, LightCraft reads and writes XMP sidecars, can read develop settings stored in Lightroom-style crs: tags, and loads preset files in its own format and in XMP form. It also ships profiles of its own (Color, Neutral, Vivid, Portrait and Monochrome among them) rather than copies of Adobe's.

Switching checklist

1. Pick one finished shoot and import it in place, so the originals stay where they are.
2. Check each camera model's colour against the same frames in Lightroom, since raw colour support is the largest variable.
3. Open an XMP sidecar from the old workflow and see which adjustments carry over.
4. Test the masks you rely on, remembering that subject and sky selection are classical heuristics today.
5. Export a batch with your usual naming, sharpening and metadata policy, and confirm the files meet your delivery needs.
6. Keep your Lightroom catalogue until the result satisfies you.

Cost and ownership

LightCraft is released under MIT or Apache-2.0 and the README states no account, no cloud, no telemetry and no subscription. Your catalogue is a human-readable log on your own disk, and sidecar files hold the edits next to the photos, so leaving the program later is a matter of copying folders.

Lightroom's strengths here are the ones a photographer pays for: cloud sync across devices, a mobile app, camera-specific profiles and a long list of presets. LightCraft does not offer sync, and its README presents the catalogue as local-first. If you work on one computer, that is fine. If you edit on a phone or a second machine, plan for a manual workflow.

Comparison table

Other gaps the README lists

• AI masks, AI denoise and super resolution are not implemented.
• HDR editing and export, video, and the Print, Book and Map modules of the original are not covered.
• Camera lens profiles of its own are still to come.
• The browser build is working but WebGPU and Safari and Firefox testing are in progress.

The maintainers rate their feature coverage at about 79 percent and day-to-day replacement at 60 to 70 percent. These are self-assessments, and they are unusually specific about what holds the score down.

Which should you pick

Pick Lightroom if you shoot a camera whose raws LightCraft cannot develop, rely on cloud sync across devices, or edit with presets and profiles you already own.

Pick LightCraft if you shoot DNG, Nikon or Sony, want a library with no account and no subscription, or want to script edits through its command line and MCP server.

Pick darktable or RawTherapee if you want a mature open-source raw workflow today. The photos category lists more tools, and PhotoCraft from the same team handles layered pixel editing rather than raw development.