The Shoot That Almost Broke My Business

A few years into running my commercial photography business, I handed my laptop to a client so she could scroll through some selects. She accidentally knocked it off the conference table. The machine survived. My external drive, plugged into the USB port at the time, did not. I lost two weeks of catalog work: metadata, keywords, star ratings, color labels, develop settings. The raw files were fine on a second drive, but every organizational decision I had made was gone.

That afternoon cost me about six hours of rebuild time and one near-panic attack. It also cost me nothing permanently, because I had a catalog backup that was three days old. Three days of re-editing is painful. Total loss would have been catastrophic.

That incident is why I now treat my Lightroom catalog with the same paranoia I treat my raw files. Most photographers protect their images and completely ignore the catalog. That’s backwards.

What the Catalog Actually Is, and Why It’s Fragile

Lightroom Classic’s catalog is a single SQLite database file with the extension .lrcat. Everything lives in that one file: your entire edit history, all metadata, every keyword, every collection, every flag, every slider adjustment you’ve ever made. The previews are stored separately in a .lrdata folder alongside it, but the actual work, the intellectual labor, is locked inside that .lrcat file.

SQLite databases are fast and efficient, but they are not inherently crash-proof. If Lightroom is writing to the catalog when power fails, or when a drive throws an error, that file can corrupt. Adobe does include a built-in backup option, but the default setting ships at “once a week,” and the default backup location is the same drive as the catalog itself. Both of those defaults are wrong.

Catalog Structure That Actually Scales

I run one master catalog for all client work. Some photographers swear by per-project catalogs, but managing dozens of separate catalogs creates friction and makes global searches and smart collections useless. One catalog, consistently organized, has served me through over 400 commercial shoots.

Inside Lightroom, I organize by folder structure mirroring what’s on disk: /Year/Client Name/Job Name/. A typical path looks like: 2024/Apex Design/Brand Refresh March/. I use four-digit years as folder prefixes so they sort chronologically without any clever tricks. Every job gets a dedicated collection set on import, which takes about 45 seconds and saves enormous time during culling.

For keywords, I use a controlled vocabulary I built in 2019 and have expanded over time. It now has about 340 terms organized in a hierarchy: Subject, Location, Client, Usage Rights. Keywording adds maybe four minutes per job at import and makes asset licensing searches, which clients ask for constantly, take seconds instead of hours.

Backup Settings Worth Actually Using

In Lightroom Classic, go to Edit > Catalog Settings > General. Set backup frequency to “Every time Lightroom starts.” Yes, every time. The backup process takes between 8 and 45 seconds depending on catalog size. My current catalog is 2.3 GB and backs up in about 20 seconds. That is not a meaningful interruption.

Change the backup destination to a separate physical drive, not the same drive your catalog lives on. I keep mine going to a dedicated 2 TB Samsung T7 that sits in a drawer next to my desk. It is not the working drive, it is not the raw file drive. It exists solely for catalog backups and software installers.

After every catalog backup, Lightroom gives you the option to run “Test Integrity” and “Optimize Catalog.” Run both. The integrity check has caught minor errors in my catalog twice in ten years. The optimization keeps query speeds reasonable as the catalog grows.

Finally, include your catalog in your offsite backup. I use Backblaze at $99 per year for unlimited data. My catalog and its backup folder are both in the Backblaze backup set. So is the .lrdata previews folder, though previews can always be regenerated from raw files. The catalog cannot be regenerated. Prioritize accordingly.

The 90-Second Restore That Proved the System Works

My twins are nine years old. A couple of years ago, one of them was using my editing machine to watch YouTube while I was in a client call in the next room. When I came back, an entire collection of client proof selects was gone. Not the raw files. The collection, the edits, the crop marks I’d spent an hour setting.

I restored the catalog backup from that morning, relaunched Lightroom, and had everything back in about 90 seconds. My kid looked genuinely impressed. I used it as a teaching moment about not touching other people’s computers, but honestly I was mostly relieved that the system I’d built held up under exactly the kind of random real-world stress that you never plan for.

That’s the point of a tested system. You don’t build it for the disasters you imagine. You build it for the ones you don’t see coming.

Naming Conventions That Survive the Long Term

One last piece this whole system depends on: consistent file naming at import. I use a custom naming preset in Lightroom that produces: YYYYMMDD_ClientCode_Sequence. So a file might be named 20240315_APX_0047.arw. Every file in my archive is uniquely named. Duplicates are impossible. Searches across years are clean.

Set this in Lightroom’s Import dialog under File Renaming. Build the preset once, save it, and never think about it again. This step takes three minutes to set up and will save you from naming collisions and client confusion for the rest of your career.

The catalog is not glamorous work. Nobody posts their folder structure on Instagram. But this is the architecture your entire business runs on, and if it fails at the wrong moment, the images you protected so carefully are stranded without their context, their edits, or their history. Build it right once, and then stop worrying about it.