Does my camera support PoE: check the port before you buy

A camera that runs on one Ethernet cable is the cleanest install on a machine: one cable per camera, one switch, no separate 24 V loom to wire and label. The disappointment comes after unpacking, when the body turns out to carry no Ethernet jack at all, or an Ethernet jack with no PoE line anywhere in its data sheet. This guide is the five-minute check: what the connector on the body tells you, which data-sheet line decides PoE support, how many watts each IEEE class delivers at the camera end, and the budget arithmetic that keeps a bank of cameras from browning out one switch. If the camera fails the check, you will know exactly which power lead to plan instead.

Does my camera support PoE?

It does only if two things are true at once: the body carries an Ethernet port (RJ45 or M12 X-coded) and the data sheet lists an IEEE 802.3af, 802.3at or 802.3bt line, because PoE is a power standard, not a plug style. Miss either one and the answer is no. A Wi-Fi-only body has no wired Ethernet path for power to ride, and an Ethernet port without a PoE listing is data-only hardware.

Both checks take minutes. The connector tells you whether Ethernet is even possible; the data sheet tells you whether power shares the cable. A camera sold as a network or IP camera is not automatically PoE-capable — a Wi-Fi radio is not Ethernet — and a series can ship in both PoE and data-only variants, so judge the exact model, never the series name.

Run the test while you browse the area scan cameras: filter Interface: GigE first, then confirm the PoE line on each shortlisted data sheet.

What port does a PoE-capable camera actually have?

A PoE camera's data connector is an RJ45 jack or an M12 X-coded 8-pin circular connector, and both carry GigE data and PoE power over the same cable; a DC barrel jack, a 6-pin or 12-pin I/O connector, or USB tells you power and data arrive separately. An RJ45 jack is the square 8P8C connector used on office Ethernet. On sealed or washdown-rated bodies the same interface appears as a round M12 connector with an X-coded 8-pin insert, which carries GigE data and PoE power together.

Connectors that are not Ethernet: USB Type-C or USB-B, the coaxial fittings used for CoaXPress, the SDR connectors used for Camera Link, 6-pin and 12-pin circular I/O connectors, and the DC barrel jack. The round metal connector on an industrial camera is usually power and I/O, not data. Ethernet over M12 is a specific insert — X-coded for GigE, D-coded for 100 Mbit/s — so the insert type settles it.

A shop card puts the data-interface line where you cannot miss it, under the photo with the filter values:

On the card above, Interface: GigE names the data interface, next to the sensor format and the mount. GigE says nothing about power. The PoE listing, when a camera carries one, is its own line in the power section of the data sheet, and that line — not the interface line — answers your question.

How do you check a camera's data sheet for PoE in four steps?

Four checks settle it: confirm the Ethernet connector on the body, read the interface line for GigE or 10GigE, hunt for a separate line naming IEEE 802.3af, 802.3at or 802.3bt with a class, then compare that class's delivered watts against the camera's maximum draw.

1. Find the data connector on the body. The mechanical drawing or connector photos in the data sheet settle it. An RJ45 jack or an M12 X-coded insert means Ethernet is possible. USB, coaxial, Camera Link or a bare barrel jack means there is no Ethernet path, so PoE is out: plan separate power and stop.
2. Read the interface line, then the power section. GigE or 10GigE in the interface line names data only. The PoE support line, when it exists, sits in the power section and names IEEE 802.3af, 802.3at or 802.3bt, often with a class number.
3. Write down two numbers. The camera's maximum power consumption in watts, and the delivered power of the PoE class it lists: 12.95 W for 802.3af, 25.5 W for 802.3at. The class must exceed the draw.
4. No PoE line? Spec the lead. Take the DC input voltage from the power section — 12 V and 24 V are the common industrial values — and size the current as watts divided by volts: a 10 W camera on 12 V needs 10 ÷ 12 = 0.83 A, so the next standard supply rating, 1 A, covers it with margin.

How much power does PoE deliver to a camera?

IEEE 802.3af supplies 15.4 W at the switch and guarantees 12.95 W at the camera after cable loss; 802.3at raises both figures to 30 W and 25.5 W, and 802.3bt reaches 51 W or 71.3 W at the camera for Types 3 and 4.

The difference between the two columns is the cable-loss allowance: 2.45 W for 802.3af and 4.5 W for 802.3at, budgeted so the full camera-end figure holds for any run up to 100 m. Classes refine the first two types: Class 0 advertises 15.4 W, Classes 1 to 3 deliver 3.84, 6.49 and 12.95 W, and 802.3at adds Class 4 at 25.5 W.

Keep 20% headroom. On 802.3af that makes 12.95 × 0.8 = 10.36 W the heaviest comfortable draw; a camera rated at 12 W maximum leaves just 12.95 − 12 = 0.95 W and belongs on 802.3at. A thin margin shows up in the image before it reaches any log: brightness sagging mid-exposure as the supply dips under load, the failure pattern the PoE camera illumination droop guide walks through. To prove delivery rather than argue about it, measure with the camera running at full frame rate — the PoE power troubleshooting walkthrough shows that measurement.

Can an adapter, injector or special cable add PoE to a camera that lacks it?

No — PoE needs the powered-device electronics inside the camera; a passive injector feeds its voltage into any port without a detection handshake and can destroy a data-only Ethernet jack, while a compliant active injector detects no valid signature and never switches power on. PoE lives in the camera's powered-device circuitry: the port presents a 25 kΩ detection signature and advertises its class, and only then does a compliant power source — a PoE switch port or an active midspan injector — apply its nominal 48 V. A port without that circuitry cannot negotiate power, and no cable changes a port's electronics.

An active injector follows the standard's rules: it probes, finds no valid signature on a data-only camera, and never energizes the line. You get no PoE and no damage. A passive injector skips detection and feeds its full voltage into the pins continuously, which is where the damage risk comes from.

A PoE splitter runs the other direction — it extracts power from a live PoE line into a DC plug — and helps only a camera that already has both an Ethernet port and a DC-in socket; the conditions are spelled out in the FAQ below. A Wi-Fi-only body has nothing for any of these devices to connect to, so the fix there is a different camera. When the check fails and you need the workable wiring, the camera power over Ethernet guide lays out the alternatives.

What hardware does a PoE camera installation need?

Three parts: a PoE-capable camera, a PoE source (a switch with PoE ports or a midspan injector) and one Ethernet cable per camera; a 15 m or even a 100 m run delivers the full class, because 802.3af budgets 2.45 W and 802.3at budgets 4.5 W for cable loss.

• A PoE source. A switch with PoE ports, or a midspan injector between a plain switch and the camera. An 802.3at port powers an 802.3af camera; the reverse is not true.
• One Ethernet cable per camera. Cat 5e or better carries 802.3af and 802.3at alongside GigE data, and the standard holds the full camera-end figure for runs up to 100 m.
• Two numbers from each data sheet. Maximum draw in watts and the PoE class, which feed the budget check below.

The accessories finder filters these by length and connector. For the run itself, pick the cable for length, flex and locking:

Both are standard Ethernet camera data cables; PoE rides the same twisted pairs as the data, so the cable adds no power requirement of its own. The LS-CBL-0199 suits short drag-chain runs at 3 m, and the LS-CBL-0117 covers longer static runs at 15 m with locking RJ45 studs.

Worked example: eight cameras on one switch

Example values: each camera's data sheet reads 10 W maximum draw, the switch is an 8-port PoE unit with a 130 W power budget, and the runs are 15 m.

Per camera: 12.95 − 10 = 2.95 W of margin on 802.3af, about 23% headroom, so the class fits each camera. Whole switch: 8 × 10 W = 80 W of real draw against the 130 W budget, which leaves 50 W spare. Even with every port negotiating the full Class 3 source rating, 8 × 15.4 W = 123.2 W still sits under 130 W. Cable: 15 m runs sit far inside the 100 m the standard budgets, so no extra allowance applies.

Decision: this bank runs on 802.3af with room to spare. A ninth 10 W camera makes 90 W of real draw, still under budget, but pushes the worst case to 123.2 + 15.4 = 138.6 W, past 130 W — that is the point to move to a PoE+ switch or a bigger budget.

When should a machine-vision camera skip PoE and take separate power?

Skip PoE when the camera's maximum draw exceeds its PoE class — a 14 W camera browns out on 802.3af's 12.95 W — when an I/O cable for triggering exists anyway, or when recovery by power cycle matters more than cable count.

The draw beats the class. A model rated above 12.95 W has no business on an 802.3af port: either the series lists 802.3at, or it takes separate power.

The I/O lead exists anyway. When triggering and strobing already run a cable to each camera, merging power into the Ethernet run saves less than it seems; separate power then costs almost nothing extra.

Recovery matters. A hung camera that only a power cycle clears resets instantly from a switched supply or relay. Resetting over PoE requires the switch to power-cycle its ports on command, which not every managed switch does.

If recovery drives the design, the power lead is its own cable on the camera's power and I/O connector:

The LS-CBL-0300 carries power and I/O over an M8 8-pin connector to open leads across 7 m of drag-chain-rated cable, so the supply and the trigger wiring land on one connector.

A USB3 camera takes PoE out of the decision entirely — power arrives with the data connection — and the checks that matter there are trigger support and link stability, as in the USB camera external trigger guide.

What should you confirm before you order?

Before you order, confirm the port on the body, the IEEE PoE line with its class in the data sheet, and a switch or injector budget that covers every camera's draw with 25% headroom — the six-line list below is the whole pre-order audit.

• The connector on the body, from the data sheet drawing: an RJ45 jack or an M12 X-coded insert.
• The data sheet PoE line: IEEE 802.3af, 802.3at or 802.3bt, with its class.
• The camera's maximum draw in watts, from the power section.
• Class fit: delivered power at least 1.25 times the draw.
• Source budget: every camera's draw summed, times 1.25, against the switch or injector rating.
• Cable category: Cat 5e or better for 802.3af and 802.3at with GigE data.
• The exact model variant, because PoE and data-only versions share a series name.

Wire the plan together in the camera finder: filter Interface: GigE, shortlist, then open each power section. The system configurator pairs the chosen camera with its cables and accessories. Once wired, the two stalls you may still hit at bring-up are a firewall eating discovery packets — the GigE Vision firewall guide covers it — and two interfaces answering for one camera, diagnosed in the duplicate PoE camera discovery guide. More integration checks sit on the systems topic page, and the team answers wiring questions before you order through the contact page.