
In digiKam Time Adjust, Update only existing timestamps does not select every date field automatically. It prevents creation of selected fields that are absent. You must still choose the timestamp destinations you intend to change.
The Time Adjust manual makes this distinction explicit. A date field left unchanged may reflect target selection rather than a failed offset calculation.
Trace source, calculation and destination separately
Open Item > Adjust Time & Date for the selected images. The tool separates Timestamp Used, Timestamp Adjustments and Timestamp Updated.
For a hypothetical camera-clock correction, an existing EXIF original date might supply the source, an Add or Subtract operation supply the intended offset, and selected EXIF/XMP entries receive the result. A filesystem modification date is another possible destination, not the same field under another label.
The family-scan date guide explains why a digitization date and a depicted event date should not be conflated. Do not choose a source merely because it is the first timestamp available.
Select destinations before applying the existence restriction
Inspect the Timestamp Updated group and mark the entries required by the job. Then choose whether missing selected entries should be created or excluded.
The difference can be expressed without an arbitrary date example:
| Destination state | Selected, existing-only enabled | Not selected |
|---|---|---|
| Field already exists | Eligible for the chosen update | Unchanged |
| Field is absent | Not created by that policy | Unchanged |
The table describes the documented scope, not an actual file test. It explains why an unchecked destination can remain wrong even while the existing-only box is enabled.
Check the original clock assumption
Confirm the calculation against a recognizable reference before applying it to the full group. The tool offers a clock-photo difference helper, but the reference itself still needs a valid relationship to the capture.
For location work, the GPX time-offset guide explains why aligning a tracklog is different from rewriting camera metadata. Decide which operation the job actually requires.
Do not rewrite every date merely to make a map appear plausible. Capture time, digitization, metadata modification and file modification can legitimately describe different events.
Inspect the target fields after the change
Use a disposable copy for a proposed check. Record one existing selected field, one absent selected field and one unselected field before applying the operation. Reread those same fields afterward.
This makes target selection and creation policy observable. Looking only at the date displayed in digiKam's main view may conceal a difference between database and file metadata.
If the selected existing fields remain unchanged, inspect the source and adjustment operation next. If unselected fields change through another synchronization process, investigate that route separately. The existence checkbox is not a global guarantee that every application leaves all other timestamps untouched.
Related tasks
- How Do I Date Scanned Family Photos When Every File Says Today?
- Lightroom GPX Auto-Tagging Misses Photos: Check the Tracklog Time Offset
Sources and scope
- digiKam Manual: Time Adjust: The clock-photo calculator can determine an offset. Updating existing tags still requires target fields to be selected; database and file timestamps are different targets.
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.