IP CAMERA NETWORKING GUIDE

IP Camera Network Bandwidth & PoE Planning

A practical design method for bandwidth, uplinks, PoE power, NVR storage and N-1 resilience across 100, 300 and 500 cameras.

Video SurveillancePoE BudgetNVR StorageN-1 Resilience

Camera projects become difficult to operate when video bandwidth, switch uplinks, power and storage are planned in separate models. This guide ties the assumptions together from camera edge switches to the recording system.

1. Define the design inputs

Record resolution, codec, frame rate, average and peak bitrate, camera count, peak PoE draw, retention days and the required failure condition. H.265 often uses less bandwidth than H.264, but the actual saving depends on scene motion, GOP settings and vendor profiles.

2. Estimate video bandwidth

Total video bandwidth = camera count × per-camera bitrate × overhead factor
Storage (GB) = bitrate (Mbps) × 86,400 × retention days ÷ 8 ÷ 1,000

Use an overhead factor of about 1.10–1.20 for protocol overhead and bursts. Keep average and peak rates separate: recording needs sustained capacity, while uplinks must tolerate synchronized bursts.

Worked planning cases

CamerasExample bitrateVideo totalWith 15% overhead
1004 Mbps400 Mbps460 Mbps
3004 Mbps1.2 Gbps1.38 Gbps
5004 Mbps2.0 Gbps2.30 Gbps

Group cameras by access switch and size each uplink for the busiest switch, including the N-1 state. A 1G uplink can suit a small 100-camera deployment only when cameras are spread across enough switches. For 300 or 500 cameras, 10G aggregation is generally a safer starting point.

Rule: required uplink capacity ≥ peak camera traffic × growth margin. Verify normal operation and a failed-link condition.

4. Calculate the PoE budget

Sum peak powered-device draw and add design margin. Use camera peak draw rather than idle power, and include infrared illuminators, heaters, microphones and motorized PTZ loads where present.

PoE budget = camera count × peak PoE watts × 1.25 design margin

For 100 cameras drawing 12 W at peak, the planning budget is 1,500 W. Distribute the load across switches and verify each switch power supply, port class and battery-backed power path.

5. Size NVR storage

Convert sustained bitrate into daily storage, then reserve capacity for RAID, filesystem overhead, metadata and expansion. One hundred cameras at 4 Mbps each generate about 4.32 TB per day before overhead; 30 days is about 130 TB raw. Apply the same calculation to 300 and 500 cameras instead of relying on a nominal disk count.

6. Test the N-1 condition

N-1 means one required component may fail while the surveillance service still meets its target. Test one uplink, access switch, PoE power supply and NVR node at a time. After each failure, check remaining link capacity, PoE headroom, recording ingest rate and storage write path.

N-1 acceptance: remaining capacity must cover peak traffic; remaining PoE must cover connected peak draw; recording retention must still meet the requirement.

7. Recommended engineering workflow

  1. Confirm camera and codec assumptions.
  2. Calculate average, peak and overhead-adjusted traffic.
  3. Map cameras to access switches and uplinks.
  4. Calculate PoE budgets per switch and for the site.
  5. Calculate raw and usable NVR storage.
  6. Repeat each check after one component fails.
  7. Add growth reserve and document assumptions.

Engineering boundaries

This is a first-pass planning model. Before procurement and acceptance, verify vendor bitrate tables, VBR behavior, multicast or unicast distribution, recording protocol, RAID write performance, cable length and ambient temperature.

FAQ

Can resolution alone predict bandwidth?

No. Codec, frame rate, scene motion and bitrate controls can matter more than the resolution label.

Should PoE planning use average or peak watts?

Use peak draw with a documented margin, especially for infrared and PTZ cameras.

When should I use the calculator?

Use it to compare scenarios, then replace assumptions with vendor data before final design.

Conclusion

A defensible camera design connects bitrate, uplinks, PoE, storage and N-1 in one model. Start with 100, 300 and 500 camera scenarios, then refine every input with measured or vendor data.