My twins were seven years old when they discovered that the delete key on my keyboard did exactly what the name implies. I was in the kitchen making coffee. They were “just looking” at my computer. Somewhere in that five-minute window, they wiped an entire folder of client proofs, roughly 340 processed selects from a corporate headshot session due for delivery the next morning.

I had them restored from my backup in 90 seconds.

That moment taught me something I already knew intellectually but had never felt in my gut: a catalog is only as good as the infrastructure holding it up. Most photographers spend hours learning how to use Lightroom’s develop module and roughly zero hours thinking about how their catalog actually works, where it lives, and what happens to their business when it breaks. That gap is expensive.

What Your Catalog Is Actually Doing Behind the Scenes

Lightroom Classic’s catalog is a SQLite database, a single .lrcat file that stores every edit, keyword, collection, rating, and metadata change you have ever made. It does not store your images. It stores instructions about your images and pointers to where those images live on disk. This distinction matters enormously.

When that pointer breaks, because you moved a folder outside of Lightroom, renamed a drive, or plugged your external hard drive into a different USB port and your operating system assigned it a new drive letter, Lightroom cannot find the file. The image goes offline. Your edits still exist in the catalog, but they are attached to a ghost. If your catalog file itself becomes corrupted, which happens most often during a hard crash or improper shutdown, you can lose every metadata record for every image you have ever imported.

The catalog is the brain. Treat it that way.

The Folder Structure That Actually Scales

I use a folder hierarchy that has not changed in over a decade: Client Name / Year / YYYY-MM-DD_JobDescription. Every shoot lands in that structure before I import a single file. Inside each job folder are three subfolders: RAW, Selects, and Exports. The RAW folder holds the originals. Selects holds any DNG conversions or JPEGs I pull for the client’s review round. Exports holds the final deliverables.

This costs me about four minutes per job to set up and saves me from the specific hell of hunting through a folder called “Photos - 2022 - FINAL - USE THIS ONE” at 11pm before a deadline.

In Lightroom, I keep one catalog per year. Not one catalog ever, not one catalog per client. One per year. My current catalog sits at around 18GB for roughly 40,000 images. That is a manageable file size that opens fast and backs up quickly. Splitting by year also means that if I need to archive 2021, I can move that catalog to cold storage without touching anything active.

Backup Settings That Match the Actual Risk

Lightroom’s built-in catalog backup, found under Edit, Catalog Settings, Backup, is set to “Never” by default on many installs. Change it to “Once a day, when exiting Lightroom.” The backups go into a folder called Lightroom Backups inside your Pictures directory unless you change it. Change it. Point it to an external drive or a network location, not the same disk where your catalog lives. A backup that burns in the same fire as the original is not a backup.

I keep three physical backup drives, a 4TB Samsung T7 I carry with me, a 4TB WD My Passport that stays at home, and a 4TB backup that I update weekly and store at my studio. I test each drive monthly, not just plug it in, but actually open a file from it. I also use Backblaze for offsite cloud backup at $99 a year, which continuously backs up my entire system including the catalog folder. For $99, it is the cheapest insurance policy in professional photography.

The Lightroom backup is not a replacement for this. It is one layer of a system, and it only covers the catalog file, not the actual image files.

Keeping the Catalog Fast and Clean

A slow catalog is usually a bloated one. Run the optimization tools under File, Optimize Catalog at least once a month. This rebuilds the database index and clears out fragmentation that accumulates over thousands of import sessions. If you have never run it on a catalog you have used for a year or more, the first optimization can cut your catalog size by 15 to 30 percent and noticeably speed up scrolling and filtering in the Library module.

Purge your cache periodically too. Go to Preferences, Performance, and set your Camera Raw cache to something reasonable for your drive size. I run mine at 20GB on my 2TB internal SSD. Letting it balloon to 50 or 60GB because you never checked it does not improve performance; it just eats storage and occasionally causes Lightroom to slow to a crawl during export.

What Happens When You Skip All of This

I worked at a newspaper early in my career where missing deadline was not a recoverable offense. That environment hardwired something into me: the work is not done until it is delivered safely, and safe delivery requires a system, not good intentions.

Every few months I hear from a photographer who has lost a hard drive, or whose catalog corrupted, or who cannot find a client’s files from three years ago because the folder was named something like “Smith - maybe wedding - DONE.” The pain in those conversations is real. These are not lazy people. They are talented photographers who underestimated how much the boring operational side of the business protects the creative side of it.

A catalog management system will never make you a better photographer. But a broken one can end your business faster than a slow season or a lost client ever could. Build the system once, maintain it in minutes per month, and it will quietly hold everything together while you focus on the work that actually got you into this.