What is the difference between PoE, PSE, and PD?

# What is the difference between PoE, PSE, and PD?

> Meta Description: PoE, PSE, and PD explained: what each means, how they work together, and why B2B buyers need to understand the difference to avoid compatibility issues.

> Target Keyword: PoE PSE PD difference

You're sourcing power supplies for a new batch of IP cameras. The spec sheet says "PoE compatible." You order 60W injectors. The cameras arrive, you plug them in, and nothing happens—or worse, they power on but don't establish a link. The vendor says, "It's your PSE." Your installer says, "It's the PD." And you're left wondering: *aren't they all just PoE?*

The short answer is no. PoE, PSE, and PD are three distinct layers of the same ecosystem, and confusing them is the number one source of procurement mismatches we see in global B2B shipments. Understanding the difference isn't just academic—it determines whether your devices power up reliably, negotiate the right wattage, and comply with safety standards.

Let's break down each term, how they interact, and what you need to check before you place your next order. 

### PoE: the standard, not the device

Power over Ethernet (PoE) is the *technology*—a set of IEEE standards (802.3af, 802.3at, and 802.3bt) that define how electrical power is delivered alongside data over standard Ethernet cables. It's the protocol, the voltage range (44–57V DC), the pinout options (Mode A or Mode B), and the negotiation handshake that ensures safe power delivery.

Think of PoE as the *language* spoken between two devices. It tells the power source how much power the load needs, and it tells the load that power is available. Without PoE, every networked device would need a separate power brick or wall outlet. With PoE, you can run a single cable for both.

Crucially, "PoE" is not a device—it's a capability. A switch might be "PoE-enabled," and a camera might be "PoE-powered," but the term itself refers to the protocol, not the hardware.

### PSE: the power source

PSE stands for **Power Sourcing Equipment**. This is the device that *injects* power onto the Ethernet cable. PSEs come in two physical forms:

- **Endspan** (or PoE Switch): a network switch that has built-in PoE circuitry on each port. It's the most common deployment for new installations.

- **Midspan** (or PoE Injector): a standalone device placed between a non-PoE Switch and the powered device. It adds power to the cable without altering data traffic.

A PSE's job is to:

1. Detect whether a connected device is a valid PD (using a low-voltage probe).

2. Classify the PD's power class (up to 90W for 802.3bt Type 4).

3. Supply the requested power and continuously monitor the connection for faults or disconnection.

Not all PSEs are created equal. Some support only 802.3af (15.4W), while others support 802.3bt (up to 90W). Some use Mode A (power on data pairs) and others use Mode B (power on spare pairs) – most modern PSEs support both, but legacy injectors may not. When sourcing, always check the **standard** and **power budget** per port.

### PD: the powered device

PD stands for **Powered Device**. This is the equipment that *receives* power from the cable. Common PDs include IP cameras, wireless access points, VoIP phones, lighting fixtures, and industrial sensors.

A PD has to:

- Present a specific signature resistor (25 kΩ) to indicate it is PoE-capable.

- Communicate its power class to the PSE during the negotiation phase.

- Accept the delivered voltage and convert it to its internal operating levels (usually 5V, 12V, or 24V).

The critical point: a PD will only draw the power it needs, up to the maximum the PSE can provide. If a camera requires 30W (802.3at) and you connect it to a PSE that only delivers 15.4W (802.3af), the camera may either not power on at all or enter a low-power mode with reduced functionality (e.g., no heater, no night vision). This is the most common field failure we see in B2B deployments.

### How they work together: the negotiation

When you plug a PD into a PSE, the following happens automatically:

1. **Detection** – The PSE sends a small current-limited voltage and checks for the 25 kΩ signature resistor. If not present, the PSE assumes it's a non-PoE device and does not apply power.

2. **Classification** – The PSE applies a higher voltage and measures the PD's current draw to determine its power class (0 to 8). The PD signals its maximum power requirement.

3. **Power on** – The PSE supplies the agreed voltage (typically 48V) and continuously monitors for overcurrent, short circuits, or disconnection.

This handshake is defined by the IEEE standards and is mandatory for safe operation. A "passive" PoE Injector that skips detection and classification (common in some low-cost devices) can damage non-PoE equipment—a risk we constantly warn our clients about.

### Why the distinction matters for procurement

When you're buying PoE components, here's what you need to ask:

- **For PSEs (switches or injectors):** What PoE standard do they support? What is the maximum power *per port* and the total power budget? Are they 802.3bt-compliant for high-power devices? Do they support both Mode A and Mode B? If you're planning to power multiple devices from one injector, check the number of ports and total output.

- **For PDs (cameras, APs, etc.):** What is their power classification? What voltage range do they accept (most work from 37–57V, but some older models are narrower)? Do they require a specific pinout (Mode A or B)? Some legacy equipment only accepts power on the spare pairs—if your PSE uses Mode A, they won't power up.

- **For cables:** PoE requires at least Cat5e for 30W and Cat6 for 60W+ to minimise voltage drop. Cable length must stay within 100m; beyond that, power and data both degrade.

### Common pitfalls we see in global shipments

As a trading house, we've processed thousands of PoE-related orders. The three most frequent mismatches are:

1. **Underpowered PSE** – A client buys a 16‑port switch with a total budget of 150W, but connects ten 30W PTZ cameras (300W total). The switch overloads and shuts down. Our recommendation: total PoE budget should exceed the sum of all connected PDs by at least 20%.

2. **Passive injectors disguised as standard** – Some low-cost injectors skip the detection handshake and force 48V onto the line. Plugging a non-PoE device (e.g., a standard laptop) into such an injector can fry the Ethernet port. We always advise our clients to demand "active" or "IEEE-compliant" injectors that perform detection.

3. **Ignoring distance-induced voltage drop** – At 90m, a 30W PD may only receive 20W due to cable resistance. This is a cable quality issue, not a PSE fault. We suggest using Cat6a for long runs and oversizing the PSE by one class (e.g., using an 802.3bt injector for an 802.3at device) to compensate.

### A real‑world example

Suppose you're outfitting a warehouse with 50 Wi‑Fi 6 access points, each requiring 25W (802.3at). You need a PSE—either a switch with 50 PoE+ ports and a total budget of at least 1250W + 20% margin (1500W), or a set of midspan injectors. Each access point is a PD that will negotiate the power. The cables must be Cat6, and each run must be under 90m. If any of these variables fails, the system won't work as expected—and the difference between PoE, PSE, and PD becomes painfully real.

### The procurement perspective

When sourcing, always request the product datasheets that clearly state the IEEE standard compliance, the power class, and the pinout configuration. We pre‑qualify suppliers based on their test reports for detection timing, inrush current, and thermal performance across temperature ranges. For project‑based orders, we offer sample kits so you can test your specific PDs with our PSEs before committing to full volume.

Ready to simplify your PoE procurement? We provide end‑to‑end compatibility testing, mixed‑model consolidation, and technical support for deployment. Contact us with your PD list and power requirements—we'll recommend the right PSEs and cables, and even run a lab simulation for your longest cable runs. Let's make sure your PoE project powers up on the first try.