PoE vs PoE+ for Security Cameras

PoE and PoE+ both carry network data and electrical power over Ethernet, but they do not provide the same power capacity. For most fixed cameras, standard PoE may be enough. Cameras with heaters, stronger illuminators, moving PTZ mechanisms, or other accessories may require PoE+ or a higher-power standard.

The practical answer is:

• Choose standard PoE, based on IEEE 802.3af, when each camera’s maximum power requirement fits within the switch’s available PoE budget.
• Choose PoE+, based on IEEE 802.3at, when a camera needs more power or when you need additional headroom for features such as heaters, PTZ operation, or powerful illuminators.
• Do not select a switch only by its port count. Check its total PoE budget, the camera’s maximum power draw, the cable run, and the bandwidth available to the NVR or network uplink.

Browse security cameras after confirming the power standard and maximum consumption required by the models you are considering.

PoE vs. PoE+: What is the difference?

Power over Ethernet, or PoE, allows a network switch, injector, or midspan to send both data and power through an Ethernet cable. A compatible camera receives power without a separate electrical outlet at the camera location.

The commonly used standards provide approximately these power levels:

Standard	Maximum power supplied by PSE*	Maximum power available to powered device**	Typical planning use
IEEE 802.3af PoE	15.4 W per port	12.95 W	Basic fixed cameras and modest accessories
IEEE 802.3at PoE+	30 W per port	25.5 W	Higher-power cameras, heaters, stronger illuminators, and many PTZ applications
IEEE 802.3bt	Higher power classes	Varies by class and equipment	Cameras or devices with unusually high power requirements

\* PSE means the power-sourcing equipment, such as a PoE switch or injector. \** The powered-device figure accounts for power lost in the cable.

These are standard limits, not guarantees that every camera uses the full amount. The camera’s data sheet remains the authority for its minimum, typical, and maximum power requirements.

A PoE+ switch can usually power a lower-power PoE camera because the standards are designed for backward compatibility when both devices use active, standards-based negotiation. However, compatibility should still be confirmed for the specific switch, injector, camera, and cable installation.

The main buying consequence

PoE+ does not automatically improve image quality, resolution, night vision, or recording. It provides more electrical capacity. A PoE+ switch is useful only when the camera needs that capacity or when it gives you practical headroom for operating conditions and accessories.

Start with camera count and connection type

Before comparing switch standards, list every device and how it connects.

Wired PoE cameras

A PoE camera normally needs:

• One Ethernet cable back to a PoE switch, injector, or midspan
• A compatible Ethernet port
• An available power budget
• A network path to the recorder, computer, or viewing application

A camera connected to a non-PoE switch port will not receive power unless you add a compatible PoE injector or midspan.

Wi-Fi cameras

A Wi-Fi camera generally needs:

• Local electrical power or a suitable power adapter
• Adequate wireless signal at its installed location
• Sufficient wireless capacity on the access point
• A network path to cloud storage, an NVR, or another recording system

Wi-Fi does not make a camera wireless in the power sense unless the camera uses a battery. A Wi-Fi camera with a plug-in power adapter still needs an outlet or low-voltage power run.

Do not plan a mixed installation by counting Wi-Fi cameras as PoE switch ports. Instead, account for their power adapters and their wireless bandwidth separately.

NVR ports and network ports are not always interchangeable

Some NVRs include built-in PoE ports. Others are recording appliances that connect to a separate network switch. Confirm:

• Whether the NVR’s PoE ports are on the same network as your LAN
• The NVR’s total PoE budget
• Whether its ports support the required PoE standard
• The supported camera connection method
• Whether cameras connected directly to the NVR can be accessed from your normal network
• The recorder’s maximum incoming bitrate and camera capacity

A camera may receive power successfully while still failing to record if the NVR cannot support its network protocol, bitrate, resolution, or stream configuration.

Size the PoE power budget separately from bandwidth

Power and bandwidth are different limits. A switch can have enough electrical power for every camera but lack sufficient uplink capacity. It can also have plenty of network bandwidth while running out of PoE power.

PoE budget formula

Use the camera’s maximum rated power rather than its typical idle consumption:

Required PoE budget = sum of maximum camera power + design margin

A practical estimate can include 20% to 30% headroom when the manufacturer does not provide a more specific planning recommendation. This is a rule of thumb, not a guarantee.

Also check whether the switch’s advertised budget is:

• The total available across all ports
• The maximum per port
• Available continuously or affected by a power-supply mode
• Based on the same power standard you need

For example, a switch may have many PoE+ ports but a total power supply that cannot operate every port at its maximum simultaneously.

Worked PoE example

Assume an installation has six cameras:

• Four fixed cameras rated at a maximum of 8 W each
• Two cameras with an estimated maximum of 18 W each because of additional lighting or heating features

These figures are illustrative planning assumptions. Use the actual maximum values from the camera documentation for a real installation.

4 × 8 W = 32 W

2 × 18 W = 36 W

Total camera load = 68 W

Adding a 25% planning margin:

68 W × 1.25 = 85 W

The switch should therefore provide at least 85 W of usable total PoE budget. Each 18 W camera also needs a port and power standard that can deliver its required power. A PoE+ switch would generally provide more per-port capacity than standard PoE, but the switch’s total budget still needs to meet the calculation.

If one camera requires more than the per-port or powered-device limit of PoE+, do not assume that adding a larger total switch budget solves the problem. You may need an IEEE 802.3bt device, a manufacturer-approved injector, or a separate power arrangement.

Account for startup and accessory loads

Some devices draw different amounts of power depending on operating conditions. Examples include:

• Infrared illuminators switching on at night
• White-light deterrence lights activating
• Heater or blower operation in cold conditions
• PTZ motors moving or zooming
• A camera powering an attached microphone, speaker, or alarm accessory

Use the highest documented operating requirement if available. Do not size the system from a daytime reading alone.

Size network bandwidth independently

Camera resolution affects storage and network bandwidth, but resolution alone does not determine bitrate. Actual traffic depends on factors such as:

• Configured bitrate
• Frame rate
• Compression format
• Scene movement
• Image noise, especially at night
• Main stream and substream settings
• Audio and analytics traffic
• Whether the camera sends footage to an NVR, cloud service, or both

A camera with night vision may produce more traffic in a noisy, low-light scene than in a static daytime scene, even when its resolution is unchanged.

Bandwidth formula

Total camera bandwidth = sum of configured camera bitrates

Then allow for network overhead and non-camera traffic:

Required network capacity = total camera bandwidth + protocol overhead + network headroom

As a planning rule, leaving 20% to 30% headroom is sensible, but the actual requirement depends on the network design and traffic pattern.

Worked bandwidth example

Assume six cameras are configured at an estimated 6 Mbps each for their main streams:

6 cameras × 6 Mbps = 36 Mbps

If the cameras also send substreams, audio, or other traffic, add those values rather than assuming the 36 Mbps figure is the total.

A 36 Mbps camera total may fit comfortably on a 100 Mbps link in simple circumstances, but a gigabit uplink is often more appropriate for a multi-camera installation because it leaves room for:

• NVR traffic
• Live viewing
• Playback
• Substreams
• File transfers
• Internet access
• Future cameras

This is a bandwidth estimate, not a statement about any particular camera or NVR’s capability. Check the maximum incoming bitrate of the recorder and the speed of the switch uplink.

Avoid the uplink bottleneck

A switch can have gigabit ports for cameras but use a slower uplink to the NVR or core network. In that case, the uplink becomes the bottleneck.

Check the path:

Camera ports → access switch → uplink → router or core switch → NVR

If multiple cameras share one uplink, size that link for their combined traffic, not for one camera. A separate VLAN does not increase available bandwidth; it only helps organize and control traffic.

When PoE+ is the better choice

PoE+ is worth considering when one or more cameras have documented requirements that exceed standard PoE or leave little operating margin.

PTZ cameras

PTZ cameras may use more power while motors move than while they are stationary. Check the camera documentation for:

• Maximum power draw during movement
• Heater or defogger requirements
• Illuminator load
• PoE class or required standard
• Whether continuous movement changes the power requirement

Do not size a PTZ camera from its idle consumption.

Heaters and cold-weather features

A built-in heater can add a significant load in cold conditions. The camera may use little power in mild weather but approach its maximum rating when the heater operates.

If the installation is outdoors, size the PoE system for the documented maximum under the expected environmental conditions. Also verify that the camera itself is rated for the location and temperature range; PoE+ does not make an indoor camera suitable for outdoor use.

Infrared and white-light illuminators

Night vision may use infrared LEDs, while active deterrence cameras may use visible lights. These loads can change when lighting conditions change.

Check whether the camera’s stated power draw includes:

• IR illumination
• White-light illumination
• Audio
• Alarms
• Heater operation
• Other attached accessories

Future expansion

A PoE+ switch can provide useful headroom for a later camera replacement or an accessory upgrade. That does not mean every port must be PoE+. Compare the extra cost and power supply capacity with your likely expansion plans.

Cable distance, cable type, and voltage drop

Standard Ethernet channel design supports up to approximately 100 meters, including the permanent cable and patch cords, when the installation uses suitable cable and compatible equipment.

Plan for:

• Up to 90 meters of permanent horizontal cabling
• Patch cords at both ends
• Cable routing that avoids excessive bend radius and electrical interference
• Proper terminations
• Weather protection for outdoor connections
• Cable rated for the installation environment

Longer runs may require an approved PoE extender, an intermediate switch, fiber with power provided locally, or another design. Do not assume that a stronger PoE standard automatically extends the Ethernet distance.

At long distances, cable resistance can reduce the voltage available to the camera. Poor terminations, thin or unsuitable cable, damaged conductors, and high-temperature environments can make the problem worse. If a camera reboots when its IR lights or heater activates, investigate the cable path and power budget rather than assuming the camera is defective.

Active versus passive PoE

Standards-based active PoE negotiates power before applying the appropriate level. Passive PoE may apply a fixed voltage without the same negotiation process.

Never connect a passive-PoE injector or switch to a camera unless the camera explicitly supports that exact power arrangement. A physically compatible Ethernet plug does not prove electrical compatibility.

Wi-Fi quality still matters in a mixed system

Adding PoE cameras can reduce wireless load, but Wi-Fi cameras still need a reliable radio connection.

Evaluate the camera’s actual installed location rather than the signal strength next to the access point. Building materials, exterior walls, metal structures, distance, neighboring networks, and weatherproof enclosures can affect performance.

For Wi-Fi cameras, check:

• Signal quality at the camera location
• The access point’s available capacity
• Whether several cameras share the same channel
• The camera’s power source
• Whether the camera needs continuous upstream bandwidth
• Whether the recorder is local or cloud-based
• Whether the camera can reconnect after a temporary network interruption

A strong signal does not necessarily mean unlimited capacity. Several cameras transmitting high-bitrate video can consume substantial airtime even when each device appears connected.

IP planning and network isolation

A small installation may work with DHCP, but deliberate IP planning makes troubleshooting and expansion easier.

Choose an addressing method

Options include:

• DHCP reservations on the router or DHCP server
• Static IP addresses configured on the cameras
• A manufacturer-managed discovery and addressing system

DHCP reservations are often easier to document and change centrally. Static addresses can be useful in controlled installations but must be kept outside the automatic DHCP pool to avoid conflicts.

Document each camera’s:

• Location
• MAC address
• IP address or reservation
• Switch port
• PoE standard
• Maximum power requirement
• Recording channel
• Firmware and configuration date

Consider a camera VLAN

A separate camera VLAN can help isolate cameras from general devices and limit unnecessary access. If you use one, confirm that:

• The NVR can reach the camera VLAN
• Viewing devices can reach the NVR as intended
• Required discovery, management, or time-sync traffic is allowed
• Internet access is blocked or restricted when cloud access is not required
• Router and switch rules are documented

A VLAN does not replace strong passwords, updates, encrypted connections where available, or careful remote-access configuration. Avoid exposing camera or NVR administration directly to the public internet.

Plan for recording and privacy

Local NVR recording can reduce dependence on an internet connection, while cloud recording may require reliable upstream bandwidth and an account with the service provider. Some systems support both, but capabilities vary by camera and recorder.

Before installation, decide:

• Where recordings will be stored
• How long they should be retained
• Who can view them
• Whether audio recording is needed and legally permitted
• Whether cameras capture neighboring property or public areas
• How remote access will be secured
• What happens if the internet connection fails

Power and network planning should include the recorder, switch, router, and access points. An uninterruptible power supply can help keep a wired camera system and NVR operating during brief outages, but its runtime depends on the connected load and battery capacity.

PoE compatibility checklist

Use this checklist before buying or installing the system:

• [ ] Count wired PoE cameras separately from Wi-Fi cameras.
• [ ] Record each camera’s maximum power requirement.
• [ ] Confirm whether each camera needs PoE, PoE+, or a higher-power standard.
• [ ] Add the maximum power of all cameras, then include planning headroom.
• [ ] Check the switch’s total PoE budget, not only its number of PoE ports.
• [ ] Check the per-port power limit.
• [ ] Confirm that injectors, switches, and cameras use compatible active standards.
• [ ] Avoid passive PoE unless the camera explicitly supports it.
• [ ] Keep Ethernet channel runs within the supported distance.
• [ ] Use suitable cable, connectors, weather protection, and installation practices.
• [ ] Calculate camera bandwidth from configured bitrates, including substreams and audio.
• [ ] Check the speed and capacity of every uplink to the NVR or core network.
• [ ] Confirm the NVR’s supported camera count and incoming bitrate.
• [ ] Verify that the NVR and cameras use compatible connection methods.
• [ ] Test Wi-Fi signal and capacity at every Wi-Fi camera location.
• [ ] Plan DHCP reservations, static addresses, or another documented IP method.
• [ ] Consider a camera VLAN and restrict unnecessary internet access.
• [ ] Decide between local recording, cloud recording, or both.
• [ ] Review privacy and audio-recording requirements before positioning cameras.
• [ ] Test night operation, IR or white-light activation, PTZ movement, and heater operation where applicable.
• [ ] Label every cable, switch port, camera, and recorder channel.

The right choice is not simply “PoE+ for every camera.” Match the standard to the highest documented power demand, provide a sensible margin, and separately verify bandwidth, cable distance, recording compatibility, and network design. For additional options, review the available security cameras and compare their documented power and connectivity requirements before finalizing the switch.