CalibRaw carries editable RAW photo adjustments between desktop and Android
The quiet catch is in the backup: an original photo alone leaves its adjustments behind. Graphics drivers also decide which older machines can join in.
A photo can move between a phone and a desktop without becoming a flattened souvenir of the edits already made. CalibRaw saves the original picture and its editing instructions separately, so changing devices doesn’t have to mean starting over with a JPEG and a small grudge.
The project’s README describes JSON sidecars holding sliders, curves and masks. Android uses the same engine and sidecar format as the desktop app, with controls laid out for touch. That puts the interesting promise in a tiny companion file: the exposure adjustment travels with the photo, rather than being permanently baked into a shared image.
A backup that includes only the RAW file misses those instructions. Copying the photo and its .calibraw file together preserves the ingredients and the recipe. It is a useful distinction before a folder gets renamed, moved to another computer or cleaned up by someone convinced every unfamiliar extension is clutter (a familiar temptation).
The editor includes the ordinary development controls that a masking demo can skip past: tone curves, color grading, highlight recovery, lens correction and retouching brushes. Presets can carry selected adjustment groups and masks to other images. The workflow documentation also describes applying a preset and a LUT during batch export without changing the saved edits. One set of source adjustments can therefore feed a different exported treatment without rewriting the original work.
AI adds subject and sky selection, object removal and RAW denoising, according to the maker. The README says models download “only after you agree,” receive a SHA-256 check, and then run offline. The local processing claim covers the editing operations; the first model download still needs a connection. The subscription bill stays out of the picture, which is a pleasant change of exposure.
Hardware remains the less photogenic condition. CalibRaw processes images through Vulkan, Direct3D 12 or Metal, and its graphics requirements explicitly exclude OpenGL-only drivers. Android needs a Vulkan-capable GPU and driver. Linux has a slow software-rendering route on some systems, and Windows can use its software renderer when the required hardware APIs are unavailable. Local doesn’t promise fast, especially when the CPU gets handed the GPU’s chore list.
Camera compatibility comes from LibRaw and Rawler. The supported-formats section says the editor tries Rawler when LibRaw cannot open a camera’s RAW, and points to their maintained camera lists. It also accepts rendered formats including JPEG, PNG, HEIC and TIFF. These are the developer’s documented capabilities, rather than results from a hands-on compatibility test.
Large exports have their own provision: tiled rendering is intended to avoid GPU memory limits, and a command-line tool handles batch rendering. That gives the phone-to-desktop promise a practical next step once a few images become a whole folder. Whether a particular camera file, driver and adjustment set completes that trip cleanly still needs a trial on the actual devices.
The edits ride sidecar.