
Before removing digiKam duplicate results, decide how the Reference Image Selection Method chooses the item to keep. A folder-based preference can make the reference come from a selected album or from outside it. That keeper policy is separate from how broadly the duplicate search runs.
The Find Duplicates section explains reference selection, search restrictions and similarity results. A high similarity score does not decide which file belongs in the approved archive.
Assign the reference role before the search
Identify the album containing the preferred masters and explain why those versions are preferred. A folder's name is not proof that its files have the best resolution, metadata or accepted edit.
In a hypothetical consolidation, the working archive contains approved originals and a temporary import album contains similar copies. The intended policy is to keep the approved archive version while reviewing copies in the incoming set.
Use Prefer selected folder as reference when the selected album should supply the keeper, or Prefer other than selected folder as reference for the opposite relationship. Do not rely on an automatic newer-date preference if “newer” is not the keeper criterion.
Separate reference selection from search restriction
digiKam exposes both reference-image methods and restrictions on where to search. Inspect them independently.
A preferred reference album does not necessarily mean only that album is searched. Conversely, restricting the search can exclude the comparison set needed to find the duplicates you intended to review.
The suspected-duplicate guide illustrates why each tool's criteria matter. digiKam's fingerprint comparison and explicit reference method are not the same contract as Lightroom's import-time checks.
Keep the search small enough to inspect when establishing this policy. Expanding scope before verifying the first reference group can amplify a mistaken keeper choice.
Read the group around its reference image
Inspect the identified reference and its candidate duplicates. Compare actual file content, dimensions and useful metadata before any removal.
The reference designation is an operational role, not an independent certification that the file is the original camera capture. A processed derivative can be visually very similar while serving a different purpose.
The Photos duplicate-merge guide describes a different consolidation mechanism. Do not import its retention assumptions into digiKam's reference-and-removal workflow.
Make removal a separate approved action
For a proposed first-group check, identify the intended keeper and confirm that digiKam selected it as the reference. Then inspect what would be removed. Retain a recoverable archive before performing a real cleanup.
If the keeper is wrong, change the selection policy or search scope and rerun the small comparison. Do not manually delete a preferred master to force the result list to appear consistent.
This guide prepares and checks the keeper decision. It does not execute deletion, assert file-byte identity from visual similarity or promise that every candidate should be removed. The accepted result is an understandable group whose reference and removal candidates match the actual archive requirement.
Related tasks
- Why Does Lightroom Mark a Photo as a Suspected Duplicate?
- What Does Photos Keep When I Merge Detected Duplicates?
Sources and scope
- digiKam Manual: Similarity View: Similarity requires fingerprints, can protect a reference item and can use an external example image. 100% visual similarity is not a byte-identity test.
- digiKam Manual: Find Duplicates: Maintenance duplicate search has album restrictions and similarity-range controls; results still require a keeper decision.
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: Rumeyda Tutak / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.