I used to think catalog management was the kind of thing you figured out as you went. Early in my newspaper days, that was almost true. You shot, you filed, you moved on to the next assignment before the ink dried on the last one. Speed was the whole game. But when I made the jump to commercial photography, I started accumulating years of client work, and the chickens came home to roost. I spent 45 minutes one afternoon looking for a specific product shot from a shoot I’d done 18 months prior. The client needed a high-res version of a file I knew I had. I found it eventually, in a folder labeled “FINAL_v3_USE THIS ONE.” That was the day I completely rebuilt my system from scratch.

Why Your Catalog Isn’t Just a Filing Cabinet

Most photographers treat their Lightroom catalog like a shoebox: photos go in, you find them eventually, life goes on. But a catalog is actually a database, a SQLite file that stores every edit, every metadata tag, every star rating, and every organizational decision you’ve ever made. When that database gets large and fragmented, or when it lives in the wrong place, performance degrades and corruption risk increases.

Lightroom Classic’s catalog file (.lrcat) should never live on an external drive that you unplug while the software is open. It should not live in a synced cloud folder like Dropbox or Google Drive, because those services can corrupt the file mid-write. It belongs on your internal SSD, period. Your actual raw files can and should live on an external drive. The catalog is a map. The raws are the territory. Keep the map fast and local.

The Folder Structure That Survives Five Years

My folder hierarchy goes: Year, then Client Name, then Job Number plus shoot date plus short descriptor. A real example looks like this: 2024 / Martindale_Foods / MF-2024-0312-PackagingHero. Inside that folder I have three subfolders: RAW, Exports, and Selects. RAW holds only originals, never touched after import. Exports holds anything that goes to a client, named with the job number and a four-digit sequence. Selects is where I park smart previews or full-res TIFFs I’m delivering for approval.

I rename every file at import using Lightroom’s built-in rename template. My template string is: {Job Number}-{Date (YYYYMMDD)}-{Sequence # (0001)}. So a file might be MF-20240312-0047.ARW. That file can be identified from its name alone, no metadata required, no catalog open. If someone emails me a filename two years from now, I can find the shoot in under 60 seconds.

Catalog Size, Smart Previews, and the 1:10 Rule

A single Lightroom catalog can handle 500,000 images without buckling, but that doesn’t mean you should let it. I keep one catalog per year, with an archive catalog for anything older than three years. My current working catalog sits at around 22 GB for roughly 80,000 images, and it opens in under 8 seconds on a MacBook Pro M2 with 32 GB RAM.

Smart previews are the secret weapon most photographers underuse. They’re compressed DNG previews that average about 1 MB each, compared to a 45 MB Sony ARW file. When I’m traveling and my primary drives aren’t connected, I can still develop and edit from smart previews. I build smart previews on import for every job. The storage overhead for a 500-image shoot is roughly 500 MB, a completely reasonable tradeoff for the flexibility you gain. Render previews at 1:1 while you’re eating lunch, and you’ll never wait for them when you’re actually culling.

The Backup Protocol I Don’t Negotiate On

My twins are nine years old and they have gotten into my office exactly once since the Great Folder Incident of 2022. They managed to drag an entire client proof folder into the Trash and empty it before I walked back in with my coffee. I had that folder restored from a Time Machine backup in about 90 seconds. I didn’t even raise my voice, which honestly impressed me more than the backup speed.

Here’s the actual setup: my internal SSD backs up to Time Machine on a 2 TB Samsung T7 every hour. My external working drive mirrors to a second external via Carbon Copy Cloner on a nightly schedule. A third drive, a 4 TB WD My Passport, lives in my car and gets manually updated every Friday. I test all three drives the first Monday of every month by restoring a random file. That test takes four minutes and it has saved me from silent drive failures twice in the past three years.

For the catalog specifically, Lightroom’s built-in backup is set to “Every time Lightroom exits.” Those backups go to the second external, and I keep the last 10 copies before letting the older ones delete. The catalog backup is a full copy of the .lrcat file, typically around 20-25 MB. It costs nothing in time or space and it is the single most underused setting in Lightroom Classic.

Metadata: The Work You Do Once, The Time You Save Forever

Every image I import gets a copyright watermark applied via a Develop preset: my name, year, website, and “All Rights Reserved” baked into the IPTC fields automatically. I also apply a job-specific keyword set at import: client name, shoot type, location, and year. It takes about 30 seconds to configure before I hit Import, and it means I can search my entire catalog by client or by location in an instant.

Collections in Lightroom are how I manage deliverables and client-facing sets without moving files. I create a Collection Set for every client, with individual Collections inside for each job. Smart Collections automatically pull images with four-star ratings from a specific keyword, which gives me a rolling portfolio set that updates itself every time I complete a new job and do my culling.

The entire catalog system is really just one question answered at scale: can you find any file, from any client, from any year, in under two minutes? If the answer is no, the system is costing you money, even if you can’t see the invoice yet.