IP Camera Bandwidth: Why the Switch (and PoE Budget) Fail Before the Network Does

The basic formula

Formula: Total bandwidth = number of cameras × average bitrate per camera.

Example: 16 IP cameras at 4 Mbps each. 16 × 4 = 64 Mbps total. That's the minimum video traffic your NVR and switch uplink need to handle — with practical headroom added on top for motion spikes and future growth.

That number is correct, and it's exactly what the IP Camera Bandwidth Calculator gives you. But total bandwidth alone doesn't tell the whole story of whether an install will actually work — two other constraints matter just as much, and they're the ones that cause real problems in the field.

What a complete bandwidth picture actually needs

Beyond camera count and average bitrate, a full sizing pass accounts for: resolution, frame rate, H.264 vs. H.265, CBR vs. VBR bitrate mode, main-stream and sub-stream bitrate separately, whether audio is on, recording type (continuous vs. motion), PoE power draw per camera, the switch's total PoE power budget, port speed (100 Mbps vs. 1 Gbps), and NVR uplink speed. Each of these can be the actual bottleneck even when the headline bandwidth number looks fine.

The mistake that actually breaks installs: switch uplink overload

Individual camera ports are rarely the problem — a 100 Mbps port easily carries one camera's stream. The real bottleneck shows up at the switch uplink, where every camera's traffic converges on its way to the NVR.

Example: 24 cameras at 8 Mbps each = 192 Mbps total. If multiple switches all feed that combined traffic through a single 100 Mbps uplink back to the NVR, that uplink becomes the bottleneck — cameras drop frames or the stream stutters, even though every individual port is well within spec. This is a security system; dropped frames aren't a cosmetic issue, they can mean missing footage exactly when it matters. Size the uplink for the sum of everything it carries, not for a single camera's rate.

The mistake that's easy to miss entirely: PoE power budget

Bandwidth and power are two separate constraints, and a network can be sized correctly for bandwidth while still failing on power. PoE switches have a total power budget, and every camera on it draws from that same shared pool.

Example: 24 cameras at 12W each = 288W total draw. If the switch's total PoE budget is only 250W, some cameras simply won't power up or will brown out under load — regardless of how much bandwidth the switch has available. This is the mistake that catches junior technicians most often, because it doesn't show up in a bandwidth calculation at all; it has to be checked separately, camera by camera, against the switch's rated PoE budget.

Rule for the field: always calculate bandwidth and PoE power budget as two separate checks, never one. A network that passes the bandwidth check can still fail on site if the switch's power budget is undersized — and that failure looks like a hardware fault, not a design mistake, which makes it slower to diagnose after the fact.

Putting it together

Run camera count, resolution, fps, and codec through the IP Camera Bandwidth Calculator to get your total bandwidth and recommended uplink. Then, separately, add up each camera's PoE power draw and confirm it against the switch's total PoE budget — not just its per-port maximum. Both checks have to pass; either one alone isn't enough.