RAW file management: a sane system for terabytes of photos

Somewhere in your office is a drive labeled "2023, SORT LATER." Later never came. RAW file chaos isn't a character flaw; it's what happens when every shoot adds thousands of files and no system decides where they live, what they're called, or when they're allowed to die. Here's a system that makes all three decisions once, so you never make them again.

One root, one pattern, zero exceptions

Everything hangs off a single root folder, not scattered across Desktop, Downloads, and three drives. Inside it, one pattern:

• Photos → Year → Job folder. The job folder is date-first plus client: 2026-06-02_smith-family. Date-first means folders sort chronologically forever; the client name means you can find the Smiths without remembering the date.
• The same subfolders inside every job: RAW (everything off the cards), Selects (the photos you selected, if your workflow separates them), Exports (finished JPEGs as delivered), Docs (shot lists, timelines, the signed contract).
• Organize by shoot, never by device. "Card 1 / Card 2 / drone" folders describe your gear, not your work. Merge everything from a job into one RAW folder at ingest, capture time keeps it sortable.

The point isn't this exact scheme. It's that a boring pattern applied identically to every shoot beats a clever one applied when you have energy. Your folder structure should be so predictable that you could find any file from any year while on the phone with a client.

Files named for a decade, not for tonight

Camera filenames recycle: every few months another _1047.ARW is born, and someday two of them meet in the same folder. Rename on ingest (Lightroom, Photo Mechanic, and most ingest tools do this automatically) to a pattern like 20260602_smith_0001: date, client, sequence. Now every file is globally unique, self-describing, and traceable to its job even if it escapes its folder into an email or a print order.

Two bans worth enforcing: no spaces or special characters (they break scripts, web uploads, and some backup tools), and no version adjectives, final_final_v3_ACTUAL is how deliveries go wrong. Versions belong in your catalog or your Exports folder, not in adjectives.

Cull-then-archive vs keep everything

Here's the math that forces the decision. A full wedding day typically produces 2,000 to 4,000 RAW frames, of which 400 to 800 become delivered images (typical industry ranges, per self-published platform data from Snapeen). That means the majority of every wedding you store, at modern RAW sizes, easily hundreds of gigabytes per job once backups are counted, is frames you already decided weren't good enough. Multiply by a season, then by your 3-2-1 backup copies, and "keep everything" quietly becomes the most expensive subscription you own.

The middle path is the sane one for most photographers. Keep your picks and the plausible near-picks (the second-best frame of each scene, cheap insurance for re-edits and close calls). Delete the hard rejects, blinks, focus misses, the lens cap, after the gallery ships and a buffer period passes. Those frames have no future; you rejected them once with fresh eyes and you'll never choose them later. A tight cull, in other words, isn't just a faster edit. It's a permanently smaller storage bill, which is one more reason culling well matters (start with the complete culling guide if yours is ad hoc).

Put the expiry date in your contract, then honor it

Most photographers keep RAWs forever out of vague guilt: what if they ask? Replace guilt with policy. Choose a retention period you can afford to honor, write it into your contract as an archival clause, "RAW files are retained for X after delivery, then deleted; delivered images are yours to keep", and mention it in the delivery email. (Vague or missing archival terms are a classic contract gap; see the photography contract guide.)

A stated policy does three jobs at once: it lets you reclaim drives on schedule without fear, it turns extended archiving into a sellable add-on rather than a free forever-service, and it sets client expectations before the tearful "we lost our downloads" email arrives, which, with a policy, has a calm answer either way. Where the archive physically lives, working drives vs cold storage vs cloud tiers. Is its own decision, covered in our cloud storage guide.

FAQ