RawTherapee: a raw developer for photographers who want the controls in front of them

What RawTherapee solves, and for whom

RawTherapee takes a raw file from a digital camera and turns it into a developed image. The README describes the input range as raw files from a broad range of cameras, HDR DNG files, and non-raw formats including JPEG, TIFF and PNG. The output side is deliberately unfinished: the README says professionals may use it while enjoying complete freedom, but will probably lack peripheral features such as Digital Asset Management, printing and uploading, and it states plainly that RawTherapee is not aimed at being an inclusive all-in-one program.

That sentence is the whole positioning. If you want one window that imports, develops, catalogues and prints, this is the wrong tool and the project says so. If you want the development stage itself exposed, it is the right one. The README names the target audience as enthusiast newcomers who want to broaden their understanding of how digital imaging works, through to semi-professional photographers, and notes that knowledge of color science is not compulsory but that you should be ready to read RawPedia and look up basic concepts elsewhere.

The dcraw fork and why demosaicing is the centre of the program

The architecture described in the README is a C++ engine with a GTK+ front end. Raw decoding is not written from scratch: RawTherapee uses a patched version of dcraw for reading raw files, with an in-house solution that the README says adds the highest quality support for certain camera models unsupported by dcraw and improves the accuracy of certain raw files that dcraw already handles.

That fork matters more than it sounds. A camera released after the last dcraw update is exactly the case where a patched reader earns its place, and it is also the case where a new body may render incorrectly or not at all until support lands. The repository layout reflects the split: rtengine/ holds the processing engine, rtgui/ the interface, and rtdata/ the bundled data the program loads at runtime. The README singles out advanced control over the demosaicing and development process as what the program is notable for, which is a design commitment rather than a feature list item: the early pipeline stages are surfaced to the user instead of being hidden behind a default.

Installing RawTherapee and processing your first raw file

The README does not give install commands. It points to https://www.rawtherapee.com/downloads for binaries and to https://www.rawtherapee.com/shared/source/ for source tarballs, and it sends anyone building from source to RawPedia, with separate pages for Linux, Windows and macOS. Treat those pages as the install instructions, because the README itself does not carry them.

On a Debian or Ubuntu system the package route is a single command, and the binary is named rawtherapee:

sudo apt install rawtherapee
rawtherapee

What you should see is the GTK+ window opening with a file browser on the left. If the version reported by your package is older than 5.13, the release published on 2026-07-26, you are running something behind the current release and the download page is the alternative.

With the program open, the working loop is: point the file browser at a folder, select a raw file, and the editor opens with the tool panels on the right. The README's own framing is that you should expect to read RawPedia alongside the program, so the practical first step is to open the Demosaicing panel and the Exposure panel and change one setting at a time rather than applying a preset you cannot explain. The README does not document a preset workflow, so nothing here should be presented as one.

Where RawTherapee is the wrong choice

The clearest failure mode is the one the README admits: no Digital Asset Management, no printing, no uploading. A photographer who needs a searchable catalogue of ten thousand images across multiple drives will not find it here, and the README's answer is that the open-source community offers those peripheral features in other specialized software. That is a real boundary, not a roadmap gap.

The second limitation is the reading layer. Because raw decoding depends on a patched dcraw plus in-house additions, support for a newly released camera body is a code change, not a configuration. The README does not document a fallback for unsupported bodies, so the practical check before adopting is whether your specific model is handled. The third is the learning curve the README itself sets as a precondition: it recommends you are eager to learn and ready to read the documentation. Anyone who wants a slider that says what it does and nothing more will find the demosaicing and development controls excessive.

How RawTherapee differs from darktable

darktable is the comparison people search for, and the difference in approach is structural rather than a matter of which sliders exist. darktable is built around a database: images are imported into a catalogue, and the catalogue is the thing you work from. RawTherapee's README describes no such layer at all; it describes a raw processing program whose file browser reads a folder, and it explicitly hands Digital Asset Management off to other software.

That changes daily behaviour. With a folder-based tool you keep your own directory structure and the program has no opinion about it, which suits someone who already has a filing system and wants a developer, and frustrates someone who wants to search by keyword or track which images were already exported. The second difference is the pipeline. RawTherapee's README highlights advanced control over demosaicing and development, which puts the earliest and least visible stage of raw conversion in front of the user. Both programs are free software and both target raw shooters; the choice comes down to whether you want a catalogue at the centre or the demosaicing stage at the centre.

Version, licence and what upgrading costs you

RawTherapee is released under the GNU General Public License Version 3. For anyone using the program, that means no licence fee and no per-seat accounting. For anyone embedding it in a product, GPL-3.0 is a copyleft licence and the terms govern redistribution, so the licence file in the repository root is the document to read rather than a summary. Nothing here is legal advice.

The release history is the upgrade picture: 5.13 on 2026-07-26, a 5.13-rc1 on 2026-06-21, and 5.12 on 2025-05-28. That is roughly one release a year, with a release candidate ahead of it. The last push to the dev branch was on 2026-09-21, two days before this writing, so development is ongoing rather than dormant, and the default branch is dev rather than a stable branch. The cost of upgrading is the ordinary one for a raw developer: a new version may change how an existing edit renders, and the README does not document rollback or side-by-side version installation. If you keep long-lived edits, decide before you upgrade how you will compare the old and new rendering of a file you care about.

Editorial conclusion

Adopt RawTherapee if you develop raw files one at a time and want to see and tune the demosaicing and development stages rather than accept a preset pipeline; the README states the target audience runs from enthusiast newcomers willing to read RawPedia up to semi-professionals. Do not adopt it expecting a single application that also catalogues, prints and uploads, because the README says outright that it is not aimed at being an inclusive all-in-one program. Before you commit, verify two things yourself: that your camera body is handled by the patched dcraw reader, and that the build you install matches the 5.13 release rather than an older package sitting in your distribution's repository.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. Project website
3. RawTherapee/RawTherapee on GitHub
4. README
5. Releases