I’ve shot somewhere north of 200,000 images in my career. Early on, I stored photos in folders called “Best Shots,” “Backup,” and “Maybe These.” I lost three months of work to a corrupted drive. That failure cost me money and nearly killed a client relationship. It also taught me that a chaotic file system isn’t just annoying—it’s a liability.

Over the last fifteen years, I’ve refined a naming and folder structure that scales. I’m sharing it because every photographer I mentor makes the same mistakes I did.

Start With a Root Structure That Grows With You

Your hard drive’s top level should have exactly three folders: Active, Archive, and System.

Active holds current and recent projects. I keep nothing older than two years here. Archive stores completed work going back to day one—organized by year, then client name. System contains Lightroom catalogs, templates, presets, and business files. This separation means I’m never digging through five years of weddings to find last month’s corporate headshots.

Within Active, I create folders only for current clients or projects. The moment a job wraps, it moves to Archive. This keeps my active workspace lean and searchable.

Use Naming Conventions That Prevent Disasters

Here’s my non-negotiable naming rule: YYYY-MM-DD_ClientName_ProjectDescription_ShotType

Example: 2024-01-15_SmithCorp_AnnualReport_Portraits_001.CR3

The date prefix does three critical things. First, it makes chronological sorting automatic—no more wondering when you shot something. Second, it prevents filename collisions; if you shoot two jobs on the same day, the client name differentiates them. Third, it’s instantly recognizable in file recovery scenarios.

The shot type matters. I use suffixes like _BTS (behind-the-scenes), _Selects, _Rejects, or _Exports. This tells me at a glance whether I’m looking at raw files or deliverables.

Never use spaces in filenames. Use underscores instead. Spaces cause issues when you’re batch processing, uploading to servers, or moving files between Mac and Windows systems.

Backup Strategy Isn’t Optional—It’s Insurance

I operate a 3-2-1 system: three copies of every shoot (working drive, backup drive one, backup drive two), stored in two different locations, with one copy offsite.

Specifically:

  • Working drive: Fast SSD for active editing
  • Backup one: Second internal drive, updated weekly via Time Machine
  • Backup two: External drive rotated offsite monthly

This sounds excessive until you experience drive failure on a 50-image wedding. Then it’s the best money you’ve ever spent. I’ve had two drive failures in fifteen years. Both times, I recovered everything within hours.

Implement This Today—Not Eventually

Start fresh if you can. If you’re working with legacy images, block off a weekend and reorganize them using this system retroactively. Yes, it takes time. No, you won’t regret it.

For Lightroom users, your folder structure in Lightroom must match your hard drive structure exactly. I’ve seen photographers with internal organization in Lightroom but files scattered randomly on disk. That’s a recipe for losing images when you move drives or restore from backup.

Create a written SOP (standard operating procedure) document for yourself and anyone else handling your files. Document your folder structure, naming conventions, and backup schedule. When a new assistant starts, they should understand your system in one hour.

The Real Payoff

Good file management is invisible when it works. You don’t think about it. But the moment you need to find a specific image from three years ago or recover from a disaster, you’ll know whether you invested in this foundation.

I’m faster than colleagues not because I’m more talented—because I never waste time searching. That efficiency compounds. Over a career, it amounts to thousands of billable hours reclaimed.

Set this up now. Your future self will thank you.