
A surviving darktable export can sometimes carry the development history needed to recover a lost XMP. The current manual allows an exported image to be loaded like a sidecar when its format and metadata settings retained that history. You still need the original source image. A JPEG’s visible pixels alone do not reconstruct RAW processing parameters.
Establish which evidence survives
The history stack manual describes loading an exported image as a recovery source. It also states that loading a sidecar completely replaces the selected image’s current history and cannot be undone. Preserve the surviving files and present editing data before attempting that operation.
Make an inventory of the original capture, candidate exports, remaining sidecars and any approved reference. Identify which export actually corresponds to the desired edit. A newer export can contain a different treatment; a file processed by another service may no longer retain the needed metadata.
The RAW and sidecar handoff guide explains why the source and instructions are separate. This recovery route adds a less obvious carrier: processing instructions may survive inside an exported file even when the ordinary sidecar is missing.
Try the route in an isolated recovery copy
Imagine a hypothetical product photograph whose RAW survives but whose sidecar was lost. An earlier full-size export remains in a delivery archive. Do not begin by loading that file into the only current working image.
- Preserve the original capture and surviving metadata without renaming or replacing them.
- Prepare an isolated recovery copy using the installed application’s supported procedure. Ensure the intended source alone is selected.
- In the lighttable history stack module, use load sidecar file and select the candidate exported image, as described in the manual.
- Inspect whether recognizable processing modules and parameters have been recovered.
- Compare crop, tonal treatment and local corrections with the retained reference. Record any missing or incompatible component.
This is a proposed procedure, not a completed recovery test. The replacement warning matters even when an operation appears to be a read or import: its destination is the selected image’s history.
Test the promised editing scope
If parameters appear, choose one harmless change in the recovery copy and confirm that the expected processing relationship remains adjustable. Compare a fresh rendering with the earlier reference. Do not accept recovery solely because a thumbnail looks familiar or because one exposure control is present.
Use the approved-version record to distinguish a recovered candidate from the accepted master. Record the source file identity, donor export, installed darktable version and comparison result. Keep the donor export intact while resolving differences.
Recognize a genuine limit
Some formats or export settings omit the required history. A stripped social-media copy can preserve appearance while losing its recovery value. The export manual notes metadata caveats; therefore failure to recover from one file does not establish that every archived export is equally unsuitable.
If no processing history survives, look for a catalog or metadata backup rather than promising exact recovery from flattened pixels. The undo-versus-saved-state guide explains this boundary. Keep any newly reconstructed approximation labeled as a reconstruction. A recovery succeeds only to the extent that the required original adjustments and resulting appearance can actually be verified.
Related tasks
- Why Does My RAW Photo Lose Its Edits on Another Computer?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Why Can I Edit My Saved Layers but Not Undo Yesterday’s Steps?
Sources and scope
- darktable user manual: history: Supported exports may retain full history and be loaded like XMP; original source is required. Load sidecar replaces selected history irreversibly.
- darktable user manual: export: Export formats and settings have metadata inclusion caveats.
Based on the current online darktable manual reviewed October 31, 2026. Check the installed release. Examples and acceptance checks are proposed, not hands-on test results.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.