One of the things Lightroom is supposed to do well is protect us from ourselves.
When you import photos, Lightroom has that comforting checkbox: “Don’t Import Suspected Duplicates.” In theory, if an image already exists in the catalog, Lightroom should recognize it and skip it.
In theory.
Recently, I ran into a situation where that safety net completely failed—and it failed in a big way.
The Project Context Matters
This wasn’t a casual shoot or a small catalog.
I’m currently organizing and cleaning up a photographer’s archive spanning more than 40 years. That means:
- Multiple Lightroom catalog moves over time
- Original files now living primarily on a NAS
- Original SSD drives are still kept as an additional layer of backup
- A second full copy of the files
- Cloud storage through PhotoShelter
In other words: the files are safe, redundant, and well cared for—but the catalog has been through some mileage.
The Problem: “These Files Don’t Exist” (Except They Do)
I inserted several memory cards containing thousands of images. These were cards I knew had already been ingested at some point in the past.
Yet Lightroom happily showed them as new files, ready to import.
No duplicate warnings.
No greyed-out thumbnails.
Nothing.
If I had trusted Lightroom blindly, I would have created thousands of duplicates across decades of work—exactly the kind of mess this project is trying to prevent.
Why This Was a Red Flag
Lightroom doesn’t check duplicates by filename alone. It uses a combination of metadata, capture time, file size, and internal catalog references.
When Lightroom suddenly “forgets” that files already exist, it’s often a sign that the catalog itself is starting to lose its internal efficiency—not that the files are missing.
Given that this catalog had been:
- Moved between systems
- Reconnected to storage multiple times
- Grown very large over many years
…I suspected a catalog health issue, not user error.
The Fix: Optimize the Catalog
Before doing anything drastic, I tried the simplest maintenance step that often gets ignored:
File → Optimize Catalog
After the optimization was completed, I tried the import again.
This time?
Lightroom correctly recognized the existing images and blocked the duplicates.
Problem solved.
Why Optimizing the Catalog Matters More Than You Think
Optimizing a Lightroom catalog:
- Rebuilds internal indexes
- Cleans up inefficiencies from years of edits, imports, and moves
- Improves how Lightroom references existing files
If you’ve:
- Migrated a catalog to a new computer
- Moved originals to a NAS
- Reconnected drives multiple times
- Or are you working with a very large, long-term archive
…catalog optimization isn’t optional maintenance. It’s essential.
A Practical Takeaway
If Lightroom suddenly stops recognizing duplicates—especially when you know files already exist—don’t assume the software is “just broken.”
Try this first:
- Back up the catalog
- Run Optimize Catalog
- Then retry the import
It can save you hours (or days) of cleanup and prevent massive duplication mistakes.
Final Thought
Lightroom is a powerful tool, but it’s only as reliable as the catalog behind it. Long-term projects—especially multi-decade archives—need periodic care, just like the files themselves.
If you’re managing large photo libraries or legacy archives, a little preventative maintenance can save you from some very expensive headaches later.