The Folder That Cost Me a Weekend

A few years into running my commercial operation, I opened Lightroom on a Monday morning and watched it spend four minutes trying to find images that had moved over the weekend. Previews were missing. Folders showed question marks. A client was waiting on final selects by noon. I’d done nothing wrong, technically. I’d just never built a system that could survive a drive letter change after a Windows update swapped my external from E:\ to F:\ overnight.

That was a slow-motion disaster, not a catastrophic one. I recovered in about an hour. But it reminded me what I already knew from my newspaper days: a workflow that depends on everything going right is not a workflow. It’s a wish.

Catalog management isn’t glamorous. Nobody posts about it on Instagram. But it is the single structural decision that will either protect your business or quietly undermine it at the worst possible moment.

What a Lightroom Catalog Actually Is (And Why That Matters)

Most photographers treat their catalog like a magic box. Images go in, edits happen, files come out. What’s actually happening is more specific, and understanding it changes how you manage things.

Your Lightroom catalog is a SQLite database file with a .lrcat extension. It does not store your photos. It stores pointers to your photos, plus every edit you’ve made, every keyword you’ve applied, every star rating, every collection. The actual raw files live on your drive, wherever you put them. This means two things that are critical to understand.

First, if your catalog file gets corrupted and you don’t have a backup of it, you lose every edit you’ve ever made, even if all your raw files are completely intact. Second, if your raw files move and the catalog doesn’t know about it, Lightroom throws up question marks and goes looking, burning your time and your nerves.

Lightroom does offer automatic catalog backups, but the default setting ships at “Once a week,” and the backup location defaults to the same drive as the catalog itself. That means if the drive fails, you lose both. Change the backup frequency to “Every time Lightroom exits” and point it to a separate physical drive. On my setup, catalog backups go to a dedicated 2TB Samsung T7 that I keep on my desk.

The Folder Structure That Scales With Your Business

Here is exactly how I organize files, after years of iteration and a few painful lessons.

Root folder on my primary working drive: Photography. Inside that, two subfolders: Client Work and Personal. Inside Client Work, folders follow this format: YYYY-MM_ClientName_ProjectType. So a product shoot for a hardware company in March 2025 becomes 2025-03_AcmeCo_ProductShoot. Inside each project folder: Selects, Exports, and Delivery.

This naming convention does three things. It sorts chronologically in any file browser without needing to rename anything. It makes client projects instantly findable in six months when the client comes back asking for the original files. And it keeps final exports separated from working files, so I never accidentally deliver a layered PSD when a client wanted a JPEG.

Catalog-wise, I run one master catalog for all commercial work, not a catalog per project. I know photographers who do per-project catalogs and they spend half their lives managing exports and imports between them. One catalog, organized with collections and smart collections, handles everything and keeps your search and filtering working across your entire archive.

Backup Isn’t a Single Drive, It’s a Policy

I have three backup drives, and I test each one monthly by attempting to open a random file from it. That sounds excessive until you’ve watched a drive pass every S.M.A.R.T. diagnostic right up until the morning it didn’t. Drives don’t always announce failure. Sometimes they just stop.

My backup structure: the primary working drive (a 4TB WD My Book), one local backup via Carbon Copy Cloner on a 4TB Seagate, and one offsite backup through Backblaze at $9 per month for unlimited storage. After ingesting any shoot, I run a backup before I do anything else, including culling. Not after editing. Not at the end of the day. Before.

The catalog backup sits on the Samsung T7 on my desk, as I mentioned, and Backblaze picks it up as part of the continuous cloud backup. So at any moment, I have the current catalog in three places. Restoring from backup is a ten-minute process, not a crisis.

My twins once got into my office and deleted a folder of client proofs they probably thought were boring landscape photos. I had them restored from the local Seagate backup in about 90 seconds. They were unimpressed. I was privately very relieved and moderately smug about my own systems.

Keywording, Ratings, and the Hours You Get Back Later

Metadata is where photographers consistently leave time on the table. Keywording at ingest takes two minutes. Searching for an untagged image six months later takes twenty.

I apply keywords immediately after import using Lightroom’s keyword sets. I keep one set for client work (industry type, location, shoot format) and one for subject matter (architecture, portrait, food, product). I apply a one-star rating to everything that isn’t an obvious technical failure during the first pass, then work up to three stars for selects and five stars for portfolio candidates. Reject flagging with the X key handles the clear discards.

Smart collections do the rest. I have a smart collection that pulls every five-star image tagged as commercial work taken in the last two years. That’s my portfolio shortlist, always current, always filtered, never requiring manual curation.

The catalog management work happens in the first ten minutes after every shoot. If you push it to later, it won’t happen, and in eighteen months you’ll have 40,000 untagged, unrated, unsearchable files and no idea where anything is.

Build the system before you need it, because the moment you need it, you won’t have time to build it.