How do you find and remove duplicate photos in Lightroom Classic without deleting the wrong ones?
Quick Answer
Lightroom Classic 15.4.1 and later has a built-in duplicate finder: select All Photographs and open the Duplicates view, and Lightroom stacks each exact copy behind its original. It only catches byte-identical image data, so re-imported exports, edited JPEG copies and resized versions slip through. Back up the catalog first, then choose Remove, not Delete from Disk.
Nobody imports the same card twice on purpose, but after a few years of drive moves, phone imports and "just in case" re-imports, most catalogs carry a few hundred copies of something.
I build Lightroom Classic plugins, so I spend a lot of time inside the catalog. The key fact for a safe cleanup: Lightroom tracks a photo by its file path and its catalog record, not by what the picture looks like.
Does Lightroom Classic have a duplicate finder now?
Yes. Lightroom Classic 15.4 (June 2026) added automatic duplicate detection, and you should be on 15.4.1 or later to use it. Adobe pulled 15.4 because Delete Rejected Photos, run in the new Duplicates view, could delete photos that were not rejected; 15.4.1 fixed it.
To open it:
- Go to the Library module and click All Photographs in the Catalog panel. Duplicates are found across folders, so a single folder view would hide most of them.
- Show the toolbar if it is hidden (press T) and open the duplicate view from there.
- Let the scan finish. On a large catalog it takes a while, and you can keep working in the meantime.
Lightroom then puts each original at the top of a stack with its duplicates behind it. The header shows the detection status and how many originals, duplicates and hidden photos it found, and the toolbar has a Show Hidden Duplicates option. Right-click a stack and choose Expand Stack to see every copy.
Why does the built-in finder miss most real duplicates?
Because it compares image data, not pictures. Two files count as duplicates only when their image data is identical, whatever their metadata says. That is reliable for the same file imported twice from two folders, and blind to almost everything else.
Here is what it will not flag:
- Exports you re-imported. An exported JPEG is a new render of your edit. Different bytes, so no match with its RAW.
- RAW + JPEG pairs. The camera's JPEG and the RAW are two different files. If you did not tick "Treat JPEG files next to raw files as separate photos" in Preferences, Lightroom already pairs them; if you did, you have two records per shot that no byte compare will link.
- Resized or recompressed copies. The 2048px version you saved for a forum, or the copy a phone backup app recompressed.
- Burst near-matches. Twelve frames of one moment are culling work, not duplicates.
One thing it correctly ignores: virtual copies. A virtual copy is a second set of develop settings pointing at the same file, so there is nothing to duplicate. Deleting one never frees disk space.
How do you find near-duplicates and similar shots?
Stop new duplicates at the door
In the Import dialog's File Handling panel, tick Don't Import Suspected Duplicates. Lightroom treats a file as a suspected duplicate when its original filename, capture date and time, and file size match a photo already in the catalog. That is a different test from the Duplicates view.
Sort and filter by hand
In All Photographs, set the sort order to Capture Time. Copies of the same shot land side by side even when their filenames differ. Then open the Library Filter bar (press \), choose Metadata, and add columns for File Type and Camera. A JPEG from your camera body sitting next to its RAW, or a "Camera: unknown" file in the middle of a shoot, is usually a re-imported export or a stripped copy.
Use image similarity for the rest
Catching an edited JPEG of a RAW needs a tool that looks at the picture. Modern ones turn each photo into an embedding, a list of numbers describing its content (the CLIP-style approach), and compare those. Two versions of the same frame score close to 1.0 even at different sizes and with different edits.
I measured this while building a plugin that does the same kind of encoding: a 2560px smart preview scored a median 0.96 against its full-size original across an 80-photo sample. A byte compare calls those two files strangers, and that gap is what the built-in finder leaves behind.
Remove from catalog vs delete from disk: how do you clean up without losing edits?
Remove deletes the catalog record and leaves the file on your drive; Delete from Disk sends the file to the Trash or Recycle Bin as well. When you press Delete in the Library module, Lightroom asks which one you want. On a first cleanup, always pick Remove.
The bigger trap is which copy you keep. Your develop history, keywords, ratings, collections and publish history all live on the catalog record, not in the file. If you edited the copy and Lightroom put the untouched one on top of the stack, removing the "duplicate" throws away the work.
- Back up the catalog first. File > Back Up Catalog (my catalog backup guide covers where the copy goes). The catalog is the only place those edits exist unless you write XMP.
- Collect the duplicates in one place. Select them and add them to a collection called "Duplicates to review" before removing anything.
- Check each stack before you clear it. Look for the badge that says a photo has edits, keywords or collection membership. Keep the record that carries the work, not the one that happens to be first.
- Merge before you remove. If both copies carry something you want, copy the edits with Sync Settings and the keywords with Sync Metadata onto the keeper, then remove the other.
- Remove, wait a week, then delete from disk.
Watch out for published collections. If a duplicate you remove was published, the publish service will want to delete it from the destination on the next Publish. Check the collection before you press Publish.
Built-in finder vs Excire Search vs PhotoSweeper vs manual: which catches what?
Use the built-in finder first because it is free and safe; the others are for what it leaves behind.
| Method | What it catches | Cost | Works inside Lightroom Classic |
|---|---|---|---|
| Built-in Duplicates view (15.4.1+) | Byte-identical image data only, across folders | Included | Yes |
| Excire Search 2026 | Visually similar photos, plus search, faces and culling | $229 one-time | Yes (plugin, Lightroom Classic 14+) |
| PhotoSweeper | Exact and similar copies, including edited versions | Low one-time price, Mac App Store | No: a separate Mac app that reads the Lightroom catalog |
| Manual sort + filters | Whatever you spot by capture time, file type and camera | Free | Yes |
A few hundred copies from one messy migration? The built-in view plus an hour of sorting is enough. Years of exports re-imported next to their RAWs is where a similarity tool earns its price.
Prevention checklist for future imports
- Keep Don't Import Suspected Duplicates ticked in every import preset.
- Never import your export folder back into the catalog. Export to a folder outside the folders Lightroom watches.
- Use one catalog. Two catalogs on two machines are how the same card gets imported twice.
- Fix a missing folder with Find Missing Folder, never by re-importing it.
- Run the Duplicates view once after any big migration, while you still remember what you moved.
Frequently asked questions
Does Lightroom delete duplicate files automatically?
No. The Duplicates view only finds and stacks exact copies. Nothing is removed until you select photos and choose Remove or Delete from Disk yourself, so you can review every stack first.
Are virtual copies duplicates?
No. A virtual copy is a second set of develop settings on the same file, so it takes no extra disk space and the duplicate finder does not flag it. Deleting one only removes that version of the edit.
Why does Lightroom say "suspected duplicate" on import?
Because the incoming file has the same original filename, capture date and time, and file size as a photo already in the catalog. With Don't Import Suspected Duplicates ticked, Lightroom greys those files out in the Import dialog and skips them.
Can I find duplicates across two catalogs?
Not directly, since the finder works on one catalog. Merge them first with File > Import from Another Catalog, then run the Duplicates view on the merged catalog. Back up both catalogs before you merge.
Will removing duplicates break published collections?
It can. Removing a photo that was published queues it for deletion from that service on the next Publish. Check your published collections for the photos you removed before you press Publish.
Got a catalog cleanup question I did not cover? The contact form comes straight to me.