RapidRAW combines a photo library with a GPU editor
RapidRAW imports folders into a library, builds thumbnails, rates and tags photographs, and stores non-destructive edits in .rrdata sidecars. The editor covers exposure, white balance, curves, HSL, color wheels, sharpening, noise reduction, lens correction, crop, perspective, effects, and layered masks. Batch work, virtual copies, presets, a filmstrip, and a headless export command make it more than a single-image demo. Original files remain separate from the adjustment records.
Version 1.6.2 added camera tethering, focus stacking, built-in film emulations, rewritten sharpening, and drag-and-drop organization. Existing features include HDR merging, panorama stitching, local AI masks, generative editing through an optional backend, and exports to several common and specialist formats. The breadth is appealing, but every camera decoder, GPU backend, sidecar operation, and export path expands the compatibility surface photographers must verify.
Packaged releases cover four platforms, with limits
The release page provides Windows, Intel and Apple Silicon macOS, Ubuntu, and experimental Android packages. Linux users also have a Flatpak route in the README. Windows and macOS packages are not code-signed, so Windows may show SmartScreen and macOS users are told to remove the quarantine attribute. That is a real trust decision for software that scans and edits a photo library; packages should come from the project's official release.
Tethering ships separately on macOS and Linux because it dynamically links to libgphoto2. Users must install that system library before the tethering build will launch. Windows and Android tethering are unsupported. The dedicated build avoids burdening ordinary installs with the dependency, but a studio must check its exact camera, live view, controls, ingestion directory, disconnect behavior, and preset application before using it on a paid shoot.
What happened when we ran it
Our sandbox installed 427 npm packages in 19 seconds and used 320 MB on disk. The build succeeded in 5 seconds at commit 240169c. The checkout contained 386 files, roughly 87,731 lines of source, and 19.1 MB before dependencies. Npm audit found 0 known vulnerabilities: 0 critical, 0 high, 0 moderate, and 0 low. The environment was an unprivileged Debian container with 3 CPUs and 8 GB of RAM.
There was no tests script or target, so our harness skipped tests. The repository also had no tests directory, though it contained 5 CI workflow files and no Dockerfile. A successful 5-second build proves that the measured frontend command completed. It does not validate RAW decoding, shader output, sidecar round trips, EXIF preservation, camera tethering, or batch export across Windows, macOS, Linux, and Android. That missing regression surface lowers the maturity score.
Batch export and metadata reports matter more than a pretty preview
Issue 1571 reports 2 incorrect images across about 850 exported files on Windows 11 with RapidRAW 1.6.0. In each case, a file was saved using content from a later photograph, with altered darkness or cropping, while individual export worked. The reporter could not reproduce it deterministically. Even a rare mismatch is serious because photographers often leave large batches unattended and trust filenames to identify the output.
Version 1.6.2 advertises full EXIF preservation, while issue 1612 reports three fields missing from an exported JPEG made from an uncompressed DNG even with metadata retention enabled. The fields displayed inside RapidRAW but did not reach the file. Before delivery, compare filenames, pixel content, dimensions, color, orientation, timestamps, camera data, copyright fields, and location data with both the source and a second metadata reader.
GPU acceleration makes hardware testing mandatory
The README recommends 16 GB of RAM and a dedicated GPU for high-resolution RAW files, undo history, and layered masks. It warns that older graphics hardware may be slow or unstable. Users can manually choose Vulkan, DirectX 12, OpenGL, or Metal when automatic backend selection crashes in edit mode. Linux Wayland systems, particularly some NVIDIA setups, may require WebKit environment variables or X11.
Current issue 1597 reports a v1.6.2 image becoming partly transparent on Windows 10 shortly after edit mode opened. Issue 1603 reports vertical and horizontal transforms operating in the unrotated coordinate system after a 90-degree rotation, with a fix pull request open. These are individual reports, not universal failures. They show why the trial set should include rotated images, masks, transparency, multiple GPUs, large files, and every export format used in production.
Local AI is optional, while ComfyUI adds another stack
Built-in tools cover subject, sky, foreground, depth, color, and luminance masks. Those local features can support ordinary editing without an account. Generative removal and replacement can use a self-hosted ComfyUI instance through the RapidRAW AI Connector, which manages image caching and workflow injection. That path needs a capable GPU, ComfyUI, model assets, custom nodes where workflows require them, and another service to update.
The README also describes a future optional cloud subscription with an unspecified price. That statement is an intention, not a current plan a buyer should budget around. Choose RapidRAW for the features that ship now. Local AI results still need inspection at export resolution, especially around hair, skies, repeated texture, and mask edges. A mask that looks convincing at fit-to-window zoom can leave artifacts in the delivered file.
Same-day activity cannot replace workflow evidence
GitHub recorded 9,615 stars, 370 combined open issues and pull requests, and a last push on August 26, 2026. Release v1.6.2 arrived on August 21. Current activity includes bug reports, frontend cleanup, export changes, transform work, metadata requests, and feature pull requests. The project is actively maintained, while the size and pace of its issue surface fit a young editor supporting many cameras, GPUs, operating systems, and file formats.
RapidRAW is easy to recommend for an enthusiast's second editor and worth evaluating for a small studio with time to qualify it. Our 0-advisory npm audit and successful 5-second build are good repository signals, yet the absent test target and current export reports keep it out of a trust-by-default role. Preserve originals, keep the established catalog, and make repeated correct batches earn promotion into the primary workflow.