Security & Surveillance Tool
Work out how much network bandwidth an IP camera system needs — per camera, total, and against your switch or NVR uplink capacity.
Quick Answer
Add camera rows by resolution, frame rate and quantity. Pick a codec and scene complexity that apply to the whole system, add overhead for network reality, and check the total against your uplink.
System Settings
These apply to every camera row below.
Cameras
Add each camera group by resolution, frame rate and quantity.
| Label | Resolution | Custom MP | FPS | Qty | Mbps/cam |
|---|
Real bitrate depends on scene content, camera firmware, codec tuning, GOP/I-frame interval and rate-control mode — not a datasheet or guaranteed figure. Manufacturer datasheet values are lab CBR maximums, usually higher than real-world average bitrate.
Formula / Method
Each camera starts from an H.264-at-30fps baseline for its resolution (field-reference values for 2/4/5/8MP, or a linear megapixel-scaled estimate for custom resolutions), scales linearly with frame rate, then applies a codec factor (H.265 ≈ half of H.264, H.265+ ≈ 30% of H.264) and a scene-complexity factor (static/medium/complex). Camera totals are summed, an optional sub-stream is added, then network overhead is applied for the final figure.
Mbps/cam = baseline(MP) × (fps/30) × codec factor × scene factor
Inputs
Per camera row: label, resolution (2/4/5/8MP or custom megapixels), frame rate and quantity. System-wide: codec, scene complexity, network overhead %, optional sub-stream bitrate, and optional uplink capacity to check against.
Uses
Sizing switch uplinks and NVR network interfaces, comparing codec choices before purchase, planning camera rollouts on shared or constrained links, and feeding the bandwidth figure into storage sizing.
FAQ
H.265 (HEVC) typically needs about half the bandwidth of H.264 for the same visual quality. H.265+ (a vendor-tuned variant with smarter rate control) can save around 70% versus H.264 on static scenes, less on busy ones. Check that both the camera and the NVR/VMS support the codec you plan to use.
Modern codecs are content-adaptive — a busy junction with constant motion encodes far more data per second than a quiet night-time hallway, even on the identical camera and settings. Scene complexity is often a bigger swing factor than resolution.
Not necessarily. Manufacturer datasheet bitrates are usually the CBR (constant bitrate) lab maximum, measured on a fixed test scene. Real-world average bitrate with VBR rate control is normally lower and varies with the actual scene. Treat this calculator as a planning estimate, not a guarantee.
Learn More
Project
ITCOREOPS can support camera network design, switch/uplink sizing, PoE budgets, structured cabling and infrastructure documentation.
Disclaimer
Planning-level estimate — real bitrate depends on scene, camera firmware, codec tuning, GOP/I-frame interval and rate-control; not a datasheet or guaranteed figure. Verify against your actual cameras and NVR.
Workflow
Use this calculator before specifying network hardware or committing to a camera count and codec, so uplink shortfalls surface on paper, not on site.
Support
For camera network design, uplink sizing, PoE budgets and operational infrastructure support, visit ITCOREOPS.
Feedback
Report display problems, calculation issues or suggestions for improving this calculator.
Worked example
Inputs: 8× 4MP cameras @ 15 fps, H.265, medium scene, 20% overhead, no sub-stream.
Result: per camera 8 Mbps (H.264 base) × (15/30) × 0.5 (H.265) × 1.0 (medium) =2 Mbps; × 8 cameras = 16 Mbps; + 20% overhead = ≈19.2 Mbps total. On a 1 GbE uplink (≈940 Mbps usable) that's comfortably fine.
English available
Prefer English?
DCIM Professionals is also available in English.
