My twins are nine years old. A few years back, they were playing around on my editing workstation while I was on a call in the next room. By the time I walked back in, one of them had dragged a folder of client proofs into the Trash and emptied it. Forty-seven selects, color-graded and ready to deliver. I had them restored from a versioned backup in under 90 seconds. My kids thought I was a wizard. I just knew where my files lived.

That’s what catalog management actually buys you: not speed, not a prettier workspace. It buys you the ability to fix problems fast, whether the problem is a nine-year-old or a corrupted drive at 2 a.m. the night before a client deadline.

Why Lightroom’s Catalog Isn’t What Most Photographers Think It Is

A lot of photographers treat their Lightroom catalog like it’s a folder full of photos. It isn’t. The catalog is a database, a .lrcat file that stores every edit, keyword, rating, collection, and metadata change you’ve ever made. Your actual image files sit somewhere else entirely. Lightroom is just reading and writing to that database while pointing at your files on disk.

This matters because if your catalog gets corrupted, you don’t lose your RAW files. But you do lose every edit, every keyword, every star rating, and every collection you’ve built. For a working photographer with five years of client work in one catalog, that’s a catastrophic loss even if the images themselves survive.

The other thing most photographers miss: Lightroom’s catalog slows down as it grows. A catalog with 200,000 images will render previews, build smart previews, and execute filter searches noticeably slower than one with 50,000. That slowdown compounds over time, and most photographers just assume their computer is getting old.

The Folder Structure That Actually Works Under Real Deadlines

I use a consistent folder hierarchy that hasn’t changed in nearly a decade. Top level is the year. Under that, each job gets a folder named with the date in YYYYMMDD format, the client name, and a two or three-word job description. Something like 20240315_Marchetti_ProductLaunch. No spaces, no special characters, no abbreviations that’ll confuse me in three years.

Inside each job folder I keep three subfolders: RAW, Exports, and Deliverables. RAW gets the cards dumped straight from the camera. Exports is where Lightroom sends any intermediate files. Deliverables is what goes to the client. I never rename the original RAW files. I let my camera set the filename and I leave it alone. Renaming originals is how people introduce confusion.

On the Lightroom side, I keep annual catalogs. One catalog per year. January first, I create a new catalog, import everything forward, and archive the previous year’s catalog to cold storage. My current working catalog never exceeds about 40,000 images. Previews stay fast, catalog file stays small, and if something goes wrong I’ve limited my exposure to one year of edits at most.

Backup Settings Nobody Talks About (But Should)

Go to Lightroom Preferences, then Catalog Settings. You’ll see a dropdown for catalog backups. Most photographers have this set to “Once a week” or “Once a month.” Set it to “Every time Lightroom exits.” Yes, it adds 15 to 30 seconds when you close the program. No, that is not a good reason to skip it.

Those backups pile up fast though, so set a location outside your main working drive. I back up to a dedicated 2TB Samsung T7 that sits on my desk. Every 30 days I manually delete catalog backups older than 90 days from that drive. Takes two minutes.

The catalog backup only saves the database, not the actual images. For image files I use a 3-2-1 structure: three copies, on two different media types, with one offsite. My local working copy lives on a 4TB WD My Book. A second copy syncs nightly to a second drive using Carbon Copy Cloner on a scheduled task. The third copy goes to Backblaze, which costs $9 a month and has saved me from genuine panic more than once. Total cost for the whole system is under $250 in hardware plus the Backblaze subscription.

Smart Previews and the Mobile Editing Trap

Lightroom Classic lets you generate Smart Previews, which are compressed DNG files roughly 2,500 pixels on the long edge. They let you edit without the original files being connected. Useful when you’re on a laptop away from your main drives. The trap is leaving Smart Preview generation turned on at import for every single job.

Smart Previews average about 1MB each. A 1,000-image shoot generates roughly 1GB of Smart Previews on top of your standard previews. Multiply that across a year of work and you’ve quietly added 40 to 60GB to your catalog folder without noticing. I only build Smart Previews for jobs I’m actively editing away from my studio. When the job is delivered, I discard them. Edit, Library panel, Previews, Discard Smart Previews. Done.

The Test Nobody Does Until It’s Too Late

Once a month I restore a random catalog backup onto my secondary machine and verify it opens cleanly. I also do a spot-check file restore from Backblaze on a random job folder. This takes about 20 minutes. I do it the same day I test my backup drives, first Saturday of the month, coffee in hand.

I’ve seen photographers with backup systems they’ve never actually tested. That’s not a backup system, it’s a backup feeling. The restore is the only thing that counts.

Your catalog is the connective tissue of your entire photography business. Treat it like infrastructure, not an afterthought, and you’ll spend your energy on creative work instead of damage control.