PoE Power Budget Calculator
Check whether a PoE switch's power budget can support all connected devices — the total-power planning check that prevents devices from silently failing to power on.
Inputs
Typical IP camera draws 5-12W; PTZ cameras and Wi-Fi APs can draw more.
- Switch PoE Budget (W)
- Number of PoE Devices
- Power per Device (W)
Paste this into any page — the widget stays live and updates automatically as this calculator improves. Using WordPress or Notion? See the embed guide.
Saved Scenarios
— select 2+ to compare| Metric | |
|---|---|
Remaining Budget (W)
50.0
Total Power Draw (W)
70.0
Spark says
How it's calculated
Formula
- Switch\ Budget
- — The switch's total PoE power budget, from its datasheet
What is the PoE Power Budget Calculator?
A PoE switch's total power budget is shared across all connected devices — this calculator checks whether your device count and per-device draw fit within that budget, with headroom to spare.
Use this when planning how many PoE devices a specific switch can support, checking whether an existing switch has remaining capacity for additional devices, or comparing switch models with different PoE budgets against a planned installation's total power needs.
How to use it
- 1 Enter your switch's total PoE power budget (from its datasheet — not the per-port maximum).
- 2 Enter how many PoE devices are connected.
- 3 Enter the typical power draw per device.
Understanding PoE Power Budget Calculator
PoE switches present a subtlety that trips up a lot of installation planning: the number of PoE-capable ports a switch has and the number of PoE devices it can actually power simultaneously are two genuinely different numbers, and confusing them is one of the most common PoE deployment mistakes — one that typically surfaces at the worst possible moment, when a device that should work simply refuses to power on despite being plugged into what looks like a perfectly good, available port.
A PoE switch has two separate power-related specifications that serve different purposes. Per-port maximum power output describes how much power any single port is capable of delivering to a connected device, following whatever PoE standard the switch supports (standard PoE tops out around 15.4W per port, PoE+ around 30W, and PoE++ variants going considerably higher). Total PoE power budget, by contrast, describes how much power the switch's internal power supply can deliver across all its ports combined, simultaneously — and critically, this total budget is almost always meaningfully less than what you'd get by multiplying per-port maximum by total port count, because switch manufacturers design around realistic assumptions about typical device power draw rather than provisioning for the theoretical worst case of every single port simultaneously drawing its absolute maximum rated power.
This design assumption is entirely reasonable from a manufacturing and cost perspective — building a switch with enough power supply capacity to run every port at maximum PoE++ power simultaneously would be considerably more expensive than most real-world deployments actually need, since most connected devices (a typical IP camera, for instance) draw well below a port's theoretical maximum capacity in normal operation. But it does mean that an installer can't assume 'this switch has 24 PoE ports, so it can power 24 typical devices' without actually checking the total power budget specification against the sum of real expected device draw — a switch with a lower total power budget might genuinely only support powering a subset of its physical ports simultaneously at typical device power levels, something that's easy to discover unexpectedly partway through an installation rather than proactively during planning.
When a switch's power budget is exhausted, the practical failure mode is usually not a dramatic error or warning that clearly points to the root cause — most managed PoE switches simply refuse to energize additional ports once the budget limit is reached, following some internal priority scheme (often based on port number or an administrator-configured priority setting), meaning newly connected devices on lower-priority ports simply never power on, which can look confusingly like a bad cable, a faulty device, or a port hardware failure rather than what it actually is: a straightforward total power budget shortfall. This is exactly why proactively calculating total expected device draw against a switch's rated power budget during planning — rather than assuming port count alone determines capacity — avoids a genuinely common and initially confusing installation problem, and why building in some power budget headroom beyond current device count is worth the modest extra cost of a slightly higher-capacity switch, given how disruptive discovering an exhausted budget mid-installation or mid-expansion can be.
Worked examples
Advantages
- •Directly checks the constraint that actually matters — total switch power budget — rather than just per-port capacity.
- •Simple, quick calculation useful for both new installation planning and evaluating existing capacity.
- •Helps avoid the common mistake of assuming per-port PoE rating alone determines how many devices a switch supports.
- •Useful for comparing switch models against a specific installation's total power requirements.
Limitations
- •Uses each device's nameplate/typical power draw — actual draw can spike briefly above the rated figure (e.g. PTZ cameras during movement).
Common mistakes
- ⚠️ Assuming a switch can power as many devices as it has PoE-capable ports, without checking whether the switch's total power budget actually supports that many devices simultaneously at their rated draw.
- ⚠️ Using a device's per-port maximum PoE standard rating (like 30W for PoE+) instead of the device's actual typical power draw, which is often meaningfully lower than the port's maximum supported capacity.
- ⚠️ Not accounting for the possibility of adding devices later, sizing a switch's budget exactly to current needs with no headroom for planned or likely future expansion.
Tips
- 💡 Always check a switch's total PoE power budget (a datasheet figure, distinct from per-port maximum) against the sum of all connected devices' actual typical power draw, not just port count.
- 💡 Use each device's actual typical power draw from its datasheet, not the maximum the PoE standard supports, since these are often quite different numbers.
- 💡 Build in headroom beyond current device count when choosing a switch, since adding PoE devices later is a common need, and discovering the existing switch's budget is already exhausted can mean an unplanned switch replacement.
- 💡 For PTZ cameras or other devices with variable power draw (motors, heaters, IR illuminators), budget toward the higher end of their draw range rather than their idle or average consumption.
Real-life uses
- Planning how many PoE devices a specific switch can support
- Checking whether an existing switch has remaining capacity for additional devices
- Comparing switch models with different PoE budgets against a planned installation's power needs
- Diagnosing why a newly added PoE device won't power on despite an apparently available port
Frequently asked questions
What happens if I exceed the switch's PoE budget?
Most managed switches will refuse to power additional ports once the budget is exhausted, prioritizing by port order or configured priority — devices simply won't power on.
Is total PoE power budget the same as per-port maximum times port count?
No — total power budget is almost always meaningfully less than per-port maximum multiplied by port count, since switch manufacturers design around realistic assumptions about typical device draw rather than the theoretical worst case of every port at maximum simultaneously.
Should I use a device's rated maximum or typical power draw for planning?
Use actual typical power draw from the device's datasheet — the PoE standard's maximum per-port rating (like 30W for PoE+) is often considerably higher than what a typical connected device actually consumes.
Why might a newly connected PoE device fail to power on despite an available port?
The switch's total power budget may already be exhausted by other connected devices, even if a physical port is free — most switches simply won't energize additional ports once the total budget limit is reached.
Should I choose a switch with headroom beyond my current device count?
Generally yes — adding PoE devices later is common, and discovering an existing switch's power budget is already exhausted often means an unplanned, disruptive switch replacement rather than a simple device addition.
calixo.cloud/cctv-networking/poe-power-budget-calculator/ — free calculator, no signup required.