Your result
Click Calculate
Enter your values, then click Calculate result.How this calculator helps
Estimate aggregate traffic and modeled link capacity from concurrent streams, supplied rates and a maximum utilization assumption. Per-stream rate is a supplied megabits-per-second assumption, not a loaded application requirement. Multiply it by a whole-number simultaneous stream count, then add other aggregate traffic once. Streams need not mean video; they can represent repeated identical flows. If their rates differ, establish a compatible weighted aggregate separately rather than treating unlike flows as one uniform stream rate.
How to use it
- 1
Select the correct input roles for bandwidth requirement calculator and enter the values described below. The demonstration defaults illustrate the method; they are not independently verified personal measurements or live market data.
- 2
Review utilization reserve and the original source record. Match units, signs and the chosen mode before submitting, rather than relying on a familiar-looking default number.
- 3
Click Calculate result to submit the current fields. Editing an input preserves the prior submitted output until you calculate again; the pending-change message distinguishes that saved output from the new values.
- 4
Check the labeled output against the worked example and independent verification steps. Review operational boundaries before using the result in another document, and keep the complete input basis with a copied answer.
Formula and methodology
Aggregate Mbps = per-stream Mbps×concurrent streams+other Mbps. Capacity = aggregate/(utilization/100). Decimal GB/hour = aggregate×3600/(8×1000).
The calculator applies the displayed arithmetic to the values entered on this device. It does not silently load a local tax rate, currency conversion or commercial assumption.
Worked calculation example
Ten simultaneous streams at 5 Mbps plus 20 Mbps other traffic creates 70 Mbps aggregate load. Planning for at most 70% utilization gives modeled capacity 100 Mbps, or 0.1 Gbps. Sustaining the 70 Mbps load for one hour transfers 31.5 decimal GB. These figures depend on supplied traffic and do not guarantee an actual provider plan will sustain that throughput.
How to interpret your result
Mbps and Gbps here use decimal prefixes: one Gbps is one thousand Mbps. Eight bits make one byte. The supporting data-per-hour value is decimal gigabytes using one billion bytes per GB. It represents the supplied sustained traffic load, not the larger reserved link capacity. Binary GiB quantities and storage-file sizes use a different prefix basis and need explicit conversion before comparison.
For different inputs or formulas, use Download Time Estimator; Time-Lapse Calculator; IPv6 Subnet Calculator.
Related questions this calculator covers
- bandwidth calculator
Scenario comparison
| Scenario | What it shows |
|---|---|
| No reserve | 100% utilization makes capacity equal aggregate load. |
| No streams | only the separately supplied other traffic remains. |
| Doubling flows | identical streams double their contribution to aggregate load. |
Common mistakes to avoid
- Confusing megabits with megabytes.
- Adding reserve as a traffic percentage instead of using the stated utilization model.
- Mixing payload and on-wire traffic without an explicit overhead basis.
Multiply stream rate by count, add other traffic and check that load divided by capacity equals the chosen utilization fraction. Convert one hour of load from megabits to bytes and then decimal GB independently. Set utilization to one hundred percent and confirm capacity equals load. Compare actual observed peak traffic and link constraints separately from the arithmetic.
Authoritative reference. Method and scope reviewed on 5 October 2026. SolvePilot provides the original worked example and bounded browser implementation. Editorial and arithmetic review by Mohammad Qasim does not certify user measurements, a real contract or an individual professional decision. The reference supplies method, unit or source-record context; it does not approve this implementation or its inputs.What can affect the result?
Concurrent traffic model
Per-stream rate is a supplied megabits-per-second assumption, not a loaded application requirement. Multiply it by a whole-number simultaneous stream count, then add other aggregate traffic once. Streams need not mean video; they can represent repeated identical flows. If their rates differ, establish a compatible weighted aggregate separately rather than treating unlike flows as one uniform stream rate.
Utilization reserve
Maximum planned utilization is greater than zero and no more than one hundred percent. Capacity divides load by that fraction so the planned load occupies the selected share of modeled capacity. At seventy percent, reserve is thirty percent of capacity, not thirty percent of traffic. Adding thirty percent to load would produce a different utilization target and should not be substituted for the displayed division formula.
Bits, bytes and prefixes
Mbps and Gbps here use decimal prefixes: one Gbps is one thousand Mbps. Eight bits make one byte. The supporting data-per-hour value is decimal gigabytes using one billion bytes per GB. It represents the supplied sustained traffic load, not the larger reserved link capacity. Binary GiB quantities and storage-file sizes use a different prefix basis and need explicit conversion before comparison.
Rate assumptions
Use either payload traffic or on-wire traffic consistently. If the supplied application rates omit protocol overhead, the worksheet does not invent that overhead automatically. Peak demand can differ from sustained average, and traffic bursts can exceed a simple aggregate estimate. Upstream and downstream should be planned separately when the link or workload is asymmetric. A single combined scalar is not a full network traffic engineering model.
Operational boundaries
The tool does not measure your connection, run a speed test, account for wireless signal, latency, packet loss, shared bottlenecks or provider shaping. A capacity result is a supplied-assumption estimate rather than a purchased-plan recommendation. Zero traffic gives zero modeled capacity, while extremely low utilization can create an unrealistically large numerical requirement. Validate demand with observed traffic before making an actual procurement decision.
Privacy and browser processing
Values entered on this page are processed in the current browser session. SolvePilot does not require an account and does not receive the values entered into the calculator. Refreshing or closing the page clears the working values unless the browser itself restores a previous session. Avoid entering identifying or account information because the calculation needs summary values only.
Accuracy and verification
Accuracy depends first on input quality. Confirm definitions, scales, dates and source information before entering a value. Keep an independent record of any result used for planning because this page does not create an official statement or retain a calculation history.
Limits of this estimate
The tool does not measure your connection, run a speed test, account for wireless signal, latency, packet loss, shared bottlenecks or provider shaping. A capacity result is a supplied-assumption estimate rather than a purchased-plan recommendation. Zero traffic gives zero modeled capacity, while extremely low utilization can create an unrealistically large numerical requirement. Validate demand with observed traffic before making an actual procurement decision.
Sources and review information
Frequently asked questions
Is Mbps the same as MB per second?＋
No. Mbps means megabits per second. Divide by eight to obtain decimal megabytes per second before other time conversions.
Why divide by utilization?＋
The traffic must occupy only that fraction of capacity. A seventy-percent target means capacity is traffic divided by 0.7.
Does the tool load stream requirements?＋
No. Enter rates from your workload records or justified assumptions; application quality settings and codecs can change them.
Does reserved capacity count as transferred data?＋
No. The hourly data row uses actual modeled traffic load, not unused reserved capacity.
Will the result guarantee streaming quality?＋
No. Latency, losses, bursts, Wi-Fi conditions and other bottlenecks are outside this arithmetic estimate.