DNxHR LB storage requirements

One hour of DNxHR LB in UHD at 25p takes 60 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.

DNxHR LB: GB per hour

DNxHR LB is per-frame constant (0.68 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.

DNxHR LB storage in GB per hour (2026)
Resolution24p25p30p50p60p
HD 1920×10801415183036
UHD 3840×2160576072120143
4K DCI 4096×2160616477128153
6K 6144×3240138143172287344
8K 8192×4320245255306510612

From GB to a shoot day

A typical shoot day produces 2–4 hours of footage per camera. At DNxHR LB in UHD 25p that is 120–239 GB per camera — before copies. With 3-2-1 backup (three copies) it multiplies to 0.5 TB per three hours of material. The table runs three full shoot-day scenarios:

Shoot-day scenarios with DNxHR LB (UHD 25p, one camera)
FootageRaw data1 TB cards3-2-1 volumeOffload per copy (400 MB/s)
2 h120 GB10.35 TB5 min
4 h239 GB10.70 TB10 min
8 h478 GB11.40 TB20 min

Planning offload and backup

Cards are the second calculation: the calculator on the main page derives card count from daily volume and card size — including the spare that stays locked while offloading.

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 DNxHR LB need?

In UHD at 25p: 60 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.