GB to hours for ProRes LT @ 100 Mbps Video

16 GB = about 0.36 hours · fixed video-size estimate · ProRes LT @ 100 Mbps Video

Direct Answer

At ProRes LT @ 100 Mbps, 16 GB stores about 0.36 hours of video

This result uses the fixed ProRes LT @ 100 Mbps Video bitrate profile to turn storage budget back into viewing time from 12.5 MB/s.

For 1 GB, the ProRes LT @ 100 Mbps Video bitrate estimate gives about 0.02 hours of video duration.

Converter Calculator

0.36 hours

Switch

Explanation

Formula: hours = (GB x 1000) / (12.5 x 3600) (bitrate 100 Mbps). Why: this page fixes the ProRes LT @ 100 Mbps Video video bitrate profile so duration-to-size calculations stay tied to one explicit bitrate assumption.

File size (GB): decimal gigabytes of storage, where 1 GB = 1,000,000,000 bytes.

Duration (hours): elapsed video time in hours.

This route is useful when estimating how much video duration fits into a storage budget under the fixed ProRes LT @ 100 Mbps Video bitrate profile.

This conversion is profile-based rather than universal: encoded video size depends on bitrate and duration, so mirror pages should keep the same bitrate profile to remain comparable.

Method & Bitrate Profile

  • Method basis: fixed bitrate estimate inverted to recover duration from storage size at 12.5 MB/s.
  • Profile reference: ProRes LT @ 100 Mbps Video (12.5 MB/s bitrate basis).
  • Consistency rule: direct answer, calculator, FAQ, and common-value rows all use the same fixed bitrate profile for this route.

Common Conversion Values

File size (GB)Duration (hours)
1 0.02
2 0.04
5 0.11
10 0.22
16 0.36
32 0.71
64 1.42
128 2.84

Frequently Asked Questions

Which bitrate assumption is fixed on this page?

ProRes LT @ 100 Mbps with nominal video bitrate 100 Mbps.

How do I reverse File size to Duration?

Use the mirror Duration to File size route; it applies the inverse relationship for the opposite direction with the same assumptions.

Can this be used for upload-time and storage planning?

Yes. It provides baseline estimates useful for archive sizing, CDN planning, and upload budget checks.