As an Amazon Associate we earn from qualifying purchases.
Choose a PoE switch for security cameras by checking usable camera ports, each port’s power capability, the shared power budget, and the recorder connection. Passing one check does not make the others pass. An eight-port switch can have fewer than eight ports available for cameras once an uplink is connected, and a 30W-per-port specification does not mean every port can supply 30W simultaneously. TP-Link’s TL-SG1008MP specifications illustrate that distinction with eight ports and a 153W shared budget.
Quick selection rule: Draw the network, reserve uplink ports, match the cameras’ documented PoE requirements, add their maximum required power allocations, then check the switch’s environment and the NVR’s limits. Choose expansion room deliberately rather than relying on a camera-count claim.
This guide is for homeowners and small-site installers sizing an Ethernet camera network. It uses documented switch examples and vendor connection guidance, without claiming measured throughput, camera consumption, or universal camera-to-recorder compatibility.
As an Amazon Associate, we earn from qualifying purchases. We may earn a commission when you buy through links on this page.
In this guide
- Count usable ports before power
- Match the camera’s PoE requirement, then compare watts
- Use a power worksheet with explicit assumptions
- Compare these documented switch examples
- Draw the recorder topology before connecting cables
- Check cables, bandwidth and management separately
- Commission the whole camera path
- Common PoE switch questions
- Order from a complete sizing sheet
Count usable ports before power
Power over Ethernet, or PoE, supplies power and network data through Ethernet cabling when the source and connected device support the required standard. The switch is the power sourcing equipment, abbreviated PSE; the camera is the powered device, or PD. These terms matter when comparing watt figures. Axis’s datasheet guide defines the power classes and source-versus-device distinction.
Start with the physical connections. Count the cameras, the switch’s upstream connection, and any recorder or other device that plugs into it. Then distinguish total network ports from powered ports. A product with five network ports and four PoE ports has a different expansion path from a product with eight ports that are all PoE-capable.
For example, the captured US TL-SG1005P specification lists five Gigabit RJ45 ports, with PoE on ports 1–4. Its remaining network port can serve the uplink while leaving four powered camera connections. The TL-SG1008MP lists eight Gigabit ports and eight PoE+ ports. If one of those ports connects upstream, seven remain for cameras; if a recorder also uses another port on that switch, six remain. This is a connection-count example, not a restriction on all possible layouts. TL-SG1005P specifications, TL-SG1008MP specifications.
Write future camera locations into the drawing now. An empty powered port is useful only if the shared power budget and recorder capacity can support the future camera as well.
Match the camera’s PoE requirement, then compare watts
Check the camera’s exact datasheet for the required IEEE PoE standard and maximum power requirement. Do not treat a generic “PoE” description as complete compatibility information, and do not assume passive power equipment is equivalent to a standards-based PoE switch.
Source and device watts are not interchangeable. Axis lists these class examples:
| PoE class example | Power at the source | Maximum at the powered device |
|---|---|---|
| Class 3 / IEEE 802.3af | 15.4W | 12.95W |
| Class 4 / IEEE 802.3at, commonly PoE+ | 30W | 25.5W |
Source: Axis PoE class definitions.
The practical lesson is to compare requirements on the same basis. A camera that needs 30W at the device is not established as compatible by a port advertised to supply 30W at the source. Use the manufacturer’s supported class and allocation instructions, including the allowance needed for the installed cable path and power negotiation.
The switch’s total PoE budget is another limit. The TL-SG1008MP specifies up to 30W per port but a shared 153W budget. Eight multiplied by 30W is 240W, which exceeds that shared figure. A large per-port number therefore cannot be multiplied across every socket as a guaranteed simultaneous output. TP-Link also cautions that the published budget is laboratory-based and actual results vary with connected clients and environmental factors. Source: TL-SG1008MP power specifications.
Use a power worksheet with explicit assumptions
For each camera, record the exact model, required standard, maximum device requirement, and the corresponding source allocation used for switch sizing. Use maximum supported operating requirements rather than an assumed daytime average. If the manufacturer distinguishes power needs for enabled features, use the requirement for the configuration you intend to run.
| Camera position | Exact model | Required PoE standard | Required source allocation | Intended switch port |
|---|---|---|---|---|
| Front entrance | Record from label | Record from datasheet | Record in watts | Assign after checking port capability |
| Driveway | Record from label | Record from datasheet | Record in watts | Assign after checking port capability |
| Side entrance | Record from label | Record from datasheet | Record in watts | Assign after checking port capability |
| Rear entrance | Record from label | Record from datasheet | Record in watts | Assign after checking port capability |
Consider two hypothetical four-camera designs. These examples assume the listed watt figures are complete source-side allocations, already accounting for required losses and class headroom; they are not measured camera consumption.
- Four allocations of 12W total 48W. Against a 65W pool, the arithmetic leaves 17W unallocated, subject to per-port compatibility and operating conditions.
- Four allocations of 20W total 80W. A 65W pool is insufficient even if the individual ports otherwise support the cameras.
The 65W figure is the captured TL-SG1005P shared budget. TP-Link says its power management cuts lower-priority port power when total consumption exceeds that budget. Overloading it can therefore mean losing a camera feed rather than simply sharing power evenly. Source: TL-SG1005P power management.
Reserve capacity for uncertainty and intended additions, but do not present an arbitrary percentage as an IEEE rule. The useful question is whether your documented maximum allocations, installation conditions, and planned additions remain within the chosen switch’s limits. If the design works only by assuming a feature will never activate, revisit that assumption before ordering.
Compare these documented switch examples
These US-page examples show the tradeoffs between a compact four-camera installation and a larger powered-port pool. They are specifications-based options to evaluate, not a tested ranking.
| Selection point | TP-Link TL-SG1005P | TP-Link TL-SG1008MP |
|---|---|---|
| Total ports | Five Gigabit RJ45 | Eight Gigabit RJ45 |
| PoE-capable ports | Four, ports 1–4 | Eight |
| Shared PoE budget | 65W | 153W, with laboratory/conditions caveat |
| Per-port check | Verify exact hardware revision and manual | Up to 30W per port on the captured page |
| Cooling | Fanless | One fan |
| Published operating temperature | 0–40°C | 0–50°C |
| Placement format | Desktop/wall mounting described | Desktop/rack mounting described |
Sources: TL-SG1005P US specifications, TL-SG1008MP US specifications.
There is a version detail to resolve for TL-SG1005P: the captured page’s older overview mentions 802.3af, while its specification table lists 802.3af/at. Verify the hardware revision and its current manual before buying for a camera that requires PoE+. Do not borrow a per-port limit or extended mode from another region’s product page.
Choose the smaller model only when four powered camera ports, its shared budget, and its verified port capabilities fit the complete design. Investigate the larger model when you need more powered ports or more shared capacity, while allowing for the uplink’s socket and the presence of a fan. Neither example should be selected for an exposed outdoor location based solely on an operating-temperature figure; humidity, enclosure requirements, and actual site conditions also need checking.
After checking the exact revision, you can search Amazon for TP-Link TL-SG1005P switches or search Amazon for TP-Link TL-SG1008MP switches. A search does not confirm a seller’s revision, specifications, availability, or price.
Draw the recorder topology before connecting cables
The same switch can behave differently depending on which recorder port it connects to. Topology means the arrangement of those connections. Use the NVR manufacturer’s diagram for the actual recorder rather than treating all Ethernet sockets as interchangeable.
Reolink’s shared-router layout connects the NVR and PoE switch to the same router, with cameras on the switch. Those cameras obtain router-assigned addresses and can be added to the recorder over the local network. Cameras directly connected to the NVR’s camera ports obtain recorder-assigned addresses instead. Reolink also distinguishes separately accessible standalone cameras from kit add-on camera exceptions. Source: Reolink connection methods.
For a switch connected on the camera side of RLN8-410 or RLN16-410, Reolink does not recommend that arrangement and limits the cited case to eight cameras because of the recorder-port bandwidth. Its connection article identifies the camera-side ports as 100Mbps, while the NVR LAN port is Gigabit. A Gigabit switch does not turn the recorder’s 100Mbps port into a Gigabit link. Connection methods, switch-between-camera-and-NVR guidance.
Reolink security cameras should follow the connection method documented for the recorder and camera combination. In its depicted camera-side switch arrangement, Reolink warns against also connecting both the switch and NVR LAN to the router because disconnections can occur. That warning is specific to the depicted layout; it is not a prohibition on Reolink’s separately documented shared-router method.
For RLN36, Reolink suggests distributing a 36-camera design over four switches with nine cameras each rather than concentrating every camera on one switch. This is vendor-specific planning guidance, not a universal nine-camera switch limit. Source: Reolink topology guidance.
Check cables, bandwidth and management separately
Both captured TP-Link pages specify a maximum of 100m for their listed copper Ethernet media. Check the full installed path and the required cable specification. Do not assume a longer run will work because another switch revision or region advertises an extended-distance feature. TL-SG1005P media specifications, TL-SG1008MP media specifications.
PoE camera installation should account for cable length, termination quality, power requirements and recorder layout together. Test the intended routes before closing walls or finalizing mounts. A short bench connection that powers the camera does not establish performance over the completed site cabling.
For network capacity, add the intended camera stream rates that cross each uplink and compare them with the relevant switch and recorder connection limits. Preserve room for the actual design’s other traffic. The camera count alone cannot settle aggregate bandwidth, and sufficient PoE power cannot establish codec or stream compatibility with the NVR.
Managed-network requirements are a separate purchase criterion. Axis describes IEEE 802.1X as network authentication involving managed switches and a RADIUS server. If your site requires that control, specify it explicitly and verify it in the switch documentation. Do not infer authentication or other management features from a device’s PoE wattage. Source: Axis network security definitions.
Commission the whole camera path
Before installing all cameras, verify one representative camera through the intended switch and recorder path. Confirm power, address assignment, live video, and recording playback. Then add the remaining cameras while checking the total allocation and the switch’s status indicators or available management information.
Wired security camera systems need both a supported network path and successful recording verification. Check the system with the features you intend to use enabled, rather than verifying only that every camera has a power light. If a feed drops, distinguish loss of power from an addressing, stream, or recorder problem before changing equipment.
Keep an installation record with camera models, switch revision, assigned ports, cable routes, power allocations, and the NVR diagram used. That makes a later camera replacement or expansion easier to assess without reconstructing the network from memory.
Common PoE switch questions
Will an eight-port PoE switch run eight cameras?
Only if eight suitable camera connections remain in your actual layout and the per-port, shared-power, bandwidth, and recorder checks all pass. If a switch has eight total ports and one is used for the uplink, seven remain for cameras. Dedicated extra uplink ports change that count.
Does PoE+ guarantee recorder compatibility?
No. PoE+ addresses a power-standard question. The NVR must also support the camera, its streams and codecs, and the chosen network arrangement. Use separate camera-to-switch and camera-to-recorder compatibility checks rather than assuming power delivery proves video interoperability.
Which figure matters most: watts or ports?
Both are necessary, along with topology. Four available ports are insufficient for five cameras; enough ports cannot fix an inadequate shared power budget. Use your port drawing and source-allocation worksheet together, then check the recorder and cable path.
Order from a complete sizing sheet
The right PoE switch for security cameras fits the whole installation: usable camera ports after uplinks, compatible per-port power, enough shared capacity, a supported recorder topology, and appropriate cabling and placement. Finish those checks before comparing prices. Then verify live video and saved recordings through the intended network before calling the installation complete.
