Many users want to try out the latest features of the developer version (Development Build/Nightly) without jeopardizing their stable working environment.

The problem:
By default, all darktable versions use the same configuration folder with the same files, including databases. When you install then start a newer version, it updates your existing database, so your previous version will no longer be able to read the database.

The solution:
If you would like to use a development (dev) version to test, you need to let darktable know to create and use its own configuration folder. This is done via the start parameter --configdir.

Here are instructions for each operating system.


1. Preparation (for all systems)

Before you start, you should know where your current configuration files are if you want to make backups:

  • Windows: C:\Users\[DeinName]\AppData\Local\DarkTable
  • macOS: ~/.config/DarkTable
  • Linux: ~/.config/DarkTable

2. Instructions for Windows

On Windows, creating a shortcut is the easiest solution.

  1. Install: Install your stable version as normal. Download the dev version (usually a zip file or installer) and install it to a new folder (e.g. C:\Program Files\darktable-dev)
    • NOTE 1: do not uninstall your previous version.
    • NOTE 2: if you are attempting to install to “only me” and it does not allow you to create a new darktable-dev folder, choose to “install for everyone” instead.
  2. Create a shortcut:
    • Go to the newly created folder darktable-dev > bin folder.
    • Right click on darktable.exe > “Send to” > “Desktop (create shortcut)”.
  3. Add parameters:
    • Right click on the new shortcut on the desktop > Properties.
    • In the field “target” is the path to the exe. At the very end (after the …\darktable.exe) add a space and then the following text:
      --configdir "C:\Users\your_name\AppData\Local\darktable-dev"
    • replace your_name with your Windows username.
  4. Start: If you now start this shortcut, darktable creates a completely new, empty folder for settings and database. Your stable version remains unaffected.

3. Instructions for macOS

It’s a bit trickier on the Mac because apps are “packages”. We use the “script editor” to build a safe starter.

  1. Install:
    • Install the stable version in “Programs”.
    • Download the dev version, rename it in darktable-dev.app and also put them in “Programs”.
  2. Starter build:
    • Open the app “Script Editor” (Search via Spotlight).
    • Copy this code into: Do Shell Script “/Applications/DarkTable-Dev.App/Contents/MacOS/DarkTable –ConfigDir ~/.config/DarkTable-Dev”
  3. Save:
    • go to filing > Export.
    • Enter a name (e.g. “Start dt dev”).
    • Choose from file format: Program (application).
    • Save it to desktop or dock.
  4. start: From now on, use this icon to start the Dev version safely.

4. Instructions for Linux

Linux users are usually familiar with the terminal, but here too you can build a starter (.desktop file).

  1. Install: Install the Dev version (e.g. from the master repo or as Flatpak/AppImage).
  2. Start by terminal (to test): darktable –configdir ~/.config/darktable-dev
  3. Permanent Solution (Desktop Icon):
    • Copy the file /usr/share/applications/darktable.desktop to ~/.local/share/applications/darktable-dev.desktop.
    • Open the new file with a text editor.
    • Change the line name= to name=DarkTable Dev.
    • Change the line exec= to:
      exec=/usr/bin/darktable --configdir ~/.config/darktable-dev %u
      (Adjust path to the binary if necessary).

Important Notes

  • Where are my photos? The dev version starts “empty”; you don’t see your pictures. That’s okay! You have to re-import images or your database (library.db). NOTE: see Backup & Storage for more information.
  • XMP files: If you edit images in the dev version, it writes XMP files (Sidecars) – see “Recommendation” below. Caution: If you later open these images in the old, stable version, the edits may be lost or throw errors, since the old version does not yet know the new features of the XMP file. NOTE: see Backup & Storage for more information.
  • Recommendation: When testing a dev version, to preserve you original edits, you may want to follow one of these options:
    • turn off the saving of XMP edits in Preferences > Storage > XMP sidecar files
    • use copies of your images or a separate folder from your original images (this takes more room on your computer, but you can use XMP sidecar files if you desire)

January 16, 2026

This Post Has One Comment

  1. vim

    On MacOS
    Install the stable version in “Programs”. – not Programs, but Applications.

Leave a Reply