You open Lightroom, and instead of your library, you get a red error: “The Lightroom catalog cannot be opened.” Most people’s first thought is the worst one: did I just lose every photo?
Take a breath. In the large majority of these cases your pictures are fine. What Lightroom can’t open is the ledger it uses to keep track of them, and the most common flavor of this problem is fixed by moving a single file. Below is the exact, Adobe-documented order of fixes, plus how to recover from a backup catalog and the habits that keep it from happening again.

The good news: your photos are almost certainly still there
Think of the catalog as the checkout ledger in a library. The photos themselves are the books sitting on the shelves; the catalog is the notebook that records which book is on which shelf and who borrowed it. If the notebook tears, finding a book gets awkward, but the books on the shelf didn’t vanish.
That’s why this error is rarely a photo-deletion event. The real risk is the work you’ve piled up inside Lightroom: your edits, star ratings, keywords, and collections. Those live in the catalog, not in the original image files.
This fix is for Lightroom Classic, not the cloud version
Adobe ships two different Lightroom apps, and this whole problem belongs to Lightroom Classic only.
- Lightroom Classic manages photos on your own hard drive using a catalog file.
- Lightroom (the cloud version) stores photos in Adobe’s cloud and has no
.lrcatcatalog at all.
If you saw a “cannot open catalog” message, you’re on Classic. That distinction matters because a lot of search results mix in cloud-version fixes that simply won’t apply here.
Why Your Lightroom Catalog Cannot Be Opened: 5 Real Causes
“Can’t open it” can mean very different things depending on the rest of the message:
- A leftover lock file. You’ll see: “The Lightroom catalog cannot be opened because another application already has it opened.” This happens when Lightroom closed badly and left a
.lrcat.lockfile behind. - A corrupted catalog. Messages like “An error occurred while reading the catalog file” or “The catalog is damaged and cannot be used or backed up.” Adobe notes catalogs are databases and can be corrupted by system crashes, hardware faults, or power loss.
- Permissions, disk space, or a second instance. Adobe’s troubleshooting guide asks you to check admin rights, confirm Lightroom is running only once, and confirm you have free disk space.
- A bad storage location. The catalog sits on a network drive, or an external drive got unplugged mid-write.
- A version mismatch. You try to open a catalog that a newer version upgraded, in an older Lightroom. Adobe says you’ll see: “This catalog is too new to be opened by this version of Lightroom.”
Know Your Lightroom Catalog Files — and the One You’re Allowed to Touch
Open your catalog folder and you’ll see some unfamiliar files. Here’s what each one does:
| File | Role | Can you delete it? |
|---|---|---|
.lrcat |
The main catalog file: stores where your photos live and every edit you made. | Never |
.lrcat-data |
Helper data file added in Classic 11+. Adobe says include it in backups. | Never |
.lrcat.lock |
A lock marker that blocks duplicate access while Lightroom runs. Auto-deleted on a clean exit. | Sometimes (move it) |
.lrcat-journal |
Used to confirm in-progress writes on an open catalog. | Never (unless deleting the whole catalog) |
.lrdata |
Preview cache (Previews, Smart Previews). | Yes, but it takes time to rebuild |
The names look similar, and that’s exactly why people accidentally delete the wrong one. The only file you’re generally safe to move is .lrcat.lock. Leave the rest alone.
Match Your Symptom to the Right Lightroom Catalog Fix
Even when the error says the same thing, starting from the right place saves a lot of time. Pick based on the exact message:
| What the screen says | Try first | Then | If that fails |
|---|---|---|---|
| “Another application already opened it” | Fully quit and restart Lightroom | Move the .lrcat.lock file |
Reboot and retry |
| “Error reading” or “catalog is damaged” | Open with Integrity Test | Recover from a backup catalog | Create a new catalog and import |
| Fails with no message | Check admin rights and disk space | Check for a second running instance | Reboot and retry |
| Catalog on an external or network drive | Check the connection | Copy it to a local drive and open | Move to the corruption steps |
| “Too new to open in this version” | Check your Lightroom version | Update to the latest version | Export from the older version |
This table is the backbone of the whole article. Everything below just expands each cell.
Step 0: Copy your catalog folder before touching anything
Before any move-or-delete step, do this. It takes about three minutes and it’s your undo button.
- Fully quit Lightroom.
- Go to your catalog folder. By default Adobe places it at
C:\Users\[you]\Pictures\Lightroomon Windows, or/Users/[you]/Pictures/Lightroomon macOS. - Copy the entire folder to another drive or your desktop.
With that copy in hand, even if you botch a later step you can return to square one. Deleting files without a backup is the only mistake here that can’t be undone.
Quick checks to try first (in order)

- Confirm Lightroom is really closed. In Task Manager (Windows) or Activity Monitor (macOS), check no Lightroom process is left running. Adobe specifically tells you to make sure only one instance is touching the catalog. This alone fixes a surprising number of cases.
- Reboot the computer. It sounds too simple, but it’s in Adobe’s official steps. It clears leftover locks and file handles.
- Check permissions and disk space. Make sure you’re on an admin-level account and the drive holding the catalog has free space. Opening a catalog involves write operations, so a full drive can fail the open outright.
- If it’s on an external drive, check the connection first. A cable or recognition glitch is enough. Adobe warns that if the drive drops mid-write, corruption can follow.
Fix a Lightroom Catalog That Cannot Be Opened — Leftover Lock File (.lrcat.lock)
This is Adobe’s documented procedure for the “another application” message:
- Quit Lightroom Classic.
- Open the folder containing your
[CatalogName].lrcatfile. - If a
[CatalogName].lrcat.lockfile is in the same folder, move it to the Recycle Bin (don’t delete it yet). - Relaunch Lightroom Classic.
- If it opens normally, then empty the Recycle Bin.
One hard rule: never delete or move the .lrcat main file itself. Adobe says so explicitly. A lock file is normally created while Lightroom runs and auto-deleted on a clean exit. The problem is only the one left behind after a crash.
Fix a Lightroom Catalog That Cannot Be Opened — Corrupted Catalog
If you’re seeing a damage-related message, Adobe’s order is:
- Open with the Integrity Test. Hold
Alt(Windows) orOption(macOS) while launching Lightroom Classic. The catalog picker appears. Select the problem catalog, check the Test integrity option, and open. - Open a backup catalog. (Covered in the next major section.)
- Create a new catalog and import. From the same picker, build a new catalog and use Import to bring in the damaged one.
- If it’s on an external drive, copy it local first, then open.
One note from Adobe: when recovery runs, it places a backup of the original catalog in a Corrupt Catalogs folder beside your file. If you see a “recovering” notice, don’t force-quit. Let it finish.
Fix: Move the Catalog Off the Network or Sync Folder
This catches a lot of people off guard. Adobe states plainly that catalogs cannot be stored on a network. You can share original photos over a network, but not the catalog itself.
The reason: a catalog is a database that has to keep a constant grip on its file while writing. Network and sync folders copy the file around constantly, which is like someone yanking the ledger out of your hands mid-entry. OneDrive and iCloud Drive behave the same way. Adobe recommends excluding the catalog location from sync, or keeping it in a separate folder entirely.
The stable setup is the reverse of what feels natural: keep the catalog on the internal drive, and keep original photos on the external or network drive. If you want to edit external-drive photos offline, use Smart Previews.
Fix: The Catalog Is Too New for This Lightroom Version
“This catalog is too new to be opened by this version of Lightroom” means you’re trying to open a catalog that a newer Lightroom upgraded, using an older one.
Adobe explains that major updates change the database structure, which triggers a catalog upgrade, and a pre-upgrade copy is saved as a zip inside the catalog folder. Your data, edits, and presets are preserved. The fix goes two ways:
- Update Lightroom to the latest version, or
- From the older version, export the catalog to a new catalog, then import that into the newer version.
Fix: Free Up Disk Space First
Free up space and try again. The preview cache (.lrdata) is a space hog, and deleting it is safe because Lightroom rebuilds it. But rebuilding takes time, so treat that as a last resort after the other fixes.
Recover a Lightroom Catalog That Cannot Be Opened — Use a Backup

When corruption strikes, the most reliable card is a backup catalog. Lightroom is set by default to create one each time you exit.
Where are the backups?
Per Adobe, backups live in a Backups folder, with a subfolder named after the backup time in YYYY-MM-DD HHMM format (24-hour, no colon between hour and minute). For example:
Pictures\Lightroom\[CatalogName]\Backups\2026-07-30 1930\[CatalogName].lrcat
You can see and change the backup location in Catalog Settings (Edit menu on Windows, or Lightroom Classic menu on macOS), under the Backup tab, where you can also open the backup list and jump straight to a backup folder.
Recovery steps
- With Lightroom closed, copy your current catalog folder in full (the Step 0 move).
- In the
Backupsfolder, pick a date before the problem started. The newest backup may already contain the damage, so step back one at a time if needed. - Copy that catalog file into the folder where your original lives. If the backup is zipped, unzip it first.
- If names collide, rename the existing file (e.g.
old_problem_catalog.lrcat) rather than overwriting. Rename is safer than overwrite. - Double-click the copied catalog, or hold
Alt/Optionwhile launching and pick it from the catalog chooser.
Worth knowing: a backup catalog is a snapshot from backup time. Edits made after that point may be missing. The originals are untouched, but a few days of edit history could be gone, so try the Integrity Test first and fall back to a backup only if that fails.
Five things you must NOT do
- Don’t delete or move the
.lrcatmain file. Adobe explicitly forbids this. - Don’t delete the
.lrcat-journalfile unless you’re deleting the entire catalog. - Don’t tidy files inside the folder without a backup. You can’t undo it.
- Don’t force-quit during recovery. Interrupting an in-progress database operation can make things worse.
- Don’t touch the original photo folder first. Catalog problems and originals are separate; moving originals just breaks the link and creates more work.
Four Habits That Keep Your Lightroom Catalog From Breaking

- Keep the catalog on the internal drive. Adobe recommends local storage; network storage isn’t supported.
- Turn on backups and confirm they’re actually accumulating. Set the cadence in Catalog Settings. If you’ve been hitting “skip” every time the backup prompt appears, now’s the time to stop.
- Enable the Integrity Test and Optimize options on backup. Adobe lists these as corruption-prevention measures. The earlier you catch damage, the more you can roll back.
- Never unplug an external drive while Lightroom is open, and always shut the computer down normally. Most of Adobe’s listed corruption causes come from exactly this.
Quick situation checklist
- Did you read the full error message (lock vs. damage vs. version)?
- Did you copy the whole catalog folder?
- Is the Lightroom process fully closed?
- Is the catalog on an internal drive?
- Is it not inside a sync folder (OneDrive, iCloud Drive, etc.)?
- Do you have enough free disk space?
- Is there a recent backup in the
Backupsfolder? - Did you leave the
.lrcatmain and-journalfiles untouched?
Wrapping up
“The Lightroom catalog cannot be opened” is scary the first time, but it’s almost never a photo-loss event. Start by copying your catalog folder, then work the symptom table top to bottom: clear a leftover lock file, run the Integrity Test, and reach for a backup catalog only if you need it. Do that, and you’ll usually be back to editing within minutes.
If this saved you a panic, bookmark it for next time and share it with a friend who shoots with Lightroom Classic. A few minutes of setup now beats an evening of recovery later.
Next read: Want to make sure this never happens again? Browse our Lightroom Classic backup and troubleshooting guides so recovery is always one click away.

