Start with the approved master
Choose the file the team currently treats as authoritative. If no one can identify it, stop and resolve that ownership question first. A similarity tool can compare files, but it cannot decide which version the organization approved.
Separate three kinds of duplication
Exact technical copies
Identical file bytes confirm a technical copy. Matching normalized previews can still hide different metadata, vector structure or editable content. Inspect the originals and delivery purpose before merging anything.
Close production variants
A dark-mode mark, one-color export, icon-only symbol or horizontal lockup can look very close while serving a legitimate use. Label its role instead of deleting it.
Stale or unexplained versions
Files that resemble the master but contain small undocumented geometry, typography or color changes need human review. Ask who created them, where they are used and whether they remain approved.
Use a decision rule
- Merge: same visual asset and no distinct delivery purpose.
- Review: related construction with unclear status or use.
- Keep: documented lockup, colorway, market or production role.
Export the decision list before moving or renaming files. That evidence makes cleanup reversible and gives collaborators a reason for every action.