Why Your Storage Estimate Was Wrong: The Variables Most Calculators Ignore

The Producer Who Ran Short on Day Two

A producer on a five-day commercial shoot calculated storage at 120GB per day for a BRAW 6K 12:1 codec at a 10:1 shooting ratio. Five 256GB drives purchased. The math checked out on paper. On day two, the DIT reported that Drive 1 was nearly full. The problem was not the codec or the shooting ratio -- it was everything else: the 1080p proxy files generated in-camera, the dual-system Sound Devices audio, the BTS footage the director had quietly started capturing on a second body, and the working copy plus backup copy now required on separate drives.

The original estimate covered one variable and ignored nine others.

This post identifies each variable a complete storage estimate must account for, shows how they compound, and explains how to use the Storage and Footage Calculator as a base before adding each layer manually.

The codec data rates referenced below are drawn from manufacturer specifications published by Blackmagic Design, ARRI, RED Digital Cinema, and Sony for their respective acquisition formats.

Why Basic Calculators Start From an Incomplete Baseline

A typical storage calculator asks for: codec, bitrate (MB/s), shoot days, and shooting ratio. It multiplies them out and returns a single number. That number is camera originals only. It is the raw amount of footage captured by the principal camera at the specified codec -- nothing more.

A complete production storage estimate must add six categories on top of that baseline number.

Category 1: Proxy Files

Many modern cinema cameras generate simultaneous proxy files alongside camera originals. On the ARRI ALEXA 35, ProRes 422 Proxy files run at approximately 5% of the ARRIRAW data rate. On Sony FX9, simultaneous proxy recording adds around 4MB/s for a 4K ProRes 422 LT proxy. On Blackmagic cameras, a 1080p BRAW proxy adds roughly 12% to the primary file size. If proxy recording is enabled (and on many productions it is, for client preview and dailies), add 5 to 15 percent to the raw acquisition figure.

Category 2: Dual-System Audio

Productions using a separate audio recorder (Sound Devices MixPre series, Zaxcom, Lectrosonics) generate audio files independent of the camera. A Sound Devices MixPre-6 recording 6-channel audio at 48kHz / 24-bit generates approximately 6.3MB per minute per channel. On a 10-hour production day with 6 channels active, that is: 6.3 x 6 x 600 = 22,680MB = 22GB. Small in absolute terms but systematically missing from camera-only estimates on every production day.

Category 3: Overcranked / Slow-Motion Takes

At 4x slow motion (96fps played at 24fps), data generation is 4x the standard rate for the duration of each take. If 20% of your shooting time is slow-motion inserts at 4x overcrank, add 60% to the total acquisition figure for that day. A basic calculator set to your standard frame rate does not account for this multiplication.

Category 4: Backup Copies

Professional data management follows the 3-2-1 rule: three copies of every file, on two different media types, with one copy offsite. This means every byte of acquisition data requires 3x storage capacity in total -- one working copy plus two backups. A basic calculator returns the acquisition data. The real drive purchasing decision is 3x that number.

Category 5: Transcoded Edit Media

When the editing system requires a different format than the acquisition codec (common when ARRIRAW or BRAW is cut on a system without native decoding hardware), the editor generates transcoded media. Transcoding BRAW 6K to ProRes 4444 for editorial approximately doubles the file size. Not every production transcodes for editorial -- but productions that do should add 80 to 150% of the acquisition figure for the transcoded edit drives.

Category 6: Miscellaneous Production Data

BTS footage, stills, sound reports, call sheets, script PDFs, and delivery paperwork all land on production drives. In aggregate this is typically 2 to 8GB per day -- small but systematically uncounted.

Three Complete Estimates vs. Basic Calculator Output

Example 1: Five-Day Commercial, BRAW 6K 12:1, Sony FX9 Principal + BTS Body

Basic calculator output: 120GB/day x 5 days = 600GB

Adding proxy files (10%): +60GB

Adding dual-system audio (Sound Devices, 8 channels): +30GB

Adding overcranked inserts (30% of shoot at 4x): +180GB

Adding 3-2-1 backup multiplier: x3 = 2,610GB total

Complete estimate: approximately 2.6TB across three drives versus 600GB on one.

Example 2: Ten-Day Documentary, ARRIRAW LT, No Proxy, Single-System Audio

Basic calculator output: 3.5TB total at 140MB/s for 7 usable shooting hours per day

No proxy, no overcrank: no adjustment

Adding single-system audio in camera (included): no addition

Adding 3-2-1 backup: x3 = 10.5TB

Adding edit transcodes to ProRes HQ: +4.2TB

Complete estimate: approximately 14.7TB versus 3.5TB from the basic calculator.

Example 3: Three-Day Music Video, RED V-RAPTOR 8K Full Frame RAW, 4x Slow Motion Throughout

Basic calculator output at standard frame rate (24fps, 48fps equivalent bitrate average): 2.4TB

Adding 60% overcrank adjustment for heavy slow-motion usage: +1.4TB

Adding proxy recording: +0.2TB

Adding dual-system audio: +0.05TB

Adding 3-2-1 backup: x3 = 12.2TB

Complete estimate: approximately 12.2TB versus 2.4TB from the basic calculator.

Storage Variables Reference Table

The table below shows which variables to include by production type. Check marks indicate the variable is typically present and must be added to the base estimate.

No production type avoids the 3-2-1 backup multiplier. The first budget error most productions make is treating the acquisition number as the final storage budget rather than as the starting input.

How to Build a Complete Storage Estimate: Step by Step

Step 1: Run the base acquisition estimate in the Storage and Footage Calculator. Enter codec, bitrate, daily recording hours (estimated from shooting ratio and scheduled hours), and shoot days. Record the raw acquisition total.

Step 2: Confirm with the DP and DIT whether proxy recording is enabled on the principal camera. If so, get the proxy bitrate from the camera's manual and add the proxy data rate as a percentage of the primary. On most cameras, proxy adds 5 to 15 percent to the daily acquisition figure.

Step 3: Confirm whether the production uses dual-system audio. Calculate audio data: channels x bitrate x recording minutes per day. A 6-channel, 48kHz / 24-bit session records approximately 6.3MB per minute per channel. Multiply by the estimated daily recording time.

Step 4: Flag any scheduled overcranked or slow-motion setups. For each such setup, estimate the percentage of total daily recording time at the overcranked frame rate and multiply the data for those minutes by the overcrank ratio (4x slow motion = 4x data rate for those minutes).

Step 5: Sum all variables and multiply the total by 3 for the 3-2-1 backup requirement. This is the minimum total drive capacity to purchase or provision before the shoot. If editorial will require transcoded media, add the estimated transcode size on top of that.

At the end of this process you have a full storage budget figure, broken down by variable, that you can defend to a line producer.

Pro Tips and Common Mistakes

Pro Tip: Build the storage estimate as a spreadsheet with each variable in a separate row rather than one lump figure. This lets you identify which line items are the biggest contributors -- and which can be trimmed if budget is tight. On most productions, the 3-2-1 multiplier and the editorial transcodes are the two largest items after raw acquisition. Understanding that breakdown helps you decide whether to reduce shooting ratio, eliminate proxy, or negotiate a smaller editorial transcode window.

Pro Tip: The Shooting Ratio Calculator helps you arrive at an accurate shooting ratio estimate before production, which is the most uncertain input in the base estimate. Most productions overestimate the shooting ratio and then overcalculate storage, or underestimate the ratio and undercalculate. Getting this number from a realistic scene-by-scene breakdown is worth 30 minutes of pre-production time.

Pro Tip: For multi-camera productions, run the Storage and Footage Calculator separately for each camera body, then sum the results. A-camera and B-camera often run different codecs, shooting ratios, and proxy configurations. Lumping them together produces inaccurate estimates when the bodies are shooting different amounts of material.

Common Mistake: Calculating the shooting ratio from scheduled hours rather than from planned coverage. A 12-hour shooting day where 6 hours are given to one scene produces a very different shooting ratio from a 12-hour day covering 8 different locations. Pull the shooting ratio estimate from the script breakdown, not from the day's length.

Common Mistake: Forgetting that the DIT's on-set backup happens during production, not after. Drives must be available for the DIT to begin cloning before the shoot day ends. If the storage budget is tight and drives are arriving just-in-time, the DIT has nowhere to put the clone. The fix: order all drives and have them on location before the first shoot day, not mid-production.

Frequently Asked Questions

How do I calculate storage if I don't know the exact shooting ratio yet?

Use a bracketed estimate. Run the Storage and Footage Calculator three times: once with a conservative shooting ratio (8:1), once with a realistic estimate (15:1), and once with a worst-case figure (25:1). Budget for the realistic estimate, add a 20% contingency buffer, and make sure the worst-case scenario does not exceed the physical drives you can physically bring to set.

Should proxy files be stored on the same drives as camera originals?

Operationally, yes -- during production. Proxies generated from the principal camera typically travel with the camera originals in the DIT's cloning workflow. In long-term archive, proxies may be separated from originals to reduce retrieval costs, since only the originals need to be preserved at full fidelity. During production, keeping them together simplifies the offload process and reduces the risk of a proxy file being separated from its camera original.

What happens to the storage estimate if the shoot goes over its planned shooting ratio?

The estimate scales proportionally. If you planned 15:1 and shoot 22:1, your acquisition data is 47% larger than estimated. This is why the 3-2-1 contingency calculation should include a buffer -- typically 15 to 20 percent above the calculated total -- to absorb shooting ratio overruns without a mid-production emergency drive order.

Is cloud storage a viable replacement for physical drives during production?

Not as a primary storage medium during acquisition. Upload speeds at most locations cannot match modern acquisition bitrates in real time. Cloud storage is viable as the third leg of the 3-2-1 backup -- the offsite copy -- but the on-set working drive and the on-set backup drive should both be physical media at every stage of production until picture is locked.

Related Tools

The Storage and Footage Calculator computes the base acquisition figure from codec, bitrate, and shooting ratio. The Codec Storage Calculator shows file sizes per minute for every common acquisition codec, which is useful for building the per-variable estimate line by line. For managing the offload timeline on set, the Media Offload Time Calculator estimates how long cloning will take given drive speed and data volume.

For how shooting ratio affects storage across different genres and production types, Shooting Ratio Explained covers the benchmarks and how to set a realistic target. For the full context of data management strategy on production, Film Production Storage: The Complete Guide covers acquisition through archive with practical recommendations.

The Number a Producer Actually Needs

The output of a basic storage calculator is the start of an estimate, not the end of one. Every variable covered in this post adds real bytes that real drives must hold on a real production. The 3-2-1 multiplier alone triples the acquisition figure before any other variable is added. Build the full estimate before the drive order goes in -- it is significantly cheaper than an emergency overnight courier from a drive supplier on day two of a five-day shoot.

This post focuses on single-camera productions. Multi-camera live events and broadcast productions involve additional storage architecture considerations outside the scope of a standard acquisition estimate. What variable has most surprised you in a storage estimate that fell short -- and by how much?