I’ve watched photographers lose months of client work not because their hard drive failed, but because their catalog was so disorganized they couldn’t find the files even when they were technically still there. The drive was fine. The images were intact. But three years of haphazard folder naming, missing previews, and a single catalog bloated past 40GB had turned their archive into a black hole. That’s not a backup problem. That’s a catalog problem, and it’s more common than anyone wants to admit.

What a Catalog Actually Is (And Why Most Photographers Get This Wrong)

Lightroom’s catalog is not your photos. I want to be direct about that because the confusion around this point causes real damage. The catalog is a database, specifically a SQLite file with a .lrcat extension, that stores every edit, keyword, star rating, and collection you’ve ever created. Your raw files live somewhere else entirely, on whatever drive you pointed Lightroom toward when you imported them. The catalog just knows where they are and remembers what you did to them.

This architecture is powerful, but it means you have two things to protect, not one. If your catalog file gets corrupted or deleted and you only backed up your raw files, every hour you spent editing is gone. Conversely, if your raws disappear but your catalog is intact, you have a perfectly organized record of files that no longer exist. Neither scenario is acceptable for a working professional.

Building a Folder Structure That Survives Five Years

The folder structure you build today is the one you’ll be fighting with in 2029, so get it right. I organize everything under a root folder called PHOTO_ARCHIVE, with subfolders by year, then by client or project. A typical path looks like this: PHOTO_ARCHIVE / 2024 / Hendricks_Wedding_0615 / or PHOTO_ARCHIVE / 2024 / Commercial / TechCorp_ProductShoot_Q3. Every folder name includes a date fragment, no exceptions.

Inside each shoot folder I keep three subfolders: RAW, EXPORTS, and SELECTS. RAW holds the original files, untouched. EXPORTS holds the full-resolution JPEGs or TIFFs I deliver. SELECTS is where I put smart collection exports or any curated subset I needed to reference later. This three-folder system costs me about 45 seconds per job to set up and has saved me from client requests for “that photo from last October” more times than I can count.

For the catalog itself, I run one catalog per year. Not one master catalog for everything, not one catalog per shoot. One per year. My 2024 catalog sits at around 8GB right now, which keeps preview rendering fast and backups manageable. At year’s end I close it out, export a final backup, and start fresh. Old catalogs get archived to my secondary NAS and I know exactly where every year lives.

Catalog Backup Settings Nobody Actually Changes

Open Lightroom, go to Catalog Settings, and look at the backup frequency. The default is “Once a week.” Change it to “Every time Lightroom exits.” Yes, it adds ten seconds when you quit. Do it anyway.

Those backups go to a Lightroom Backups folder by default, usually buried somewhere on your system drive. Move that destination to a separate physical drive. On my setup, catalog backups land on a dedicated 2TB Samsung T7 that I keep on my desk. The backup files are compressed, so a full year’s catalog backup runs about 1.2GB. I keep the last 60 backups, which takes up roughly 72GB and gives me two months of recovery points.

Here’s the part most people skip: Lightroom’s built-in backup does not back up your previews folder. That folder, named yourCatalogName Previews.lrdata, can be several gigabytes and contains all the rendered previews that make browsing fast. You don’t need to back it up, strictly speaking, because Lightroom can regenerate previews from raws. But regenerating previews for a 10,000-image catalog takes hours. I include the previews folder in my nightly Time Machine backup and on my Backblaze cloud backup, which runs continuously at around $9 a month. Cheap insurance.

The Moment That Taught Me to Test, Not Assume

My twins are 11 now. A couple of years ago, one of them wandered into my office while I was on a call and, through a sequence of clicks I still can’t fully reconstruct, moved an entire folder of client proofs to the trash and emptied it. Around 340 JPEGs, gone from the export folder. I heard the Finder sound, wrapped up my call, and had every file restored from my Time Machine backup in about 90 seconds.

I tell that story not to brag but to make a specific point: the restore worked because I had tested the restore process before I needed it. I knew exactly which drive to navigate to, which folder structure to look in, and how Time Machine’s “Enter Time Machine” interface worked under pressure. Most photographers back up religiously but have never once practiced getting files back. Set a calendar reminder right now, once a quarter, to restore a random folder from backup and confirm the files open correctly. Backups you’ve never tested are just optimism.

When to Use Multiple Catalogs vs. One

The one-catalog-rules-everything approach sounds efficient but creates fragility. A single catalog holding ten years of work is a single point of failure with an increasingly long rebuild time if something goes wrong. More practically, it gets slow. Once a Lightroom catalog passes about 15GB, you’ll feel it in preview load times and filter response.

My split-by-year method keeps individual catalogs lean and fast while keeping the archive accessible. If a client from 2021 calls, I open the 2021 catalog, find their images in under a minute, and close it. The 2024 catalog I’m actively working in never has to carry that load. If you shoot significant volume across different business types, say, weddings and commercial work, you might split by year and business line. Just document your own system somewhere you’ll actually find it.

Your catalog structure is a business decision as much as a technical one. Treat it that way from day one, and you’ll spend less time hunting for files and more time making them.