Start here
Establish a consistent bitrate model, then replace its assumptions with camera data sheets and measured traffic.
Review bandwidth, per-link uplinks, PoE budget and raw/usable NVR capacity.
Open the camera network planner →Recommended engineering path
- Set resolution, codec, frame rate and scene complexity; verify peak bitrate.
- Aggregate camera traffic and validate access and aggregation uplinks.
- Size PoE power, ports and power resilience using maximum device draw.
- Size NVR capacity for retention and verify failure behavior.
Engineering boundaries
Bitrate varies with scene complexity, GOP, VBR configuration, audio and vendor implementation. Storage also depends on recording policy, RAID, filesystem and retention behavior. N-1 assumes independent dual uplink paths and that either surviving link can carry all camera traffic; validate stack/MLAG, power and switch failure domains separately. This calculator is for preliminary planning and does not replace device specifications or measured acceptance tests.
Frequently asked questions
Why do resolution, codec and frame rate all matter?
Codec efficiency, frame rate, scene motion and image detail change bitrate. Use the estimate for early planning and calibrate with vendor peak settings or measured traffic.
Does an N-1 pass mean there are no single points of failure?
No. The calculator checks modeled dual-uplink bandwidth capacity only. Switches, stack control planes, power feeds, intermediate links and NVR failure domains need separate review.