Photo Backup Workflow: How Photographers Protect Client Work

Every photographer knows someone with a data-loss story: the corrupted card from a wedding ceremony, the dead drive containing three years of archives, the laptop stolen with the only copy of yesterday's shoot. The uncomfortable truth is that storage failure isn't an "if" — drives have annual failure rates, cards corrupt, and laptops get stolen. The only variable you control is whether a failure costs you a file or a client.

This is the backup workflow that working photographers actually use, stage by stage, from the moment the shutter fires to long-term archive.

The 3-2-1 Rule, Translated for Photographers

The industry-standard rule is simple: 3 copies of every file, on 2 different types of storage, with 1 copy off-site. In photographer terms:

• Copy 1: your working drive (the files you're editing)
• Copy 2: a local backup drive (automatic, on a schedule)
• Copy 3: cloud storage or a drive stored at a different location

The off-site copy is what most photographers skip — and it's the one that saves you from fire, flood, theft, and ransomware, the scenarios that destroy both your working copy and your local backup at once.

Stage 1: On the Shoot

Dual card slots — use them

If your camera has two card slots, configure simultaneous writing (RAW to both, or RAW + JPEG). This is your insurance against card corruption, which is most likely to happen during writing. If you shoot weddings or other unrepeatable events on a single-slot camera, that camera is a business risk — many wedding photographers consider dual slots non-negotiable for a primary body.

Card handling rules

• Never delete images in camera to free space — it invites file-system corruption. Swap cards instead.
• Used cards go in a separate pocket or case, label-side down, and never get reformatted until the shoot is verified on two drives.
• For multi-day events, don't reuse day-one cards on day two if you can avoid it.

Stage 2: Ingest — the Most Dangerous Moment

More photos are lost in the hours after a shoot than at any other stage, because the temptation is to copy files once, see them on the laptop, and format the card. Don't. The ingest routine:

1. Copy — never move — files from card to your working drive.
2. Make the second copy immediately, to your backup drive, before any culling or editing. Ingest tools like Photo Mechanic, Lightroom's secondary-copy option, or a checksum copier (TeraCopy, Hedge) can write to two destinations in one pass.
3. Verify — open a sample of files at 1:1, check the file count matches the card.
4. Keep the cards untouched until the project is delivered, if you have enough cards to rotate. Cards are your third copy during the editing window.

Stage 3: While You Work

Your catalog and edits deserve the same protection as the RAWs. Lightroom catalogs, Capture One sessions, and sidecar files represent hours of work — back them up on the same schedule as image files. Two habits cover this:

• Automated local backup — Time Machine, FreeFileSync, or any scheduled mirroring tool keeping your working drive synced to a backup drive daily.
• Catalog backups on exit — Lightroom offers this natively; say yes weekly at minimum, and let it test integrity.

Stage 4: Cloud — the Off-Site Copy

For most photographers the practical off-site copy is cloud storage. The realistic options:

• Backblaze Personal — flat-rate unlimited backup of one computer plus attached drives. The default recommendation for simplicity and cost.
• Backblaze B2 / Wasabi / AWS S3 — pay-per-GB object storage, better for selective archives and NAS users, used with a sync tool.
• Dropbox / Google Drive — fine for delivered finals and documents; expensive per TB for RAW archives.
• A rotated physical drive — the zero-subscription alternative: two drives, one always at a different location (studio, family member's house), swapped on a schedule. It works if you actually maintain the rotation.

Whatever you pick, the test is the same: if your office burned down tonight, what would still exist tomorrow? If the answer is "nothing newer than last month," your off-site cadence is too slow.

Stage 5: After Delivery — Archive Policy

Decide explicitly — and tell clients — what you keep and for how long. A common professional policy:

• Delivered finals: archived indefinitely or for a stated number of years. They're small; keeping them is cheap goodwill and a re-delivery service clients remember.
• Selected RAWs (the keepers that made the final gallery): archived 1–5 years.
• Rejected RAWs: deleted after delivery plus a safety window (30–90 days). Storing every frame you've ever shot is a cost with no client on the other end of it.

Also be deliberate about delivery-link lifetime. Download links shouldn't live forever — they're unguarded public copies of client work. A defined window (with a clear expiry shown to the client) prompts clients to download promptly and keeps your storage and privacy posture clean.

Test Your Restore — Once a Year

A backup you've never restored from is a hope, not a backup. Once a year, pretend a drive died: pick a random old project and actually restore it from your backup and from your cloud copy. You're testing three things — that the files exist, that they're intact, and that you remember how the restore works under calm conditions rather than learning it in a panic.

The Minimum Viable Setup

If this all feels heavy, here is the floor — the least any paid photographer should run:

1. Dual-slot recording in camera (if available)
2. Ingest to working drive + immediate copy to one backup drive
3. Backblaze (or equivalent) running continuously on the working machine
4. Cards not formatted until delivery

That's two pieces of hardware, one subscription, and zero ongoing effort after setup. Compared to explaining to a couple that their wedding photos no longer exist, it's the cheapest insurance in the business.