The Folder That Almost Ended a Client Relationship

My twins were seven years old when they found my laptop open on the kitchen table. I was making coffee. By the time I came back, one of them had dragged a folder of client proofs into the trash and emptied it. Four hundred selects from a corporate headshot session, gone. I had them restored in 90 seconds from a local backup, but that moment clarified something I already believed deep in my bones: your catalog is not just an organizational tool. It is the spine of your entire business. If it breaks, or gets corrupted, or simply becomes too bloated to navigate under deadline pressure, you will lose time, money, and clients.

Most photographers treat their Lightroom catalog the way people treat their car’s check engine light. They know something is probably wrong, but they keep driving.

Why Catalogs Fail and What’s Actually Happening

Lightroom Classic stores all of your edits, metadata, star ratings, collections, and keywords in a single .lrcat file. Your actual raw files sit wherever you put them on disk. The catalog just points to them. When that pointer breaks, because you moved a folder outside of Lightroom, or renamed a drive, or your catalog file got corrupted during a crash, Lightroom shows you gray thumbnails with question marks and you spend an afternoon relinking files instead of shooting or editing.

The catalog file also grows over time. A working commercial photographer can end up with a catalog pushing 5 to 10 gigabytes after a few years, which slows down preview rendering, search, and export. Lightroom is reading and writing to that file constantly, and if your machine crashes mid-write, which mine did once during a storm-triggered power outage, the catalog can corrupt in ways that are genuinely difficult to recover from.

The fix is not complicated, but it requires you to actually set it up before the crisis hits.

Folder Structure and Naming That Scales

I use a dead-simple folder hierarchy that I have not changed in twelve years: Client Name > Year > Job Number - Job Name. Inside each job folder I have three subfolders: RAW, EXPORTS, and SELECTS. Every folder on every drive follows this structure, period.

Inside Lightroom, I mirror this on the left panel under Folders. I never let Lightroom manage file locations. I tell it exactly where files live, and I move folders from inside Lightroom only, never from the Finder or Windows Explorer. That one habit eliminates the vast majority of missing file errors.

For catalog backups, go to Edit > Catalog Settings > Backup and set it to “Once a day, when Lightroom starts.” Choose a backup location on a different physical drive than the one your catalog lives on. I keep mine on a dedicated 1TB Samsung T7 portable SSD ($80-$110 depending on the sale). Lightroom’s built-in backup creates a compressed copy of the .lrcat file. It does not back up your previews, which are regeneratable, or your raw files, which are not. Those need a separate system.

A Backup Architecture That Actually Holds Up

The raw files follow a 3-2-1 structure: three copies, two different media types, one offsite. My working drive is a G-Technology 4TB desktop drive. When I come home from a shoot, the files go there first, then automatically sync overnight via Chronosync to a second 4TB drive in my office, and simultaneously upload to Backblaze at $9 a month. Backblaze backs up continuously in the background and keeps 12 months of version history. For roughly $100 a year, that is real insurance.

I test my backups monthly. Not because I enjoy it, but because a backup you have never tested is a guess, not a backup. I pull a random folder from the external, restore it to a test location, and confirm the files open. The whole process takes about 15 minutes. Most photographers never do this. Most photographers also have a story about a drive that “should have been fine.”

Pruning Your Catalog Before It Slows You Down

Every January I do a catalog audit. I run Lightroom’s built-in catalog optimization under File > Optimize Catalog, which compacts the .lrcat file and can shave 10 to 20 percent off the file size on a large catalog. I also delete previews for jobs older than two years under Library > Previews > Discard 1:1 Previews. Those preview files live in a separate .lrdata package next to your catalog and can balloon to 30 or 40 gigabytes on a mature catalog. You can always regenerate them.

I also purge rejected images twice a year. Every frame I rate one star as a reject during culling, I bulk-delete permanently after the client has received their deliverables and I am satisfied the project is closed. There is no professional reason to keep a blurry, underexposed frame from 2019. Disk space is not free, and visual noise in your catalog slows down your thinking.

The One Thing That Buys You Everything Else

The photographers I know who have never lost a client file are not the ones with the most sophisticated software setup. They are the ones who built simple, boring, consistent systems and ran them without exception.

Set up your folder naming convention today, configure your catalog backup to a separate drive tonight, and subscribe to Backblaze before you go to bed. Your future self, the one sitting across from a client asking for a reshoot of images you cannot locate, will be very grateful you did.