The Day I Realized My Catalog Was a House of Cards

I was three years into commercial work when I sat down to pull selects from a campaign I’d shot for a retail client six months earlier. They wanted two additional images for a follow-up ad buy. Simple request. Should have taken ten minutes.

It took four hours. My catalog was a disaster. I had folders named things like “FINAL_v2_USE THIS ONE” sitting next to “retouched_web_ACTUAL FINAL.” Previews were missing. Keywords were nonexistent. I found the files eventually, but I billed the client for one hour and absorbed the rest out of sheer embarrassment. That was around $180 I ate because I hadn’t built a real system.

That experience cost me less than some photographers lose, but it was enough. I rebuilt everything from scratch over the following weekend, and I haven’t had a retrieval problem since.

What a Catalog Actually Does (and Why It Can Lie to You)

Lightroom’s catalog is a database, not a storage system. This trips up a lot of people early on. The catalog file (.lrcat) stores your edits, metadata, keywords, collection memberships, and the locations of your images. The actual raw files live somewhere else entirely, on your drive, external or internal.

When those paths break, because you moved a folder in Finder or Windows Explorer instead of inside Lightroom, the catalog loses track of the files. You see those gray question marks. Your edits are still in the database, but Lightroom can’t connect them to the source files. The catalog didn’t corrupt. It just got lied to about where things are.

This is why folder management inside Lightroom matters so much. Every move, every rename, every reorganization should happen within the Folders panel in Lightroom Classic. Not in your operating system. Not ever.

Building a Folder Structure That Works Across Years

My current folder hierarchy has three levels, and it never varies. At the top is the year: 2024. Under that, the client name in all caps: MORRISON_BRANDS. Under that, the job folder with a date prefix: 2024-08-14_Product_Launch.

Inside each job folder I keep three subfolders: RAW, EXPORTS, and DELIVERY. RAW holds the unedited originals. EXPORTS holds full-resolution layered TIFFs and high-res JPEGs. DELIVERY holds the final web-sized or print-ready files that actually went to the client.

This structure means that if a client calls me two years from now asking for a larger version of an image, I can find the raw file, the retouched TIFF, and the delivered JPEG in under sixty seconds. I’ve done this in front of clients during calls. It reads as competence. It is competence, but it’s also just good filing.

File naming follows a strict convention as well: ClientCode_YYYYMMDD_JobDescription_0001.RAW. For the Morrison Brands job above, that looks like MB_20240814_ProductLaunch_0001.CR3. I set this in Lightroom’s Import dialog under File Renaming, using a custom template I built once and have never had to touch since.

Catalog Backups Are Not the Same as File Backups

Lightroom prompts you to back up your catalog. Most photographers set it to “Once a week” and think they’re covered. They’re not.

The catalog backup Lightroom creates is just a copy of the .lrcat file. It does not back up your raw files, your previews folder, or your exported images. Those need a completely separate backup strategy.

My current setup: original files on a 4TB G-Technology desktop drive connected via USB-C. Nightly backup to a second 4TB drive using Carbon Copy Cloner on a scheduled task. Weekly backup to a third drive that I keep in a different room. I also run Backblaze for off-site cloud backup at $99 a year, which runs continuously in the background.

My twins are eleven now, and a few years back one of them accidentally deleted a folder of client proofs while they were using my computer. I had everything restored from the local backup in about ninety seconds. Not because I’m particularly fast. Because the system is designed to make recovery that fast.

For the catalog itself, I set Lightroom to back up daily, and I store those catalog backups on the second drive, not the same one the working catalog lives on. Catalog backups live under Lightroom > Catalog Backups, and I keep sixty days of them before deleting the oldest.

Smart Previews and When to Actually Use Them

Smart Previews are compressed DNG copies of your raw files, small enough to edit without the original drive connected. For most photographers with a fixed studio setup, they’re optional. For anyone who edits on a laptop while traveling, they’re essential.

The tradeoff is storage. A Smart Preview for a 45MB Canon R5 raw file runs about 1.5 to 2MB. For a 5,000-image wedding job, that’s 7 to 10GB of additional storage for previews alone. That adds up fast if you’re building them for every catalog.

My practice: I build Smart Previews only for active jobs, defined as anything shot within the last ninety days or anything still in client review. Once a job is delivered and paid, I delete the Smart Previews from within Lightroom’s Library menu. I keep the raws and exports. I just don’t need the portability anymore.

This keeps my catalog lean. My current main catalog is 2.3GB for roughly 85,000 images. Without Smart Preview management it would be three times that size.

The single most important thing you can do for your photography business this week is to open Lightroom, go to Lightroom > Catalog Settings, and check where your catalog lives and when it last backed up. If you don’t know the answer off the top of your head, you’re one hard drive failure away from finding out the hard way.