How to Find Duplicate Files on Mac

Why filename matching is not enough

Comparing names fails in both directions.

False positives. Invoice.pdf from two different suppliers is two different documents with the same name. A name-based check reports them as duplicates and invites you to delete one.

False negatives. IMG_4821.jpg and holiday-2019.jpg can be identical files. A name-based check sees nothing at all.

Only a content comparison answers the actual question, which is whether two files hold the same data.

Finding them with Finder

1. Open a folder in list view and sort by Name.
2. Look for files that share a name.
3. Select two candidates and press Space to preview them side by side.
4. Use Get Info to compare their sizes and modification dates.

This works for a handful of obvious cases. It does not scale, and it cannot find duplicates that were renamed.

Finding them with Neatwise

The Duplicate File Finder groups files by content and shows each group with the location and size of every copy. The result is a set of groups where every member is genuinely identical, which is what makes the decision simple.

It is worth running the Storage Analyzer first if you are not sure where to look. Duplicates cluster in a few predictable places, and the analyzer tells you which of them is large enough to bother with.

Why duplicates accumulate

• Importing twice. Photo libraries grow when an import runs over files that were already imported.
• Downloading again. The quickest way to get a file you cannot find is to download it a second time.
• Duplicating before editing. A copy is made so the original is preserved, and then both are kept.
• Restoring from backup. Restoring into a populated folder produces a second copy of everything in the backup.
• Cloud sync. Services that keep local copies can reintroduce files you removed locally.

Deciding which copy to keep

Inside a group the contents are identical, so the decision is about location. Keep the copy in the folder you will look in later, and remove the copies in staging areas.

Two cases need care:

• Application support files. Applications look for their data at specific paths. An identical copy elsewhere does not help the application find it, so removing the copy it expects breaks the application.
• Anything referenced by a link. Aliases, symlinks, scripts and other documents can point at a specific file. Removing that path breaks the reference silently.

When either applies, keep both. The space is recoverable later.

Preventing them

Duplicates come from habits rather than accidents. Checking before importing, finding a file instead of downloading it again, and restoring backups to a clean location removes most of them at the source. A periodic pass over Downloads and the photo library catches the rest.