1
One to three scattered points: injector. Four or more: PoE switch
2
A switch saves cabling and shows port status centrally
3
Outdoor points need surge protection and earthing
01 Side by side
| Aspect | PoE injector | PoE switch |
|---|---|---|
| Point count | One to three scattered points | Four or more, centrally deployed |
| Placement | Near a socket, alongside the AP | Cabinet or comms room |
| Central management | None — points are independent | Yes — port status and power visible |
| VLAN / uplink | Requires a separate run back to the room | One run, VLANs configured on the switch |
| Cost profile | Cheap per point, expensive in labour at scale | Higher device cost, much cheaper cabling |
| Troubleshooting | Walk to each point | Check the switch port first |
02 Recommendation
- Finished interiors with one or two new points: use injectors and avoid new chases.
- Under construction or cable-friendly: go straight to a PoE switch so later APs need no new runs.
- Mixed brands: a switch makes power and addressing easier to standardise.
- Remote outdoor points: check injector surge protection and add a surge arrester at the switch.
Questions
Q1 Do injectors reduce throughput?
A gigabit injector does not — data passes through. Just avoid 100M models.
Q2 What if the switch runs out of PoE ports?
Add a peer switch for aggregation or move low-priority points to injectors and protect the high-value ones.
Related knowledge
PoE Standards Explained — 802.3af vs at vs bt Getting PoE wrong breaks deployments: under-powered devices reboot in a loop and are usually misdiagnosed as coverage problems. Here are the power classes and how to budget. How Many Devices Can One Access Point Handle? Vendor headline figures are theoretical associations, not usable concurrency. Real capacity depends on the traffic mix: browsing, video, scanning and roaming differ by orders of magnitude.
Tell us your point count and we will propose an injector/switch mix.