PoE Budget Calculator: The Camera Power Math That's Easy to Miss

Illustrative worked example. The scenario below is a hypothetical, not a record of a specific job. Its numbers can be reproduced in the PoE Budget Calculator.

Picture eight PTZ cameras on a warehouse perimeter, all fed from one 24-port PoE switch with a 250W total PoE budget. Everything comes up green on the NVR at handover. A few nights later the complaint arrives: cameras going offline at random after sunset and back up by morning. It looks like a network fault, so the cabling, the switch logs and the patch cords get checked first, and nothing turns up. Ports are up, link lights are fine, and there are no errors on the port counters.

The clue in a case like this is the timing. Cameras that drop a few minutes after dark, rather than the moment it gets dark, point to a load that switches on later, such as IR illuminators or heater elements. That points to power rather than the network.

The port count on the box doesn't tell you what you think it does

Here's the thing that's easy to miss when you're buying a switch. Port count tells you how many PoE connections the switch provides — it doesn't by itself tell you how many devices it can power at the same time. A "24-port PoE switch" doesn't mean 24 devices running full tilt. It means 24 ports capable of delivering power, split across a shared power budget that's usually a fraction of what full load would actually need. Total PoE budget and per-port capability both matter, and neither shows up in the port count on the box.

In the example, the switch has a 250W total PoE budget. If each of the eight PTZ cameras is planned at 30W of PSE-side PoE load — the 802.3at capability figure, not necessarily each camera's real full-load draw — that's already 240W of planned load against the 250W budget, leaving 10W spare at 0% headroom. Only 8 of the 24 ports are in use, so the port count is not the limit; power is.

Once the IR array and heaters kick in after dark, actual operating demand goes up across all eight cameras at once, and a power budget that was already close to full during the day can become insufficient. What happens next depends on the switch's own power-management implementation: when the available power budget is insufficient, the switch may restrict, deny, or otherwise manage PoE power depending on how it's built, rather than simply overloading.

In a case like this it can look like random ports dropping and cycling back, with a different camera in the NVR log each time. It looks like a network fault. It is power.

Know your PoE type, not just your port count

If you're speccing a PoE deployment, this is the figure that actually decides whether it works — not the port count, and not the camera's category:

Fixed indoor dome cameras usually sit comfortably under standard PoE. PTZ motors, IR arrays, built-in heaters, and floodlight cameras can all increase power requirements — but that doesn't mean every PTZ automatically needs PoE+ or higher. The right way to spec it is to pull the camera's published maximum (or planned) PoE consumption from its own datasheet, not to guess the PoE type from the device category. Budget for that worst-case figure, not the idle draw. A camera's actual consumption can increase substantially once IR, heater, floodlight, or other auxiliary loads switch on — how much depends entirely on that specific model, which is exactly why the manufacturer's published maximum (not the daytime idle figure) is the number to plan against. Skipping that step is exactly what gets missed at spec time and shows up as a "random" fault a few nights after handover.

What to check before choosing a switch

Don't rely on the port count on the spec sheet. Before choosing a switch, add up every camera's planned PSE-side load — taken from the datasheet where available, not just the PoE type — then leave headroom on top of that total. How much headroom is a planning choice, not an IEEE requirement; 20% is a practical default, since night-mode current increases are exactly where a tight budget gets eaten. In the example above, 8 × 30W = 240W, and at 20% headroom the planning load is 288W, which is 38W more than the 250W budget. If the total is anywhere near the switch's rated budget, the options are a switch with a larger budget or splitting the cameras across two switches. Same logic applies if you're running battery backup off the same panel — worth checking against the Battery Backup Calculator so the backup side doesn't get caught out the same way.

It's a short check before the install instead of a troubleshooting job after it. We built a free PoE Budget Calculator to do exactly this math, so it can be caught on the quote sheet instead of on a callback. Enter your camera count, planned wattage, and PoE standard, and it checks whether your switch's power budget actually covers it — before a camera starts dropping after handover. Once power's sorted, it's worth running the same camera list through the IP Camera Bandwidth Calculator too, since an undersized uplink can cause a similar-looking "random drop" complaint for a completely different reason.

How the PoE budget calculation works

The math behind the calculator is straightforward once you separate the two steps: what your cameras actually need, and how much margin you want on top of that.

Run it backwards — "how many cameras can I add?" — and the calculator does the same math in reverse: it takes the switch's budget, backs out your chosen headroom to get a usable planning budget, then divides that by your selected camera's wattage. That gives a power-limited camera count. It separately checks that number against how many physical ports are actually free, and reports whichever limit is reached first — power or ports — since either one can be the real ceiling depending on the job.

Frequently asked questions

How many cameras can a PoE switch actually support?

It depends on the switch's total PoE power budget, not its port count. Add up each camera's planned PSE-side PoE load, using the camera's own datasheet where possible rather than just its PoE type, and compare that total against the switch's rated PoE budget in watts. Building in some headroom, with 20% a common planning default, leaves margin for night-mode current increases from IR and heaters, though headroom itself is a design choice, not an IEEE requirement.

Why do PoE cameras reboot only at night?

IR illuminators and built-in heaters draw extra current once they activate at dusk, increasing the camera's actual operating demand above its daytime load. If the switch's total PoE budget is already close to full during the day, that extra aggregate demand can push the total over budget. Exactly what happens next, whether the switch restricts, denies, or otherwise manages power to one or more ports, depends on that switch's specific power-management implementation.

What's the difference between PoE, PoE+ and PoE++ for cameras?

These are PSE-side power capability tiers, not fixed camera power draws. 802.3af (PoE) delivers up to 15.4W and covers most fixed cameras. 802.3at (PoE+) delivers up to 30W and is often needed for PTZ cameras, heated housings, and IR-heavy models, though the exact requirement always comes down to that specific camera's published consumption. 802.3bt (PoE++) Type 3 or Type 4 delivers up to 60W or 90W and covers higher-draw devices like large PTZs or combined camera, floodlight, and speaker units.

Sources

• IEEE 802.3 Working Group: P802.3af DTE Power via MDI Task Force (IEEE Std 802.3af-2003)
• IEEE 802.3 Working Group: P802.3at DTE Power Enhancements Task Force (IEEE Std 802.3at-2009)
• IEEE 802.3 Working Group: P802.3bt DTE Power via MDI over 4-Pair Task Force (IEEE Std 802.3bt-2018)

These IEEE pages identify the standards behind the PoE types. They do not list wattage figures, so the power values on this page are not taken from them; confirm them against the standard text or the device datasheet.

Found something wrong on this page? Send feedback →