darktable
An open-source RAW photography workflow and asset manager for non-destructive editing, cataloging, color-managed export and multi-platform photo projects.
What darktable is useful for
darktable covers RAW import, cataloging, rating, filtering, non-destructive adjustments, versioning and batch export. The original files, library database, edit history, presets and preview cache have different roles. A reliable photography workflow backs up the source images and the database rather than keeping only exported JPEGs.
Color and migration boundaries
Export results depend on input and output color space, display configuration, format, size, quality and metadata settings. When moving to another computer, preserve the originals, database, configuration and presets, then verify paths and sample exports before processing the full library.
Maintenance note
This page reviews darktable 5.6.0, RAW workflow, photo library management, non-destructive modules, database backup, cache behavior, color management and export verification. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave darktable to this cloud drive
Baidu Netdisk
Save darktable to this cloud drive
darktable 5.6.0 installation and RAW workflow guide
Start with a small RAW sample, create the photo library and a backup, then complete import, rating, non-destructive adjustments, versioning and a checked export.
Before you start
- Prepare a copy of several RAW images, a library directory and enough cache space.
- Plan database, configuration, preset and export backups separately from the original photos.
- Decide whether the output is for a screen, print or web delivery and choose the target color space and size.
Installation steps
- 01
Install the matching architecture
Choose the Windows, macOS or Linux build, then verify the photo library path, database location and cache limit on first launch.
- 02
Import a test set
Validate copy, reference, metadata and thumbnail behavior with a small sample, and confirm that file paths and database records agree.
- 03
Back up the library and configuration
Save the database, configuration, presets and important styles before working on the full collection so the workflow can be restored.
Quick start
- 01
Filter with tags and ratings
Organize by date, project and subject, then use ratings, color labels and reject status to create a manageable selection.
- 02
Edit non-destructively
Work through exposure, white balance, tone, detail and lens correction while preserving the history stack and creating versions for different outputs.
- 03
Export and inspect a sample
Set format, color space, dimensions, quality and metadata, export a small group and compare skin tones, sharpness, filenames and metadata before batch export.
Usage tips
- The database stores selection and edit history, while the cache mainly accelerates previews; back up both the database and configuration.
- Module order, presets and plugins influence the result, so validate a batch on representative images first.
- Clearing a cache is different from deleting originals or database records; confirm the selected operation before cleanup.
Troubleshooting and uninstall
Why are photos shown as offline?
Check whether the source directory moved, the volume is mounted and the database path is valid; restore the original path or use a controlled relocation before rebuilding thumbnails.
Why does the export color differ from the preview?
Compare display profile, input and output color space, export format and viewer support with the same sample image in the target environment.
- Back up the complete photo projectPreserve originals, database, configuration, presets, styles and exports, and record directory mappings and version information.
- Uninstall and review cachesRemove darktable through the operating system, clear the cache only after confirming the original files and database backup are safe.
Frequently asked questions
Is darktable a pixel-compositing editor?
It is primarily a RAW workflow and asset manager with non-destructive modules. Use a dedicated raster compositor when layers and pixel-level compositing are the main task.
Is a JPEG export enough to back up a darktable project?
No. The editable workflow also depends on the RAW originals, database, configuration, presets and history. Keep those items in an independent backup.
Can the darktable cache be deleted safely?
The cache can usually be rebuilt, but confirm the operation is targeting previews rather than originals, database records or export files.