I once watched a photographer spend forty minutes looking for a client’s edited portraits from six months prior. She had the files, somewhere, but her catalog had become a junkyard. Folders named things like “FINAL_v2_USE THIS ONE” and “exports maybe.” The client was on the phone. She was sweating. She found the images eventually, but she lost something else that day that doesn’t show up in any folder: the client’s confidence.

That kind of chaos doesn’t happen overnight. It creeps in one rushed import at a time.

Why Your Catalog Isn’t Just a Filing System

Most photographers treat their Lightroom (or Capture One) catalog the way people treat their email inbox: functional until it isn’t. But your catalog is actually a relational database. Lightroom Classic’s catalog is a SQLite file that stores every edit, keyword, collection, rating, and metadata change you’ve ever made, completely separate from the actual image files. The photos live on your drive. The catalog tracks everything you’ve done to them.

This is why “my catalog got corrupted” is such a gut-punch. You don’t lose the raw files, but you lose every edit, every cull, every star rating, every virtual copy you built. Thousands of hours of decisions, gone. The catalog file itself is typically small, often under 2 GB even after years of use, but what it represents is enormous. That small file is worth treating like a master negative.

The Folder Structure That Scales Without Breaking

Here is the exact folder hierarchy I use, and have used for over a decade without ever needing to rebuild it from scratch.

At the drive root: Photography. Inside that, three folders: Clients, Personal, and Archive. Inside Clients, each job gets its own folder named with a date-first convention: 2024-09-15_Smith-Wedding. The date goes first so folders sort chronologically without any manual effort. Inside each job folder: RAW, Exports, and Working_Files (which holds PSD or TIFF layers if I’ve done compositing).

I never let Lightroom rename or reorganize my folders. I set up the structure myself, then point Lightroom at it. This way, if I ever switch software, or if Adobe disappears tomorrow, my folder structure still makes sense to a human being looking at it cold.

One rule that has saved me more than once: no spaces in folder or file names. Use underscores or hyphens. Spaces cause problems when files move between operating systems, get referenced in scripts, or end up on a client’s FTP server. This is a newspaper habit. In the wire photo world, a file name with a space could mean the wrong image went out under the wrong caption. I’ve carried that paranoia into my commercial work and I don’t apologize for it.

The Backup Stack That Actually Works

My twins deleted a folder of client proofs two years ago. I had every file restored in about 90 seconds because I run a three-location backup: one external drive connected to my workstation running Carbon Copy Cloner on an hourly schedule, one NAS on my home network using RAID 1 mirroring, and one cloud backup through Backblaze at $9 a month. When the folder disappeared, I opened the CCC backup, navigated to the folder, and dragged it back. The kids still don’t know how close that was.

The catalog specifically, I back up inside Lightroom every time I exit. Go to Catalog Settings > Backup and set it to “Every time Lightroom exits.” The backup location should be somewhere other than the same drive as your working catalog. I keep mine on the NAS. Lightroom’s built-in backup is just a copy of the SQLite file, but that copy has saved edits I would have otherwise lost to a software crash twice in the last five years.

Test your backups. I pull a random image folder from backup and verify it opens correctly on the first Sunday of every month. Takes ten minutes. If your backup never gets tested, you don’t have a backup. You have a ritual that makes you feel better.

Keywording and Collections as a Search Engine

The catalog’s real power isn’t storage. It’s retrieval. If I can’t find an image in under two minutes, my system has failed.

I keyword at import using presets. Every import gets location, client name, year, and job type applied automatically. Then I add specific keywords during culling: portrait, editorial, lifestyle, product, and so on. In five years, I’ve built a keyword library of about 340 terms. It sounds like a lot. It takes about 20 seconds per shoot to apply.

Collections are how I keep active work separated from the archive. I maintain a Current Quarter collection set with individual collections for each active client. Once a job is delivered and invoiced, I remove it from the collection but leave the catalog entry and folder intact. This keeps my workspace clean without deleting anything. A collection is just a pointer to images that already exist in the catalog. It costs nothing to have hundreds of them.

Smart Collections are underused by almost every photographer I know. I have one called Unrated Imports that automatically populates with any image that has no star rating. If something shows up there after a session is supposedly culled, I know I missed something. It’s a quality check built into the software.

The Cost of Starting Over

The single most important thing I can tell you about catalog management is this: the time to build a solid system is before you need it, not after you’ve spent a panicked hour looking for a file while a client waits.

Spend two hours this weekend standardizing your folder structure, setting up a real backup chain, and building five keyword presets. That two hours will return itself inside the first month.

Chris Hartley is a San Francisco-based commercial photographer and workflow consultant. He helps photographers build the business systems that let them focus on shooting.