
If digiKam displays a new tag but an external reader still finds the old value, check Use Lazy Synchronization. With that option enabled, a database change can be waiting for a later file write. Use Apply Pending Changes To Metadata before assessing the copied file.
Identify a pending write before editing again
Open Settings → Configure digiKam → Metadata and inspect the Behavior settings. The metadata manual describes immediate writing when lazy synchronization is disabled, and deferred writing through the status-bar pending-changes action or application shutdown when it is enabled.
Do not enter the same caption repeatedly because the external file has not caught up. First record the value visible in digiKam, the value actually embedded in the file and whether there are pending changes.
The relevant object may be an XMP sidecar instead of the image. Check the chosen write destination so an unchanged JPEG is not misdiagnosed when your policy intentionally writes only the companion.
Complete the pending-write stage
On an authorized sample, make one identifiable metadata change and use the status-bar Apply Pending Changes To Metadata action. Observe completion and any reported failure before copying the media into a handoff folder.
Then read the actual target file or companion from disk. Avoid using the same cached catalog panel as the only verification. If the receiving application reads a different representation, record that separate issue rather than concluding that the pending write never occurred.
For a hypothetical handoff, a rating may appear correctly in digiKam while the photographer copies the image before flushing the queue. The recipient consequently receives the older on-disk state. This is an illustrative failure sequence, not a report from an executed batch.
Distinguish queue timing from write capability
A flushed queue is not proof that every file type accepts the requested embedded field. Check errors, permissions, format support and the write policy if the value remains absent.
Do not make repeated changes to advanced namespace priorities to solve a simple timing problem. Nor should you enable RAW writes globally merely because a file is waiting. Decide the destination and capability before making that separate policy change.
The manual also warns that disabling modification-timestamp updates can affect external applications that rely on timestamps. A receiver's stale display can therefore require investigation beyond the pending-write action.
Accept the portable state
The handoff passes when the intended value exists in the agreed on-disk location and the recipient can read that location. Record an unverified field as unverified, even if digiKam's database already shows it.
When the question instead concerns choosing which conflicting value should win, use catalog-versus-file authority guidance. Lazy synchronization addresses when an intended write happens, not which competing description is correct.
For RAW delivery, preserve the image and required companions together. Closing the application may trigger pending writes, but a deliberate flush and file inspection makes the delivery state visible before the package leaves.
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.
Documentation-based guidance researched on 23 October 2026 (Asia/Shanghai), with proposed checks rather than reported application tests. RawPedia and digiKam manual pages were opened or returned readable official body text. ExifTool official pages were readable through public search; direct PDF/XMP tag-reference fetches returned HTTP 403. Verify installed-version controls, metadata representations and receiving-reader behavior. Decorative cover assets do not depict software or a test result.
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: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.