Powering a Headless Raspberry Pi 4 or 5: USB-C, GPIO, or PoE

Problem and takeaway

You are deploying a Raspberry Pi 4 or 5 headless, meaning without a monitor or keyboard, in a location where power access is limited or where you want to send power and data over one Ethernet cable. Choosing the wrong power source can cause silent SD-card corruption, random reboots, or CPU throttling under load. Use the official Raspberry Pi USB-C supply for most single-board deployments. Reserve GPIO 5V injection for low-power accessories only, and choose a PoE HAT when Ethernet cabling already exists and the power budget fits your peripherals.

Decision and constraints

Decision: power the board through its USB-C port unless you have a specific reason not to. Constraints that shape this choice:

• Headless operation with no local display or keyboard.
• Raspberry Pi 4 or Raspberry Pi 5; older models and the Pi 400 have different power behavior.
• Remote or limited-outlet installation.
• Attached HATs or USB devices may push total current above what the GPIO header can safely pass.

Supported options

Option	Best for	Main limitation
Official USB-C supply	Most headless Pi 4 and Pi 5 deployments	Requires a nearby AC outlet; adds one cable
GPIO 5V header, pins 2 and 4	Low-power accessories fed by an existing regulated 5V rail	Bypasses onboard input protection; not recommended as the primary supply under load
PoE HAT, 802.3af or 802.3at	Sites with a PoE switch and an Ethernet run already in place	Added cost; fan noise possible; power is shared with the fan and attached HATs

Trade-offs

Official USB-C gives the board full current headroom and keeps the onboard protection and filtering circuitry in the path. The downside is the need for an AC outlet near the Pi.

GPIO 5V injection removes the USB-C cable but backpowers the board. It bypasses the input protection, so a sagging 5V rail may not be logged cleanly and can corrupt the SD card. Do not use it as the primary supply when USB devices or HATs draw significant current.

A PoE HAT delivers power and data over one Ethernet cable, which simplifies cabling in remote closets or outdoor enclosures. However, the available current is capped by the PoE class and the switch, and the HAT fan and any attached HATs share that budget. A Pi 5 with several peripherals may exceed what a marginal PoE setup can provide.

Implementation: official USB-C supply

1. Use the official Raspberry Pi USB-C supply matched to your model. Confirm the exact voltage and current rating in the official documentation for your board revision before purchase.
2. Connect the supply to the Pi’s USB-C port. Do not connect USB-C while also injecting 5V into the GPIO header; simultaneous sources can backfeed and damage the board.
3. If you are omitting an SD card and booting from USB, check bootloader support first. Run this command on the Pi over SSH:

vcgencmd bootloader_version

vcgencmd is the VideoCore command-line utility used to query firmware and hardware status on the Pi. It normally requires no special permissions. Review the output to confirm whether your bootloader version supports USB boot; enable it through the official Raspberry Pi Imager or raspi-config only if your model and bootloader version support it.

Implementation: GPIO 5V header

Use this only when an external regulated 5V supply is already present and USB-C is impractical.

• Connect regulated 5V to GPIO pins 2 and 4.
• Connect ground to GPIO pins 6, 9, 14, and 20, or any available ground pin.
• Never connect a USB-C supply at the same time.
• Use a fused supply and keep wiring short to reduce voltage drop.

Implementation: PoE HAT

• Confirm that your network switch supports 802.3af or 802.3at and that the HAT class matches your Pi model.
• Mount the PoE HAT on the GPIO header and connect one Ethernet cable from the HAT to the PoE switch.
• Expect the HAT fan to spin; it may be audible in quiet environments.
• Keep the combined load of the Pi, fan, and attached HATs within the HAT’s rated output.

Validation

Check for under-voltage and throttling with vcgencmd over SSH. No special permissions are normally required:

vcgencmd get_throttled

Expected result at idle and under load: throttled=0x0. Any non-zero value means an under-voltage event, frequency cap, or thermal throttle has occurred since the last boot.

To stress the Pi, run one yes process per CPU core in the background:

yes > /dev/null &
yes > /dev/null &
yes > /dev/null &
yes > /dev/null &

Run this for several minutes while polling vcgencmd get_throttled. Stop the load with killall yes when finished. Background CPU load raises temperature; the Pi will throttle to protect itself, but ensure the case has adequate airflow.

Measure the 5V rail directly with a multimeter while under load. Place the positive probe on a GPIO 5V pin and the negative probe on a ground pin. A sustained reading below about 4.75 V indicates an insufficient supply. Risk: slipping with the probe can short adjacent GPIO pins and damage the board; power down or probe carefully.

Limitations and verification

Behavior differs for the Pi 400, Compute Module, and older Pi 1, 2, and 3 models; official supply ratings are model-specific. vcgencmd get_throttled records events since boot but may miss very brief voltage dips. Exact peak current for a given HAT combination should be confirmed against official Raspberry Pi documentation before deployment. Treat model-specific ratings and PoE class compatibility as items for human review against current official documentation.

Practical check: after installation, run vcgencmd get_throttled at idle, then again after five minutes of CPU load. If both return throttled=0x0 and the multimeter reading stays above 4.75 V on the 5V rail, the power arrangement is adequate for that workload.