Lightroom & duplicate cleanup
Short answer: it can't corrupt your catalog, and it can't lose your edits — but it can make photos go missing until you put them back.
Your develop settings, crops, ratings, keywords and collections live inside the catalog file, not inside the photo. Moving or deleting a photo on disk doesn't touch any of that. What it does is break the catalog's pointer to the file, and Lightroom shows that photo as missing.
Whether that's a scare or a disaster depends entirely on one thing: whether the tool you used can put the file back exactly where it was.
Stated plainly up front: DuplicateFinder Pro does not read your Lightroom catalog. It skips Lightroom's working folders, but it has no idea which photos you've catalogued. What it has instead is a 24-hour quarantine and a restore that puts files back on their exact original path — which is why a mistake here is a one-click fix rather than lost work. The full detail on that gap ↓
Almost every worry about duplicate finders and Lightroom comes from one misunderstanding: people assume their editing work lives in the photo. It doesn't.
Lightroom is a non-destructive editor. It never rewrites your RAW file. Every adjustment you have ever made is a database row in the catalog, pointing at a file path on disk.
This is why the answer above is what it is. A duplicate finder operates on the right-hand column only. It has no way to alter the left-hand column, because it never opens the catalog file at all.
Lightroom keeps preview images of its own, so the first surprise is that nothing looks broken immediately. You'll still see thumbnails. What you get is a small exclamation-mark badge on the affected photos, and a message about the file being offline or missing when you try to develop or export one.
That state is entirely recoverable, and it's recoverable in two different ways:
The first is far less work, and it's the one that matters when choosing a tool. A duplicate finder that deletes leaves you only the second option — and only if the file went to the Recycle Bin and is still there.
Two things by design, and one honest gap.
Lightroom's .lrdata preview folders and .cache directories are excluded from scanning outright, alongside Windows, Program Files, the Recycle Bin and Adobe Premiere Pro's working folders. Preview pyramids contain many similar-looking files, which is exactly the kind of thing a duplicate scan should never be turned loose on. You can add your own exclusions on top and save them as reusable profiles.
Files identified as duplicates are moved to a quarantine folder on the same drive and recorded — not erased. For 24 hours they can be restored with one click, and restore returns each file to its exact original path. Because the path is identical, Lightroom reconnects by itself: no Find Missing Photo, no re-linking, no lost edits. After the hold, files stay in quarantine until you choose to empty it yourself, and restore is never locked behind a licence.
DuplicateFinder Pro has no knowledge of which photos are in your catalog and which aren't. It sees files on disk. If you quarantine a photo Lightroom has catalogued, Lightroom will show it as missing until you restore it — which is a one-click fix rather than lost work, but it is a real inconvenience and worth knowing before you start. Catalog awareness is a planned feature, not a shipped one, and this page will say so until that changes.
This sequence works with any duplicate finder, not just this one.
.lrcat somewhere safe. It takes seconds and it is the only irreplaceable file in the whole operation.
DuplicateFinder Pro finds duplicate photos, RAW files and videos across folders and across separate drives by comparing file contents rather than filenames — and quarantines them instead of deleting them.
Not by moving or deleting photos. The catalog is a separate database file that a duplicate finder never opens. What can happen is that photos show as missing because their file paths no longer resolve — a broken link, not a corrupted database.
Your develop settings stay in the catalog regardless. If you restore the file to its original path, the photo reconnects with every adjustment intact. If the file is permanently gone and you have no backup, the settings remain but have nothing to apply to.
That depends on your workflow, not on the tool. If the JPG is an export you can regenerate from the RAW, removing it is low-risk. If you catalogued both and built collections around the JPG, treat it as a catalogued photo like any other and check Lightroom before emptying quarantine.
No. Preview pyramids contain many near-identical images by design, and they're rebuildable working files rather than originals. DuplicateFinder Pro excludes .lrdata and .cache directories automatically for this reason.