Best PoE switch for Frigate cameras

One cable per camera is the nice part of PoE. The less glamorous part is making sure the switch has enough powered ports and watts left when every camera turns its lighting on. Get those two numbers right and the switch can get on with being boring—which is exactly what you want behind a recorder.

Start with the TP-Link TL-SG1005P for a compact four-camera 802.3af network. Choose the NETGEAR GS305EP when you want VLAN controls, or the TL-SG1008MP when you need more ports and a bigger power budget. The GS305Pv3 is the simple NETGEAR alternative.

This research-based guide uses maker specifications; camera power figures come from models in our Frigate camera guide.

The parts lists offer alternative switches. Buy one that fits your camera count and power plan, rather than treating the list as a bundle.

Quick picks

• Best for four cameras: TP-Link TL-SG1005P. Four powered ports, a separate Gigabit uplink, a cited 15.4 W per-port limit and a 65 W total budget. It suits four Color4K-T-S2 cameras in the calculated example below.
• Best with VLANs: NETGEAR GS305EP. Four powered ports and a 63 W budget, with local browser management, 802.1Q VLAN tagging and per-port PoE controls. Choose it for a small camera network you want to manage.
• Best eight-port pick: TP-Link TL-SG1008MP. Eight powered Gigabit ports and a 126 W budget in the version compared here. It is the growth choice for the six-camera examples—and it has a fan.
• Best tiny pick: TL-SG1005P again. Its maker lists a 99.8 × 98 × 25 mm case and a fanless design. The four-camera pick and the compact pick share a winner.

Compare the ports, power and controls

Switch	Total / powered Gigabit ports	Per-port limit	Total PoE budget	PoE profile used here	VLAN configuration	Cooling
TP-Link TL-SG1005P	5 / 4	15.4 W	65 W	802.3af (conservative)	Unmanaged	Fanless
NETGEAR GS305Pv3	5 / 4	30 W	63 W	802.3af/at	Unmanaged	Fanless
NETGEAR GS305EP	5 / 4	30 W	63 W	802.3af/at	Local browser; 802.1Q tagging	Fanless
TP-Link TL-SG1008MP, 126 W version	8 / 8	30 W	126 W	802.3af/at	Unmanaged	One fan

Sources: TL-SG1005P specifications, GS305Pv3 specifications, NETGEAR managed-switch datasheet and TL-SG1008MP V1 specifications.

TP-Link’s TL-SG1005P page lists 15.4 W per port and 802.3af in its overview, while its technical table also says at/af. This guide uses the conservative 802.3af/15.4 W profile until revision-specific maker documentation resolves that conflict. Use one of the verified PoE+ models here for the T54PRO-ZE or a camera needing more than 15.4 W. A 65 W total cannot raise an individual port’s limit.

Keep the model suffix and hardware version with the specification. GS305P and GS305EP are different products: the E brings management here. The NETGEAR listing selected for GS305P identifies v3. For TL-SG1008MP, this comparison uses the 126 W version; TP-Link’s current unversioned page lists 153 W. That higher figure belongs to that specification, not an automatic extra allowance for the 126 W version.

Count the uplink before counting your cameras

The five-port switches give you a convenient layout: four cameras plus one connection back to the network. The eight-port TP-Link has eight PoE-capable ports, but one still carries the uplink. That leaves seven camera ports, not eight cameras plus a free ninth connection.

If you also plug the Frigate host directly into that switch, it takes another port. Eight total ports can then hold six cameras, one host and one uplink. Count a directly connected access point or other device too, including its power demand if it uses PoE.

A non-PoE uplink device uses a data port without consuming camera PoE power. Port count and power budget are separate shopping checks; passing one does not make the other disappear.

Calculate the camera power budget

Use the camera maker’s maximum PoE input, not its idle draw or a different DC-input figure. Our existing camera shortlist includes:

• EmpireTech Color4K-T-S2: 802.3af, 9.6 W maximum PoE input with the maker’s listed warm-light, intelligence and stream conditions.
• EmpireTech IPC-T54PRO-ZE: 802.3at PoE+, 12.8 W maximum PoE input with the maker’s listed lighting, siren and intelligence conditions.

Those are Color4K-T-S2 and T54PRO-ZE specifications, not wall-meter results. The T54PRO-ZE still needs the specified PoE+ source even though its stated input is modest: match the standard as well as the wattage.

For these shopping examples, add a chosen 25% planning allowance to the summed camera maximum. That leaves room beyond the listed inputs instead of spending the whole switch budget on paper. It is our example planning rule, not a maker rating or a substitute for checking the switch’s actual PoE allocation.

Camera	Count	Combined maximum camera input	With the assumed 25% allowance	Switches passing the stated profile and planning checks
Color4K-T-S2, 9.6 W each, 802.3af	2	19.2 W	24 W	All four shortlisted models
Color4K-T-S2, 9.6 W each, 802.3af	4	38.4 W	48 W	All four shortlisted models
Color4K-T-S2, 9.6 W each, 802.3af	6	57.6 W	72 W	TL-SG1008MP
T54PRO-ZE, 12.8 W each, 802.3at	2	25.6 W	32 W	GS305Pv3, GS305EP, TL-SG1008MP
T54PRO-ZE, 12.8 W each, 802.3at	4	51.2 W	64 W	TL-SG1008MP
T54PRO-ZE, 12.8 W each, 802.3at	6	76.8 W	96 W	TL-SG1008MP

The arithmetic is camera count × maximum PoE watts, then multiply by 1.25 for the stated allowance. Mixed fleets work the same way: add each camera’s maximum first. Include any extra powered devices before applying your reserve. The calculation checks the camera’s required PoE standard, the per-port limit with the chosen allowance, the available camera ports and the shared total separately.

Four Color4K-T-S2 cameras land at 48 W with that allowance, comfortably inside the 63 W and 65 W options. Four T54PRO-ZE cameras land at 64 W. Choose the TL-SG1008MP: the 63 W models miss that allowance, and the TL-SG1005P’s conservative 802.3af profile excludes this PoE+ camera regardless of its total budget. Both six-camera examples point to its larger budget and port count.

The switch’s advertised total is power available to connected devices, not your electricity bill. Switch electronics, cable losses and the power supply belong in the complete power picture. For an outlet-level electricity check, use a wall meter rather than calling the camera-input sum “wall watts.”

Check the per-port limit as well as the total

The GS305Pv3 maker page specifies up to 30 W per powered port with 63 W shared. The GS305EP manual gives the same limits for that model. The TL-SG1008MP V1 page gives 30 W per port and 126 W shared. The TL-SG1005P overview gives 15.4 W per port and 65 W total, the limits used here.

You cannot multiply a port maximum by every socket and assume the power supply delivers the result. Nor can a large total budget make an 802.3af-only profile suitable for a device requiring 802.3at.

On the GS305EP, the PoE controls expose output power and per-port limits. The manual distinguishes a user-set limit from a limit based on the attached device’s power class. Read the allocation and device status after connecting the cameras; include that behavior in your startup test alongside the calculation.

If a camera is denied power or drops out as other devices start, inspect the PoE status and budget before changing Frigate’s detector settings. Camera power, video decoding and object detection are different jobs.

Choose GS305EP when you want a camera VLAN

The GS305EP is the managed choice here. You get four powered ports, a local web interface and VLAN controls without buying a large rack switch. Its 63 W budget suits the four-camera, lower-power example; use the table to size a different fleet.

For a separate camera network, plan the switch and router together:

1. Create the camera VLAN on your router/firewall and plan which traffic the Frigate host needs.
2. In the switch’s advanced 802.1Q mode, assign the camera-facing ports as U (untagged) members of the camera VLAN and set their matching PVIDs. Click APPLY to save each change.
3. Open VLAN 1 → EDIT and set those camera-facing ports to E (Exclude), then click APPLY. Repeat for every other unwanted VLAN and verify those camera ports show E in each membership table. Advanced mode starts with all ports untagged in VLAN 1; adding a camera VLAN and changing PVIDs does not remove that default membership.
4. Carry the camera VLAN tagged on the uplink where your router expects tags. Keep an administrator connection on the management VLAN while changing memberships.
5. Apply the router/firewall policy for access between networks. Test isolation: from a test device on VLAN 1 or another prohibited network, confirm the camera connection is blocked; from the camera VLAN, confirm prohibited LAN access is blocked too. Then verify the authorized Frigate host can still receive streams, record video and reach any permitted camera services.
6. Restart the switch in a controlled test and repeat the membership and isolation checks, alongside the permitted-stream test.

The NETGEAR manual documents default VLAN 1 membership, T/U/E membership controls, APPLY, PVIDs and PoE controls (pages 37–43). VLAN membership separates the switch traffic; the router/firewall decides which routed connections are allowed. The unmanaged switches in this table give you no equivalent camera-port VLAN configuration menu.

Use the switch and NIC guide for the wider wired network, and the Wi-Fi 7 router guide when you also need router, IoT-network and faster-backbone features.

Fanless desk box or larger power supply?

TL-SG1005P, GS305Pv3 and GS305EP are fanless. They are the easy choices for a desk or small shelf when their ports and watts fit. GS305Pv3 offers the same four-powered-port layout as the TP-Link compact pick, with a 63 W budget and no VLAN setup.

The cited TL-SG1008MP specifications list one fan. Choose its larger PoE budget for the job it does, then place it where fan cooling fits your setup.

All four shortlisted switches use Gigabit Ethernet. If the switch will also feed faster access points or carry heavy NAS transfers, size those links separately. For a camera-only purchase, start with powered ports, the camera budget and management features rather than buying a 2.5GbE badge first.

Set it up, then test the whole camera crew

Connect one camera first and confirm its stream in Frigate. Then add the rest and check the power status with all devices connected. Exercise their night lighting and any features included in the maker’s maximum-power figure, so the test covers more than a quiet daytime picture.

Restart the switch in a controlled test and confirm that every camera returns, live views work and recordings resume. Save the managed switch configuration as described in its manual. Put the switch and recorder on suitable UPS protection if you want both power and recording to survive a short outage.

Then move on to the video workload. The Frigate camera guide covers detect and recording streams; Coral versus Hailo helps you choose a detector—or use OpenVINO on suitable Intel hardware you already own. Keep building from the Home Assistant hub.

The pick: TL-SG1005P for a compact 802.3af start, GS305EP for a small managed camera network, or TL-SG1008MP when the port and power calculations call for the larger box. Count the uplink, add the camera watts, leave room to grow, and let the switch fade into the background.

Put another PoE port to work

A wall dashboard can share the switch with your cameras. Our PoE-to-USB-C tablet guide explains charging profiles and the difference between a power-only path and USB-C wired data; reserve its power before you fill the remaining camera ports.

Sharing the switch with wireless access points? Use the Omada vs UniFi PoE AP guide to add their maker maximum draw, required PoE standard and powered-port count to the camera plan.