Shooting Ratio Calculator: Footage Hours and Storage Needed

Nick HartyBy Nick HartySeptember 14, 20263 min read

What it does

The shooting ratio calculator multiplies finished runtime by your shooting ratio and the number of cameras rolling to get hours of footage, then uses the recording data rate to estimate storage for one copy of the camera originals, in total and per shoot day. Presets cover ProRes and H.264 or H.265 at 100 Mbps, and any data rate can be typed in.

On this page
  1. Using the calculator
  2. The formulas
  3. Worked example
  4. Apple's published ProRes rates
  5. Storage the estimate misses
  6. Where this fits

Shooting ratio calculator

Scripted features often land between 10:1 and 20:1; documentaries go much higher

Storage for camera originals

12.09 TB

one copy; plan for at least three

Footage per camera

19 h

1140 min

Total recorded

38 h

2 cameras

Per shoot day

672 GB

Storage uses decimal gigabytes (1 GB = 1,000 MB). Real data rates vary with frame rate, resolution, and image content. Sound files, proxies, and VFX plates add to the total.

Using the calculator

Enter the finished runtime in minutes, the shooting ratio as a single number (12 for 12:1), and how many cameras roll at once. Pick a recording format to fill the data rate, or type the rate from your camera's manual. Choosing a format and then editing the rate switches the format to Custom. Shoot days is only used for the per-day figure.

Before you trust the storage number, compare the data rate field with the table below or with the manufacturer's figure for your exact resolution, frame rate, and codec. The rate is the one input that changes storage in direct proportion.

The formulas

  • Footage per camera (minutes) = runtime × ratio
  • Total recorded (minutes) = footage per camera × cameras
  • Storage (GB) = total minutes × 60 × Mbps ÷ 8 ÷ 1,000
  • Per shoot day = storage ÷ shoot days

Dividing by 8 turns megabits into megabytes, and dividing by 1,000 gives decimal gigabytes, the way drive makers label capacity. Results of 1,000 GB or more are shown in TB.

Worked example

The tool opens on a 95-minute feature at 12:1 with two cameras over 18 shoot days.

  • Footage per camera: 95 × 12 = 1,140 minutes, shown as 19 h
  • Total recorded: 1,140 × 2 = 2,280 minutes, shown as 38 h

For storage, use Apple's target rate for ProRes 422 HQ at 3840 x 2160 and 24p, which is 707 Mbps:

  • 2,280 × 60 × 707 ÷ 8 ÷ 1,000 = 12,089.7 GB, so about 12.09 TB for one copy
  • Per shoot day: 12,089.7 ÷ 18 = 672 GB

Apple's table also lists 318 GB per hour at that setting, and 38 hours × 318 GB = 12,084 GB, which agrees. With three copies the show needs about 36 TB of drives for camera originals before sound, proxies, or VFX pulls. The DIT would size daily shuttle drives off the 672 GB figure, with room for a heavy day.

Apple's published ProRes rates

From the target data rate tables in Apple's ProRes white paper (April 2022), for 24p:

Format1920 x 10803840 x 2160 (UHD)
ProRes 422117 Mbps (53 GB/hr)471 Mbps (212 GB/hr)
ProRes 422 HQ176 Mbps (79 GB/hr)707 Mbps (318 GB/hr)
ProRes 4444 (no alpha)264 Mbps (119 GB/hr)1,061 Mbps (477 GB/hr)

These are targets. Apple notes that actual rates vary with image content, and higher frame rates scale up: UHD ProRes 422 HQ at 30p is listed at 884 Mbps. Raw formats and camera-specific codecs aren't in Apple's table, so take those rates from the camera maker.

Storage the estimate misses

  • Uneven camera use. Every camera is counted for the full ratio. If B camera rolls on about half the setups, enter 1.5 in the cameras field.
  • Sound. Production audio is small next to UHD video, but multitrack WAV files still add up over 18 days.
  • Proxy files, transcodes for dailies, and VFX plates, which add to the total.
  • High-frame-rate and higher-resolution shots mixed into a show. Run those separately at their own rates.
  • Binary capacity. Operating systems that count in binary units report a "12 TB" drive as about 10.9 TiB, so buy with headroom.
  • Backups. The result is one copy. Multiply by the number of copies in your data management plan.

Where this fits

The shooting ratio mostly comes from how much coverage the director shoots. That's a conversation for prep, before anyone orders drives. The assistant editor and post supervisor will want the same numbers to plan ingest time, and the post-production workflow guide covers what happens to the footage after it leaves set.

Frequently asked questions

What is a normal shooting ratio for a feature?

The tool's hint says scripted features often land between 10:1 and 20:1, and documentaries run much higher. The ratio depends mostly on how much coverage the director shoots and how many takes each setup gets.

How much storage does ProRes 422 HQ need per hour?

Apple's ProRes white paper lists 318 GB per hour for ProRes 422 HQ at 3840 x 2160 and 24p, and 79 GB per hour at 1920 x 1080 and 24p. Real files vary with image content.

Does a second camera double the storage?

In this calculator, yes: every camera is counted as rolling for the whole ratio. On set a B camera often rolls less than A, so a lower camera count or ratio may be closer to the truth.

Why does the storage card say to plan for three copies?

The figure is a single copy of the camera originals. The tool suggests planning for at least three, for example a working copy and two backups kept in different places, until the project is finished and archived.

Sources

Work from the whole script instead

Storiara reads your script and keeps page counts, the stripboard, cast day out of days, and the budget connected, so a change in one shows up in the others.

Start Planning for Free
Nick Harty

Nick Harty

Technical Lead, Storiara

Technical architect and full-stack engineer building the core systems that power Storiara. Creates technology that enhances creative workflows.