How Much Storage You Actually Need for a Multi-Day Shoot
I once watched a photographer on a shared production genuinely panic on day three of a five-day shoot because he'd calculated storage needs based on a single sample day rather than the actual variation across a full multi-day assignment. He'd budgeted enough space for what a typical day produced, but a single unexpectedly productive day, more setups than planned, more coverage than expected, blew through his buffer with two days still left to shoot.
Storage planning is one of those unglamorous logistics questions that doesn't feel like real photography work until it goes wrong mid-trip, at which point it becomes the only thing that matters. If you want the broader gear and logistics framework I use for planning multi-day assignments generally, I cover it in The Adventure Travel Photographer's Playbook. Here's how I actually think through storage needs for a multi-day shoot.
Why a Single Day's Average Doesn't Predict a Multi-Day Total
The mistake that photographer made, and one I made myself early on, is calculating storage needs by multiplying a typical day's output by the number of days on the schedule. That math looks reasonable on paper, but real shoot days vary considerably in actual output, and a multi-day assignment nearly always includes at least one day that produces meaningfully more than the average.
Weather delays that compress multiple planned setups into a single available shooting window, an unexpectedly cooperative subject who allows for more coverage than scheduled, a location that offers more compelling material than anticipated, all of these push a single day's actual output well past whatever the planning average assumed.
I now budget storage based on my highest realistic single-day output, not my average, multiplied across the full trip length, with additional buffer on top of that. This overshoots on most days, but it means I'm never caught short on the one day that actually produces more than expected.
Raw File Size Realities That Shape the Math
Working in raw format, which I do for essentially all client work given the flexibility it preserves in post-production, means individual file sizes are considerably larger than compressed alternatives, and that reality has to anchor any honest storage calculation rather than being treated as a minor detail.
I calculate storage needs based on my actual typical raw file size for whatever camera system I'm currently shooting, multiplied by a realistic high-end estimate of frames captured in a single demanding day, rather than a lower, more optimistic frame count that undersells how much a genuinely active shoot day actually produces.
This calculation shifts over time as camera systems and resolution capabilities evolve, which means I revisit my personal storage math periodically rather than assuming an estimate from several years ago still applies accurately to my current gear and typical shooting volume.
The 3-2-1 Backup Principle Applied to Field Work
Storage planning isn't just about having enough total capacity, it's about having that capacity distributed safely enough that a single card or drive failure doesn't threaten an entire trip's material. I follow a version of the standard backup principle in the field: multiple copies, on multiple types of storage, with at least one copy physically separated from the others.
In practice, this means every card gets backed up to at least two separate physical drives before I consider that day's shooting safely secured, and those drives get stored in genuinely separate locations within my travel setup, not simply two drives sitting next to each other in the same bag where a single incident could affect both.
On longer or more remote trips, I've also started using cloud backup as an additional layer when connectivity allows, understanding that remote locations won't always support this reliably, but treating it as a valuable extra layer whenever the infrastructure happens to be available rather than skipping it by default.
Card Failure Is Rare But Real, and Redundancy Is Cheap by Comparison
Memory card failure doesn't happen often, but when it does happen mid-trip with no backup yet made, the cost is total and unrecoverable for whatever material was on that single card. Given how genuinely inexpensive additional storage capacity is relative to the cost of losing even a single day of client work, I treat redundancy as a near-mandatory expense rather than an optional upgrade.
I use multiple smaller cards rather than one very large card whenever practical, specifically because a card failure then only threatens a fraction of a day's work rather than potentially an entire multi-day trip's material if a single large card fails partway through. This is a deliberate tradeoff of convenience for genuine risk reduction.
I also test every card before a trip begins, formatting fresh and running a basic write-read check, rather than assuming a card that performed fine on the last several trips will continue performing reliably indefinitely. Cards do wear out, and catching a degrading card before a trip beats discovering it mid-shoot.
Backing Up in the Field Without Reliable Power or Internet
Remote adventure locations frequently lack reliable power access, which means backup routines have to account for genuinely limited charging opportunities rather than assuming laptops and external drives will always have full battery available whenever backup time comes around each evening.
I carry portable power solutions specifically sized to get a full backup routine done each night regardless of whether reliable outlet power is available at camp or a remote lodging location, treating backup power capacity as its own separate line item in trip planning rather than assuming general device charging needs will happen to cover it.
Internet access for cloud backup is often unavailable entirely in genuinely remote locations, which means the physical, offline backup routine, multiple drives, careful physical separation, has to be treated as the primary and fully sufficient system on its own, with cloud backup as a bonus rather than something the core plan depends on.
Planning Around Unpredictable Shooting Volume, Not Just Trip Length
Some activities and assignments naturally produce more frames per day than others, and I've learned to weight my storage planning around the specific nature of the assignment rather than applying a flat per-day estimate across every type of shoot regardless of its actual demands.
A fast-action sequence, skiing, mountain biking, paddling in moving water, tends to produce a much higher frame count per useful moment than a slower, more deliberate shoot like a portrait-heavy editorial assignment, simply because capturing the right instant in fast motion often means shooting in bursts rather than single, carefully composed frames.
Understanding the specific shooting style a given assignment calls for, before the trip starts, lets me calibrate storage planning to the actual demands of that specific work rather than relying on a generic multi-day estimate that doesn't account for how differently various types of adventure photography actually consume storage capacity.
Video Adds an Entirely Different Storage Calculation
When an assignment includes video capture alongside stills, which happens increasingly often given how many clients now want both deliverables from a single trip, the storage math changes dramatically, since video file sizes at any reasonable quality level dwarf even a large volume of raw stills captured across the same day.
I calculate video and still storage needs as two entirely separate line items rather than lumping them into one combined estimate, since underestimating video's actual storage appetite by treating it as a minor addition to still photography needs is one of the more common ways multi-day storage planning goes wrong for photographers newer to hybrid deliverables.
For any assignment that includes meaningful video capture, I bring noticeably more total storage capacity and more backup drives than a stills-only trip of the same length would require, treating video as its own major storage category rather than an afterthought layered onto a stills-focused plan.
What I Actually Pack for a Typical Multi-Day Assignment
For a typical multi-day adventure assignment involving stills only, I pack enough card capacity to cover my highest realistic single-day estimate for the full length of the trip without needing to reuse a card before backing it up, plus a meaningful buffer beyond that calculated total for the unexpectedly productive day that inevitably shows up.
I pair that card capacity with at least two separate backup drives, sized to hold the full trip's expected total output with room to spare, stored and used in a way that keeps them physically separated from each other throughout the trip rather than traveling together in the same case where a single incident could compromise both.
This setup adds real weight and cost to a trip, and I've heard photographers push back on carrying this much redundant capacity as overkill. I'd rather carry the extra weight than risk losing even a single day of irreplaceable client work to a storage shortfall or a single card failure with no backup made yet.
Adjusting the Plan for Genuinely Remote, No-Backup-Opportunity Trips
Some multi-day trips involve genuinely no opportunity to offload or verify backups until the entire trip concludes, no lodging with power, no return to a base camp, just continuous field time until the assignment wraps. These trips call for an even more conservative storage plan than a typical multi-day assignment with nightly backup opportunities built in.
For trips like this, I carry meaningfully more total card capacity than I'd need for a trip with regular backup windows, since every card has to survive the entire trip length without any intermediate backup opportunity, and a single card failure on a no-backup trip threatens a much larger share of the total material than it would on a trip with nightly backup routines already completed.
I also test this exact no-backup scenario mentally before committing to it for a real assignment, walking through what a single card failure would actually cost given the specific plan, and adjusting card count and redundancy until that worst-case loss feels genuinely acceptable rather than catastrophic to the overall assignment.
Organizing Files in the Field So Nothing Gets Overwritten or Lost
Storage capacity alone doesn't solve the problem if the actual organization of files in the field is sloppy enough that something gets accidentally overwritten or a backup step gets skipped in the fatigue of a long shoot day. I've built a strict, repeatable naming and folder convention that I follow identically on every trip, regardless of how tired I am at the end of a long day.
Every card gets labeled physically and tracked on a simple written log noting which day and which general subject matter it covers, backed up to labeled folders that mirror that same structure across both backup drives. This might sound excessive for a solo operator, but on a multi-day trip with dozens of cards cycling through use, memory alone isn't reliable enough to track which cards have been safely backed up and which haven't.
I never reformat or reuse a card until I've physically confirmed, not just assumed, that both backup copies exist and are readable. This confirmation step takes a few extra minutes each night but has caught more than one near-miss where a backup appeared to complete but had actually failed partway through, something that would have gone unnoticed without this verification habit built in.
This kind of unglamorous, disciplined organization matters just as much as the raw storage math itself. A trip with technically sufficient total storage capacity can still lose material if the actual field workflow isn't disciplined enough to guarantee that capacity gets used correctly and verified consistently throughout a demanding multi-day schedule.
Budgeting the Actual Dollar Cost of Storage Into a Project Quote
Storage and backup equipment represents a real, recurring cost that I've learned to price into project quotes explicitly rather than treating as a sunk overhead absorbed silently into my general business expenses. Cards wear out, drives eventually fail or get replaced, and cloud backup services carry ongoing subscription costs that scale with how much material a given project actually generates.
For larger multi-day assignments specifically, I now include a specific line item covering data management and backup in my quotes, rather than folding that cost invisibly into a flat day rate that doesn't distinguish between a lean single-day shoot and a demanding two-week expedition with dramatically higher storage and backup demands.
Clients have generally responded well to this transparency, since it makes clear exactly what they're paying for rather than leaving data security as an unstated assumption buried inside a broader fee. Being upfront about this cost has also given me the ongoing budget to keep replacing aging cards and drives proactively, rather than pushing worn equipment past the point where reliability starts to genuinely suffer.
Revisiting the Whole Storage Plan After Every Major Trip
After every genuinely demanding multi-day trip, I take time to review whether my storage and backup plan actually held up as designed, or whether a specific assumption, about daily output, about backup timing, about redundancy levels, turned out to be wrong once tested against real field conditions.
This review has led to real changes over time, adjusting my baseline storage estimates upward after a trip that produced more material than expected, or refining my backup verification routine after catching a near-miss that could have gone unnoticed with a less careful process. Treating the storage plan as something that improves iteratively, rather than something finalized once and applied unchanged to every future trip, has made each successive assignment noticeably more secure than the one before it, and it's the single habit I'd most recommend to any photographer who's built a storage plan once and never revisited it since. Treating the plan as a living document, rather than a fixed checklist copied unchanged from trip to trip, is what actually keeps it matching the real demands of the work as both gear and assignments continue to evolve, and that ongoing discipline has quietly become one of the more reliable parts of how I run every multi-day assignment now, regardless of destination, activity, or how many times I've already run a similar trip before.
If you're building out a fuller logistics and gear-planning framework for multi-day assignments beyond storage specifically, I go through that broader planning process in The Adventure Photographer's Playbook.
Reflection Questions
- Is your current storage plan built around a typical day's output, or your highest realistic single-day output across a full trip?
- Do your backup drives travel and get used in a way that keeps them genuinely physically separated, or do they sit together in the same bag?
- Have you tested your memory cards before a trip, or are you assuming continued reliability based purely on past performance?
- If a single card failed mid-trip with no backup yet made, how much material would that actually cost you under your current plan?
Dalton Johnson is a professional adventure and editorial photographer with over a decade of experience creating images on all seven continents. His client work includes Patagonia, GoPro, Arc'teryx, Four Seasons, Nike, Rivian, Big Agnes, Ford Bronco, and 160+ other brands. He runs Dalton Johnson Media as a full-service studio, from pre-production through post and distribution.