Network Bandwidth Calculator
Find the total network bandwidth needed to stream multiple cameras or devices simultaneously — the core sizing calculation for any link carrying sustained, continuous traffic.
Inputs
- Number of Devices
- Bitrate per Device (Kbps)
Paste this into any page — the widget stays live and updates automatically as this calculator improves. Using WordPress or Notion? See the embed guide.
Saved Scenarios
— select 2+ to compare| Metric | |
|---|---|
Total Bandwidth (Mbps)
16.38
Spark says
How it's calculated
Formula
- Devices
- — Number of cameras or streaming devices
What is the Network Bandwidth Calculator?
Streaming devices that run continuously (like CCTV cameras) each consume their full bitrate constantly — this calculator sums per-device bitrate to find the total sustained bandwidth a network link or switch needs to handle.
Use this when sizing an internet uplink or internal network switch to support a planned number of CCTV cameras or streaming devices, checking whether an existing network connection has enough capacity for additional devices, or budgeting for a network upgrade ahead of a device count increase.
How to use it
- 1 Enter the number of devices streaming simultaneously.
- 2 Enter the bitrate each device uses.
Understanding Network Bandwidth Calculator
Sustained-bandwidth applications like continuous CCTV recording present a different network sizing challenge than typical internet usage, and understanding that difference is the key to why this simple multiplication — device count times per-device bitrate — is actually the right approach here, even though it would be an overly pessimistic way to size a network for most other kinds of traffic.
Most everyday internet usage is bursty rather than sustained: loading a web page consumes bandwidth in a short spike, then the connection sits mostly idle until the next page load or download; even video streaming from consumer services typically buffers ahead and doesn't require a perfectly continuous data rate at every instant. This burstiness is exactly why internet service providers can oversubscribe their infrastructure — selling more total nominal bandwidth to their customer base than the underlying infrastructure could support if every customer used their full rated bandwidth simultaneously — and get away with it in practice, because in normal usage patterns, not everyone is bursting at the same moment.
Continuous CCTV recording breaks this assumption entirely. A camera configured for constant-bitrate (CBR), 24/7 recording genuinely does consume its full rated bitrate continuously, every second, for as long as it's operating — there's no bursty, intermittent usage pattern to average out, because the camera is always transmitting video data at essentially the same rate. This means a network link carrying multiple such cameras needs genuine sustained capacity equal to the sum of all the cameras' individual bitrates, not some smaller 'typical usage' estimate that might work for bursty traffic — exactly the straightforward summation this calculator performs, without the more forgiving oversubscription assumptions that make sense for other kinds of network traffic.
This distinction is also exactly why wired Ethernet connections are strongly preferred over Wi-Fi for sustained CCTV bandwidth specifically, beyond Wi-Fi's general reliability concerns. Wi-Fi is fundamentally a shared medium — all devices on the same wireless network compete for the same available airtime, and a wireless access point's total real-world throughput is typically well below its advertised maximum rating, especially once multiple devices, interference, and distance from the access point are factored in. For bursty traffic, this shared, variable nature is often tolerable, since not every device needs peak throughput simultaneously. For sustained, continuous CCTV streams specifically, where every camera genuinely does need its full bitrate available at all times, Wi-Fi's variability and shared capacity make it a poor match — a wired connection, by contrast, provides genuinely dedicated, predictable bandwidth to each connected device, exactly matching what sustained streaming traffic actually requires.
For real-world network planning, the raw sum-of-bitrates figure this calculator produces is best treated as a floor rather than a target to design exactly to — protocol overhead (the additional data consumed by network packet headers, error checking, and occasional retransmissions) typically adds a meaningful percentage on top of the raw video payload bitrate, and running any network link consistently at its absolute rated maximum capacity leaves no margin for momentary spikes or unexpected additional load, which is exactly why the standard practice of adding 10-20% headroom beyond the calculated minimum exists — treating the raw calculation as a floor to build from, not a precise target to hit exactly.
Worked examples
Advantages
- •Simple, direct calculation for sustained-load bandwidth planning, avoiding underestimation from assuming burst rather than continuous traffic.
- •Works for any device count and bitrate combination, from a small home setup to a large commercial installation.
- •Useful for both new network planning and evaluating whether existing infrastructure can support additional load.
- •Straightforward multiplication that's easy to verify and sanity-check.
Limitations
- •Doesn't account for network overhead (packet headers, retransmissions) — add 10-20% headroom for real-world links.
- •Assumes every device streams continuously and simultaneously at its full rated bitrate — actual peak usage may be lower if devices don't all draw maximum bandwidth at the same moment, though CCTV specifically often does approach this worst case.
Common mistakes
- ⚠️ Sizing a network link based on burst or average bandwidth for applications (like continuous CCTV recording) that actually require sustained, near-constant bandwidth for their full operating duration.
- ⚠️ Forgetting to add headroom for protocol overhead, which typically adds a real but often underappreciated percentage on top of the raw payload bitrate.
- ⚠️ Running sustained high-bandwidth loads like CCTV over Wi-Fi rather than wired connections, when Wi-Fi's shared, variable throughput makes it a poor fit for this kind of continuous, predictable-bandwidth requirement.
Tips
- 💡 Add 10-20% headroom beyond the raw calculated bandwidth to account for protocol overhead and avoid running a link at its absolute maximum capacity.
- 💡 For sustained loads like CCTV, always prefer wired Ethernet over Wi-Fi — wired connections provide the predictable, dedicated bandwidth that continuous streaming needs, while Wi-Fi's throughput varies and is shared across all connected devices.
- 💡 When sizing an internet uplink specifically (versus an internal network), remember to check both the upload and download bandwidth of your connection, since CCTV and similar continuous-streaming applications are typically upload-heavy.
- 💡 Verify a switch's backplane capacity (its total internal switching throughput) isn't a bottleneck separately from the uplink bandwidth, especially for larger installations with many ports active simultaneously.
Real-life uses
- Sizing an internet uplink or internal network switch to support planned CCTV cameras or streaming devices
- Checking whether an existing network connection has enough capacity for additional devices
- Budgeting for a network upgrade ahead of a planned device count increase
- Diagnosing whether network congestion could be caused by insufficient total bandwidth capacity
Frequently asked questions
Should this bandwidth run over Wi-Fi or wired?
For sustained loads like CCTV, wired Ethernet is strongly preferred — Wi-Fi's real-world throughput is inconsistent and shared across all connected devices.
Why can't I just size the network for average or typical usage like other internet traffic?
Continuous CCTV recording consumes its full rated bitrate constantly, unlike bursty everyday internet traffic — there's no idle period to average against, so the network needs genuine sustained capacity equal to the full sum of all device bitrates.
How much headroom should I add beyond the calculated bandwidth?
A common practice is adding 10-20% beyond the raw calculated figure, to account for protocol overhead and to avoid running the link at its absolute maximum capacity with no margin for spikes.
Does this calculation apply to upload or download bandwidth?
For CCTV specifically, cameras are typically uploading their video stream to an NVR or cloud service, so upload bandwidth is usually the relevant figure to check against this calculation, not download bandwidth.
Why is Wi-Fi a poor fit even if it has a high advertised maximum speed?
Wi-Fi is a shared medium — all connected devices compete for the same airtime, and real-world throughput is typically well below the advertised maximum, especially with multiple devices, interference, or distance from the access point involved.
calixo.cloud/cctv-networking/network-bandwidth-calculator/ — free calculator, no signup required.