darktable on your phone.
A touch-friendly Android photo editor built on darktable's own processing engine.
Droidtable does not imitate darktable — it runs it. The original darktable processing modules render your RAW files on the phone, and your edits are stored in the same XMP sidecar files desktop darktable reads and writes. Start an edit on the go, finish it at your desk, or the other way round.
- 93original darktable modules in the engine
- 5.6.2darktable release the engine is pinned to
- XMPsidecars shared with desktop darktable
- GPL-3.0free and open source
Why Droidtable?
The real engine
No re-implementation of darktable's maths in another language. Droidtable builds libdarktable for Android without GTK and calls the unchanged processing code, so a module behaves the way it does on the desktop.
One edit, two devices
A RAW file opens together with its <name>.xmp sidecar. Saving writes
the same format desktop darktable reloads — history, module instances and masks
included. No export/import step, no proprietary catalogue.
Made for touch
A new Kotlin and Jetpack Compose interface designed for fingers instead of a mouse: large sliders, tap-to-type values, gestures on the preview and a layout that works on a phone first.
What you can do today
The app is under active development. The following already works in the development builds on a real Android phone:
Lighttable & Darkroom
- Browse a folder of RAW and JPEG files with thumbnails
- Open a photo with its existing desktop sidecar
- Fast, incremental preview while you drag a slider
- Histogram, waveform and vectorscope
- History panel with undo and redo
- Export of the developed image
- darktable's workflow setting: scene-referred (sigmoid, filmic, AgX) or display-referred
Editing tools
- Multiple instances of a module, each with its own label
- Drawn masks (circle, ellipse, path, brush, gradient) with a zoomable editor
- Mask overlay rendered by darktable itself
- External raster masks
- Tap any slider value to type an exact number
- Desktop-style curve graphs where a module needs them
Modules with a touch interface
Every module can render; these already have a dedicated control panel in the app. More follow with every release.
Base & tone
Color
Correct
Composition & effects
Desktop ↔ phone workflow
-
Copy or sync your RAW files and their
.xmpsidecars to the phone — any folder you can open with Android's file picker works. - Edit in Droidtable. Existing desktop edits are rendered by the same modules; you continue where you left off.
- Save. Droidtable writes the sidecar safely (a failed write never damages the old one) in darktable's own XMP format.
- Back on the desktop, darktable 5.6.1 or later reloads the sidecar and shows exactly the same history.
How it works
:engine processphoto.CR2 + photo.CR2.xmp — the desktop-compatible sidecarKeeping darktable's results
-
Image processing is never changed. The darktable changes only hide
desktop GUI code behind a build switch (
DARKTABLE_ENGINE_ONLY), split shared headers into core and GUI parts, and fix small differences of Android's C library and compiler. - Verified against desktop darktable. The engine-only build is bit-exact with the official desktop release on x86; on the phone's ARM CPU, renders are compared pixel by pixel within a measured tolerance policy.
-
Every change is public. The fork keeps one commit per change on top of
the darktable release tag, labelled
build:,engine:orandroid:. Each engine version is taggeddroidtable-5.6.2-dd.Nand published with its prebuilt package, licenses and corresponding source. - Releases, not nightlies. Droidtable follows darktable releases only. A new release is adopted by replaying the fork's commits onto it and re-running the full compatibility suite.
Status & roadmap
-
Desktop compatibility baselinePinned darktable 5.6.2, reference renders and sidecars produced by desktop darktable.
-
GTK-free engine with all 93 modulesBuilt without the desktop UI, bit-exact with the official desktop build.
-
Engine on AndroidCross-compiled for arm64 with the Android NDK, running inside the APK in its own process behind a Binder contract.
-
App shell & sidecar round-tripOpen files through the system picker, render previews and full-size images, edit and save XMPs that desktop darktable reloads.
-
Editor in progressModule panels, masks, histogram scopes, history and export are working. Next: parametric masks, before/after view, a generic panel for the remaining modules, "Open with" integration and tablet layouts.
-
Optimize & releaseSpeed and memory tuning, GPU acceleration after CPU correctness, automated round-trip tests and a first public release.
Requirements (current development builds)
- Android 15 (API level 35) or later.
- 64-bit ARM device (
arm64-v8a). - darktable 5.6.1 or later on the desktop to exchange sidecars.
- RAW formats supported by darktable's 5.6.2 decoders; JPEG and other common formats as well.
FAQ
Is Droidtable an official darktable project?
No. Droidtable is an independent project that builds on darktable's source code under its GPL license. It is not affiliated with or endorsed by the darktable team. Please report Droidtable problems to Droidtable, not to darktable.
Does it give exactly the same result as desktop darktable?
It runs the same processing code. On the same CPU architecture the result is bit-exact; between a desktop x86 CPU and a phone's ARM CPU tiny floating-point differences remain, which are measured and kept within a documented tolerance.
Can I use every darktable module?
The engine contains all 93 processing modules, so every edit made on the desktop is rendered. Editing on the phone needs a touch panel for each module; the list above grows with each release.
Does it have a photo library database like darktable?
No catalogue is needed: the XMP sidecar next to the image is the source of truth, which is what makes moving between desktop and phone simple.
Is GPU (OpenCL) processing used?
Not yet. Correct CPU results come first; GPU acceleration is part of the optimization phase.
Where is the source code?
All darktable changes and the engine packages with their corresponding source are public in the droidtable/darktable fork. The app source will be published together with the first app release.
Links
License
Droidtable's own source code is licensed under GPL-3.0-or-later. darktable is licensed under the GPL as well; the corresponding source — including all changes to darktable — is public in the droidtable/darktable fork. Third-party libraries shipped with the engine keep their own licenses, which are included in each engine package.