Frigate Network Requirements: Bandwidth & PoE Guide

Frigate camera network planning

A reliable Frigate network is built around stable camera streams, not around the fastest Ethernet number available. The important questions are how many streams cross each link, whether cameras are isolated, how many direct connections each camera must serve, and whether the NVR also moves recordings to network storage. This guide calculates aggregate camera bandwidth, shows current NIC and managed-switch options near the top, and explains when 1GbE is sufficient, when 2.5GbE is useful, and when 10GbE is justified by the wider storage architecture.

See live hardware Size my workload

Quick answer

What this Frigate workload needs

Wired Ethernet should be the baseline for permanent Frigate cameras when practical. Add the record and detect stream traffic that actually crosses each uplink, give the network headroom, and use go2rtc restreaming when it can reduce duplicate direct connections to a camera. A 1GbE NVR link can support many typical cameras; 2.5 or 10GbE becomes valuable when many streams, NAS traffic or other server workloads share the same path.

Live Amazon hardware

Current products that fit this decision

Compare current Amazon listings relevant to this guide. Product availability and prices can change.

Checking the dedicated Frigate Storage catalogue…

Buying decision

Match the hardware to the bottleneck

Do not upgrade the NVR NIC just because the camera count sounds large. Calculate aggregate Mbps first and identify where traffic converges. A faster link is worthwhile at the real bottleneck—often the NVR-to-core or NVR-to-NAS path—not necessarily on every camera-facing port.

Interactive decision tool

Frigate Network Bandwidth Planner

Use the workload inputs to size a practical Frigate hardware tier before comparing live products. Results are planning guidance; verify current Frigate support, camera bitrates and the exact hardware configuration before deployment.

Compatibility checklist

Four checks before you purchase

Keep live products near the decision

Current Amazon listings appear above the long guide so capacity, interfaces and prices can be checked before deep reading.

Measure the real workload

Use camera bitrate, retention, PoE draw and network aggregation instead of relying on fixed per-camera rules.

Separate application and recording storage

Keep the Frigate configuration/database role distinct from bulk video retention so each storage tier can be sized correctly.

Verify the complete data path

Camera, switch, NVR, storage and UPS are one recording system; a weak link anywhere can affect reliability.

Calculate aggregate camera traffic at the uplink

Add the configured bitrate of each record stream and any separate detect streams that traverse the same network link. Then include live-view or restream clients that leave the NVR host. This produces a more useful number than multiplying camera count by an arbitrary fixed bandwidth. Compare the result with the slowest shared uplink and keep comfortable headroom for bursts and management traffic.

Separate camera links from server aggregation

A single camera usually consumes only a small fraction of a gigabit, so 1GbE at the camera edge is ample. The NVR, switch uplink or NAS link aggregates many streams and may carry backups or playback simultaneously. That is where 2.5GbE and 10GbE can make sense. Spend network budget at aggregation points instead of giving every low-bitrate endpoint a multi-gig port it cannot use.

go2rtc can reduce duplicate camera connections

Frigate includes go2rtc for restreaming and live-view functions. The official documentation explains that restreaming can let Frigate and another consumer use the relayed feed instead of each opening a separate connection to the camera. This is useful for cameras with low connection limits and can simplify the network path. Configure and test one camera first before rolling the design across the whole installation.

Use wired Ethernet for predictable camera transport

Wi-Fi cameras can work, but wireless performance changes with interference, distance, roaming and shared airtime. A wired PoE camera gives the NVR a more deterministic link and combines power with data. For permanent security coverage, that predictability is valuable. If wireless cameras are unavoidable, monitor signal and bitrate stability and avoid assuming a strong speed-test result guarantees continuous RTSP reliability.

A camera VLAN can reduce the trust surface

Segmenting cameras onto a dedicated VLAN lets the firewall control which devices can reach them and whether they can reach the internet. Frigate needs network access to the streams, and management may require DNS, NTP or vendor services depending on the device. Start with the minimum practical rules, document exceptions and keep the NVR routing path simple enough that a firewall change does not unexpectedly stop every camera.

RTSP uses TCP in Frigate camera connections

Frigate documentation notes that it uses TCP for camera RTSP connections. That makes packet loss behavior different from a pure UDP streaming design and reinforces the value of stable switching and cabling. When diagnosing intermittent feeds, inspect link errors, camera reboots and switch logs rather than treating every disconnect as an application problem.

Plan restream and WebRTC ports deliberately

RTSP restreaming is commonly exposed on port 8554, while WebRTC uses its own mapped ports depending on installation mode. Open only what is required and understand whether the service is intended for the local network or remote clients. Avoid broad port exposure just to make a live view work. Network design should preserve the convenience of restreaming without turning the NVR into an unnecessarily exposed endpoint.

NAS recording can make the NVR uplink the bottleneck

When recordings are written to a NAS, camera traffic enters the NVR and storage traffic leaves it again. Depending on topology, the same host NIC can carry both directions plus playback and management. That does not automatically require 10GbE, but it can make 2.5GbE more useful than camera-only math suggests. Model the whole data path rather than only inbound camera bitrate.

Monitor bandwidth after deployment

Frigate exposes system and network statistics that can help show whether the host is approaching a link limit. Switch port counters are also useful for packet errors and traffic trends. Compare peak observed traffic with the planned number. If the system uses only 120 Mbps on a gigabit link, upgrading to 10GbE will not fix a camera authentication or codec problem.

Keep network headroom for failure and maintenance

A network that normally runs at 85 to 95 percent of line rate has little margin for playback bursts, firmware updates, backups or a temporary reroute. Design for lower steady utilization at aggregation points. The exact headroom depends on the site, but 25 percent or more makes troubleshooting and future camera additions less stressful than an uplink sized to the theoretical minimum.

Choose NICs for driver support as well as speed

A 10GbE adapter is useful only if the host operating system, hypervisor and physical network support it reliably. Intel and Mellanox families are common in home labs because driver support is well understood, but exact controller revisions still matter. Verify slot width, PCIe lanes, transceiver or copper requirements, thermals and driver support before treating a marketplace NIC listing as a plug-and-play upgrade.

Document the camera network before it grows

Record camera IPs, switch ports, VLAN IDs, PoE load, uplink path and stream roles. This becomes extremely valuable when a camera is replaced or a switch is upgraded. A network diagram turns a random collection of cameras into an operable system and makes it much easier to identify whether a failure is at the camera, cable, switch, router, NVR or NAS layer.

Questions people ask

Frigate Network Requirements FAQs

How much network bandwidth does Frigate need?

Add the actual configured camera stream bitrates that cross the relevant link, then include restream, playback or NAS traffic and keep headroom.

Is Gigabit Ethernet enough for Frigate?

For many home installations, yes. Typical camera streams use only a fraction of 1 Gbps. Upgrade aggregation links when measured or calculated traffic justifies it.

When does Frigate benefit from 2.5GbE?

It becomes more useful when the NVR also moves large recordings to a NAS, serves multiple clients, or aggregates many high-bitrate cameras on one host link.

Does Frigate need 10GbE?

Rarely for cameras alone. 10GbE is more relevant for large systems, fast NAS storage, backups or a multi-purpose server where several high-throughput workloads share the link.

What does go2rtc change on the network?

It can restream camera feeds so multiple consumers use a relay instead of each opening a separate camera connection, and it supports Frigate live-view features.

Should Frigate cameras be on their own VLAN?

A dedicated VLAN is a common security and management choice. Ensure the NVR and required services still have the correct firewall access.

Does Frigate use TCP or UDP for RTSP cameras?

Frigate documentation says it uses TCP for camera RTSP connections.

Can Frigate cameras use Wi-Fi?

They can, but wired Ethernet is generally easier to make stable for continuous recording. Wireless interference and shared airtime can cause intermittent problems.

Do I need a second NIC for Frigate?

Not necessarily. A second NIC can help certain segmented or storage designs, but VLANs and a capable single uplink are enough for many installations.

What should I monitor on the Frigate network?

Watch aggregate bandwidth, link errors, camera reconnects, PoE status and the NVR/NAS uplinks. Measure before upgrading hardware.

Official references and methodology

Verify current Frigate support before deployment