What Is a .lrcat File, and Which Catalog Files Can You Delete?

By David Maizil · November 2, 2026 · 7 min read

Quick Answer

A .lrcat file is your Lightroom Classic catalog: a SQLite database holding every edit, keyword, rating and collection, but not the photos themselves. With Lightroom closed you can delete Previews.lrdata and Helper.lrdata. Never delete the .lrcat, the .lrcat-data folder, or a -wal or -journal file.

Open the folder your catalog lives in and you will find six to ten items with names that look like they were designed to scare you. This post puts every one of them in a single table with a plain verdict.

I build Lightroom Classic plugins, so I read and write the catalog through Adobe's SDK every day. Once you know the .lrcat is a SQLite database, every other file in that folder starts to make sense.

What is a .lrcat file?

A .lrcat file is a single SQLite 3 database that stores everything you have done to your photos in Lightroom Classic. That means develop settings, history steps, keywords, ratings, flags, collections, face regions, folder paths to your originals, and every Publish Service's sync history.

What it does not hold is the photos. Your RAW and JPEG files stay wherever you imported them. The catalog only stores their paths and a set of instructions for rendering them, which is why a 200,000 photo library can sit in a 2-4 GB .lrcat.

Here is the plugin builder's detail: the SDK gives plugins no direct access to that database. Every write goes through a single queued call, and Lightroom applies writes one at a time. Nothing else should touch the .lrcat while Lightroom has it open, including a sync client.

What are the other files in the Lightroom catalog folder?

Every other item in the folder is either a cache Lightroom can rebuild, a SQLite housekeeping file, or a flag. Assuming the default catalog name, this is what you will see:

On a Mac the .lrdata items look like single files. They are package folders: right-click and choose Show Package Contents to see inside.

Which Lightroom catalog files are safe to delete?

Only the caches are safe to delete, and only with Lightroom Classic fully quit. Here is the full verdict:

File or folder Verdict What it costs you
Previews.lrdata Safe, Lightroom closed Hours of preview rebuilding on a big catalog; Library feels slow until it finishes
Helper.lrdata Safe, Lightroom closed Nothing lasting; a common fix when keywording goes sluggish
Smart Previews.lrdata Costs you something No offline editing; can't be rebuilt until the original drive is connected again
Sync.lrdata Only to fix a sync problem Lightroom rebuilds the sync state, which can mean a long rescan
.lrcat.lock Only a stale one, after a crash Nothing, if Lightroom really is closed. Deleting it while open invites corruption
Old Backups subfolders Safe; keep the newest 3-5 Older restore points
.lrcat-wal, .lrcat-shm, .lrcat-journal Never Your most recent edits, or a half-finished write that only the journal can roll back
.lrcat-data Never Every AI mask, Remove and Denoise result has to be recomputed
.lrcat Never All of your work

The -wal file is the one people delete by mistake, because it shows up after a crash and looks like junk. It is the opposite: after a crash it can hold your last hour of edits. Open the catalog in Lightroom and it gets folded back in on its own.

The October problems roundup has the step by step for deleting Helper.lrdata when keywording slows down.

How do you know which .lrcat is your current catalog?

Open Catalog Settings, and the General tab shows the path of the catalog that is open right now. On a Mac it is under Lightroom Classic > Catalog Settings; on Windows, Edit > Catalog Settings. Click Show to jump to it in Finder or Explorer.

You will often find several .lrcat files side by side, named something like "Lightroom Catalog-v13.lrcat". Each major Lightroom upgrade that changes the database format copies your catalog to a new file with a version suffix and leaves the old one untouched. The old one is a frozen snapshot from upgrade day.

To retire old-version catalogs safely:

  1. Confirm the current catalog's path in Catalog Settings, as above.
  2. Quit Lightroom and move the older .lrcat files (with their matching Previews.lrdata) to an archive drive, rather than deleting them.
  3. Work for a few weeks. If nothing is missing, delete the archived copies.

Why is my .lrcat file so big, and how do I shrink it?

A big .lrcat is almost always history steps and AI edit metadata, and File > Optimize Catalog is the first fix. Optimize runs SQLite's own compaction, reclaiming space left by deleted photos and old records. On a catalog that has never been optimized, the saving can be large, and it takes a minute or two.

If your whole catalog folder feels huge, the .lrcat is rarely the culprit. Previews.lrdata is usually several times its size, especially with 1:1 previews set to never discard. Set Catalog Settings > File Handling > Automatically Discard 1:1 Previews to After 30 Days. Smart previews add roughly 1-5 MB per photo; my post on Lightroom Classic smart previews covers when they are worth that.

The last lever is history. Every slider move is a stored step. For finished archive shoots, select the photos in Library and choose Photo > Develop Settings > Clear History; the final edit stays, only the undo trail goes.

How do you move, rename or back up a .lrcat safely?

Treat the whole catalog folder as one unit. Quit Lightroom, move or copy the entire folder, then double-click the .lrcat in its new home. Moving only the .lrcat leaves the previews and the .lrcat-data folder behind.

One note on plugin data: anything a plugin writes as keywords lives in the .lrcat like your own. Face Tagger, for example, tags people as ordinary keywords, so they are covered by a catalog backup and travel in XMP sidecars if those are on. No separate database to lose.

Frequently asked questions

Can I open a .lrcat file without Lightroom?

Only to read it. Any SQLite browser can open a copy of a .lrcat and show its tables, but never edit the real file that way. Lightroom Classic is the only program that can use it as a catalog.

Can I delete the .lock file?

Yes, but only if Lightroom is definitely closed and still says the catalog is in use, which means a crash left the lock behind. If Lightroom is running, leave it alone.

What is the .lrcat-data folder?

It holds the computed results of AI masks, Remove and Denoise, which are too large to store in the .lrcat itself. Back it up with the catalog and never delete it.

Does deleting Previews.lrdata delete my edits?

No. Edits live in the .lrcat. Previews.lrdata is only rendered images, and Lightroom rebuilds them as you browse or when you choose Library > Previews > Build Standard-Sized Previews.

Can Lightroom Classic and Lightroom (cloud) share a .lrcat?

No. The cloud-based Lightroom app does not use a .lrcat at all. It can import a Classic catalog once with File > Migrate Photos, but after that the two libraries are separate.

More plain-English guides to how Lightroom Classic really works. Browse the Lightroom Tools blog →

David Maizil Creator of Lightroom Tools. Building Lightroom Classic plugins to simplify photographers' workflows. Spend less time managing photos, more time shooting them. Like these guides? Add Lightroom Tools as a preferred source on Google and it will show you more of them.