Selecting a PoE Switch by Project Scale: Ports, Uplink, Budget
Port count is the number every spec sheet leads with and the least useful one on its own. Two switches with 24 ports can differ by a factor of two in power budget and by a generation in uplink. The decisions that cause trouble on site sit in three columns — how many ports are powered, how much total power the switch can deliver at once, and where the traffic leaves the box. The tiers below follow project size, because that is how integrators actually buy.
What Actually Changes Between a 4-Port Site and a 24-Port Floor?
At four ports the switch is a power supply with a network port: one uplink to the router, one spare, and a budget that a single PTZ with a heater can exhaust. At 24 ports it becomes a distribution point that must carry every device's worst-case draw at the same moment, and it becomes a single point of failure for a whole floor.
Two numbers scale differently from port count. Power budget follows the sum of simultaneous peak loads, not average draw, and aggregation bandwidth follows how many cameras share one uplink. A 4-port design is usually decided by power; a 24-port design is usually decided by the uplink.
How Many Ports Should You Specify — and How Many Should Stay Spare?
Count every powered device: cameras, access points, intercoms, readers, PoE clocks, signage. Then add the non-PoE devices on the same segment — recorder, controller, one laptop port. PoE port count and total port count are different numbers, and the spec sheet only guarantees the PoE ones.
Then add 20–30% spare. An 8-camera retrofit becomes 11 within two years, and stepping from an 8-port to a 16-port chassis costs far less than a second switch, cabinet and uplink. Uplinks are not spare PoE ports either: on a "4+2" switch, one uplink feeds the router and only the second is genuinely free.
How Do You Build a Power Budget That Holds at 2 a.m. in Winter?
Budget from the PSE side, because that is the number printed on the switch. 802.3af delivers 15.4 W at the switch and 12.95 W at the device; 802.3at delivers 30 W and 25.5 W; 802.3bt Type 3 delivers 60 W and 51 W, Type 4 90 W and 71.3 W. The gap within each pair is cable loss, which is why a 12.95 W device is not reliable on an injector labelled 12 W.
The number that fails projects is simultaneity. PTZ motors draw peak current on start, and outdoor housings with heaters add 20–40 W in cold weather on top of camera draw. A 24-port 802.3at switch with a 370 W budget cannot power 24 ports at 30 W; it supports roughly 12 at full at-power. List peak draws, sum them, add 20–30% for inrush and future devices, and compare against the switch total — never against ports × per-port rating.
Above about 60 W the cable joins the power design. Conductor heating in bundled runs forces de-rating, and bt installations move to Cat6A with attention to bundle size rather than treating the cable as a data-only decision.
When Does an 8-Port Switch Stop Being Enough?
Two triggers. The first is uplink saturation: eight 8 MP cameras at 12 Mbps main stream total 96 Mbps, which leaves nothing on a 100 Mbps uplink once management traffic and recorder streams are counted. The second is physical: a floor with 14 devices is not an 8-port floor, whatever the budget says.
The usual compromise is cascading 8-port switches behind a 24-port aggregation switch. That works when the uplinks are Gigabit and fibre leaves the building, and fails when three 8-port switches are daisy-chained on 100 Mbps copper. Aggregation ratios give the working rule: 1:4 to 1:8 where every camera may stream simultaneously, 1:15 to 1:20 for bursty Wi-Fi and office data.
What Uplink Does Each Tier Actually Need?
Copper Gigabit covers most links inside one building up to the 100 m channel limit. Fibre earns its place in three cases: runs beyond 100 m, links between buildings where copper imports a potential difference, and any link that must stay immune to the surge a long outdoor cable invites.
10G SFP+ on an aggregation switch is headroom, not present demand: 24 cameras at 8 Mbps use roughly 20% of one 1G uplink. If you buy two SFP ports, the second is path redundancy, so dual-home to two upstream switches rather than bonding both toward a peer that fails as a unit.
Do Managed Features Change the Tier You Should Buy?
Unmanaged is fine for four ports in a shop. From eight ports up, three features pay for themselves: IGMP snooping, without which IP camera multicast floods every port; VLANs, which keep camera traffic away from guest Wi-Fi; and per-port PoE control with remote power cycling, the difference between a truck roll and a click.
Watchdog ping matters on remote sites for the same reason — a hung camera that recovers on a power cycle is a support call only if the switch cannot cycle that port. PoE extenders change topology more than the switch does: each hop consumes 2–4 W of budget and adds a device needing power and housing, so budget them as loads, not as cable.
Which Tier Fits Which Project?
| Tier | PoE / total ports | Uplink | Typical budget | Fits | Failure mode to avoid |
|---|---|---|---|---|---|
| A — small site | 4–6 PoE / 6–8 total | 1–2 × 1G copper | 60–65 W | Shop, villa, single gate: 2–4 cameras + 1 AP | One PTZ with heater exhausts the budget |
| B — floor | 8–10 PoE / 10–12 total | 2 × 1G copper or SFP | 120–150 W | One floor: 6–10 cameras or 6–8 APs | 100 Mbps uplink, or daisy-chaining |
| C — aggregation | 16–24 PoE / 24–28 total | 2–4 × 1G SFP, or 2 × 10G | 370–400 W (af/at); 600–740 W (bt) | Warehouse, campus floor, multi-switch core | Assuming every port runs at full at-power |
Read the budget column against the device list, not the port count. Tier C at 370 W supports about 12 ports at 30 W, which is ample for a camera mix and short for a row of heated PTZ units.
Where the schedule does not say how many housings carry heaters, size for the heater case; it is cheaper than replacing the switch mid-project.
FAQ
Do I need 802.3bt on a normal project?
Only where a device genuinely exceeds 30 W: heated PTZ, some Wi-Fi 6E access points, LED luminaires, large signage. A bt switch powers af and at devices normally, since negotiation happens per port, but paying for bt capacity you never load is budget taken from the uplink.
Can I mix 802.3af and 802.3at devices on one switch?
Yes. Each port negotiates independently and an at switch feeds af devices at af levels. The constraint is the switch's total budget, not the mix — so a mixed fleet usually needs less budget than the port count suggests.
Is a 370 W switch enough for 24 PTZ cameras?
Only if their average draw fits. Twenty-four ports at 30 W is 720 W, so a 370 W unit supports roughly half that load at full at-power. Add heater draw in winter before deciding, and split across two switches if the sum does not clear.
When should the uplink be fibre instead of copper?
Beyond the 100 m channel, between buildings, or wherever the two ends sit on separate electrical systems. Fibre removes the metallic path that carries both potential differences and surge current between buildings.
Do 100 Mbps PoE ports still make sense?
Yes for 2–4 MP cameras at modest bitrates on short runs, and they remain the cheapest way to light up a small point. They stop making sense the moment several cameras share one uplink or resolution reaches 8 MP.
