Find duplicate photos before you back up

Backup pain without dedup

A 500 GB photo library with 80 GB of byte-identical duplicates still backs up 500 GB every cycle. Removing exact copies first shrinks the working set. Incremental backups afterward only track real changes.

Workflow before Time Machine or NAS

Run dedup again after major imports (vacation, wedding).

• Scan library folder with DupShelf
• Review groups; set keepers
• Move duplicates to dupshelf-duplicate-images
• Verify in file manager; delete quarantine
• Run Time Machine, rsync, or cloud sync

Cloud backup (Backblaze, Drive, etc.)

Smaller upload footprint after dedup saves days on residential upload speed. Dedup locally first; cloud tools still back up what exists on disk.

3-2-1 rule still applies

Dedup is not a substitute for multiple backups. Do not delete the only copy of data. Keep a second drive until you confirm quarantine is safe to remove.

Photographer and studio archives

Client delivery folders often contain duplicate exports. Dedup before archiving to LTO or cold storage—years of savings compound.

Versioned backups and dedup order

If your backup tool keeps file versions, deduping the live library first prevents backing up the same duplicate into every version snapshot. For cloud backup with infinite retention, a smaller source folder also reduces re-upload churn when you replace files after cleanup.

Time Machine and local snapshots on Mac

Time Machine copies what is on disk at backup time. Eighty gigabytes of duplicate photos mean eighty extra gigabytes in history until you dedup and thin snapshots. Run DupShelf on your Pictures and Downloads folders, remove quarantine after review, then let the next backup run overnight on power. APFS local snapshots may still hold old blocks until macOS reclaims space—dedup is still worth it for future backup size. If you migrate to a new Mac, dedup before Migration Assistant to avoid carrying junk forward.

NAS and rsync home backups

Home NAS users often rsync entire user folders weekly. Duplicates inflate each run’s duration and disk wear. Dedup on the laptop source before rsync, or scan the NAS mirror folder during maintenance window. Document scan date on the NAS share so you know the mirror was cleaned. RAID is not backup—dedup does not replace a second offline copy of family photos.

Scheduling dedup before backup Sunday

Pick a recurring slot before automated backup runs. Monthly dedup keeps incremental backups smaller over time.

rsync and hard links

Power users using hard links should still verify DupShelf move behavior on their filesystem; CSV export is safer on exotic setups.

Summary and next steps

Backup strategy starts with what you feed the backup. Dedup is compression of reality—same bytes need not be stored six times in Time Machine snapshots. Run DupShelf before big life events import and after. Test restore from backup occasionally; dedup does not replace restore drills. Cloud backup users save upload days. Enterprise users reduce legal hold volume when duplicates were junk. Photographers shrink LTO writes. Always keep one untouched cold copy until quarantine review completes. Backup software is loyal; it backs up mistakes faithfully—give it lean inputs. Schedule dedup the night before your backup window, not after a failed backup alert when you are rushed. Compare backup size before and after in your tool’s report—many users see double-digit percentage drops on photo-heavy Macs. If you use multiple backup products, dedup once on the source folder they share rather than twice. Document excluded paths if legal requires certain raw folders untouched. Smaller backups restore faster. Dedup Sunday, backup Monday.