The Folder That Almost Ended a Client Relationship

A few years back, I sat down to pull selects from a corporate headshot session — 340 frames, solid work, client expecting a gallery by end of week. Lightroom opened, I navigated to the shoot, and every thumbnail showed a gray question mark. The images were there on the drive. Lightroom just had no idea where they were anymore. I’d moved a parent folder during a hard drive reorganization without telling the catalog, and now I was staring at 340 broken links with a deadline in two days.

That’s a recoverable situation if you know what you’re doing. For a lot of photographers I’ve talked to, it isn’t. They panic, they reimport, they duplicate, they create a mess that takes longer to sort out than the original problem. Catalog discipline isn’t glamorous. Neither is calling a client to tell them their images are delayed because of a file management mistake.

What a Catalog Actually Is (And Why Most People Misunderstand It)

Lightroom Classic’s catalog is a SQLite database, a single .lrcat file, that stores every edit, every star rating, every keyword, every collection, and every file path you’ve ever touched inside the program. The actual raw files live on your drive. The catalog just points to them.

This matters because moving files outside of Lightroom, through Finder on a Mac or File Explorer on Windows, breaks those pointers. Lightroom has no idea you moved the folder. The edits aren’t lost, but they’re stranded. And if your catalog file itself gets corrupted, or you’re running one giant catalog for six years of client work with no backup, you are one bad hard drive sector away from losing years of metadata, culling decisions, and edits that no longer exist anywhere else.

Most photographers I’ve met run a single catalog, store it on the same drive as their images, and back up neither with any consistency. That’s not a workflow. That’s wishful thinking.

Building a Catalog Structure That Doesn’t Fight You

I use one catalog per year. Each year’s catalog lives on my main internal SSD, backed up automatically every time I close Lightroom, using Lightroom’s built-in backup prompt set to “Every time Lightroom exits.” Those backups go to a folder on a separate external drive, not the same drive as the catalog itself.

Inside the catalog, I organize by client, then by date. The folder structure on my drive mirrors this exactly: Photography > Clients > [Client Name] > YYYY-MM-DD_JobDescription. Every folder I create on disk, I create inside Lightroom using Lightroom’s folder panel, so the catalog always knows where things are. I have never, in the past eight years, used Finder to move a client folder.

For active jobs, I shoot to two cards simultaneously when my camera supports it. Raw files go to a 1TB Samsung T7 portable SSD the day of the shoot, then get ingested into Lightroom with “Make a Second Copy To” checked, sending duplicates to a 4TB WD My Passport drive. That’s three copies before I’ve even started editing: the cards, the primary drive, and the backup drive.

Catalog file sizes matter too. A single Lightroom catalog for 10 years of work can hit 2-3 GB and start slowing down. Annual catalogs stay lean, typically under 400 MB for my shooting volume, and are easier to archive when the year closes out. I export the finished catalog at year’s end with all previews, burn it to a third drive I keep in a drawer, and start fresh January 1.

Previews, Smart Previews, and Not Wasting Hours

Standard previews are rendered JPEG versions of your raw files that Lightroom stores in a .lrdata folder next to the catalog. They’re what you see when you browse images. Build 1:1 previews during import, under File > Import Photos, by setting the “Build Previews” dropdown to 1:1, and Lightroom renders everything at full resolution while you’re making coffee. Do it later and you’re waiting every time you zoom in to check sharpness.

Smart Previews are a separate thing. They’re compressed DNG-like files, about 1-5 MB each, that let you edit even when the original raw files are disconnected, like when your archive drive is at home and you’re working on a laptop. For commercial clients, I build Smart Previews for every job at import. It adds maybe 10-15 minutes per 300-image shoot during ingest, and has saved me more than once on travel jobs where I wanted to cull on the plane without lugging an extra drive.

The Lesson My Kids Taught Me Without Knowing It

My twins are nine. A while back, one of them was poking around on my office computer and managed to drag an entire folder of client proofs into the Trash and empty it before I caught it. About 180 processed JPEGs from a product shoot, gone. I’d like to say I was calm. I was not calm.

But because I run Time Machine on my office Mac with a dedicated 2TB backup drive, and because I also back up that folder to Backblaze for off-site cloud storage at $9 a month, I had those files restored and back in the client delivery folder in under two minutes. The client never knew. I bought the kids ice cream anyway, because honestly it was a good reminder that the system worked.

Backblaze runs in the background continuously. The Time Machine drive sits on my desk and backs up hourly. These are not optional expenses. They’re the cost of being a professional.

The One Thing That Changes Everything

Catalog management isn’t a feature you turn on. It’s a set of habits you build before something goes wrong, because by the time something goes wrong, it’s already too late to build them. Get your structure right on the next shoot, not the one after the disaster.