XAVC-I (Class 300) storage requirements

One hour of XAVC-I (Class 300) in UHD at 25p takes 110 GB. The table below runs the numbers for every common resolution and frame rate — including how many cards and how much backup volume a shoot day actually needs.

Footage Storage Calculator

Source (camera/codec)fpsHoursGB
Footage per day
With all copies
Cards needed
Offload time (1 copy)

Data rates: ProRes/DNxHR are per-frame constants from the Apple/Avid specs; RAW derives from resolution × bytes/pixel (nominal). Details further down this page.

XAVC-I (Class 300): GB per hour

XAVC-I (Class 300) is per-frame constant (1.25 MB per UHD frame per the spec) — the data rate scales linearly with frame rate and pixel count. That is why 50p is exactly twice 25p, and 8K four times UHD.

XAVC-I (Class 300) storage in GB per hour (2026)
Resolution24p25p30p50p60p
HD 1920×10802627335566
UHD 3840×2160105110132220264
4K DCI 4096×2160113117141234281
6K 6144×3240253264316527633
8K 8192×43204504695639371,125

From GB to a shoot day

A typical shoot day produces 2–4 hours of footage per camera. At XAVC-I (Class 300) in UHD 25p that is 220–439 GB per camera — before copies. With 3-2-1 backup (three copies) it multiplies to 1.0 TB per three hours of material. The table runs three full shoot-day scenarios:

Shoot-day scenarios with XAVC-I (Class 300) (UHD 25p, one camera)
FootageRaw data1 TB cards3-2-1 volumeOffload per copy (400 MB/s)
2 h220 GB10.64 TB9 min
4 h439 GB11.29 TB19 min
8 h879 GB12.57 TB38 min

Planning offload and backup

Offload is the underrated line: securing a 1 TB card over a 400 MB/s link takes about 42 minutes per copy. Book the DIT only for wrap and you have booked a night shift.

In the schedule this number belongs in two places: as a card budget on the equipment list and as an offload window in the day plan. TillyGen keeps both in the same plan — change the shooting hours and the offload window moves with them.

Frequently asked

How much storage does 1 hour of XAVC-I (Class 300) need?

In UHD at 25p: 110 GB. At 50p, double that. Every resolution is in the table above.

Are the numbers exact?

ProRes/DNxHR are specified target rates; real files land within a few percent. For capacity planning, use the nominal value plus 10 % headroom.