Start with the recording model.

Enter physical duration in minutes. This browser calculator estimates quantities from your inputs; it does not inspect media files or select codec bitrates automatically.

Use bitrate for encoded video; pixel model for a specified stored layout.
Elapsed minutes, including any fractional minute.
Video only; 1 Mbps = 1,000,000 bits per second.
Total across channels; 48 kHz × 16 bits × 2 channels = 1.536 Mbps.
Whole complete copies, including the first copy.
Your chosen extra percentage per copy; not a universal recommendation.

45.691 GBPayload, one copy (GB)
42.553 GiBPayload, one copy (GiB)
100.521 GBPlanned, all copies + allowance (GB)
93.617 GiBPlanned, all copies + allowance (GiB)
12.692 MB/sAverage payload rate

60 minutes · 100 Mbps video + 1.536 Mbps audio · 2 copies · 10% extra per copy. Payload: 45,691,200,000 bytes. Planned capacity: 100,520,640,000 bytes.

Convert bits per second to bytes.

This estimator uses eight bits per byte, decimal Mbps and MB/s. One GB is 1,000,000,000 bytes; one GiB is 1,073,741,824 bytes. These are two ways to express the same payload, rather than an extra storage loss.

seconds = minutes × 60
payload bytes = ceil((video Mbps + audio Mbps) × 1,000,000 × seconds / 8)
planned bytes = ceil(payload bytes × (1 + allowance / 100)) × copies
GB = bytes / 1,000,000,000 · GiB = bytes / 1,073,741,824

ceil means round upward to a whole byte. The allowance is rounded per copy before multiplying by the copy count. GB and GiB displays round to three decimal places.

One hour: 100 Mbps video plus 1.536 Mbps audio
QuantityBytesDecimal GB
Video payload45,000,000,00045.000
Audio payload691,200,0000.691
Combined, one copy45,691,200,00045.691
Two copies, 10% extra each100,520,640,000100.521

Specify the stored pixel layout.

The uncompressed model multiplies width, height and aggregate stored bits per pixel. Packed RGB with three 8-bit components uses 24 bits per pixel. A component’s bit depth alone is insufficient: channel count, subsampling and packing affect storage. This tool does not infer those properties.

pictures = ceil(requested seconds × exact picture fps)
bytes per picture = ceil(width × height × stored bits per pixel / 8)
covered seconds = pictures / exact picture fps
audio bytes = ceil(covered seconds × audio Mbps × 1,000,000 / 8)
payload bytes = pictures × bytes per picture + audio bytes

Duration rounds upward to cover whole picture frames; audio covers that same rounded duration. Fractional picture rates use exact rational values. Row padding and frame headers are excluded unless already represented in the entered storage model. This is not a universal DPX or v210 file-size predictor.

One minute: 1920 × 1080, packed RGB 24 bpp, 24 fps, 1.536 Mbps audio
QuantityCalculated result
Picture count1,440
Bytes per picture6,220,800
Video payload8,957,952,000 bytes
Audio payload11,520,000 bytes
Combined, one copy8,969,472,000 bytes (8.969 GB)
Two copies, 10% extra each19,732,838,400 bytes (19.733 GB)

Validate the estimate against your workflow.

A target bitrate is an approximation for a variable-bitrate recording. Apple describes ProRes as VBR, with actual rates varying by encoded content. Enter a measured average or an appropriate documented rate for your exact recording format. The 100 Mbps example is illustrative, not a claimed codec preset.

Average payload rate does not certify peak write throughput or playback performance. Container metadata, file headers, row padding, proxies, caches, additional audio, filesystem allocation and RAID overhead can add requirements. Available drive capacity and existing files are not modelled. Choose an allowance for your workflow and compare representative recordings with their actual byte sizes.

Use the timecode duration calculator to establish elapsed runtime, the audio samples and picture frames calculator for interval relationships, or return to production tools.

Technical references

Worked examples are calculations from the stated inputs, not measured file sizes.