Corrupt Lightroom catalog deserves a clear, practical explanation. Lightroom opens, thinks about it, and announces that the catalog is corrupt and cannot be repaired. Ten years of edits, collections, keywords and ratings. It is a genuinely awful message to see, and it is much less catastrophic than it feels — provided you understand what the catalog actually is.
The short answer. Your photos are files on disk and they are untouched. The catalog is a SQLite database holding edits and metadata. Let Lightroom attempt its repair, and if that fails, open the most recent automatic backup. Worst case you lose edits made since that backup, not images.
Corrupt Lightroom catalog: Let it try to repair first
Lightroom’s built-in repair works more often than its grim wording suggests. Let it run and do not interrupt it, even if it sits at a percentage for a long time on a large catalog. Before you start, copy the whole catalog folder somewhere safe — if the repair makes things worse, you want the original to fall back to.
Then go to the backups
Lightroom writes zipped catalog backups into a Backups folder next to the catalog, on whatever schedule you set. Most people set it and forget it, which means there is usually something in there. Sort by date, take the newest, unzip it somewhere separate and open that. If it opens cleanly, you are back — minus whatever you did since that backup ran.
- Backups are zip files. Unzip before opening; do not point Lightroom at the archive.
- Work on a copy of the backup, not the backup itself, so you can try an older one if needed.
- Previews are in a separate .lrdata folder and can be rebuilt. Do not panic if they are missing.
- Smart previews likewise. Slow to rebuild, but not lost data.
If every backup is also corrupt
That normally means the disk holding them is the real problem, not Lightroom. A drive with failing sectors will corrupt the catalog you are writing and the backups you write next to it. Check SMART on that drive before you spend an evening on database repair — you may be repairing the symptom.
Recovering catalogs and photos from a failing disk
If the drive holding your catalog and backups is the thing that failed, the catalog repair is the wrong job. Stellar Data Recovery pulls the .lrcat file and its backups off a damaged volume along with your raw files, and handles the photo formats — CR3, NEF, ARW, DNG — rather than treating them as anonymous blobs.
Recover the catalog and raws with StellarAffiliate link — we may earn a commission at no extra cost to you.
Rebuilding from scratch, if it comes to that
If the catalog is unrecoverable, you can import the photo folders into a fresh catalog and get everything back except your edits, collections, keywords and ratings. That is a real loss, but it is worth knowing what survives: any edits written to XMP sidecar files come back automatically, as does anything you exported with metadata embedded.
This is the argument for turning on automatic XMP writing even though it slows things down slightly. It puts a plain-text copy of your develop settings next to every raw file, which makes your edits independent of the database entirely.
Setting it up so this does not happen again
- Keep the catalog on a local SSD, never on a network share. SQLite over SMB is how catalogs get corrupted.
- Set backups to every time you exit, and test one occasionally by actually opening it.
- Turn on Automatically write changes into XMP.
- Back up the catalog folder to a different physical drive, not just the Backups folder beside it.