How Power over Ethernet works for IP cameras: PoE, PoE+ and PoE++ explained, sizing a switch for your cameras, cable limits, and how to spot power faults early.
Power over Ethernet sends power and data to a camera down one cable. It is the biggest single installation saving IP cameras offer over analogue.
Plan for peak power with infrared, heaters and PTZ motors all running, never idle power. The worst case is a cold, dark night.
Check a switch's total PoE budget, not its per port maximum. A 24 port PoE+ switch almost never has 24 times 30W available.
Insist on solid copper cable. Copper clad aluminium is the most common hidden cause of PoE faults.
Weak power rarely shows as a dead camera. It shows as a camera that reboots when its infrared switches on, and only uptime history in your video platform reveals it.
Power over Ethernet (PoE) lets one network cable carry both the data connection and the electricity for a device. For a camera, that removes the second cable, the local socket and the electrician visit that an analogue camera would need.
Three benefits matter even more than the cable saving.
Central power. Every camera on a PoE switch draws from one place. Put that switch on a UPS (uninterruptible power supply) and the whole camera network rides through a power cut. With local adapters, you would need a UPS at every camera.
Remote reboot. A PoE port can be switched off and on from the switch's management screen, so a frozen camera can be restarted without anyone climbing a ladder. On a spread out estate, this alone pays for a managed switch.
Safe delivery. The standards require the switch to confirm a genuine PoE device is attached before sending power, and to agree how much it needs. A PoE port will not push power into a laptop plugged in by mistake.
Every specification quotes power twice, and mixing them up is the most common budgeting error. The switch figure is what leaves the port. The device figure is what reaches the camera after losses in the cable. Size switches on the port figure; choose cameras on the device figure.
IEEE 802.3af, ratified in 2003 and simply called PoE, is Type 1. It supplies 15.4W at the port and about 12.95W at the device: enough for a fixed dome or bullet camera without a heater.
IEEE 802.3at, ratified in 2009 and called PoE+, is Type 2. It supplies 30W at the port and about 25.5W at the device: enough for PTZ cameras, infrared lights and mild heaters.
IEEE 802.3bt, ratified in 2018 and called PoE++, covers Type 3 and Type 4. Type 3 supplies 60W at the port and about 51W at the device; Type 4 supplies 90W at the port and about 71.3W at the device. Both use all four wire pairs and power multi sensor cameras, heated PTZ housings and cameras running their own onboard AI.
Two traps catch people. "Passive PoE" is not PoE at all: some budget equipment ships with injectors that push a fixed voltage down the cable with no safety check, and plugging the wrong device into one can destroy it. If a datasheet says "24V passive", it will not work properly with a standard PoE switch. And power class is not the same as power type: devices announce a class from 0 to 8, and switch datasheets sometimes quote class and sometimes type, so read carefully.
Knowing the handshake explains most field faults. It runs in four steps.
Detect. The switch applies a small voltage and looks for the electrical signature of a PoE device. No signature, no power. This is what protects ordinary devices.
Classify. The switch measures how much the device asks for, places it in a power class, and reserves that amount from its total budget.
Power up. Full power is applied, typically 44 to 57 volts DC, and the camera boots.
Fine tune. Under PoE+ and PoE++, the camera and switch can renegotiate once the link is up. A camera that booted asking for a lot but needs less day to day can hand the spare back, freeing budget for other ports. Turn this on deliberately: on a tight switch it is often the difference between every camera powering up and the last two ports staying dark. It needs a switch feature called LLDP-MED, which is not always on by default.
This is where installations go wrong, so do the sums rather than trusting a rule of thumb.
A switch has a total PoE budget that is separate from its per port maximum. A 24 port switch offering PoE+ on every port rarely has 24 times 30W, or 720W, to give. Around 370W is typical: enough for about twelve PoE+ ports at full draw, not twenty four.
Plan on peak draw. A fixed camera that idles at 5W can more than double when several loads switch on together: infrared at full power after dark, heaters and defrosters in the cold, PTZ motors during a patrol tour, and onboard AI if the camera runs its own. The worst case is a cold, dark night, which is exactly when you least want cameras dropping. Assume everything is on at once, because on that night it will be.
A worked example. Take a 24 camera site: sixteen fixed domes peaking at 9W with infrared, four heated PTZ cameras peaking at 25W while moving, and four multi sensor cameras peaking at 30W. That is 144W plus 100W plus 120W, or 364W at the cameras. Add about ten percent for cable losses and you need roughly 400W at the switch.
Then add headroom. Size the switch at least 25 percent above the calculated peak, so 400W of need calls for a 500W switch or larger. Leave spare ports and watts for the cameras that will be added later, because they always are. If one switch is not enough, use two rather than one giant one: a switch failure then takes out half the cameras, not all of them.
PoE needs no special cable, but cable quality matters far more than it does for data alone.
Category. Cat5e is fine for PoE and PoE+. For PoE++ Type 3 and Type 4, use Cat6 or better: the higher current heats the wires, and thicker conductors carry that heat away.
Copper. Insist on solid bare copper, not copper clad aluminium. This is the single most common cause of mysterious PoE faults on budget installations. Copper clad aluminium resists current far more, so the camera at the end of a long run browns out under load while testing perfectly on the bench. It also fails the TIA cabling standards. Specify solid copper, then check what actually arrived on site.
Distance. The 100 metre limit is an Ethernet limit and covers the whole run, patch leads included. Voltage also drops with distance: a camera at 95 metres receives noticeably less than one at 5 metres, which is why device figures are lower than port figures. On a long run at high power, that margin disappears.
Beyond 100 metres, choose a PoE extender (each hop costs some budget), fibre with local power at the far end, or a switch in a cabinet nearer the cameras. For anything permanent, the nearby cabinet is usually cheapest and always easiest to troubleshoot.
Bundles. A thick bundle of cables all carrying heavy current heats up in the middle, which raises resistance and voltage drop. For dense bundles at PoE++ power, use Cat6A and keep bundles modest.
An injector adds power to one cable between an ordinary switch and one device. It is the right answer for one or two cameras, or a lone camera far from any PoE switch.
Beyond a handful, a PoE switch wins on every count: one power supply, one management screen, power monitoring per port, remote reboot, and no injector on a cupboard floor waiting to be unplugged by someone looking for a socket. Injectors also give you nothing to look at when a camera browns out.
A sensible rule: three or more cameras justify a switch.
Most guides skip this part. Here is a straight list.
One point of failure. A failed switch takes down every camera on it, power and network together. Mitigate with a UPS, a spare on the shelf, and splitting large sites across several switches.
A short reach. 100 metres is short for perimeters, car parks and industrial yards, and extenders or fibre add cost.
Silent overload. Overloaded switches fail differently: some refuse the newest port, some cut the lowest priority, some brown out several cameras at once. The fault comes and goes with load, which makes it hard to diagnose afterwards.
Heat. High power PoE across dense bundles in a warm riser is a real concern. And cheap parts fail expensively: copper clad aluminium cable and passive injectors save a little at install time and cost a lot in return visits.
List the peak draw of every camera model from its datasheet, not the idle figure. Size the switch to the peak total plus cable losses plus 25 percent headroom, checking the total budget rather than the per port maximum.
Specify solid copper cable of the right category and check what arrives. Keep every run under 100 metres including patch leads, and plan fibre or a nearby cabinet where you cannot.
Put the switch on a UPS sized for the runtime the site really needs, and turn on LLDP-MED so cameras can return budget they do not use. Set port priorities so that, if the budget is ever exceeded, the switch drops a low value camera, not the one covering the main gate.
Put cameras on their own network segment, away from general traffic. Record each camera's power draw once commissioned; that baseline is your reference when something changes months later.
Finally, test after dark. Commissioning at 2 PM in summer tests nothing that matters. Check the estate with infrared and heaters running.
This is where power engineering meets daily operations, and where the problem is usually first noticed, though rarely recognised.
Weak power seldom shows as a camera that is simply off. It shows as a camera that reboots when its infrared switches on, comes back, records for a while, and drops again. From the operator's chair that looks like a flaky camera or a network fault, and it is often misdiagnosed as both for months.
The tell is timing. Outages that cluster after dusk, in cold weather or during PTZ tours point to power. Outages spread evenly through the day point to the network or camera firmware.
Visylix makes this pattern obvious. Its built in device health console rebuilds each camera's uptime over any period from its recorded history, showing availability, the number and length of outages, recording coverage and last seen time, and flags cameras below 99 percent availability as degraded and below 90 percent as critical. Because uptime is rebuilt from history rather than sampled now and then, a camera dropping every night appears clearly as a pattern of short outages.
Use it twice. At commissioning, run the site for a week and read the health console before you sign off: cameras on marginal power will already stand out. In operation, compare a degraded camera's outage times with sunset and temperature, and if they line up, check the switch port before replacing the camera.
The health console sits alongside everything else Visylix brings to a camera estate: ONVIF device packs for the top five camera brands, bulk administration, camera I/O and event ingestion, and 22 AI analytics built in house, including camera tampering detection that spots covered, blurred, frozen or moved cameras. Starter and Pro include unlimited cameras on the VMS licence, from ₹4,999 or $49 per month, with AI added per camera per month where you want it.
Whatever platform you run, the lesson holds. If it cannot tell you how long each camera was really up last month, you will never catch weak power.
PoE (IEEE 802.3af) delivers 15.4W at the switch port, about 12.95W by the time it reaches the camera. PoE+ (IEEE 802.3at) delivers 30W at the port, about 25.5W at the camera. PoE+ exists because cameras with infrared lights, PTZ motors or heated housings need more than standard PoE can supply.
A fixed dome or bullet camera without a heater usually peaks at around 5 to 9W. A PTZ camera or heated housing commonly reaches 20 to 25W and needs PoE+. Multi sensor and high power PTZ cameras can need 802.3bt. Always use the maximum figure on the datasheet, not the typical one, because the maximum is what you hit on a cold night.
Yes. Each port negotiates separately, so every device gets its own allocation. What you must not assume is that the switch can power every port at full output at once. Check the switch's total PoE budget, which is a separate and much smaller number than the per port maximum multiplied by the number of ports.
No. Power and data share the cable without interfering, and PoE does not slow the link. Bandwidth problems on camera networks almost always come from switch uplinks or stream settings, not from PoE.
It depends on the switch. Some refuse power to newly connected devices, some cut the lowest priority ports, and some let several cameras brown out and reboot over and over. Setting port priorities turns an unpredictable failure into a controlled one.
Not on a single standard run. Ethernet is limited to 100 metres, including the patch leads at both ends. Beyond that, use a PoE extender (which repeats power and data at some cost to the budget), run fibre with local power at the far end, or put a switch in a cabinet closer to the cameras.
For one or two cameras, an injector is fine and cheaper. Beyond that, a switch wins everywhere: one power supply instead of several, central management, power monitoring per port, remote reboot of a frozen camera, and port priorities. Injectors give you no visibility at all when a camera misbehaves.
Most likely its infrared light or housing heater pushes it past what the port, or the switch's total budget, can supply. Test by switching infrared off temporarily or moving the camera to a lightly loaded switch, and check the power the switch reports for that port at night rather than during the day.