How RapidRAW's Non-Destructive Workflow and Batch Editing Work
Updated
RapidRAW keeps your originals untouched by writing every adjustment to a sidecar file, and it lets you apply those adjustments to many photos at once through batch operations and saved presets. The workflow is built for photographers who want to experiment freely and then repeat a look across a shoot without re-editing each frame. It runs on Windows, macOS, and Linux, and the app itself is about 20 MB.
How the non-destructive workflow works
The core mechanism is simple: RapidRAW never overwrites your RAW file. When you change exposure, tone curves, HSL, detail, or effects, those settings are saved separately in a sidecar file that sits alongside the original. The image you see on screen is a rendering of the original plus the sidecar instructions.
That has three practical consequences:
- Your originals stay intact. You can always return to the untouched file, whether you want to start over or hand the photo to another tool.
- Edits are reversible and portable. Because the changes live in a sidecar rather than baked pixels, you can revisit an edit later and adjust any slider without quality loss.
- Deleting or moving files needs care. Since the sidecar is a separate file, keep it with its original when you reorganize folders. If you move a RAW file without its sidecar, the edit won't follow.
All adjustments are processed on the GPU, so the preview updates in real time as you drag sliders. That matters for a non-destructive workflow: you're evaluating the rendered result constantly, and slow feedback makes experimentation painful.
A concrete example
Say you shoot 200 photos at an event and want a consistent warm, slightly contrasty look. You edit one frame — adjust white balance, pull a tone curve, tune the HSL mixer, add a touch of detail enhancement — and save those settings as a preset. Your original files are unchanged; only sidecar data records the look. You then apply that preset across the rest of the set in a batch, and each photo gets its own sidecar. If one image looks off, you open it and tweak only that frame without affecting the others.
Managing a collection in the image library
RapidRAW includes a complete image library so you can browse and manage your whole photo collection in one interface rather than jumping between folders in a file manager. Combined with the sidecar model, this means your edits travel with your library view: you can scan a shoot, spot the frames that need work, and apply changes without leaving the app.
For large collections, the library is where batch work starts — you select the images you want to treat the same way, then push adjustments or a preset to all of them.
Batch operations and presets
Batch operations apply adjustments to multiple images simultaneously, and the preset system is what makes batching practical: you save a favorite look once and apply it instantly to any photo.
| Task | What you do | What happens |
|---|---|---|
| Save a look | Tune one image, save as a preset | Preset stored for reuse on any photo |
| Apply to a shoot | Select multiple images, apply the preset or adjustments | Each selected image gets the same settings in its own sidecar |
| Fix one outlier | Open that image and adjust it | Only that image's sidecar changes; the batch result for others is untouched |
A sensible order of operations: cull in the library first, edit a representative frame, save the preset, batch-apply, then review and correct individual images. Doing it in that order avoids re-batching after you've made per-image fixes.
Where AI fits into the workflow
AI masking (subject, sky, and foreground detection) and automatic image tagging are built in and run locally on your computer — fast, free, and with no setup. That means localized edits, such as brightening a sky or lifting a subject, can be part of your batch workflow without sending files anywhere.
Generative tools like object removal are different: they need an optional ComfyUI backend (self-hosted on your own GPU) or RapidRAW Cloud, an optional subscription service. If your batch workflow depends on generative edits, plan for one of those two paths; the built-in AI tools alone cover masking and tagging, not generative removal.
Common snags to plan for
- Sidecar discipline. Back up sidecars together with originals, and don't separate them when moving files between drives.
- GPU dependence. Real-time feedback relies on GPU acceleration, so performance on weaker hardware will differ; test with a representative batch before committing to a large job.
- Generative edits aren't local by default. Built-in AI is local, but object removal requires ComfyUI or the Cloud subscription — decide which before building a workflow around it.
- Presets are starting points. A preset applied across mixed lighting will need per-image correction; batch first, then refine.
If you want to go deeper, RapidRAW publishes documentation covering setup, masks and AI, presets, and complete edit walkthroughs, plus a shortcuts reference for speeding up the repetitive parts of batch work.