
A successful JPEG metadata write does not establish that digiKam is configured to embed metadata in your RAW files. Inspect the separate RAW/DNG permissions and the ExifTool backend's format support. Prefer the intended sidecar policy when the workflow does not require modifying the RAW itself.
Separate destination, permission and capability
The digiKam metadata settings manual documents three distinct controls: delegating metadata writes to ExifTool, allowing DNG writes and allowing RAW writes where possible. The DNG and RAW features are disabled by default in the documented setup.
These settings do not make every RAW format writable. They also do not override a sidecar-only policy. Write down the actual objective first: embedded metadata in a supported RAW, metadata in a companion, or a rendered delivery copy.
If the deliverable is simply an edited appearance, embedding a caption is not a substitute for the RAW processing companions and rendered reference.
Inspect backend availability
Open Settings → Configure digiKam → Metadata → ExifTool Settings. Confirm that digiKam detects the binary and examine its reported read/write support for the relevant format.
The existence of an ExifTool executable is different from read/write support for a particular extension. Likewise, a readable field in an inspector is not automatically a writable field.
Return to Behavior and review the applicable RAW or DNG option only if embedded writing is genuinely required. Do not enable every checkbox in an attempt to force an unsupported file through.
Rehearse on a real format copy
Preserve an independent original and use a duplicate of the exact camera format for the proposed test. Choose one authorized field and note its original value.
Apply the change through digiKam and complete any pending synchronization. Inspect the actual RAW and any companion separately. Verify that the field reached the intended location, then open the image through the required RAW-processing route.
This is an acceptance plan, not a claim that a camera format or decoder was tested. A correct caption readback alone does not certify every MakerNote or application-specific structure in a rewritten RAW.
Interpret the failure precisely
If the backend is unavailable, address its configuration before changing metadata policy. If the backend reports no write support, use an appropriate companion route or another agreed deliverable. If digiKam is configured for sidecars only, inspect the sidecar rather than repeatedly trying to alter the RAW.
If a write fails despite documented support, retain the exact error and working-copy identity. Do not suppress warnings or replace the preserved original just to make a batch finish.
Resolve catalog-versus-disk conflicts after establishing that a supported write actually occurred. The distinction here is operational: selecting the intended destination, explicitly permitting the format and confirming the configured backend can express the required metadata.
Related tasks
- Why Does My RAW Photo Lose Its Edits on Another Computer?
- Lightroom Metadata Conflict: Keep the Disk or Catalog Version?
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: Rumeyda Tutak / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.