Overview of Duplicate Photos in macOS Photos
Duplicate photos in macOS Photos can accumulate from repeated imports, backups, file transfers, and app syncing. This guide explains how macOS Photos defines duplicates, how they appear in Library and Albums views, and safe ways to identify and remove them without losing originals or breaking album references. The steps below focus on current public macOS versions (macOS Sonoma and earlier) and Photos app behavior that is stable across releases, making this an evergreen approach to managing duplicates.
What Counts as a Duplicate Photo
Technical definition by checksum comparison
macOS Photos does not rely only on file name or date created; it uses a checksum comparison (essentially a cryptographic hash) to determine whether two items contain identical data. If the checksums match and certain metadata aligns, Photos treats them as duplicates in its UI. This approach is robust for exact matches, including re-saved JPEGs that are byte-for-byte identical, or copies of files moved between external drives and your internal drive.
What Photos considers duplicates vs similar
- Duplicate: Same checksum and closely matching metadata, shown as a stacked badge with a number indicating how many copies exist.
- Similar: Same moment but different edits, different timestamps, or minor re-encoding; these are not flagged automatically as duplicates and must be managed manually.
Keep in mind that Photos only detects duplicates within a single library or within shared albums where local caching is enabled. It does not automatically compare across multiple libraries or iCloud Photos unless they are merged into one library or you use third-party tools designed for cross-library analysis.
Before You Start: Safety and Backups
- Ensure Photos library is regularly backed up with Time Machine or an alternative backup solution that captures the library file and related metadata.
- Verify that important moments are not only in Photos but also stored elsewhere (e.g., cloud albums, export copies) if they are irreplaceable.
- Check storage and performance: large duplicate removal operations can temporarily increase storage usage during processing.
How macOS Photos Groups Duplicates
When Photos detects duplicates, it uses a compact inline stack to show multiple items sharing the same checksum. You can expand the stack to preview each copy, and any item within the stack can be deleted independently without affecting the others. This design makes it straightforward to discard extras while preserving your preferred version. The default stack behavior is to keep the most recent or highest-quality version at the top of the group, depending on how the originals were ingested and whether edits were applied.
How to Delete Duplicate Photos in macOS Photos
Identify duplicates in the Moments or Years view
Open Photos and browse to Moments or Years, where stacked duplicates often appear automatically. You can also use the Search field and type keywords like “duplicate” or use filters to narrow by Camera, Kind, or Date to help locate candidates. For greater precision, switch to the Albums tab and create or locate an album such as “Duplicates” if your version supports third-party smart albums that use content hash rules; note this feature may depend on the Photos version and macOS integration.
Preview and confirm before deletion
Click a stacked duplicate group to expand it, then use the preview area to compare copies side by side. Select individual thumbnails to view full-size previews; this helps you verify that a seemingly duplicate file is not a different shot taken at the same time with a similar composition. Confirm which version you want to keep and which copies are safe to remove.
Delete individual duplicates from the stack
With the stack expanded, select one or more items and press Delete (or choose File > Delete [number] Photos). In the dialog that appears, choose Delete from Library; this removes the selected item(s) from the library but does not delete the original file from disk unless the file was imported directly as a managed file and the system confirms it is safe to remove. The remaining duplicate(s) in the stack stay in your library, preserving your intended keeps.
Mass removal considerations
If duplicates span stacks or libraries
For large-scale cleanup across multiple libraries or external drives, consider exporting a contact sheet of duplicates for manual review, or use a purpose-built duplicate finder that integrates with Photos and can generate a deletion list you audit before removal. Always review any batch operation summary before confirming, and run a second pass after initial cleanup to catch overlooked duplicates that were not grouped in the first pass.
Verification After Deletion
After you delete duplicates, use Photos storage management to confirm space has been reclaimed and that important albums still contain the expected keeps. Check key Moments and Albums to ensure no unintended removal occurred. If you rely on iCloud Photos, allow sufficient sync time and verify that devices show the correct, cleaned state. Note that file system free space may not immediately reflect changes on all macOS configurations due to journaling and snapshot behavior; eventual consistency at the system level is normal.
Common Pitfalls and Limitations
Photos may not detect duplicates when file formats differ (for example, a JPEG original and a re-encoded HEIC version of the same image) even if the visual content is identical, because the checksums differ. Metadata changes such as date/time edits, ratings, or caption updates do not alter the checksum but may affect how stacks are presented. Photos also does not automatically identify duplicates across separate libraries; merging libraries or using external tools is required for cross-library duplicate matching. Finally, be cautious with smart albums or rules that might incorrectly flag non-duplicates if they rely only on filenames or dates without verifying content hash.
Alternatives and Supplementary Tools
If you need to find duplicates across multiple libraries, external drives, or cloud services, third-party duplicate photo finder apps can scan at the filesystem level and produce a reviewable report before deletion. These tools often include options to compare by filename, date, file size, and perceptual hash to catch near-duplicates that exact checksum comparison would miss. Whichever method you choose, perform a trial pass on a small set, verify outcomes, and back up the library before running large deletions.
Summary of Key Actions
| Action | Verified Detail | Source Type |
|---|---|---|
| Use Checksum-Based Detection | Photos uses checksum comparison to flag exact duplicates | Platform behavior (documented) |
| Expand Stacks to Review Copies | Stacks group duplicates; each item can be previewed and deleted individually | Interface behavior (documented) |
| Delete with “Delete from Library” | Removes item from Photos library; managed imports may also remove from disk after safe removal checks | Feature behavior (documented) |
| Back Up Library Before Bulk Deletion | Back up via Time Machine or copy library file to another location | Best practice |
| Re-check Storage and Albums Post-Cleanup | Verify space reclaimed and that keeps remain in albums | Verification step |
When to Use Third-Party Tools
Consider third-party duplicate finders when you manage multiple libraries, work across external drives, or need perceptual hash matching for visually similar but not byte-identical images. Evaluate tools based on transparency about algorithms, auditability of proposed deletions, and reputation for data safety. Always run such tools on a copied library when possible and keep your original library intact until you have reviewed and validated the proposed cleanup list.