{{ result.summaryTitle }}
{{ result.primaryDisplay }}
{{ result.secondaryText }}
{{ result.statusText }} {{ result.perHourBadge }} {{ result.driveBadge }} {{ result.copyBadge }}
Video Audio Hours Copies {{ videoStorageStage.totalLabel }}
Video bitrate storage inputs
Start from a delivery, event, ProRes, or RAW shoot profile, then adjust the fields.
Enter the video stream rate; megabits per second is the normal camera/export spec.
Use 128-320 kbit/s for compressed stereo or a higher measured value for production audio tracks.
kbit/s
Enter decimal hours, for example 1.5 for 1 hour 30 minutes.
h
Use 1 for a single camera, or the number of parallel recorded angles.
streams
Use 2 for camera original plus backup, 3 for a 3-2-1 style production handoff.
20-50% is common for real shoots; lower values are tighter but easier to overrun.
%
Choose the media size for card count, shuttle drive count, or archive drive count.
Keep this near 1-3% unless your measured files include a different overhead.
%
Use 5-15% when proxies, cache files, or camera metadata move with the footage.
%
10-20% reserve keeps media from filling to the last byte.
%
Used only for budget rows; leave 0 when you do not need a cost estimate.
$/TB
Use 0 for measured CBR/average bitrate; add 10-40% for unpredictable VBR scenes.
%
MetricValueDetailCopy
{{ row.metric }}{{ row.value }}{{ row.detail }}
CheckSignalNext actionCopy
{{ row.check }}{{ row.signal }}{{ row.action }}
Customize
Advanced
:

Video storage planning is a rate-over-time problem with production consequences. The same one-hour recording can be a few gigabytes as an H.264 delivery file, hundreds of gigabytes as an edit-friendly intermediate, or much larger as RAW or high-frame-rate capture. The codec name matters, but the average data rate matters more because storage grows from bits per second multiplied by recording time.

The common mistake is treating resolution as the storage estimate. Resolution, frame rate, bit depth, chroma sampling, scene motion, and codec efficiency influence bitrate, but the drive fills according to the final average bitrate written by the camera, recorder, encoder, or export preset. Variable-bitrate recording adds another wrinkle: a published target can be lower than what busy scenes, concerts, screen captures, or fast sports actually average over a long take.

Bitrate, recording time, backup copies, and headroom flowing into storage demand

Production storage also differs from a single finished file. A shoot plan often needs camera-original media, at least one backup, transfer slack, proxy or sidecar files, and room left on cards or drives so the last few minutes of a take do not fail. For multicamera work, each independent camera angle or ISO stream multiplies the source volume before backup copies are counted.

Bit and byte units are easy to misread. Camera and encoder bitrates are usually written as Mbit/s or Mbps, while storage devices are sold in GB or TB. A byte contains eight bits, so accidentally entering MB/s instead of Mbit/s changes the estimate by a factor of eight. Decimal and binary storage labels can also differ, which is why drive counts should be treated as planning numbers, not exact promises.

Video storage planning factors
Planning factor What changes Why it matters
Average bitrate Video and audio data written each second. It is the main source of file size once duration is fixed.
Duration and streams Total recording hours and independent camera angles. A two-camera event records twice the source media of one camera at the same bitrate.
Copies and headroom Backup policy plus extra space for operational variance. Archive buying usually depends on retained copies, not just the camera card.
Usable fill limit How much of each card or drive is allowed to fill. Leaving reserve reduces failed transfers and last-minute capacity surprises.

How to Use This Tool:

  1. Choose a Recording preset such as 4K ProRes 422 HQ shoot, Long event multicam, or Cinema RAW archive, then switch to custom values as needed.
  2. Enter the Video bitrate and unit. Use the measured average bitrate for existing media, or the camera, recorder, streaming, or export target for planned work.
  3. Add Audio bitrate, Recording duration, and Cameras or streams so the source footage volume reflects every independent angle.
  4. Set Storage copies, Planning headroom, and Card or drive size to match the backup and archive policy.
  5. Open Advanced for Container overhead, Sidecar and proxy allowance, Usable fill limit, Storage price, and VBR spike buffer when those planning assumptions matter.
  6. Use Storage Plan for the main TB and drive count, Shoot Checks for cautions, and the chart tabs to compare duration and codec scenarios.

If the warning list says bitrate or duration is missing, enter a positive video bitrate and recording time before using drive counts or budget output.

Interpreting Results:

Planned storage is the headline reserve for the full copy policy. Source footage total is smaller because it is before backup copies and planning headroom. Capture media count answers the on-shoot card or shuttle-media question, while Backup/archive drive count answers the retained copy set.

  • Total stream bitrate combines adjusted video bitrate and audio bitrate for each stream.
  • Runway per drive shows how long the selected drive size lasts under the current copy and headroom settings.
  • Rough storage budget multiplies planned decimal TB by the entered price per TB.
  • Codec What-If is a relative scenario chart, not a promise of equal perceptual quality across codecs.

A low drive count does not prove a safe shoot plan. Verify the camera's actual average bitrate, media write speed, offload time, file system limit, and backup policy before committing a recording day to a small card set.

Technical Details:

Recorded video size follows a direct data-rate equation. The video bitrate is first normalized to bits per second, then adjusted by the VBR spike buffer. Audio bitrate is added, the combined stream rate is multiplied by seconds and stream count, and the bit total is divided by eight to become bytes.

Container and sidecar allowances are modeled as percentages on top of the essence media. Planning headroom is applied after the retained copy count, because retakes, transfer slack, and archive margin affect the whole storage commitment.

Formula Core

The source media estimate starts with total bitrate, duration, and stream count.

Essence bytes = Total bit/sSecondsStreams 8

The planned reserve then adds overhead, sidecars, retained copies, and headroom.

Planned bytes = Source bytes Copies 1+Headroom
Video storage calculation fields
Field Calculation role Boundary or caution
Video bitrate Normalized to bits per second, with VBR buffer added before audio. Must be greater than 0 for a meaningful plan.
Container overhead Percent added to essence bytes for wrapper metadata and indexes. Allowed range is 0% to 50%.
Sidecar and proxy allowance Percent added after container overhead for related production files. Allowed range is 0% to 300%.
Usable fill limit Selected media capacity multiplied by usable fill fraction. Values above 95% trigger a reserve warning.

With the default 4K ProRes 422 HQ shoot, 707 Mbit/s video plus 320 kbit/s audio for 6 hours across 2 streams produces about 3.82 TB of essence media. After 1.5% container overhead, 8% sidecar allowance, 2 retained copies, and 30% headroom, Planned storage is about 10.89 TB, which rounds to 4 selected 4 TB drives at a 90% usable fill limit.

Accuracy Notes:

Storage estimates are planning numbers, not media certification. Bitrate labels, VBR behavior, filesystem units, offload failures, and production policy can all change the real drive requirement.

  • Use measured average bitrate for existing files when accuracy matters.
  • Add a VBR buffer for unpredictable motion, screen capture, or live production scenes.
  • Confirm that selected media can sustain the required write speed, not only the final capacity.
  • Do not treat codec what-if factors as quality-equivalent transcode guarantees.

Worked Examples:

A short 1080p H.264 delivery recording at 8 Mbit/s video, 192 kbit/s audio, 1 hour, 1 stream, and 1 retained copy stays small enough for ordinary transfer. The Storage Plan should show a low Planned storage value and Shoot Checks will still warn that one copy is not a backup plan.

A long event using the Long event multicam preset multiplies modest bitrate by 8 hours and 4 streams. The result is driven less by the 25 Mbit/s video setting and more by duration, camera count, 2 retained copies, and 25% headroom.

If someone enters 120 MB/s instead of 120 Mbit/s, the warning about byte-per-second units is the recovery cue. Switch the unit back to Mbit/s unless the recorder specification truly reports megabytes per second.

FAQ:

Should I enter target bitrate or measured bitrate?

Use measured average bitrate for existing footage. Use target bitrate for planned recordings, then add a VBR spike buffer when scenes may run above the nominal target.

Why are capture media and archive drive counts different?

Capture media count covers the source footage plus headroom. Backup/archive drive count covers all retained copies plus headroom.

Why does MB/s make the estimate much larger than Mbit/s?

MB/s is megabytes per second. Mbit/s is megabits per second. Since one byte is eight bits, the byte-per-second unit is eight times larger at the same number.

What should I fix when the result shows warnings?

Start with positive bitrate and duration, then review copy count, planning headroom, unit choice, and usable fill limit. Those fields drive the most common warning rows.

Glossary:

Bitrate
The amount of video or audio data written per second.
Essence media
The core video and audio data before container, sidecar, copy, and headroom allowances.
VBR
Variable bitrate recording, where simple and complex scenes can use different data rates.
Sidecar files
Related files such as proxies, LUTs, thumbnails, waveform caches, or metadata.
Usable fill limit
The share of a card or drive treated as safe to allocate in the plan.

References: