Blog
ESP32 Power: Batteries, Voltage, and Consumption
How to power esp32 is the first question most people hit — usually after a board that worked on USB dies unplugged. Volts in, current spikes out: knowing which pin takes what is the battle.
How to Power ESP32?
USB is the default answer, and it’s the right one — the port feeds 5V to the onboard regulator, which steps it down to 3.3V. Beyond USB, feed regulated 5V to VIN. Never push 5V into the 3.3V pin — output only. WiFi transmits pull ~300mA spikes, so weak supplies brown out mid-transmit; resets when WiFi connects mean power, not code. Inputs vary by board — the getting-started FAQ covers USB.
How Much Power Does an ESP32 Use?
An ESP32 burns roughly 0.3–0.6W; the radio decides most of it. Idle, it draws 70–150mA at 3.3V; transmit bursts push toward 300mA; deep sleep drops to ~10µA. So how much power does esp32 use? Duty cycle: a node waking two seconds a minute runs weeks on a LiPo, a streaming board needs real planning.
How to Power the ESP32?
Input 5V through USB or VIN and let the regulator do the rest. VIN tolerance is where the official docs get vague: the datasheet targets 5V, most boards tolerate up to ~12V, some nothing above 6V. The safe number is 5V. How to power esp32 with power supply? A bench supply at 5V is cleanest.
How Many LEDs Can an ESP32 Power?
One or two indicator LEDs, honestly. A GPIO pin is comfortable around 12mA, and everything shares the 3.3V rail with a spiking radio. Beyond a status LED, drive a transistor — the ESP32 should be a switch, not a power supply.
How to Power ESP32 Without USB?
A single-cell LiPo or 18650 through a small boost or buck-boost converter is the standard answer. You can’t wire a 3.7V cell straight to VIN — the regulator wants ~5V. I ran a balcony weather node for three months on one 18650 through a $3 buck-boost, waking every ten minutes. Boards with a built-in charger are how to power esp32 without usb and still charge it: USB by day, battery by night. The free ESP32 simulator shows the current profile.
Why does my ESP32 keep resetting when WiFi connects?
That’s the brownout detector: the 3.3V rail collapses under the transmit spike. “Brownout detector was triggered” before the reboot is the giveaway. Fix in this order: cable, shorter wires, a 100–470µF capacitor across 3.3V and GND, then a supply that holds 5V under load. You can disable the detector — I’ve only done it on a bench with a scope proving the rail was clean. Resets even on a solid supply? Suspect the regulator; the debugging FAQ covers the serial log.
What’s different about powering an ESP32-CAM?
Same rails, harsher appetite. The camera draws steady current at init, so how to power esp32 cam with a phone charger usually works, while thin dupont wires from a LiPo glitch mid-frame. A 470µF cap near the board fixes most “won’t initialize” cases that aren’t firmware.
Can I give the ESP32 an external power supply?
Yes — the normal way to run anything real. How to give external power supply to esp32: regulated 5V to VIN (or the 5V pin where present), GND to GND, nothing else. USB and VIN share the same rail on most devkits, so both plugged in is fine; 12V into VIN while USB is connected is not.
Can the ESP32 power sensors and other peripherals?
The 3.3V pin sources a few hundred milliamps on a good board — enough for a sensor or two. An MPU6050 barely registers. Motors, relays, servos, and LED strips are not fine: they get their own supply, with a driver in between.
What is the most common power mistake?
Five volts into the 3.3V pin, followed by reversed battery polarity — why pinouts exist. How to supply power to esp32 safely: 5V only into VIN or USB, never feed the 3V3 pin from outside, check polarity twice. The full FAQ index has the getting-started path; the free simulator shows current draw first.
Watch a Battery Drain — Safely — In Your Browser
Power questions click into place the moment you watch voltage as a number:
- Battery voltage monitor — a divider feeding an ADC pin, printed live:
Battery: 3.87 V
Battery: 3.85 V
WARNING: Battery low!Drop the virtual supply and you hit the warning threshold — the exact moment your real project would brown out. Pair it with dual-channel ADC to compare two cells side by side, and the consumption/battery-life math above becomes something you have watched happen.