PoE Camera Bandwidth Requirements: Planning Your Frigate Network
If you’re building a local Frigate setup, bandwidth planning is one of the most overlooked variables. You can have perfect cameras and a solid NVR, but undersized network capacity will cripple your system with dropped frames, stuttering, and failed recordings. This guide walks you through the math so you don’t waste money or time troubleshooting preventable network congestion.
The Core Formula: How Much Bandwidth Does One Camera Need?
Most PoE cameras advertise bitrate ranges rather than fixed values. A typical 4MP camera might claim “1–6 Mbps,” which sounds straightforward until you realize the actual consumption depends on several variables.
The primary factors are:
- Resolution — Higher resolution = higher bitrate. A 1080p stream consumes roughly 1–3 Mbps; 4MP consumes 2–6 Mbps; 8MP (5K) consumes 4–12 Mbps.
- Codec — H.265 (HEVC) is roughly 50% more efficient than H.264. If your NVR and cameras support it, H.265 halves your bandwidth bill.
- Frame rate — 30 fps vs. 15 fps is a significant difference. Most cameras let you tune this per stream.
- Compression/quality setting — Cameras have bitrate modes: CBR (constant), VBR (variable), or quality presets. VBR adapts to motion—static scenes use less; action spikes higher.
- Substreams — Many cameras offer a high-res main stream and a lower-res substream. Frigate can be configured to record the main stream while using the substream for live view.
Practical example: A 4MP camera set to H.264, 30 fps, quality-balanced mode might consume 4–5 Mbps average, spiking to 8–10 Mbps during motion. The same camera with H.265 and 15 fps might drop to 1.5–2.5 Mbps average.
Calculating Your Total Network Load
Here’s the realistic approach: assume peak consumption, not average.
If you have four 4MP PoE cameras on your network, and each could theoretically hit 8 Mbps during motion:
- 4 cameras × 8 Mbps = 32 Mbps peak load
Now compare that to your available bandwidth:
- 1 Gigabit Ethernet (1,000 Mbps) — can easily handle 100+ standard 4MP cameras
- 100 Mbps Ethernet — maxes out at roughly 10–15 cameras
- WiFi 5 or 6 — nominally higher capacity, but in practice interference and overhead reduce usable throughput to 50–70% of advertised speed
The key takeaway: Even a modest Frigate setup with decent cameras needs gigabit PoE infrastructure. If your NVR is on 100 Mbps, add a gigabit switch. If you’re mixing WiFi cameras (not recommended, but people do it), account for 30% overhead loss.
Camera Selection Impact on Bandwidth
Different camera classes have wildly different bandwidth profiles. A budget 1080p turret will use 1–2 Mbps; a flagship 8MP PTZ can push 12+ Mbps. When evaluating cameras for your system, check the spec sheet’s bitrate range, but assume the upper bound for motion-heavy areas.
If bandwidth is tight, consider this hierarchy:
- Best balance: 4MP with H.265 codec — Reolink RLC-810A and Reolink RLC-823A are solid choices that sit around 2–4 Mbps average.
- Budget-conscious: 2MP cameras like Reolink RLC-510A or Amcrest IP5M-T1179 drop bandwidth to 1–2 Mbps while still offering reasonable clarity for most use cases.
- High-res requirement: If you need best 4K PoE security camera for Frigate, budget 6–10 Mbps per camera and ensure your PoE infrastructure is oversized.
Network Architecture: Where Bandwidth Matters Most
Your Frigate NVR connects to cameras via Ethernet. The critical link is between your PoE switch and your NVR (or between the switch and your router if your NVR is networked separately).
Bottleneck scenarios:
- PoE switch to router: If your NVR is remote and you’re pushing 40 Mbps of camera streams over a single uplink, that link must be gigabit. A 100 Mbps uplink will drop frames.
- PoE switch capacity: A cheap 8-port “gigabit” PoE switch sometimes has only a 100 Mbps backplane. Check the switch specs—you want switching capacity (in Gbps) to be at least 2–3× your peak camera load.
- PoE injector limitations: If you’re using passive PoE injectors instead of a managed PoE switch, ensure your injector and cabling are rated for the bandwidth. This is rare to be a real constraint, but old Cat5 (non-Cat5e) cabling can theoretically throttle at very high bitrates—use Cat6 or better.
Tuning Cameras for Bandwidth Efficiency
Once your cameras are installed, Frigate gives you granular control. In your config.yml, you can set separate resolutions and frame rates for recording vs. detection:
cameras: front_door: ffmpeg: inputs: - path: rtsp://192.168.1.100:554/stream1 roles: [detect, record] detect: width: 1280 height: 720 fps: 10 record: enabled: true
This example uses a low-res, low-fps stream for motion detection (cheap CPU) and let the camera handle the high-res recording independently. Many cameras support dual streams—use them.
Also check your camera’s web interface for bitrate mode:
- Switch from VBR to constant bitrate (CBR) mode if you want predictable network load (useful for planning).
- Reduce maximum bitrate if your camera offers it—capping a 4MP camera at 4 Mbps instead of 8 Mbps won’t destroy image quality.
Scaling Beyond Four Cameras
If you’re planning a larger system, bandwidth math becomes critical. Eight 4MP cameras at 4 Mbps average = 32 Mbps reserved just for cameras, leaving headroom for other network traffic (NAS backups, streaming to your phone, etc.). A gigabit connection theoretically offers 1,000 Mbps, so this scales comfortably.
However, storage becomes the bottleneck first. A single 4MP camera at 4 Mbps uses roughly 1.8 TB per month with 24/7 recording. Plan your storage accordingly—see our guide on best night vision PoE camera for Frigate for camera + storage balance recommendations.
FAQ
Q: Can I run my Frigate NVR on WiFi?
A: Technically yes, but not recommended. WiFi introduces latency, packet loss, and interference that breaks real-time streaming. Use gigabit Ethernet for your NVR and PoE switch. WiFi-only cameras (like Reolink E1 Outdoor) work for backup monitoring, but not as your primary system.
Q: What if I exceed my bandwidth budget?
A: Drop frame rate (go from 30 fps to 15), reduce resolution on non-critical cameras, or enable H.265 codec. You can also split cameras across multiple PoE switches if your architecture allows. Start with the easiest lever: frame rate reduction saves roughly 50% per cut.
Q: Does PoE power consumption affect bandwidth?
A: No. PoE power and data run the same cable but are electrically isolated. A camera pulling 10W vs. 5W doesn’t impact bandwidth. However, cheaper PoE switches may have power supply limitations that affect how many cameras you can physically power—check the injector/switch wattage spec.