Security Camera Network Bandwidth

Volume I  ·  May 2026  ·  381 words

A single security camera uploading 2K video continuously consumes 2–8 Mbps of upload bandwidth. Four cameras can saturate a typical cable internet connection's 10–20 Mbps upload capacity. For households with data caps — Comcast's 1.2 TB monthly cap, for example — continuous cloud recording from multiple cameras can consume 500 GB to 2 TB per month depending on resolution and frame rate. Understanding the bandwidth math determines whether cloud recording is feasible or whether local storage is required.

Per-camera bitrate. A 2K camera at 15 FPS encoded in H.264 consumes approximately 4–6 Mbps for continuous recording; in H.265, approximately 2–3 Mbps. A 4K camera doubles these numbers. The Eufy SoloCam S340 and Reolink Argus 4 Pro use H.265 encoding, halving bandwidth requirements compared to H.264 cameras. For event-based recording — the default on battery cameras — bandwidth consumption drops to 1–5% of continuous recording because the camera uploads only when motion is detected. This makes battery cameras viable on connections with limited upload bandwidth.

Wi-Fi channel planning. Each camera streaming video is a persistent Wi-Fi client generating continuous traffic. Multiple cameras on the same 2.4 GHz channel can cause co-channel interference, increasing latency and reducing throughput. The practical limit is approximately 3–4 cameras per 2.4 GHz access point before congestion becomes noticeable. The 5 GHz band provides more non-overlapping channels but shorter range — cameras at the perimeter of a property may have marginal 5 GHz signal strength. A mesh Wi-Fi system or a dedicated outdoor access point is the recommended solution for installations of 4+ Wi-Fi cameras. For PoE cameras connected via Ethernet to an NVR, Wi-Fi bandwidth is irrelevant — all video traffic stays on wired Ethernet, and only the user's viewing device (phone, tablet) consumes Wi-Fi bandwidth when accessing live or recorded footage.