5.10

To get the source code, either clone from git and git checkout 5.10, or use the rawtherapee-5.10.tar.xz tarball below. Do not use the Source code (zip/tar.gz) tarballs auto-generated by GitHub below, they lack some metadata.

5.10-rc1

To get the source code, either clone from git and git checkout 5.10-rc1, or use the rawtherapee-5.10-rc1.tar.xz tarball below. Do not use the Source code (zip/tar.gz) tarballs auto-generated by GitHub below, they lack some metadata.

5.9

To get the source code, either clone from git and git checkout 5.9, or use the rawtherapee-5.9.tar.xz tarball below. Do not use the Source code (zip/tar.gz) tarballs auto-generated by GitHub below, they lack some metadata.

5.9-rc1

To get the source code, either clone from git and git checkout 5.9-rc1, or use the rawtherapee-5.9-rc1.tar.xz tarball below. Do not use the Source code (zip/tar.gz) tarballs auto-generated by GitHub below, they lack some metadata.

Automated Builds

Here you can download automated builds of the latest development version of RawTherapee. For pre-dev builds, see Pre-dev Builds.

Development build filenames follow this structure:
RawTherapee_<branch>_[operating-system]_<build-type>.<extension>

• Branch
  Each commit happens on a branch. The main branch is called dev. New features are developed on their own branches, and then merged into dev when ready. When in doubt, get dev.
• Operating system
  A build is made for a specific operating system: win64 builds run on any modern 64-bit version of Windows, macOS_10.15 builds run on the specified version of macOS or newer, and Linux builds which should run on any modern distro omit the OS segment and instead use AppImage as the extension.
• Build type
  The build type is either release or debug. Release-type builds are optimize to run fast, but do not provide any useful information in case of a crash. Conversely, debug-type builds are capable of producing useful information during a crash for a bug report, but will run significantly slower. When in doubt, get release.

Every time the source code is changed, a development build is automatically created. These builds are provided for the sole purpose of allowing you to try out the newest features and the latest fixes, and to report your findings back to us via GitHub or the forum.

Development builds are not intended for production use and we provide no backward or forward compatibility for sidecar files (pp3) created using a development build! That means that a sidecar file created using a dev build will very likely lead to different results when used in a stable release or in another dev build. If stability and compatibility are key for you, we always recommend that you use the latest stable release. If you want to make use of a feature or fix present in the latest dev build in production, you have to wait until we release the next stable version.

Signed-in GitHub users can download older or additional build artifacts from the GitHub Actions page.

To build RawTherapee yourself, do not use the provided source code archives from this release as they lack some metadata.

5.8

To get the source code, either clone from git and git checkout 5.8, or use the rawtherapee-5.8.tar.xz tarball below. Do not use the Source code (zip/tar.gz) tarballs auto-generated by GitHub below, they lack some metadata.

5.7

To get the source code, either clone from git and git checkout 5.7, or use the rawtherapee-5.7.tar.xz tarball below. Do not use the Source code (zip/tar.gz) tarballs auto-generated by GitHub below, they lack some metadata.

5.6

To get the source code, either clone from git or use the tarball from http://rawtherapee.com/shared/source/ . Do not use the auto-generated GitHub release tarballs.

5.6-rc2

To get the source code, either clone from git or use the tarball from http://rawtherapee.com/shared/source/ . Do not use the auto-generated GitHub release tarballs.

5.6-rc1

To get the source code, either clone from git or use the tarball from http://rawtherapee.com/shared/source/ . Do not use the auto-generated GitHub release tarballs.