
A regular digiKam tag with a person's name is not the same object as a confirmed face tag. The Assign Tag context-menu command tags the whole image. To supply a named face reference, use the detected face's Who Is This? field in People View and confirm the assignment.
The official People View, Face Tagging section explicitly distinguishes those two routes. Renaming the ordinary tag to look like a person does not change its role.
Inspect a face region rather than the album thumbnail
Open People View and inspect the Unknown faces. Each entry represents a detected face region, and an image containing several faces can contribute several face thumbnails.
For a hypothetical group photograph, the image can correctly carry the family surname as a general subject tag while still lacking an association between one detected face and one individual. Those are useful but different descriptions.
Open the full image when needed to confirm which face region the thumbnail represents. Do not assign the whole group to one person merely because the small crop looks similar.
The Lightroom face-stack review guide addresses reviewing grouped suggestions. This digiKam distinction concerns whether the assignment creates face-region training data at all.
Confirm the intended person on the detected face
In the Unknown view, enter or select the person's name through Who Is This?. Use Confirm after checking the face.
The documented result is a named face association in the database and movement of the face entry out of Unknown. Check that change on the intended region rather than merely searching for a similarly named general tag.
For a proposed check, use one clearly identified face and inspect it again in the full photograph. Avoid confirming a large ambiguous selection just to make the Unknown count smaller.
Correct a confirmed name through the face controls
The manual explains that confirmed face tags normally show the name without the earlier buttons. Double-click the name to make the editing/removal controls reappear when a correction is needed.
That is a face-association correction, not a reason to merge every similarly named person group. The Photos People merge-versus-name-correction guide illustrates why an identity error and a duplicate grouping need different decisions.
Keep a correct ordinary image tag if it serves a separate catalog purpose. Removing it is not required merely because the face was previously unnamed.
Evaluate recognition separately
A confirmed reference supports recognition, but does not prove that every future suggestion is correct. Review candidate matches before confirming them, especially in group scenes or difficult captures.
If no face region exists, ordinary tag assignment does not replace detection or a manually added face region. If a region exists and is confirmed but later matching is poor, investigate recognition separately rather than assigning the same whole-image tag again.
The useful acceptance condition is a verified person-to-region association. A name somewhere in the tag tree is insufficient evidence of that object.
Related tasks
- Review a Lightroom Face Stack Before Naming Everyone in It
- Should I Merge Two Photos People Groups or Correct Their Names?
Sources and scope
- digiKam Manual: People View: Face detection, recognition, model availability and confirmation are distinct stages. Assigning an ordinary tag does not create the same training evidence as confirming a face.
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: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.