Open-source project
RawTherapee/RawTherapee avatar
RawTherapee/RawTherapee

RawTherapee: demosaicing control, a dev branch, and two C++ formatters

A powerful cross-platform raw photo processing program

4,298 stars430 forksC++GPL-3.0

At a glance

What is it?
RawTherapee is a cross-platform raw photo developer released as libre software under the GPL, written mostly in C++ with a GTK front end, and notable for how much control it gives over demosaicing and development. Its repository carries two different C++ formatters, its default branch is dev, and it deliberately leaves asset management, printing and uploading to other software.
Who is it for?
Use RawTherapee if you want to develop raw files yourself, you are willing to read documentation before touching the controls, and your workflow does not depend on asset management, printing or uploading. Those omissions are stated rather than accidental, so do not expect them to arrive.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 6 days ago.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • RawTherapee/RawTherapee4,298 ★ · +116
Star history
Repository2026-09-242026-11-15
RawTherapee/RawTherapee4.2k4.3k

116 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The default branch is dev, and the readme is served from it

The repository's default branch is named dev, not master or main.

You can see that in the page itself. Both logo images, the light and the dark variant, are referenced through raw file URLs that include the branch name in the path, so the readme being read on the site is the one attached to development work rather than to a released version.

Releases are tagged separately and follow a release candidate pattern. The most recent is version 5.13 from July 26, 2026, preceded by a candidate build in June and by version 5.12 in May 2025. The last push to the repository is dated November 1, 2026, so work has continued on the development branch since the release.

The practical consequence is that the front page of the project and the released version are not necessarily describing the same software. If you are following the documentation to work out what a control does, check which version it belongs to before assuming the answer applies to what you installed.

Two C++ formatters are configured in one repository

Look at the top level and the formatting story appears twice.

There is a clang-format configuration file and, beside it, a file telling clang-format which paths to skip. There is also an AStyle configuration file named after the project, and a Windows batch script whose name is a contraction of the tool that runs it.

So the repository carries a clang-format setup with an ignore list and an AStyle setup, plus a batch script for running the second one on Windows.

Neither is documented in the readme, which is otherwise about what the program does rather than how the source is worked on. The contributing guide and a developer notes directory are where that would live.

For a contributor the practical question is which one applies to the file you are touching. Running both across the same source produces churn in whichever formatter is not the local convention.

dcraw is patched rather than replaced

The raw file reading path is the part of the program with the longest history, and the readme is specific about it.

RawTherapee uses a patched version of dcraw for reading raw files. On top of that it carries an in-house solution, and the description of what that solution does has two parts: it adds the highest quality support for certain camera models that dcraw does not support at all, and it improves the accuracy of certain raw files that dcraw already handles.

That is a narrower claim than replacing the decoder, and it is the kind of claim worth reading carefully. Newer camera models whose raw formats dcraw does not know about need a separate path, which is what the in-house work covers. Improving accuracy on files that already work is a different task, and it is the one that benefits existing users rather than unlocking new cameras.

The rest of the program is its own: it is written mostly in C++, and the repository separates the engine, the graphical interface and the data directories, with an external directory for third-party code.

The exposed control is demosaicing and development

The readme states one thing about what distinguishes the program, and it is about the processing pipeline rather than about features.

RawTherapee is notable for the advanced control it gives the user over the demosaicing and development process.

Those are the two decisions every raw developer makes: how the sensor's colour filter array is interpolated into full colour pixels, and how the tones are mapped afterwards. Exposing them as user-facing controls is unusual, and it is the reason the audience section below needs qualifying.

The documentation is a wiki called RawPedia, which is linked twice, once as the place to read and once as the source for how to build on each operating system. It also has a features page. And the readme is careful about its own limits: it tells you that colour science knowledge is not compulsory, that it is recommended you are eager to learn and ready to read the documentation, and that concepts outside the scope of that wiki, with colour balance given as the example, should be looked up elsewhere.

That is an unusual thing for a project to say about its own users, and it sets expectations about how much reading is involved.

Asset management, printing and uploading are deliberately absent

The target audience section is unusually blunt about what the program is not.

Professionals may use RawTherapee and enjoy complete freedom, but they will probably lack some peripheral features. The ones named are digital asset management, printing and uploading, followed by a general etc.

The justification is a positioning statement rather than a roadmap. RawTherapee is not aimed at being an inclusive all-in-one program, and the readme argues that the open source community is sufficiently developed by now to offer all those peripheral features in other specialised software.

So this is a deliberate division of labour. The program develops files; something else catalogs, prints and uploads them. If your workflow is one application from import to delivery, RawTherapee is a component of it rather than the whole of it.

The audience itself is described in the same paragraph as ranging from enthusiast newcomers who want to broaden their understanding of how digital imaging works through to semi-professional photographers. Paired with the control-over-demosaicing claim, that is a coherent position: the tool rewards people who want to understand the decisions, not people who want a panel of sliders.

Three build pages and no instructions in the readme

Compilation is handled by sending the reader elsewhere, and the elsewhere is organised per operating system.

There is a Linux page, a Windows page and a macOS page, all on the same documentation site, and the readme says that page has a detailed explanation of how to get the necessary dependencies and how to compile the program.

The repository holds the machinery those instructions operate on. There is a CMake list file, a file of CMake presets, a processor targets file, a Windows-specific CMake file, and a cmake directory, so the build is configured per platform in source rather than by a script the reader copies.

Downloads are also split in two, with a page for the program and a separate page for source code tarballs.

The last push to the repository is dated November 1, 2026, and the release notes file at the root is the per-version record, so a reader building from the branch rather than from a tarball is working with whatever the current state is.

The forum is a category on a shared site

The links section is short, and one of them is worth reading closely.

The community link is not a forum RawTherapee runs. It is a category path on a shared discussion site, under a section for software with a category for this program.

That tells you something about the project's scale: it does not host its own forum, and discussion happens alongside other image processing tools on a site that other projects use too.

The rest of the links are the website, a features page, the documentation wiki, a downloads page and the source tarballs page. Six links, all of them pointing outward, none of them a repository page, which is consistent with a readme whose job is to send a new user to the right place rather than to explain the software in place.

One file in the repository root is the exception to all of this. There is a desktop application metadata file named after the project, which is what package formats use to describe a desktop entry, and it is the one place in the tree where the program's identity as a packaged desktop application is recorded.

Editorial conclusion

Use RawTherapee if you want to develop raw files yourself, you are willing to read documentation before touching the controls, and your workflow does not depend on asset management, printing or uploading. Those omissions are stated rather than accidental, so do not expect them to arrive. Check three things before you commit. The source build is documented on separate pages per operating system rather than in the repository, so plan for that. The default branch is the development branch, which means the readme you read online is the one attached to unreleased work. And if you contribute, notice that the project carries two formatters, so match whichever one the surrounding code already follows rather than running both. Professionals who need the surrounding workflow should pair it with the specialised software the readme points at.

Frequently asked questions

Is RawTherapee completely free?

It is released as free software under the GNU General Public License Version 3, and the readme links the licence text directly. There is no paid edition mentioned anywhere in the project description.

Is RawTherapee as good as Lightroom?

The project does not make that comparison. What it says is that professionals may use it and enjoy complete freedom, but will probably lack peripheral features such as digital asset management, printing and uploading, and that it is not aimed at being an inclusive all-in-one program.

Which is better, darktable or RawTherapee?

The readme does not compare the two. It describes RawTherapee as notable for the advanced control it gives over demosaicing and development, and points readers to a shared discussion site with a category for RawTherapee.

How do I use RawTherapee?

The readme does not contain operating instructions. It points to RawPedia as the documentation, with a separate features page, and it says colour science knowledge is not compulsory but recommends being eager to learn and ready to read the documentation.

How do I build RawTherapee on macOS?

Through the documentation site, which has a page per operating system for Linux, Windows and macOS covering the dependencies and the build. The repository supplies the CMake configuration, including a presets file and platform-specific files, rather than a script to copy.

Official sources

  1. License: GPL-3.0
  2. Project website
  3. RawTherapee/RawTherapee on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/rawtherapee-rawtherapee.svg)](https://hysenlabs.com/projects/rawtherapee-rawtherapee)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/rawtherapee-rawtherapee.svg)](https://hysenlabs.com/projects/rawtherapee-rawtherapee)

Was this useful?