Wedding Day Backup Workflow: A Photographer's Complete Guide
When I first started shooting weddings, I thought the hard part was the camera changes, the lens switching, and the crazy first dance. I was wrong.
The actual hard part is the files. Wedding shots are once-in-a-lifetime moments, and if you lose them, there's no reshoot. The gear doesn't matter if the cards die and the laptop gets stolen and the cloud sync was off that day. The backup workflow is the job, and a lot of photographers — including me, for years — treat it as an afterthought.
This is the workflow I actually use. It's not glamorous. It's not the workflow your favorite YouTube wedding photographer shows off with a slick Lightroom import montage. It's just what works after eight years of second-shooting, lead-shooting, and once, a panicked phone call from a colleague whose assistant dropped an SD card in a fountain in Macau.
I'll walk you through it the way I explain it to friends — what to bring, how to shoot, how to back up in the field, what to do at the hotel, and what to do when you get home.
What I actually bring on a wedding day
Forget the marketing lists. Here's the real kit I pack the night before, every single time.
Two camera bodies. Always two. Not because the second one is "for backup" — both are working cameras, often with different lenses mounted. If one dies, the other keeps shooting. Right now I'm rotating between my main Lumix GH7 and a slightly older body I keep as a true backup; the OM SYSTEM OM-3 has been my favorite "second body" pick lately because it's tiny, weather-sealed, and the colors match my GH7 well enough that nobody notices in the final edit.
Minimum 6 memory cards. I keep meaning to bump this to 8 but 6 is what I've used for the last four years without issue. I'll go into how I split them below. They live in a small zippered pouch in my main bag, never loose in a pocket — lost cards are how you become a cautionary tale.
Two card wallets. One stays in the camera bag, the other stays on my body (in a discrete inner jacket pocket or a Peak Design camera clip pouch). Redundancy, always.
A small external SSD. This is the real "I am a professional" purchase. Right now I'm using a 1TB SanDisk Extreme Pro portable SSD. It weighs less than my phone and runs off USB-C. I carry it in the same pouch as the cards.
A laptop with card reader. 13-inch MacBook Air is plenty. The point isn't to edit on location — it's to back up the cards to the SSD before I even leave the venue. I'll explain the ritual in a sec.
A "dirty" backup drive that stays home. This is the part most beginners skip, and it's the part that has saved my butt twice. One drive travels with me to the wedding. A second, separate drive sits in my home office and gets the files at the end of the night. Two physically separate locations = real backup.
Oh, and a sharpie. Label every card and every drive with the date before the day starts. Sounds paranoid until you're sorting through 14 SD cards three weddings later and can't tell which one was the seaside ceremony versus the rooftop reception.
How I split the cards (and why)
This is the part where people get cute with spreadsheets and "the 3-2-1 rule" diagrams. Honestly? I keep it stupid simple.
I split the day into three chunks: getting ready + ceremony, cocktail + family formals, reception + open dancing. Each chunk gets two cards — one in each body. So if I'm shooting on the GH7 with the 12-40mm during the ceremony, that card goes back in the wallet when I switch to the reception setup, and a fresh card goes in. Same on the second body.
Why two cards per chunk and not one? Because cards fail. Not often, but enough. SD cards are little plastic rectangles with soldered flash chips and tiny controllers. They get hot in summer, they get yanked mid-write, they get dropped. Having a second card with parallel coverage on the second body means losing one card loses at most one chunk of the day, not the whole day.
Don't reuse cards during a wedding. Don't "save space" by formatting one halfway through. Format the night before, shoot, label, put in the wallet, done.
When the GH7 is on card #2 and the second body is on card #2, I rotate them both out and the next chunk begins. By the end of the night I have a stack of cards in chronological order, each labeled with the chunk.
The in-field backup ritual
Okay, this is the part that sounds extreme but takes about 15 minutes and saves you a year of regret.
At the end of every wedding, before I leave the venue, I sit in my car with the laptop and the SSD. Here's the exact sequence:
- Plug in the SSD.
- Plug in card reader, insert card #1.
- Open Lightroom (or Image Capture, or whatever). I use Lightroom's import-to-second-location feature because I'm already in Lightroom for culling, but you can do the same thing with a free tool like FastRawViewer or just Finder.
- Copy card #1 to `/WEDDINGS/2026-07-XX CoupleName/CARD_01/` on the SSD. I make a separate folder per card so I know exactly what's where.
- Verify the copy. This is the step people skip. Open 3-4 random files from the SSD copy and confirm they're not zero bytes, they open, and the preview renders. A copy without verification is just hope.
- Repeat for cards #2 through #6.
- Do not format the cards. I keep them full until I've done a second backup at home.
This takes about 15 minutes for a typical wedding (4,000-6,000 images, mostly RAW). On the way home I'm listening to a podcast and not thinking about whether the files survived. That peace of mind is worth the drive-time sacrifice.
Some people use a paid service like ShootProof Vault or Photo Mechanic's "verify on copy" setting which does the verification automatically. Both are worth the subscription if you shoot 30+ weddings a year.
At the hotel (or home base): the second backup
If I'm staying overnight — destination wedding, multi-day event, anything outside a 2-hour drive — I do a second copy to a different drive. The original SSD stays in my camera bag; the second backup goes onto a separate drive that does not leave the hotel room (or in a non-hotel case, sits on the desk at home).
Yes, I'm carrying two SSDs on every wedding trip now. Yes, they're tiny. Yes, the bag weight has crept up over the years. Worth it.
Important: The two drives should be different brands or at least different physical units. Don't buy two of the same SSD and call it a backup — same batch, same firmware, same potential failure mode. I keep one Samsung T7 and one SanDisk Extreme Pro so a Samsung firmware bug doesn't take out both copies.
The "dirty drive" at home
Here's the third level. The day after every wedding, before I start culling or editing:
- Copy the contents of the in-field SSD to a designated "wedding archive" drive at home.
- Verify file counts match.
- Don't touch the SSD in the camera bag for 30 days. It sits there as the "fresh" backup. If something happens to the home archive drive — ransomware, house flood, the cat knocks it off the desk — the in-field SSD is the safety net.
After 30 days, if the wedding files are safely in long-term cold storage (cloud + archive drive), I can reformat the in-field SSD and reuse it. Until then, hands off.
This isn't three backups as in "two extra copies." It's three backups in three locations over three time horizons — same-day field backup, next-day home backup, 30-day cold-storage backup. The 3-2-1 rule gets thrown around a lot in photography circles but I think for weddings it's worth being even more paranoid.
Cloud backup (yes, you need it)
I used to be the "cloud is for chumps" guy. Then a friend lost an entire wedding to a ransomware attack on his home NAS and I changed my tune fast.
What I use today: Backblaze B2 bucket, automatic upload via the laptop at home once the SSD is plugged in. Cost is something like $6/TB-month for cold storage. For 100GB of wedding files that's well under a dollar per wedding. The first time it saves a job, you've earned back ten years of subscription fees.
You can use Google Drive, iCloud, AWS S3, whatever. The point is a copy that lives offsite and offline, that ransomware can't touch. Don't rely on a single cloud drive; layer it with a backup service that does versioning.
One more thing: encrypt the upload. Wedding photos often contain minors, private family moments, contract details. A B2 bucket with at-rest encryption is fine; a public Dropbox folder is not.
What about during editing?
Once you're a week out and you've culled and started editing, don't delete the originals from your archive drive until the couple has received their final gallery, downloaded everything, and signed off in writing. I keep wedding archives untouched for at least 12 months post-delivery, longer if the couple paid for a "deluxe" package that includes re-edits.
This isn't a backup strategy per se — it's a business survival strategy. A couple who loses their gallery three years later because they formatted their laptop can come back to you and ask for a re-export. If you deleted their files, you're paying them back out of pocket.
The actual editing workflow I use (briefly, since you asked)
I see a lot of photographers edit on the road during weddings. Please don't. Editing on the wedding-day laptop should be limited to the backup ritual above. Real culling happens at home with the big monitor, the calibrated screen, and zero time pressure.
My actual sequence:
- Day 1: Backup, verify, walk away.
- Day 2-4: First cull pass. I use Photo Mechanic — it's faster than Lightroom for sorting — to flag maybe 30% of images as "keepers."
- Day 5-10: Edit the keepers in Lightroom. Export TIFFs to the archive drive.
- Day 11: Upload final gallery to the client portal (I use Pixieset, but ShootProof is fine too).
- Day 12-14: Deliver, get sign-off, archive everything to cold storage.
- Day 365: If the couple hasn't asked for re-edits, I move their folder to the long-term archive and only touch it if they ping me.
The "if something goes wrong" scenarios
Because they will.
Card fails mid-wedding. Hopefully you're shooting dual-card on bodies that support it (Lumix GH7 does, Sony A7 IV does, most modern mirrorless do). If not, switch to the second body and shoot on the remaining cards. Do not put the failed card back in the camera — it might write to it and corrupt recoverable data.
Card goes missing. Stop and retrace your steps. Check the floor around where you last changed cards. Check your pockets, your bag, the bathroom, the dinner table. Most "lost" cards are in someone's jacket. If truly lost, accept it, move on, and tell the couple before delivery — they'll respect the honesty way more than discovering it themselves later.
SSD fails during the field backup. Don't panic. The cards still have the original files. Buy a new SSD tomorrow and back up again. This is exactly why the cards don't get formatted in the field. The 3-2-1 rule paid off.
Laptop gets stolen from the car. OK, that one's bad. But because the SSD is in the camera bag (not the laptop bag), and the cards are in the wallet, you've still got the originals. Replace the laptop, buy a new SSD, copy the cards back over. Awful day, but not a catastrophic one.
Why I'm more paranoid now than five years ago
The gear got better but the risks got weirder. Crypto-locked NASes, AI-deepfake blackmail attempts on photographers, ransomware crews targeting small studios, even the occasional hardware failure on SSDs that get bounced around in camera bags.
Wedding photography isn't a hobby for the couple paying you. It's once-in-a-lifetime shots of people in their weirdest, most emotional, most irreplaceable state. The backup isn't optional. It's part of the contract the moment you sign it.
If you're just starting out and the SSD+laptop+backup-drive setup sounds expensive — yeah, the kit costs me about $400 total. That's less than the cost of a mid-tier zoom lens. It's the cheapest insurance you'll ever buy for your reputation.
Quick recap (because I know you skimmed)
- Two camera bodies, both shooting, both with cards.
- Six cards minimum, split into 3 chunks × 2 bodies. Don't reuse mid-day.
- In-field backup at the venue: SSD in the car, all cards copied, verified.
- Hotel backup: second SSD, kept separately.
- Home "dirty" backup drive the next day.
- Cloud backup at home, encrypted, automatic.
- Archive the originals for at least a year after delivery.
- Label everything with a sharpie.
That's it. It's not sexy. It's not the fun part of being a wedding photographer. But it's the part that means ten years from now, when that couple shows their kids the photos of grandma walking down the aisle, the files still exist.
And honestly? That's the part of the job I'm proudest of.