darktable Problems & Issues

Real user-reported problems, complaints, and limitations for darktable. Based on analysis of 13 signals.

Overall score: 64/100

Issues by Category

usability4 issues

darktable is too complicated: steep learning curve and cluttered interface

Reviewers and switchers repeatedly describe a cluttered interface with many modules named differently from Lightroom, making basic edits hard to find. Beginners often give up before learning the scene-referred workflow.

Frequency: 9%Sentiment: -0.60/1004 sources
Impact
7

darktable not supported on my Mac or won't open on macOS

Mac users report the app bouncing in the Dock, 'not supported on this Mac' errors and Gatekeeper warnings. Official builds are Apple silicon only (no Intel Mac builds) and require macOS 13.5 or newer.

Frequency: 6%Sentiment: -0.50/1004 sources
Impact
7

Moving from Lightroom to darktable: edits, catalog and look don't carry over

Users switching from Adobe find no catalog import, different default colors and a different tone-mapping approach (filmic, AgX, sigmoid), so old edits cannot be recreated one to one.

Frequency: 6%Sentiment: -0.50/1003 sources
Impact
6

darktable 5.6 AI features are optional and build-dependent

5.6 added optional AI (neural restore, object masks) that must be enabled at build time with -DUSE_AI=ON, and the Flatpak does not include AI. Users expecting AI out of the box can be disappointed.

Frequency: 4%Sentiment: -0.20/1003 sources
Impact
4
reliability4 issues

darktable crashes on import

Threads describe crashes or hangs when importing, often caused by one corrupted or unsupported RAW, a camera-card import path, or thumbnail generation. Importing folder by folder and capturing a debug log is the standard advice.

Frequency: 7%Sentiment: -0.70/1004 sources
Impact
8

darktable 'database is locked' error and won't open

A crash or power loss can leave data.db.lock / library.db.lock files so darktable refuses to start; corrupted databases are also reported. Restoring a snapshot or deleting stale locks fixes most cases.

Frequency: 6%Sentiment: -0.60/1004 sources
Impact
7

darktable export fails or 'could not export'

Export errors have been traced to folder permissions, metadata writing (Exiv2) failures, and format-specific limits such as no selective metadata for AVIF, EXR, JPEG XL and XCF in 5.4.

Frequency: 5%Sentiment: -0.50/1003 sources
Impact
6

Upgrading darktable breaks library compatibility

Libraries and settings updated by 5.6 are not compatible with 5.4, so downgrading is not possible without a backup. Users report surprises after upgrading.

Frequency: 4%Sentiment: -0.50/1003 sources
Impact
6
performance3 issues

darktable OpenCL not working or black image

GPU acceleration problems are a recurring theme: black darkroom or export images, driver timeouts and crashes on Intel Arc, AMD and some macOS setups. darktable 5.6.2 fixed OpenCL being disabled on Intel Compute Runtime 26.35.

Frequency: 8%Sentiment: -0.70/1005 sources
Impact
8

Why is darktable so slow to start?

Forum users report startup from seconds to very long waits, usually from huge libraries, network (SMB) storage, a Flatpak build or the 'look for updated XMP files on startup' option. Fixes exist but are not obvious.

Frequency: 7%Sentiment: -0.60/1004 sources
Impact
7

darktable gets slow in darkroom with many modules or large libraries

Users report slow switching between lighttable and darkroom, memory exhaustion and system freezes on large files, heavy modules and 5.x upgrades, especially with little RAM or without working OpenCL.

Frequency: 7%Sentiment: -0.60/1003 sources
Impact
7
support1 issue

No official support: help only from the volunteer forum

There is no company or support desk. Help comes from pixls.us, GitHub issues and Reddit; documentation for new releases lags (5.4 docs were incomplete at release). Answers are good but not guaranteed.

Frequency: 6%Sentiment: -0.40/1003 sources
Impact
5
integrations1 issue

Unsupported or newly released camera RAW files

New cameras are supported only after the volunteer team adds them via rawspeed/libraw, so very new bodies may not open or may lack profiles until a release or nightly build.

Frequency: 5%Sentiment: -0.40/1003 sources
Impact
6

Regret Patterns

Common reasons users regret choosing darktable.

Gave up after the learning curve

Users install darktable expecting Lightroom-like simplicity and abandon it after struggling with modules and color workflow.

Frequency: 8%First week

Lost time to GPU/OpenCL troubleshooting

Black images, crashes or slowness force users into driver debugging and disabling OpenCL.

Frequency: 6%First weeks

Library too big for comfortable use

Large libraries on slow or network storage make startup and thumbnails slow.

Frequency: 5%After thousands of images

Upgraded and could not roll back

A major version updates the library, making older versions unable to read it.

Frequency: 4%After upgrading

Missed cloud sync and mobile editing

Photographers who work across devices find nothing like Lightroom mobile.

Frequency: 4%After a few months

When darktable Breaks Down

Specific scenarios where darktable fails or underperforms.

Using a very new camera

RAW files may not open until the camera is supported in a release or nightly build.

Intel Arc or new Intel Compute Runtime drivers

OpenCL can be disabled or crash; 5.6.2 fixed one Intel runtime case.

Raw files on an SMB network drive

Startup and thumbnails become slow.

Power loss or crash with database open

Stale lock files block the next launch.

Intel Mac or old macOS

No official build; macOS must be 13.5 or newer.