Duplicates are the silent disk-space killer. Every backup, re-import and phone sync leaves copies behind, and it's common for 10–20% of a library to be redundant. The danger isn't finding duplicates — it's deleting the wrong ones. A safe cleanup workflow always reviews before deleting.
Copies hide in backup directories, import folders and Downloads. A scan that covers the whole library catches duplicates a folder-by-folder review misses.
An exact duplicate is the same image copied twice. A near-duplicate is two different shots of the same scene (a burst, a re-shoot). You can delete exact duplicates freely, but near-duplicates need review — one may be the sharper frame.
Never auto-delete. Look at matches side by side to confirm they're true duplicates. A good comparison view makes this fast — flip between frames and delete only what's clearly redundant.
Send unwanted files to the trash rather than deleting permanently. That way every decision is reversible, and you only lose data when you intentionally empty the trash.
Duplicates accumulate continuously. Run a cleanup scan every few months — it's a five-minute task that routinely reclaims gigabytes.
| Approach | Safety | Effort |
|---|---|---|
| Manual folder review | High | Hours per folder |
| Blind auto-delete | Low (risky) | None |
| Review-then-delete workflow | High | Minutes per library |
Lap's duplicate finder detects both exact and near-duplicate photos, shows matches side by side for review, and batch-moves unwanted files to the trash — nothing is permanently deleted until you empty it.
Duplicate photos are rarely a one-time accident; they are the output of repeated habits. Importing the same SD card twice, backup tools that copy instead of mirror, messaging apps that re-save every received image, and cloud sync conflicts each contribute their own strain of duplication. Cleaning once helps, but the habits refill the swamp.
The sustainable fix is catching duplicates at the door. A viewer with built-in detection flags exact copies the moment they enter your library, before they spread across folders and pick up different names. When you browse with Lap, duplicates surface with their locations listed, so you can confirm they are true copies — same bytes, same capture time — and delete with confidence.
Be careful with "similar photo" tools that only compare file size or dimensions; they miss cropped copies and flag legitimate bursts. Perceptual comparison plus EXIF matching is the reliable combination, and reviewing the candidates yourself — side by side, arrow keys at full speed — keeps the process honest and fast.
Deleting duplicates safely is a two-step ritual: quarantine first, delete later. Move flagged copies into a holding folder for a week instead of destroying them immediately; if nothing complains — no missing file errors, no broken album — empty the quarantine. This turns a scary purge into a boring procedure.
Backups interact with deduplication in one specific way: your backup software faithfully preserved every duplicate you ever made. After a cleanup, expect the next backup run to shrink noticeably, and consider versioning so the duplicates don't resurrect from an old snapshot when you restore something else.
Once clean, weekly maintenance is minutes: import, let the viewer flag repeats, delete, done. Duplicates then stay below one percent of the library instead of quietly doubling it, and storage budgets go toward new photos instead of redundant copies of old ones.
No. Cleanup moves files to the trash, so every deletion is reversible until you empty the trash yourself.
Yes — Lap shows matches side by side so you can confirm they're redundant before removing them.
Both — Lap detects exact duplicates and near-duplicate (visually similar) images.
Lap