My twins are nine years old. Curious, fast, and completely unafraid of computers. A few years back, one of them was “helping” me at my desk and managed to drag an entire folder of client proofs into the trash and empty it before I’d even turned around. I had those files restored from a local backup in under 90 seconds. The kid was more upset about getting caught than I was about the files.

That 90-second recovery didn’t happen by accident. It happened because I’d built a system that assumed things would go wrong, and planned for it before they did.

Most photographers I talk to have the opposite approach. They build their file system reactively, adding folders when they need them, naming files whatever Lightroom suggests, and backing up “when they remember.” That works fine until it doesn’t, and when it stops working, it usually stops at the worst possible moment.

Why Your Folder Naming Feels Fine Until It Isn’t

The problem with ad hoc file organization isn’t that it’s messy. It’s that it’s inconsistent, and inconsistency kills searchability at scale.

When you’re shooting 20 sessions a year, you can probably remember that the McKinley family portraits from 2022 are somewhere in a folder called “Fall Jobs.” At 80 sessions a year, that system collapses. You’re spending 15 minutes hunting for files instead of 15 seconds, and that compounds across every export, every revision request, every licensing inquiry from three years ago.

The solution is a naming convention you commit to before you need it. My root structure looks like this: YYYY/YYYY-MM-DD_ClientName_JobType. So a product shoot from April would live at 2025/2025-04-12_Thornfield_ProductCatalog. Every folder, every time, no exceptions. Inside that folder I keep four subfolders: RAW, Selects, Exports, and Delivery. RAW never gets touched after import. Selects are the culled keepers. Exports are sized and watermarked files. Delivery is what the client receives, zipped or linked.

This takes about three minutes to set up per job and saves hours over the course of a year.

The Actual Numbers Behind a Backup Strategy

Here’s where most photographers cut corners because the costs feel optional until they aren’t.

A basic 3-2-1 backup means three copies of your data, on two different media types, with one copy offsite. For working commercial files, I keep a local copy on my editing machine, a mirrored copy on a dedicated 8TB WD My Book ($160), and a cloud backup through Backblaze at $99 a year for unlimited storage. That’s the whole stack for under $260 to start, plus the annual fee.

I test every drive monthly. Not just “plug it in and see if it mounts.” I open a random folder, spot-check five files, and verify they open clean. A drive that mounts is not necessarily a drive that has intact data. This takes maybe 10 minutes a month and has caught one failing drive before I lost anything on it.

For card workflow specifically: I shoot to dual slots when the camera allows it. A primary card writes full-res RAWs. A second card writes JPEGs as a redundancy layer. After every shoot, cards don’t get formatted until both the primary backup and the first offsite sync have completed. That’s a rule, not a guideline.

What Culling Discipline Actually Looks Like

Lightroom’s default import dumps everything into one folder by date. That’s fine as a starting point, but it’s not a system. It’s a pile.

My culling workflow runs in two passes. First pass happens the night of the shoot: I flag obvious rejects (X key) and do nothing else. I’m tired, my eyes are tired, and I don’t trust my judgment at 11pm for fine edits. Second pass happens the next morning: I go through the unflagged images and rate keepers with a 1-star. Only 1-star images get edited. Everything else stays in the folder but doesn’t move forward.

This matters because it means my Selects folder is always clean. When a client comes back six months later asking for an alternate angle from a shoot, I know exactly where to look and exactly what I’ll find. The answer isn’t “let me dig through 800 RAWs.” It’s “give me two minutes.”

Culling ratio varies by job type. For corporate headshots I’m keeping roughly 15% of frames. For editorial work, sometimes 5%. Product photography on a good day, 30-40%. Knowing your own ratios helps you estimate delivery timelines and storage needs before a job starts, not after.

The Business Case for Treating Files Like Assets

Here’s something I learned working newspaper deadlines before I went commercial: the file is the product. Not the shoot, not the edit, the file that lands in someone’s hands in a usable state. Everything else is labor.

When a client calls asking for a high-res version of an image from two years ago, what happens next depends entirely on whether you treated your files like assets or like byproducts. If you have a clean archive, organized and backed up, that call takes five minutes and makes you look like a professional. If you have to say “I’m not sure I still have that,” you’ve just handed a competitor a reason to exist.

I charge a $75 archive retrieval fee for jobs older than 18 months. Clients almost never complain because the files are always there and always delivered fast. That fee has paid for my Backblaze subscription several times over.

Build the system once, maintain it consistently, and it works for you quietly in the background while your competitors are rebuilding their hard drives from scratch.