
In digiKam, enter directory names rather than full paths in Ignored Directories. The names are case-sensitive and separated by semicolons. A full path that looks more precise can therefore fail to express the exclusion you intended.
Understand what the rule can match
The Collections Settings manual explicitly says that only directory names are excluded and paths are unsupported. This is a basename rule, not a path-pattern language.
Suppose a hypothetical collection contains ShootA/Rejects and ShootB/Rejects. The name Rejects does not express “only the first of those locations.” Before adding it, decide whether excluding that same directory name wherever encountered fits the collection arrangement.
Likewise, Rejects and rejects should not be assumed to match the same rule. Read the actual directory spelling. Do not rename the only archive copy simply to make an untested scanning rule appear to work.
Configure a controlled example
Open Settings → Configure digiKam → Collections and locate the ignored-directory setting. For an authorized test collection, enter the exact directory name. If entering several names, separate them with semicolons rather than inventing a wildcard or a full path.
Keep the test arrangement small enough to understand: one intentionally ignored directory and one ordinary control directory with distinguishable images. Do not use removal of real catalog entries as a substitute for checking discovery behavior.
Use the collection's normal scanning route to check subsequent discovery. Record which files are discovered and which remain unscanned. This is a proposed acceptance procedure; no collection scan was executed for this guide.
Check built-in exclusions too
The visible list does not include every directory digiKam already ignores. The manual provides a Currently ignored directories link for that built-in set, including dot-prefixed directories.
If an intended image is missing, check both your custom names and the built-in exclusions. A broad directory name can explain absent discoveries without implying that image files were deleted.
A scanning exclusion also should not be treated as a privacy boundary. It does not remove the directory from disk, revoke another application's access or prove that no earlier catalog record exists.
Know when the requested rule cannot be expressed
If the requirement is excluding one exact path while retaining another directory with the same basename, this field does not provide that contract. Reconsider the collection boundaries or storage arrangement on paper before moving real data. Preserve the archive and any existing database references during that planning.
After configuration, verify both the intended exclusion and a control discovery. A smaller scan count is insufficient evidence: the wrong directory could have been excluded.
When reviewing a storage arrangement, keep portable filenames and paths and approved-version organization separate from the scan rule. A folder's editorial role and its discovery policy should agree, but one does not automatically create the other.
Related tasks
- Why Does My Artwork Package Work Here but Fail on the Recipient’s File Path?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- digiKam Manual: Collections Settings: Collections have local/removable/network roots and identifiers. Update Path maintains collection mapping. Multiple mount paths do not authorize simultaneous clients on one database. Cloud placeholders are unsupported.
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: 85 LENS (Ngô Hoàng Auth) / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.