The safe way to remove duplicate photos on a Mac is to treat deletion as the last step, not the first. Find candidates, review each group, keep the copy you want, and move the rest to the Trash where you can still undo it.
Bulk-deleting everything a tool labels as a duplicate is how people lose photos. This guide covers a review-first workflow for folders, the parts that need human judgment, and how to stop duplicates from coming back.
Why duplicates accumulate
Duplicates rarely come from one mistake. They build up through normal use:
- The same card or phone is imported twice, once by the camera app and once by a folder copy.
- Photos are exported from an editor and saved next to the original.
- Backups are restored into a folder that already has the files.
- Family members copy the same event into two places.
- Old drives are merged without checking for overlap.
The files may have different names, different folder paths, and different modification dates. That is why file name matching alone is unreliable.
Three ways to handle duplicates on macOS
| Approach | Scope | Strength | Limit |
|---|---|---|---|
| Photos app Duplicates album | Items imported into the Photos library | Built in, simple review | Does not cover arbitrary Finder folders |
| Manual review in Finder | Any folder | Full control | Slow, easy to make a mistake at scale |
| Phoaly workbench | Folders you add | Preview, journal, and undo before deletion | Runs on macOS 13+ Apple silicon |
The right choice depends on where the photos live. If your archive is a folder tree, a folder-based tool will see more than the Photos library ever will.
Rule 1: review before you delete
A duplicate list is evidence, not a decision. Before removing anything:
- Open both files and compare the actual image.
- Check resolution, file size, and format.
- Check the folder path and the file name.
- Check the capture date and camera metadata.
Two files can look identical in a thumbnail and differ in resolution, color profile, or embedded metadata. The larger file is not always the better one, and the newer file is not always the copy you want.
Rule 2: decide which copy to keep
A simple policy works for most archives:
- Keep the copy in the folder structure you intend to maintain.
- If both are in valid structures, keep the higher-resolution or less compressed version.
- If one is an export and one is an original, keep the original.
- If you cannot tell, keep both and move the decision to a review folder.
The goal is not the smallest possible library. It is a library where every remaining file has a reason to exist.
Rule 3: understand the folder relationship
Deleting a duplicate inside one folder is easy. Deleting across folders is a structure decision.
- Two copies in the same shoot: keep one, remove the other.
- One copy in a working folder and one in an archive: decide which folder is canonical.
- One copy on an internal drive and one on a backup: the backup is not a duplicate to remove in place. Leave it alone.
Write the rule down before you start. It keeps a large clean-up consistent.
Step by step with Phoaly
Phoaly includes dedupe in the same workbench used for organizing, so the result is a plan you review before anything changes.
- Add the folders you want to compare. Adding a folder builds an index and leaves the originals in place.
- Open the workbench and run the dedupe operation. You get a plan, not an immediate deletion.
- Review the preview group by group. Keep the copy that matches your policy and mark the rest for removal.
- Confirm the plan. The session is written to the journal, and removals go to the system Trash.
- Spot-check in Finder. If something is wrong, undo from the journal before starting another pass.
Nothing in your folders changes until you confirm. Scanning and previewing are read-only.
Exact duplicates and near-duplicates are different problems
An exact duplicate is the same file content in two places. A near-duplicate is a burst frame, a crop, an edit, or the same scene shot twice.
Near-duplicates need human judgment. A burst often has one frame where nobody blinked, and an edit may be the version you actually use. Review those in the cull view instead of treating them as duplicates:
- Keep, maybe, and reject each have a key.
- Marking advances to the next photo.
- Deletes go to the Trash and can be undone.
Culling is a better tool for near-duplicates because the decision is about which frame is best, not which file is redundant.
After the clean-up: prevent the next round
- Give every import one inbox folder. Sort from there, not from Downloads, Desktop, and three drives.
- Do not import the same card twice. Check the folder before copying.
- Keep exports in a separate folder from originals.
- Restore backups to a new folder, then compare, instead of merging into the live archive.
- Rebuild the index after large external changes so the app and Finder agree.
Frequently asked questions
Will Phoaly delete files without asking?
No. Dedupe runs in the workbench and produces a preview. Files change only when you confirm the plan. Deletes go to the system Trash and the session can be undone from its journal.
Does it find duplicates across different drives?
It compares the folders you add to the app. If both drives are connected and added, they are in scope. If a drive is disconnected, its place is kept in the sidebar but its files are not available to compare.
Can I recover a photo after deleting it?
Deleted files go to the system Trash, so you can restore them there until the Trash is emptied. Inside Phoaly, the session can be undone from the journal.
Should I delete the copy with the smaller file size?
Not automatically. File size can differ because of compression, editing, or metadata. Check resolution and format first, and keep the original when one file is an export.