ESP32 Power Supply Best Practices

ESP32 Power Supply Best Practices

More ESP32 project failures are caused by bad power supplies than by bad code. The ESP32 draws up to 500 mA during WiFi transmit bursts — more than most USB chargers can cleanly deliver through a thin cable. This guide covers every power scenario you will encounter and how to handle it correctly.

What the ESP32 Actually Needs

The ESP32 runs at 3.3V. Operating current varies widely:

• Deep sleep (ULP active): 5–10 µA
• Deep sleep (hibernation): 0.15 µA
• Active, CPU running, WiFi off: ~80–90 mA
• Active, WiFi transmitting: 160–240 mA typical, peaks to 500 mA
• Active, WiFi + Bluetooth active: 240–260 mA average

The 500 mA peak is critical. A power supply or LDO that cannot deliver this peak without sagging will cause brownout resets. The ESP32 brownout detector fires when VCC drops below ~2.44V.

USB Power: When It Works and When It Does Not

USB 2.0 is spec'd at 500 mA. A good USB cable from a good 5V/1A charger should supply the ESP32 DevKit adequately. However:

• Thin USB cables (cheap phone charger cables) have enough resistance to cause 200–400 mV voltage drop during peak current draw
• USB power banks often cut off when current drops too low during deep sleep — catastrophic for battery-saving firmware
• Sharing the USB 5V rail with relay coils and sensors can push total current beyond 500 mA

Fix: use a short, thick USB cable (22 AWG power conductors). Use a 5V/2A charger. Power relay boards from a separate 5V supply, not the same USB line.

LDO Regulators: AMS1117-3.3

If you are powering from a 5V supply and need a clean 3.3V rail, the AMS1117-3.3 is the standard choice on most ESP32 DevKit boards. It is rated at 800 mA output — sufficient for the ESP32 plus a few sensors. Add decoupling capacitors: 10 µF electrolytic on the output and 100 nF ceramic close to the ESP32 VCC pin.

For 12V to 3.3V: the AMS1117 will work but dissipates (12V − 3.3V) × current = ~4.4W at 500 mA. This is too much heat for the small SOT-223 package. Use a buck converter (LM2596 or MP1584) to step 12V down to 5V, then the AMS1117 from 5V to 3.3V.

Battery Power: LiPo + TP4056

For portable projects, a 3.7V LiPo battery is the natural choice. The ESP32 runs at 3.3V, and a LiPo at 3.7V nominal (4.2V full charge, 3.0V cutoff) drives the ESP32's onboard LDO cleanly throughout its discharge range.

Use a TP4056 charging module (₹20–40) for USB charging of the LiPo. The TP4056 has overcharge protection but no overdischarge protection — add a DW01A protection circuit or use a battery with built-in PCM. Most 18650 cells and many LiPo packs already include protection.

For deep-sleep sensor nodes targeting months of battery life: use a 2000–3000 mAh LiPo, enable deep sleep between readings, and disable power to all peripherals during sleep via a P-channel MOSFET gate switched by a GPIO or through the enable pin.

Mains-Powered Projects: HLK-PM01

For projects installed inside switch boxes or panels that need mains-derived power: the HLK-PM01 (Hi-Link) converts 100–240VAC to 5V/600 mA. It fits inside most Indian electrical boxes (footprint: 34 × 20 mm). Price: ₹180–250.

The HLK-PM01 output goes to the ESP32 DevKit's USB 5V pin or VIN pin, and the onboard AMS1117 provides 3.3V. Total system power for ESP32 + 4-channel relay + sensors fits within the 600 mA capacity.

For an 8-relay system, use the HLK-PM03 (5V/3W, 600 mA) or a dedicated 5V/2A adapter for the relay board and power the ESP32 separately from HLK-PM01.

Decoupling Capacitors: Always Add These

Place 100 µF electrolytic + 100 nF ceramic capacitor across the 3.3V supply as close to the ESP32 VCC pins as possible. This suppresses voltage spikes during WiFi transmission bursts. Even if everything else is correctly powered, missing decoupling capacitors can cause intermittent brownout resets that are maddening to debug.

Find AMS1117, TP4056, and HLK-PM01 modules at Circuitkar's power supply section.