
In digiKam, Read from sidecar files is not simply an extra place to look for missing fields. The manual says enabling it makes digiKam read the sidecar and ignore embedded metadata. A tag can therefore be present inside the image yet absent from the values imported through that setting.
Check the Sidecars tab under Settings > Configure digiKam > Metadata. The official Metadata Settings documentation states the read behavior separately from the available write destinations.
Make a two-resource comparison
Identify the actual image and its associated XMP file. Record the value of one disputed field in each resource without first saving another change over either.
For a hypothetical archive item, the embedded caption might describe the original scan while the sidecar holds a revised catalog caption. Neither source becomes authoritative simply because its timestamp is newer.
The disk-versus-catalog conflict guide explains why two versions of metadata need an explicit decision. This digiKam problem has an earlier boundary: the read configuration determines which resource supplies the values before deciding how to reconcile them.
Inspect read policy independently of write policy
Review whether Read from sidecar files is enabled. Then inspect the selected write mode separately: sidecar only, item and sidecar, or sidecar for read-only items.
Those choices do not answer the same question. A sidecar-only write policy does not establish that the desired embedded value was read first. Likewise, reading a sidecar does not prove that a later save updated the image itself.
Do not toggle several policies and resave the archive as one experiment. That can replace the evidence needed to determine which source originally contained the disputed value.
Confirm the correct companion file
Check the actual sidecar naming convention configured in the application and expected by the other tool. digiKam documents both extension-inclusive and compatibility-style XMP naming.
A file with the right project name in another folder is not automatically the associated sidecar. Use a copied image-sidecar pair for a proposed read check, retaining both originals.
The RAW-sidecar handoff guide covers a related dependency. Here, the acceptance question is specifically which metadata resource digiKam reads, rather than whether the recipient received enough processing instructions to reproduce an edit.
Accept a deliberate source of truth
After selecting the intended read policy, inspect the disputed field in digiKam and compare it with the resource you meant to use. Include a second field that differs between the image and sidecar so the result is not explained by an accidentally identical caption.
If a value remains absent, investigate the association and relevant metadata field mapping. Do not conclude that the embedded data was deleted merely because it was ignored during a read.
Only after that comparison should you plan any write or synchronization. This procedure does not perform a metadata merge and does not promise that conflicting image and sidecar fields are automatically combined.
Related tasks
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
- Why Does My RAW Photo Lose Its Edits on Another Computer?
Sources and scope
- digiKam Manual: Metadata Settings: Lazy synchronization defers file writes. Reading sidecars can ignore embedded metadata. Sidecar naming, extra extensions, ExifTool backend and RAW-write settings are distinct options.
The official digiKam 9.2.0 manual was opened on October 23, 2026 (Asia/Shanghai). These are documentation-based instructions with proposed examples and acceptance checks, not hands-on test results. Check controls and file associations against the installed application version.
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: Mariya Eskina / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.