VIDEO COSTS
Calculate video bandwidth from plays, watch time and bitrate
A video's duration is not the same as the time every viewer watches. Model plays, watched percentage and average delivered bitrate before comparing hosting capacity. Keep your stored library separate from the amount delivered to viewers.
A reproducible 10,000-play example
Assume 10,000 plays, a ten-minute video, 50% watched, a 10% delivery margin and 3 Mbps average bitrate. The result is 55,000 delivered minutes and 1,237.5 decimal GB. These are hypothetical audience assumptions, not measured traffic or a guarantee of a hosting bill.
| Step | Calculation | Result |
|---|---|---|
| Watched minutes | 10,000 × 10 × 0.5 | 50,000 minutes |
| Delivery allowance | 50,000 × 1.10 | 55,000 minutes |
| Bits to decimal GB | 55,000 × 60 × 3 ÷ 8,000 | 1,237.5 GB |
Why divide by 8,000?
Mbps describes millions of bits per second. Multiplying minutes by 60 converts time to seconds. Dividing by eight converts bits to bytes; the remaining factor converts megabytes to decimal gigabytes. This worksheet uses 1 GB = 1,000,000,000 bytes, not binary GiB. Keep units consistent when comparing a provider's allowance.
Choose a defensible bitrate
Use the average bitrate actually delivered across quality levels if you have it. Upload bitrate or the highest rendition may overstate a normal viewer's transfer. Conversely, treating the lowest rendition as typical can understate it. The HLS inspector lets you compare renditions as separate scenarios; it does not know your real adaptive-quality mix.
Separate library storage from playback
A library of 40 ten-minute videos contains 400 stored minutes even if nobody watches it. A minute-based service can charge for both stored and delivered minutes; a capacity-based plan may constrain storage and transfer differently. Read each plan's units and rounding rules. This calculator's capacity fit checks the modeled limits, not feature parity.
Stress-test the audience before choosing a plan
Rerun with twice the plays, higher completion and a different bitrate. Prefetch, replay and buffering behavior can change transfer, so the delivery margin is an assumption rather than a measured correction. Confirm access controls, DRM, overage terms and live-streaming requirements with the provider. A result saying a quote is needed is intentionally not an invented overage price.
Sensitivity table: the same audience at three bitrates
For 10,000 plays with five watched minutes per play, total watched time is 50,000 minutes. At 1 Mbps that represents 375 decimal GB; at 3 Mbps it is 1,125 GB; at 5 Mbps it is 1,875 GB, before an additional delivery allowance. Tripling average bitrate triples this transfer estimate. A video resolution such as 1080p is not itself a bitrate, so resolution alone cannot determine these totals.
| Average delivered bitrate | Watched minutes | Transfer before allowance |
|---|---|---|
| 1 Mbps | 50,000 | 375 GB |
| 3 Mbps | 50,000 | 1,125 GB |
| 5 Mbps | 50,000 | 1,875 GB |
Reconcile an estimate with actual delivery
Compare the model with the same reporting period and units used by your provider. Record played minutes, the quality mix, repeated viewing and the delivery volume actually billed or reported. A downloaded segment may not be fully watched, and separate audio, playlists, retries and other requests can add traffic beyond a simple video-only bitrate model. Use discrepancies to revise explicit assumptions rather than quietly changing the formula or treating a forecast as a measured result.
Separate short abandoned starts from longer viewing sessions
For a synthetic 10,000 starts at an average 3,000 kbps, suppose 30% watch 20 seconds and 70% watch 180 seconds. Weighted viewing time is 132 seconds per start. Assuming transferred media equals watched media gives 495 decimal GB; assigning every start 180 seconds gives 675 GB. Buffering, prefetch, retries, overhead and additional tracks can increase transfer. Actual delivery logs are needed to calibrate those effects. This is an estimate from explicit assumptions, not measured traffic.
mean_seconds = 0.30 * 20 + 0.70 * 180 # 132
transfer_GB = 3000 * 10000 * mean_seconds / 8000000 # 495
full_length_GB = 3000 * 10000 * 180 / 8000000 # 675Reproduce this example
50,000 delivered minutes, 400 stored minutes, and 1,125 decimal GB before extra delivery. Provider amounts use the tool's dated tariff snapshot.
Load 10,000 plays at 3 Mbps, no delivery margin
Download video-scenario.csv — synthetic data you can save or reference. The diagnostic samples contain no real addresses, credentials or hosted streams. Scenario CSVs document inputs; the calculators do not import CSV.
Download a reproducible reference
Compare three audience sizes, three average bitrates and two delivery allowances. These are arithmetic scenarios rather than a forecast or a provider quote.
Common questions
Is GB the same as GiB?
No. This tool uses decimal gigabytes. Do not compare it to a binary-gigabyte limit without converting units.
Should I add all HLS renditions together?
Not for one viewer's playback estimate. Renditions represent different quality choices; model the actual mix or separate scenarios.
Does the cheapest capacity fit include every feature?
No. Check required features and accepted terms independently before selecting a hosting plan.
Try it with your own scenario
The tool is free to use. Product inputs stay in the local browser workspace. Provider links, where present, are separate from the calculation.
References and scope
Updated 2026-10-24. Examples are illustrative calculations, not measured customer outcomes. Provider prices and terms must be checked at purchase time.