Leo · 2026-11
PoE camera power budget planning is the arithmetic that decides how many cameras one switch can actually carry. Sum what each camera draws, add what the cable loses, compare the result against the switch budget left after overhead, and keep at least 20 percent unallocated.

woCyber builds private-cloud storage and surveillance appliances for OEM and private-label programs, with research and development in Beijing and mass-production manufacturing in Shenzhen. The guidance below is written for the integrator who has a fixed camera list and an unfixed switch order, because that is the moment a power mistake becomes a truck roll.
Power fails before storage because a camera that cannot boot records nothing, while a short retention window only loses old footage. A site that runs out of port power loses every camera on that switch at once, and the symptom usually appears as random dropouts rather than as a clean overload.
Storage planning has a formula that most integrators apply without prompting, and the internal guide to nvr-storage-planning-for-ip-camera-projects covers it. Power planning has an equally simple formula that far fewer buyers apply, and the failure it prevents is more expensive to fix on site.
Each PoE standard fixes two numbers: what the switch port must supply, and what the camera can use after cable loss. The IEEE 802.3af standard supplies 15.4-W at the port and guarantees 12.95-W at the device, while 802.3bt raises the ceiling to 90-W at the port.
| Standard | Power at switch port (W) | Power at camera (W) | Typical camera class |
|---|---|---|---|
| 802.3af (Type 1) | 15.4 | 12.95 | Fixed indoor dome, 2 to 4 MP |
| 802.3at (Type 2) | 30 | 25.5 | PTZ, varifocal, IR-heavy outdoor |
| 802.3bt Type 3 | 60 | 51 | Multi-sensor or heater-equipped |
| 802.3bt Type 4 | 90 | 71 | Specialty PTZ with blower |
Power figures appear in watts throughout the article, and the gap between the two columns is not marketing margin. It is the energy that disappears in the cable, and the next section sizes that gap for the run lengths common on outdoor sites.
Every class keeps a margin between the port and the device. The 802.3at class allows 30-W at the port and 25.5-W at the device, and the 802.3af class allows 15.4-W against 12.95-W. The published difference is what the cable and the connector pair consume across a full channel, and it is the reason a port rated for one class cannot always serve a camera rated for the same class at the far end of a long run.
Two habits follow from that margin. The first is to record the run length against each port in the as-built drawing, because the longest run in a zone sets the class for that zone. The second is to treat a camera at the top of its class as a camera that needs the next class when the run is long, rather than as a camera that fits because the data sheet says so.
Neither habit costs money at the design stage. Both cost a callout when they are skipped, because the symptom of a starved port is a camera that reboots at dawn rather than a camera that never worked.
One PoE switch carries as many cameras as its total budget allows after switch overhead, not as many as it has ports. Take a hypothetical 24-port switch rated at a 240-W budget: it carries fewer than 24 cameras on the 802.3at class, even with every port populated.
Worked example, using a hypothetical 24-camera installation at a self-storage facility: 18 fixed domes on the 802.3af class and 6 outdoor PTZ units on the 802.3at class.
A midspan injector is the usual answer on a retrofit. It sits between the switch and the camera group, supplies the class from its own budget, and leaves the switch ports as data-only links. The trade is a second device to power, monitor, and mount, which is why midspans suit buildings where the existing switch cannot be replaced rather than new builds where the budget is still open.
Port count and budget diverge further on mixed sites. A switch sold as 16 ports with a 120-W budget carries seven cameras at the 802.3at class with headroom, and the remaining nine ports can still serve cameras on the lower class as long as the running total stays inside the budget. That is a viable design, and it fails the moment someone assumes every port is equal.
Dynamic allocation changes the first bullet, not the third. When a switch negotiates through LLDP, it reserves what the camera requests rather than the full class ceiling, so the same 24-camera site can fit inside a smaller budget without moving a cable. The catch is that the saving depends on firmware behavior at both ends, and a camera that has not yet negotiated still needs the ceiling available at boot.
The two totals sit more than double apart, 457.2-W against 174-W, and that gap is the whole argument for checking whether the switch supports dynamic allocation. A buyer who compares port counts alone orders a 240-W budget for a site that reserves 548.6-W, and the shortfall appears later as cameras that drop and recover.

On small sites the recorder replaces the switch as the constraint, so its published budget matters more than its port count. Buyers should obtain the port number, the per-port class, and the total budget in writing, because those three rarely appear together on a product page.
A site this small rarely justifies a separate switch and server, so the recorder carries both jobs. That changes what the buyer must ask: the port count, the classes the unit negotiates, and the total budget belong in the quotation, because a recorder that supports only the lower class cannot carry a heated PTZ regardless of how many ports it has.
Combined recorder and storage appliances vary widely on those three points, and the published material for a given model may state none of them. Buyers shortlisting one can set its stated figures against the camera list using S1 AiNAS Security Kit, then confirm whatever is missing with the supplier in writing before the order is placed.
Cameras terminate, record, and get analyzed in one box, which is what a small site needs when no server room exists. Integrators who need the wider appliance comparison can read nvr-vs-nas-for-surveillance-which-appliance-fits-your-cameras before fixing the topology, because the cabling plan follows the topology rather than the other way round.

Five power checks belong in the quote: the class for every camera model, the total switch or recorder budget, the longest run in meters, the ambient temperature range at each outdoor location, and the spare capacity left after commissioning. Each one prevents a specific callback.
Ambient temperature belongs on the list because heater-equipped cameras draw their highest current in the coldest weather, which is exactly when a marginal budget fails. Spare capacity belongs on the list because a site fully allocated on day one cannot accept a camera added for insurance reasons six months later. Twenty percent headroom costs less than a second switch, and it costs far less than a night call.
Integrators who assemble the whole bill of materials for a client can compare the storage side against the internal guide to how-to-budget-for-on-premise-storage, which applies the same arithmetic-first approach to drive capacity and retention.
An OEM kit inherits the support call, so the brand that ships it owns the power questions, and a kit that ships with a switch turns the class table into a product document rather than an installer note. The published woCyber OEM options include white-label apps, brand user interface and boot animation, logo printing or laser engraving, localized documentation, and regional power adapter variants.
Existing platforms carry an MOQ of 100 units per SKU; a design that needs new tooling or a board respin starts at 1,000. The certification set published for the product lines is CE, UKCA, FCC, RoHS, REACH, and WEEE.
For a brand assembling a camera kit, the class table belongs in the installation guide next to the switch model the kit ships with, and the support script should name the class before it names the camera. The as-built drawing that carries a length against every port is the document an installer will thank you for in February.

Whether you need surveillance storage, private cloud for business data or an OEM/ODM partner, our export team will map the right platform to your application — reply within one working day.
Explore our AI NAS & Surveillance lineup
Browse all platforms →
An off-grid security camera with local storage records onto hardware at the site, powered by the site's own supply, with no cloud…
November 20, 2026A NAS backup strategy for business rests on three pillars in 2026: a copy that is separate from the primary array, a…
November 20, 2026A security camera system without monthly fees records to storage you own, on hardware that processes video locally, instead of uploading clips…
Ask our export team for the OEM/ODM cooperation guide and a written quotation.