Why macOS Sequoia triggers Lightroom catalog corruption
Short answer: Lightroom Classic stores all your edit history, star ratings, collections, and metadata in a single SQLite database file (the .lrcat catalog — a self-contained relational database). macOS Sequoia, like all macOS updates, occasionally forces a restart. If Lightroom is open and writing to the catalog when macOS restarts — either from an update prompt or a background process — the SQLite WAL file (Write-Ahead Log — the mechanism SQLite uses to track in-progress transactions) is left incomplete. The next time Lightroom opens, it detects the inconsistency and reports "The catalog cannot be read" or "An error occurred while trying to open the catalog." Your original RAW or JPEG photos are never affected by catalog corruption — only metadata and edits live in the catalog.
How to recover a corrupted Lightroom Classic catalog on macOS
Step 1: Check Lightroom's automatic backup catalog first
Lightroom Classic creates automatic compressed backups every time you launch it (if set to do so). Navigate in Finder to the folder containing your .lrcat file (usually ~/Pictures/Lightroom/). Inside, look for a subfolder called Backups. Each backup is a date-stamped folder containing a compressed .lrcat.zip file. Unzip the most recent backup (double-click the .zip), then in Lightroom go to File > Open Catalog and select the unzipped .lrcat file. If it opens successfully, all edits up to that backup date are intact. Go to File > Optimize Catalog, then save it to a new location. This resolves the majority of Sequoia-triggered catalog corruption cases.
Step 2: Use Lightroom's built-in repair tool
If no usable backup exists or the backup is very old, Lightroom offers its own repair at the error dialog. When the "cannot be read" error appears, there are buttons for Test Integrity and Repair Catalog. Click Test Integrity first — it will report what is corrupted. If only the WAL (Write-Ahead Log) is inconsistent, the repair succeeds cleanly in most cases. Adobe's repair tool essentially runs SQLite's own integrity check and WAL recovery. Success rate for single interrupted-write corruption is high — most Sequoia-triggered corruption falls into this category.
Step 3: SQLite command-line recovery for deeper corruption
If Lightroom's repair fails, the catalog's SQLite database has more serious damage. Open Terminal and run: sqlite3 YourCatalog.lrcat ".recover" | sqlite3 Recovered.db. SQLite 3.29+ has a built-in .recover command that reads intact pages from the damaged database and writes them to a new file. This recovers all data from undamaged database pages — typically 80–95% of the catalog. After recovery, rename Recovered.db to YourCatalog.lrcat and open in Lightroom. Some edits from the period of corruption may be lost, but the bulk of the catalog history is preserved. Our data recovery team can assist with SQLite-level catalog repair for large catalogs where Terminal commands are unfamiliar.
Step 4: The India angle — wedding and event photographers
India has a large professional photography community — weddings, corporate events, fashion shoots — where a corrupted Lightroom catalog can mean the loss of weeks of editing work on client deliverables. The most painful cases we see are photographers who were culling and editing wedding photos from the previous weekend when macOS Sequoia prompted a restart and they clicked "Update Now" without closing Lightroom first. The RAW files are always intact — but recreating 200 hours of editing on 3,000 wedding images is devastating. The fix: close Lightroom before any macOS update, and set Catalog Backup to "Every time Lightroom starts" in Catalog Settings. For the broader Apple MacBook context, see our Final Cut Pro library recovery guide for similar SQLite-level recovery patterns.
When to call a specialist (and what it costs)
When to stop DIY
If the Mac's SSD is showing errors in Disk Utility First Aid — red or yellow warnings — fix the storage hardware problem before attempting catalog repair. A catalog on a failing SSD will corrupt again immediately after repair. If the .lrcat file size is 0 bytes or shows as empty, the file data was lost at the filesystem level — this requires file recovery tools (PhotoRec, R-Studio), not catalog repair tools.
Typical India cost range
Lightroom catalog backup restore and optimization: ₹500–₹1,500. SQLite-level deep catalog repair: ₹2,000–₹5,000. SSD repair before catalog recovery: ₹2,000–₹8,000 depending on fault. Apple MacBook SSD service: see our Apple MacBook repair page.
A note from the LRW Engineer Team
The single change that prevents every Lightroom catalog corruption case: set Catalog Settings > General > Back Up Catalog to "Every time Lightroom starts." It takes 5 seconds per launch and creates a compressed backup that restores a full catalog in two minutes. Combine it with a Time Machine drive for your catalog folder. We have never seen a photographer lose significant edit work who had both of these in place.