For many SMB networks, PoE for IP cameras and PoE for Wi-Fi access points is where low-voltage cabling meets real-world power planning. If the PoE cabling design is wrong, you do not just lose a link – you lose video feeds, coverage, and uptime.

1. Why PoE cabling design matters for IP cameras and APs

In modern SMB networks, it is very common to power IP cameras and Wi-Fi access points over the same structured cabling plant. The upside is obvious: no local power supplies, fewer outlets, and centralized power control. The downside is that mistakes in PoE cabling design do not just cause packet loss – they cause devices to reboot, brown-out, or fail under peak load.

Typical real-world symptoms of poor PoE planning include:

• PTZ cameras that reboot when heaters, IR LEDs, or wipers turn on.
• Wi-Fi 6 APs dropping from 4x4 to 2x2 MIMO because they are not getting enough power.
• Cameras at the end of long runs going offline in hot weather because of voltage drop and bundle heating.
• Switches that appear fine on paper, but run out of PoE power budget once all devices are online.

The goal of this guide is to give SMB integrators and project managers a repeatable way to design PoE for IP cameras and PoE for Wi-Fi access points, with enough headroom to survive real-world conditions.

2. Typical power levels: fixed cameras, PTZ, and Wi-Fi 6 APs

Before you pull a single cable, you need a clear picture of how much power each device type really needs – not just its “average” draw, but the worst-case power when all features are active.

As a rule of thumb, always base your PoE power budget for cameras and APs on the vendor’s maximum power draw, not the typical value. Then add some extra headroom – we will come back to that in Section 5.

3. Cable length, gauge, and bundle heating

Once you know the device power, the next step in PoE cabling design for SMB networks is to think about the physical link: length, conductor size, and how the cable is installed.

3.1 Cable length and voltage drop

The longer the run, the more voltage is lost in the copper. On paper, Ethernet allows up to 100 m, but PoE at very high power levels and high temperature may require shorter runs or better cable.

Key points:

• Try to keep camera and AP home runs under 90 m whenever possible.
• For high-power PTZ or Wi-Fi 6 APs near the distance limit, consider larger conductors (23 AWG Cat6/Cat6A).
• Avoid unnecessary patching hops and consolidation points on very high-power links.

For a deeper discussion of how voltage drop works, and how to calculate it for different cable types and lengths, see our detailed guide on PoE power budget and voltage drop.

3.2 Cable gauge: 24 AWG vs 23 AWG vs 28 AWG

From a PoE perspective, cable gauge directly affects resistance, which affects both voltage drop and heat in the bundle.

• 23 AWG Cat6/Cat6A – lower resistance, better for high-power PoE and longer runs.
• 24 AWG Cat5e/Cat6 – common in SMB; fine for typical cameras and low/medium-power APs.
• 28 AWG patch cords – great for space-saving in racks, but higher resistance and more heating.

If you plan to use slim 28 AWG patch cords on PoE+ or higher, make sure you understand the thermal limits and derating. We cover this in detail in our lab article on PoE+ on 28 AWG patch cords: thermal limits and voltage drop .

3.3 Bundle size and ambient temperature

PoE current generates heat in the conductors. When many cables are tightly bundled in a hot environment (ceiling, riser, outdoor conduit), that heat has nowhere to go. The result: higher conductor temperature, more insertion loss, and earlier performance limit.

In SMB projects, focus on:

• Keeping large bundles away from hot sources (lighting, HVAC, unventilated roof spaces).
• Using cable trays or ladder racks instead of over-tight bundles.
• Paying attention to manufacturer guidelines for maximum bundle size under PoE load.

4. Network topologies for PoE cameras and APs

With power and cabling constraints in mind, the next question is how to lay out the network: where to place access switches, how to route cabling, and when to use MPTL links.

4.1 Classic pattern: access switch in the telecom/weak-current room

In a simple SMB office or campus building, the most common pattern is:

• Access switch and patch panels in a small telecom/weak-current room.
• Horizontal copper cabling to camera locations and AP locations.
• Short patch cords on both ends.

This pattern works well as long as the distances are within spec and the switch has enough PoE budget. For new builds, try to place the telecom room roughly central to the floor to keep camera/AP distances reasonable.

4.2 Front-end consolidation box vs direct home-run

For dense camera deployments (parking entrances, lobbies, intersections) it is often convenient to run a trunk of copper cables to a consolidation box or mini-IDF in the field, and then fan out to individual cameras with shorter links.

Pros of using a consolidation box:

• Shorter final runs to each camera or AP, easier to re-terminate or move.
• Cleaner field terminations compared to hanging junction boxes everywhere.

Cons to consider:

• Extra connections (patch or cross-connect) can add insertion loss and failure points.
• Space, power, and environmental protection for the box itself.

When distances allow, a direct home-run from the telecom room to each camera/AP is still the simplest and most reliable design. Use consolidation points mainly when the architecture or pathway layout demands it.

4.3 When to use MPTL (Modular Plug Terminated Link)

For wall- or ceiling-mounted devices like cameras and APs, the MPTL (Modular Plug Terminated Link) pattern is becoming the preferred choice:

• Permanent cable is terminated with a modular plug directly into the device.
• No exposed outlet and patch cord between outlet and camera/AP.
• Fewer parts to fail or to be unplugged accidentally.

MPTL is especially useful when the camera or AP is mounted in a location that is hard to access or prone to tampering. For design details, test requirements, and best practices, refer to our dedicated guide on MPTL links for cameras & APs: when and how .

5. PoE power budget for cameras: a simple design workflow

With devices and topology selected, you can now build the PoE power budget. For SMB networks, a straightforward workflow works best.

Step 1 – List every PoE device and its worst-case power

For each switch, create a table with one line per port that will power a device:

• Device name and location (e.g., “Lobby PTZ 01”).
• Device type (fixed camera, PTZ, Wi-Fi 6 AP).
• Vendor-specified maximum power (not only typical).
• Planned PoE standard (af/at/bt or proprietary high-power).

Step 2 – Sum per switch and compare with its PoE budget

Every PoE switch has two key limits: maximum per-port power and a total PoE power budget shared across all ports.

For each switch:

• Sum all port power values (worst-case) for devices connected to that switch.
• Compare the result with the switch’s PoE budget from the data sheet.
• If the total is close to the budget, consider moving some high-power devices to another switch.

Step 3 – Add headroom

To keep the network stable under peak conditions, do not run PoE switches at 100% of their budget. A common rule is to leave at least 20% headroom:

• If actual calculated load is 320 W, choose a switch or PSU sized for at least ~400 W.
• Reserve unused ports for future cameras/APs or higher-power replacements.

For more detailed examples and calculation methods, see our PoE power budget and voltage drop guide .

Step 4 – Avoid “hot spots” on the switch front

Even if the overall budget is fine, you can still get “hot spots” when all high-power devices are patched into the first few ports on a switch. A better practice is:

• Distribute high-power PTZs and Wi-Fi 6 APs across the front panel.
• Mix low-power fixed cameras and phones between them.
• In larger deployments, spread high-power devices across multiple switches or cabinets.

6. Installation and testing checklist for SMB projects

A good PoE cabling design only pays off if the installation and testing are done properly. Here is a concise checklist you can adapt for your own projects.

6.1 Per-link design and installation

• Confirm device type and maximum power (fixed camera, PTZ, Wi-Fi AP).
• Select cable category and gauge (e.g., 23 AWG Cat6A for high-power or long runs).
• Verify estimated link length and add some slack, staying within 100 m.
• Decide on outlet + patch cord vs MPTL termination based on mounting and security.
• Avoid mixing data/PoE cables tightly with AC power cables in the same conduit.

6.2 Switch and power planning

• Build and review the PoE budget table per switch.
• Check that UPS and PDU capacity accounts for PoE power draw, not just switch nameplate power.
• Reserve at least 20% PoE headroom for future growth and peak conditions.

6.3 Testing and verification

• Use a field tester to verify each horizontal link (length, wiremap, performance class).
• Power up cameras/APs one zone at a time while monitoring switch PoE status.
• Check for brown-outs or reboots when cameras enable IR/heaters or APs are under heavy load.
• Log and label each port–device mapping for future maintenance.

A more general installation-focused checklist can be found in our article on network cable installation and maintenance best practices .

7. Wrap-up

Designing PoE for IP cameras and PoE for Wi-Fi access points in SMB networks does not have to be complicated, but it does need to be intentional. If you:

• Start with realistic device power numbers,
• Respect cable length, gauge, and bundle heating limits,
• Choose simple, robust topologies with MPTL where it makes sense, and
• Build a clear PoE power budget with headroom,

you will avoid most of the painful surprises that show up months after handover. You also give your customer a more flexible infrastructure that can grow with higher-power cameras and Wi-Fi 6/6E APs in the future, without ripping out the structured cabling that holds it all together.