CCTV Bandwidth Planning Guide

CCTV Bandwidth Planning Step by Step

Step 1 - Determine camera bitrate

Start with the manufacturer, camera, NVR, or VMS configured bitrate when it is known. If it is not known, use a conservative planning estimate and verify later. The Camera Bitrate Calculator can help estimate a single stream, but it is still a planning heuristic rather than a codec guarantee.

Step 2 - Count simultaneous camera streams

Count the streams that actually cross the network path you are sizing. A switch uplink, NVR port, wireless bridge, router, and WAN connection may each see a different amount of traffic depending on where cameras, recorders, clients, and cloud services sit.

Step 3 - Calculate aggregate bandwidth

Multiply camera count by bitrate per stream, then add the selected overhead. The IP Camera Bandwidth Calculator is built for this camera-count calculation.

Step 4 - Add planning headroom

There is no single mandatory CCTV headroom percentage. The margin depends on how variable the scene is, whether other traffic shares the link, how much future expansion is expected, and how critical the recording path is.

Step 5 - Include other traffic

Workstation traffic, remote viewing, backups, inter-VLAN routing, access-control systems, phones, Wi-Fi bridges, and general network traffic can all share capacity with CCTV. Include them when they cross the same link.

Step 6 - Compare against network capacity

Compare the planned demand against the actual network path, not just the camera switch label. The Network Bandwidth Calculator can combine CCTV and non-CCTV traffic with link capacity and utilization.

CCTV Bandwidth for 4, 8, 16 and 32 Cameras

For illustration, these examples assume 4 Mbps per camera and 10% planning overhead. They are not universal CCTV bandwidth requirements.

Main Stream, Sub Stream and Multiple Viewers

Many IP cameras can provide multiple streams. An NVR may record the main stream, live view may use a lower-bitrate sub stream, and other clients may request additional streams. The resulting network load depends on how the camera, recorder, and VMS handle those requests.

Do not assume every additional viewer always creates a separate full-rate stream from the camera. Some systems relay from the recorder or server. Others use multicast, proxy behavior, or client-specific stream selection. For planning, identify which device originates each stream and which network path it crosses.

Where the NVR Is Located Matters

Cameras and NVR on same switch

If cameras and the NVR are on the same access switch, recording traffic may remain local to that switch. The upstream link may only carry management, viewing, backup, or other network traffic.

NVR across an uplink

If the NVR sits beyond an uplink, all relevant camera recording traffic may need to cross that uplink. That link becomes a critical design point, especially when cameras are grouped on multiple edge switches.

Remote or cloud recording

Remote recording, cloud upload, and off-site VMS access can move the bottleneck to WAN or internet upload capacity. Local switch capacity and internet upload are separate constraints and should be planned separately.

100 Mbps vs Gigabit for CCTV

A nominal 100 Mbps link can be adequate for some small CCTV loads, but it is not a universal camera-count answer. For example, 32 cameras x 4 Mbps = 128 Mbps before overhead, so that particular scenario already exceeds a nominal 100 Mbps link.

A nominal 1 Gbps link provides more capacity, but actual throughput, other traffic, switch design, and topology still matter. Treat link speed as one part of the design, not as proof that every stream will perform correctly.

Bandwidth Planning and Storage Planning Are Connected

Sustained bitrate affects both the network path and the amount of recorded data. A higher bitrate stream requires more network bandwidth while it is active and more storage if it is recorded continuously or for long retention periods.

Use the CCTV Storage Calculator for retention-based estimates, and the NVR HDD Calculator when planning recorder drive capacity. Keep storage sizing separate from switch/uplink sizing, even though both depend on bitrate.

Common CCTV Bandwidth Planning Mistakes

• Sizing by megapixels alone instead of configured bitrate.
• Ignoring camera bitrate settings in the NVR or VMS.
• Forgetting uplink bottlenecks between camera switches and recorders.
• Treating nominal link speed as guaranteed application throughput.
• Forgetting workstation, backup, access-control, or general network traffic.
• Assuming remote or cloud traffic stays local.
• Assuming codec savings are fixed across scenes and manufacturers.
• Ignoring multiple streams, viewers, server relay, or multicast behavior.

FAQ

References

• Axis Communications: Bitrate control for IP video: technical background on bitrate limits, VBR behavior, scene complexity, GOP settings, and storage/network capacity constraints.