Frigate PoE network buying guide
A PoE switch for Frigate must satisfy two independent limits: enough Ethernet ports and enough power budget for all attached cameras. It should also leave room for growth, provide a dependable uplink to the NVR, and expose enough management visibility to troubleshoot a camera that stops responding. This guide keeps current managed PoE switches near the top and uses a calculator to turn camera count and wattage into a practical port and power target instead of choosing a switch only by the number printed on the box.
Quick answer
What this Frigate workload needs
For most wired home Frigate systems, choose a managed PoE+ switch with more ports than today's camera count and at least 20–30 percent power-budget headroom. Gigabit access ports are usually ample for individual cameras; multi-gig becomes relevant mainly for uplinks, high-density aggregation or a broader network design rather than a single IP camera.
Live Amazon hardware
Current products that fit this decision
Compare current Amazon listings relevant to this guide. Product availability and prices can change.
Buying decision
Match the hardware to the bottleneck
Buy the switch for the whole camera plan. An inexpensive 16-port model with a tiny shared PoE budget can be less useful than an 8-port switch with a strong power supply. Compare port count, PoE standard, total budget, uplink speed, management features, fan noise and UPS requirements together.
Interactive decision tool
Frigate PoE Switch Sizer
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.
Count future camera ports before shopping
Start with installed cameras, then add realistic expansion for doorways, side yards, garage, indoor zones or future higher-value viewpoints. A switch that is full on day one forces another power supply, another uplink and another failure point when one camera is added. Leaving 20 to 30 percent port headroom is usually cheaper and cleaner than replacing the switch prematurely.
PoE power budget is separate from port count
A switch may advertise 16 PoE ports but have a shared power budget that cannot run sixteen high-draw cameras at once. Add the maximum wattage of each camera, include infrared, heaters, PTZ motors or illuminators, then apply headroom. The total switch budget must exceed that number. Per-port limits also matter when a camera requires PoE+ or PoE++ rather than basic 802.3af power.
Match PoE standards to the actual cameras
Basic PoE, PoE+ and PoE++ support different power envelopes. Many ordinary fixed cameras fit easily within PoE or PoE+, while PTZ, multi-sensor or heated outdoor models can require more. Buying a higher-power standard is useful only when the connected devices need it. Verify each camera's maximum draw and standard instead of assuming that the word PoE means every switch and camera are interchangeable.
Gigabit access ports are usually sufficient
A typical IP camera consumes only a fraction of 1 Gbps, even when recording at high quality. Gigabit per camera therefore provides ample bandwidth for most Frigate deployments. The more important question is aggregate traffic through the uplink from the camera switch to the NVR or core network. Do not pay for 2.5GbE on every camera port unless the rest of the network design benefits from it.
Managed switching improves diagnosis and isolation
A managed switch can show link state, per-port traffic and sometimes PoE power draw. It also enables VLANs, which are useful for isolating cameras from the general LAN. When one camera goes offline, being able to inspect or power-cycle a port remotely is far easier than physically unplugging cables. These management features are often more valuable to an NVR than headline switching capacity.
VLANs can reduce camera exposure
Many users place cameras on a dedicated VLAN with firewall rules that restrict internet access and allow only the services required by Frigate, NTP or management. The exact policy depends on the camera ecosystem, but the switch must support the VLAN design if segmentation is part of the plan. Keep the network rules documented so a future camera replacement does not silently lose access to the NVR.
Size the uplink for aggregated traffic
Add the bitrates of all camera streams crossing the switch uplink, plus live viewing and any other traffic on that link. A 1GbE uplink handles many ordinary cameras, but a dense deployment or shared NAS path may justify 2.5GbE or 10GbE between network layers. Multi-gig uplinks can be more valuable than multi-gig camera ports because aggregation occurs at the switch boundary.
Protect the switch and NVR with the same power plan
An NVR that stays on during a short outage cannot record cameras if the PoE switch loses power. Size the UPS for the host, storage and network equipment needed to keep camera streams alive. Use actual switch consumption and camera PoE draw rather than only the UPS VA number. A coordinated shutdown plan is also useful for longer outages.
Fan noise and heat matter in home installations
High-power PoE switches can use active fans, especially at 16 or 24 ports. A model that is fine in a rack may be objectionable in a bedroom, office or living space. Compare fanless operation, thermal design and expected PoE load. Running a high-budget switch near maximum output also creates more heat, so ventilation should be part of the installation plan.
Avoid daisy chains that hide the real bottleneck
Adding small unmanaged switches behind one another can work electrically, but it makes power, VLANs, bandwidth and troubleshooting harder to reason about. Prefer a clear topology with camera access switches feeding a defined core or NVR uplink. If multiple switches are necessary, document which cameras depend on each device and make sure the inter-switch link has enough capacity.
Remote PoE cycling is a practical reliability feature
A camera can occasionally need a power cycle after firmware or network problems. Managed PoE lets an administrator restart that port without visiting the camera. This is especially useful for outdoor or high-mounted devices. It does not replace fixing recurring faults, but it reduces downtime and makes troubleshooting much faster when the physical cable and camera are difficult to reach.
Verify the exact switch listing and power supply
Amazon listings often group unmanaged, managed, PoE and non-PoE variants together. Confirm exact port count, PoE budget, included power supply, uplink type and management level before purchase. This sprint filters for managed PoE search intent, but the final seller page remains the source of truth for the exact hardware revision and package contents.
Questions people ask
Best PoE Switch for Frigate FAQs
How many PoE ports do I need for Frigate?
Use the current camera count plus expansion headroom. For eight cameras, a 16-port switch is often easier to grow than an exactly full 8-port model.
How do I calculate PoE budget?
Add each camera's maximum wattage, then add roughly 20 to 30 percent headroom. Verify per-port PoE standard as well as the total shared switch budget.
Do Frigate cameras need 2.5GbE ports?
Usually no. Individual camera bitrates are far below 1 Gbps. Multi-gig links are more useful for switch uplinks or shared high-throughput network paths.
Should the PoE switch be managed?
Managed switching is valuable for VLANs, traffic visibility and remote PoE cycling. It is not mandatory, but it improves control and troubleshooting.
Can I put Frigate cameras on a VLAN?
Yes. A camera VLAN can reduce exposure and keep traffic organized, provided firewall rules still allow the necessary path to Frigate and management services.
Does the PoE switch need a UPS?
If you want recording to continue through a short outage, the switch powering the cameras should be protected along with the NVR and critical network equipment.
What is PoE+?
PoE+ is IEEE 802.3at and provides a higher power envelope than basic 802.3af PoE. Check the exact camera requirement before choosing a switch.
Is a fanless PoE switch better?
Fanless models are attractive in living spaces, but thermal limits and power budgets vary. Choose based on actual camera load and installation environment.
Can I use multiple PoE switches with Frigate?
Yes. Make sure uplinks, VLANs, UPS coverage and aggregate bandwidth are planned so the topology remains easy to diagnose.
Does Frigate control PoE ports?
Frigate is not the switch-management platform. PoE control is handled by the switch or its controller, while Frigate consumes the camera streams.
Official references and methodology
Verify current Frigate support before deployment
Cloudzat sizes PoE switching from camera count, maximum camera wattage, power headroom and aggregate network traffic. Live listings are restricted to accepted managed PoE-switch products from this sprint's Amazon catalogue, with UPS options shown separately. Exact PoE budget and port standards must be verified on the seller/manufacturer specification.
- Frigate - Recording
- Frigate - Installation
- Frigate - Restream
- Frigate - Configuring go2rtc
- Frigate - Troubleshooting Recordings
- Frigate - Camera Setup
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, seller terms, exact configurations, camera firmware and Frigate support can change.