Low-Power ESP32 Battery Projects: Deep Sleep and Solar

A battery ESP32 project lives or dies on one number: average current. Get it right and a single 3000 mAh cell runs a field sensor for months. Get it wrong and the same cell is dead before dinner.

This guide covers the five power modes, every wake source, board-level sleep drain, battery sizing, solar sizing, and the mistakes that drain a pack in days. The sensor node build is covered in ESP32 Battery Sensor Node: Deep Sleep and Power Budget, and LiPo wiring in How to Power ESP32 and Arduino Projects on LiPo Power.

How long can an ESP32 really run on battery?

Battery life in hours equals usable battery capacity divided by average current. Average current is the awake share times the awake current, plus the sleep share times the sleep current. Source: ProjectECH; DroneBot Workshop; Hubble.

Take a node that wakes for 20 seconds at 180 mA and sleeps at 15 microamps, on one 18650 cell with a realistic usable capacity of 2400 mAh. Source: ProjectECH.

Report interval Average current Battery life from 2400 mAh
Every 10 minutes (180 x 20 + 0.015 x 580) / 600 = about 6.0 mA About 400 hours, about 16 days
Every 60 minutes (180 x 20 + 0.015 x 3580) / 3600 = about 1.01 mA About 2376 hours, about 99 days

Three lessons fall out of that table. First, the interval dominates: 60-minute reports give roughly 6 times the battery life of 10-minute reports. Second, sleep current matters: with a 5 mA sleep the 60-minute column collapses to about 17 days. Third, awake time is the other lever: Wi-Fi can spend 3 to 8 seconds just joining the network, so cut the awake window to 5 seconds. Source: ProjectECH.

Radios differ too: Wi-Fi transmit runs about 160 to 260 mA, BLE about 95 to 130 mA, and LoRa about 20 to 120 mA transmit with about 0.2 microamps in sleep. Source: ProjectECH; Hubble.

Which sleep mode does your project need?

The ESP32 has five power states. The figures below are chip-level typicals; your board will draw more. Source: DroneBot Workshop; Espressif sleep modes documentation.

Mode CPU and peripherals Radio Typical chip current What survives
Active On On or off 240 mA Wi-Fi transmit peak Everything
Modem sleep On Off between checks About 3 to 20 mA Everything, Wi-Fi association kept
Light sleep Paused Off About 0.8 mA RAM and registers, resumes where it stopped
Deep sleep Off Off About 10 to 25 microamps RTC memory only, 8 KB slow memory
Hibernation Off Off About 2.5 microamps Nothing guaranteed, not even RTC memory

Active is the normal running state; the only saving is lowering the CPU clock. Modem sleep turns the radios off between transmissions while the CPU keeps running, staying associated with the router by waking the radio on the DTIM interval. Light sleep pauses the CPU clock but preserves RAM and registers. Deep sleep powers down almost everything; only the RTC domain and optionally the ULP coprocessor stay alive. Hibernation is the deepest state: even the 8 MHz RTC oscillator and the ULP coprocessor are off, and RTC memory is not guaranteed. The only wake source is an EXT0 GPIO interrupt. Source: DroneBot Workshop.

What wakes the ESP32 from deep sleep?

The wake source defines the whole power profile. Source: ProjectECH; DroneBot Workshop; Hubble.

Wake source How it works Best for
Timer wake RTC timer fires after N microseconds Periodic sensing: wake, read, send, sleep
EXT0 wake One RTC GPIO goes high or low One event: a PIR motion sensor, a float switch, a door switch
EXT1 wake Any of several RTC GPIOs changes Several events at once
Touch pad wake A configured touch pad crosses its threshold A manual “report now” button on a sealed enclosure
ULP coprocessor Runs while the main CPUs sleep, about 150 microamps typical Wake the main CPU only on a threshold

Timer wake is the workhorse: call esp_sleep_enable_timer_wakeup(), then esp_deep_sleep_start(). EXT0 and EXT1 wake on a pin: EXT0 watches one RTC GPIO at one level, ideal for a PIR sensor, and EXT1 watches several. On the standard ESP32, RTC-capable GPIOs are 0, 2, 4, 12 to 15, 25 to 27, and 32 to 39. Touch wake uses the capacitive touch pins. The ULP coprocessor can poll an ADC channel or a GPIO while the main CPUs sleep and wake the main CPU only on a threshold. Source: ProjectECH; DroneBot Workshop; Hubble.

Always configure a wake source first, or the chip sleeps forever. Source: ProjectECH.

State survives deep sleep through RTC slow memory: variables declared with RTC_DATA_ATTR survive deep sleep, but not a power loss or a hard reset. Source: ProjectECH; TheLinuxCode; post 23387.

Why does your dev board never reach the datasheet sleep current?

The datasheet deep sleep figure is the bare chip. A dev board adds parts that draw current around the clock, and those parts dominate the sleep budget. Source: ProjectECH; DroneBot Workshop; post 23387.

A typical 30-pin DevKit board carries an AMS1117-3.3 linear regulator with a quiescent current of about 5 mA typical. With the USB chip, power LED, and pull-ups added, a “sleeping” dev board typically draws 5 to 15 mA. At 10 mA, a 3000 mAh cell lasts 300 hours, under two weeks. Source: ProjectECH; DroneBot Workshop.

Fix it in one of three ways: power the board through the 3V3 pin from an efficient external regulator; use a bare ESP32 module on a minimal breakout; or use a board designed for battery use. Measure the sleep current yourself first. Source: ProjectECH.

The XIAO boards stocked at QRC are the battery-friendly end of this scale, and the figures conflict across sources, so they are stated here as a sourced range, never as a single bench-tested number. Seeed’s wiki lists the plain XIAO ESP32S3 at 14 microamps in deep sleep, 2 mA in light sleep, and 27 mA in modem sleep. The XIAO ESP32S3 Sense with its expansion board attached is listed at 3 mA in deep sleep: the expansion board costs roughly 200 times the plain board’s sleep current, so detach it for a battery build and use the detachable camera only when the project needs it. The XIAO ESP32S3 Plus is listed at 33.51 microamps in deep sleep, and the XIAO ESP32C3 at 44 microamps. CircuitDigest measured a plain XIAO ESP32S3 board at 130 microamps in deep sleep, against a bare ESP32-S3 chip rating of 7 to 8 microamps. Plan with the worst figure in the range. Source: Seeed Studio XIAO ESP32S3 wiki; CircuitDigest; Embedded Nerd.

How do you size the battery?

Measure the build that will actually run from the battery. Source: UMA Technology; Hubble.

Step 1: measure each operating state. Record current in each state with a USB power meter, and use a multimeter in series with the battery lead for sleep. Source: UMA Technology; Hubble.

Step 2: calculate the average current. For each state, multiply current by time in that state, then sum and divide by the cycle time. Example: wake every 15 minutes, transmit for 5 seconds at 150 mA, sleep the other 895 seconds at 15 microamps. Average equals (5 x 150 + 895 x 0.015) / 900, which is 0.85 mA. Source: Hubble.

Step 3: divide capacity by average current, then derate. A 3000 mAh battery at 0.85 mA average gives about 3,500 hours, about 146 days. Now derate: usable capacity is about 70 to 80 percent of the label after aging, temperature, and self-discharge, so plan on about 2400 mAh usable from a 3000 mAh cell. Source: ProjectECH; Hubble; e-fm.tech.

Step 4: pick the chemistry. A standard LiPo at 3.7 V is workable for 6 to 12 month projects. A LiFePO4 cell at 3.2 V has low self-discharge around 3 percent per year, so it suits solar recharging. A CR2032 at 220 mAh suits only the lowest-power applications. Source: Hubble.

The biggest lever is the awake time: every second of Wi-Fi connect time at 150 mA costs as much as 150 seconds of sleep at 1 mA. Source: post 23387.

How do you size a solar panel for an ESP32 project?

A solar panel only has to replace what the board uses, plus the charging losses. Size it from the worst month, not the average: a panel sized for summer sun dies by mid-December. Source: Hubble solar sizing guide; e-fm.tech.

Step 1: daily energy. Daily energy equals average current times supply voltage times 24 hours. The 0.85 mA node at 3.7 V uses about 76 mWh per day. Source: Hubble solar sizing guide.

Step 2: battery autonomy. Size for three cloudy days: three days at 76 mWh per day is 228 mWh, or about 62 mAh at 3.7 V. Source: e-fm.tech; post 23188; post 15185.

Step 3: worst-month peak sun hours. Peak sun hours are the hours per day of full sunlight that would deliver the same energy as the real day. Look it up for your coordinates with PVGIS or NASA POWER, and use the worst month. Source: e-fm.tech.

Step 4: panel watts. Panel watts are about equal to daily energy divided by (charging efficiency times peak sun hours times a derating factor). The worked example comes out to about 0.021 to 0.11 W. In practice, fit a panel several times larger than the paper minimum. Source: e-fm.tech; Hubble solar sizing guide.

Step 5: charge controller. A small panel charging a single lithium cell needs a charger that terminates at 4.2 V and a protection circuit. The TP4056 module below charges a single cell from USB or a solar panel at up to 1 A. Standard lithium-ion and LiPo cells should not be charged below about 0 degrees C. Source: ProjectECH; e-fm.tech.

No solar panel is stocked at QRC as of 2026-11-21, so no panel is linked in this guide. The BirdBox build in Run a BirdBox Camera for Months on Solar Power shows the same pattern: panel in full sun, short cable, battery sized for three cloudy days.

How do you charge and protect the pack?

Charging, protection, and regulation are three separate jobs, and one module does not always do all three. The full wiring chain is covered in How to Power ESP32 and Arduino Projects on LiPo Power. Source: post 19087.

The TP4056 load-sharing trap. The TP4056 has no load sharing: it cannot tell current going into the battery from current drawn by your circuit. With the load on the battery terminals, the charger sees the load current as charge current, never detects the proper termination taper, and can keep pushing current into an already-full cell. Wire battery to B+ and B-, supply to IN+ and IN-, and take system power from OUT+ and OUT-. The proper fix is a load-sharing power-path circuit. Source: ProjectECH; post 19087.

The cutoff voltage has no single agreed number. Sources disagree on the per-cell cutoff, with figures from 3.0 V to 3.5 V per cell. This guide states that range and does not pick one number. Read the cutoff from the docs for the protection module and the battery you own, and wire the protection so it disconnects the pack from everything. The stocked 3000 mAh pack below has a built-in protection board. Source: post 19087.

What mistakes drain a battery pack in days?

  • Trusting the chip sleep figure for the whole board. The chip sleeps at 10 to 25 microamps; the board sleeps at milliamps. Measure the whole board.
  • Leaving Wi-Fi on between readings. A board that idles with Wi-Fi connected draws 35 mA or more. Sleep between readings.
  • Letting Wi-Fi join slowly, every cycle. Every awake second at 150 mA costs as much as 150 seconds of sleep at 1 mA. Use a static IP and cap retries at three.
  • Sizing the solar panel for summer. The panel must cover the worst month, not the average. Size from worst-month peak sun hours, and test through a cloudy week.
  • Never measuring the sleep current. Every battery estimate in this guide is arithmetic from stated inputs. Measure your own board’s sleep current and redo the math.

How do you fix a low-power project that dies too soon?

The board draws milliamps in deep sleep. Measure the board alone, then the regulator or converter alone. The likely causes are the power LED, the USB-to-serial chip, or a regulator with high standby draw. Power the 3V3 pin directly from a regulated 3.3 V supply, or remove the power LED where the board allows it. Source: DroneBot Workshop; post 23387.

The node boot-loops when the battery gets low. A nearly empty cell sags under a Wi-Fi transmit burst, and if the sag crosses the brownout threshold the chip resets mid-transmission. Treat 3.2 to 3.3 V under load as the effective empty point. The brownout fix is covered in ESP32-CAM Troubleshooting: Brownout and Camera Init Failed. Source: ProjectECH.

The battery voltage falls every week even with solar. The panel is too small for the worst month, the panel is shaded or flat, or the charge current never tapers. Check the battery voltage after the first week, and add panel size if it keeps falling. Source: post 23188; ProjectECH.

Which low-power setup fits your project?

Project Wake source Sleep mode Battery Solar
Temperature sensor, hourly reports Timer Deep sleep 3000 mAh 1S LiPo pack Not needed
PIR wildlife or BirdBox camera EXT0 on the PIR output Deep sleep 3000 mAh pack or larger Yes, worst-month panel
Always-on display or dashboard None, it must stay awake Modem sleep between updates USB power bank or mains No, the radio stays too busy
BLE beacon Timer, duty-cycled BLE scan Deep sleep between scans XIAO board with on-board charging Optional

Parts used in this guide

Prices and stock verified live on 2026-11-21. All four items below are in stock and purchasable.

Also verified live in stock: XIAO ESP32C6 1-Pack (ID 17835) $15.99 sale; XIAO ESP32-C5 1-Pack (ID 18380) $17.99 sale; XIAO ESP32S3 Sense 1-Pack (ID 17842) $32.49 sale, detachable camera; ESP32 DevKit V1, $9.99 sale; USB-C LiPo Module 1200mAh (ID 18959) $14.99 sale; HC-SR501 PIR (ID 14636) $5.99 sale; CellMeter8 (ID 3485) $19.99. No solar panel is stocked at QRC, so none is linked.

Shipped fast and securely from our secure facility in Queensbury, NY. QRC ships within the USA only.

Related guides

FAQ

How long will an ESP32 run on a battery? It depends on the average current, not the pack size alone. A node that wakes 5 seconds at 150 mA every 15 minutes and sleeps at 15 microamps averages about 0.85 mA, so a 3000 mAh battery gives about 146 days. Source: Hubble.

Why does my ESP32 use milliamps in deep sleep? The datasheet figure is the bare chip. The dev board adds a linear regulator with about 5 mA quiescent current, a USB-to-serial chip, and a power LED. Source: ProjectECH; DroneBot Workshop.

What wakes an ESP32 from deep sleep? The RTC timer for periodic work, EXT0 for one pin event such as a PIR sensor, EXT1 for any of several pins, a touch pad for a button, and the ULP coprocessor at about 150 microamps. Source: ProjectECH; Hubble.

How big a battery do I need for an ESP32 sensor? Work out the average current first, then divide capacity by average current, then derate to about 70 to 80 percent usable. Source: ProjectECH; Hubble.

Can I run an ESP32 on solar power? Yes. Work out the daily energy, size the battery for three cloudy days, look up the worst-month peak sun hours, and divide daily energy by charging efficiency times peak sun hours times a derating factor. Source: Hubble; e-fm.tech.

What is a safe cutoff voltage for a LiPo on an ESP32 project? No single cutoff voltage is universal: sources disagree, with figures from 3.0 V to 3.5 V per cell. Use a protected pack or a protection module, read the cutoff from its docs, and wire it so it disconnects the pack from all loads. Source: post 19087.

Sources

Last updated: 2026-11-21

ESP32 SuperMini vs XIAO: Which Tiny Board Wins?

Pick the XIAO for battery builds, WiFi range, or a board that solders flat onto a carrier PCB. Pick the SuperMini for the lowest price per board, a breadboard-friendly header, or an on-board LED for blink and debugging.

The two families share the same chips, so the decision is about the board around the chip: the antenna, the battery circuit, the pins, the mounting, the documentation, and the price per board. Both run the same Arduino, MicroPython, and ESP-IDF code for the same chip once the pin names are changed: the XIAO uses D0 to D10 names and the SuperMini uses GPIO numbers.

How big is each board, and how does it mount?

Board Size Mounting
XIAO ESP32C3 21 x 17.8 mm (Seeed wiki) Castellated, solders flat onto a carrier PCB
ESP32-C3 SuperMini About 22.5 x 18 mm (seller listings only) Through-hole header pins, fits a breadboard
XIAO ESP32S3 21 x 17.8 mm (Seeed wiki) Castellated, solders flat onto a carrier PCB
ESP32-S3 SuperMini About 23.5 x 18 mm (espboards) Through-hole header pins, fits a breadboard

The XIAO is smaller by about a millimetre and a half in each direction, and its castellated edges let it solder flat onto a carrier board like a module. That suits a finished product, a wearable, or a sensor tag that has to sit flat inside a case.

The SuperMini is the breadboard board. Its through-hole header pins plug straight into a breadboard with room to spare, which is why it is the easier pick for a first build, a classroom set, or a prototype you plan to rewire. The trade off is height.

Measure your own SuperMini before you design a case around it. There is no single manufacturer, so pin labels, LED color, flash size, and antenna layout can vary between sellers and revisions.

Which board has more pins?

The SuperMini breaks out more pins on both chips. The XIAO keeps the same 11-pin header on every board: a feature when a sketch moves between XIAO boards, a limit when the build needs more pins.

XIAO C3 SuperMini C3 XIAO S3 SuperMini S3
Broken-out GPIO 11 (D0 to D10) 13 (GPIO0 to GPIO10, 20, 21) 11 (D0 to D10) 13 plus TX/RX
Analog header pins 4 (D0 to D3) 6 (GPIO0 to GPIO5) 9 (D0 to D5, D8 to D10) 13 (GPIO1 to GPIO13)

Sources: Seeed wiki pin maps; NuttX docs; TeachMeMicro.

Three pin differences matter. First, the XIAO bus pins never move: I2C is always D4 and D5, SPI is always D8, D9, and D10, and UART is always D6 and D7 on every XIAO board. The SuperMini has no such promise: the bus pins follow the chip, and the I2C pins on the C3 SuperMini sit on GPIO8 and GPIO9, which are also strapping pins, so the NuttX docs recommend GPIO0 and GPIO1 for I2C instead.

Second, the SuperMini gives you more analog pins: 6 ADC-capable pins on the C3 against 4 on the XIAO C3, and 13 on the S3 against 9 on the XIAO S3. The store listing states 4 analog pins for the C3 SuperMini against 6 in the NuttX table; the gap is the ADC2 channel on GPIO5, which reads unreliably while WiFi is running. Use GPIO0 to GPIO4 for analog reads when WiFi is on.

Third, strapping pins need care on both families, but on different pins. On the XIAO C3, D0, D8, and D9 decide the boot mode. On the C3 SuperMini, GPIO2, GPIO8, and GPIO9 do. On the XIAO S3, D2 (GPIO3) is the strapping pin on the header. On the S3 SuperMini, GPIO3 is the one to use with care. A sensor that pulls a strapping pin to the wrong level at reset can stop either board from booting. Full pin tables are in our SuperMini guide and our XIAO pinout guide.

How do the C3 boards compare?

The C3 comparison is the cleanest one, because the chips are identical. The ESP32-C3 datasheet v2.5 is the source for the chip figures.

Feature XIAO ESP32C3 ESP32-C3 SuperMini
Chip ESP32-C3, single-core RISC-V, up to 160 MHz Same chip
SRAM / flash 400 KB SRAM, 4 MB flash Same
Deep sleep, board level 44 uA per the Seeed wiki No board-level figure published for the generic board
QRC price $13.99 for one board $22.99 for four boards ($5.75 per board)

Sources: Espressif C3 datasheet v2.5; Seeed wiki C3 page; Mischianti; NuttX docs.

The C3 decision comes down to two questions. Does the build run on a battery? The XIAO charges a LiPo over USB with no extra parts, and its 44 uA board-level deep sleep figure is published by Seeed. The SuperMini usually has no charging circuit, and no board-level figure is published for the generic board. The bare C3 chip can sleep near 5 uA, but a finished board draws more.

Does the build need WiFi range? The XIAO needs its external antenna connected, and with it fitted Seeed states over 100 m line of sight. The SuperMini ceramic antenna needs nothing fitted and works well at short range, but range varies by batch. One user test on the Seeed forum measured the SuperMini at -33 dBm next to a phone against about -60 dBm for a XIAO with no antenna fitted: with its antenna fitted, the XIAO is the stronger board.

How do the S3 boards compare?

The S3 comparison is where the memory gap shows up, and it is the biggest spec difference between the two families.

Feature XIAO ESP32S3 ESP32-S3 SuperMini
Chip ESP32-S3R8, dual-core Xtensa LX7, up to 240 MHz ESP32-S3, dual-core Xtensa LX7, up to 240 MHz
PSRAM / flash 8 MB PSRAM, 8 MB flash 4 MB flash, 2 MB PSRAM on the common FH4R2 version
Deep sleep, board level 14 uA per the Seeed wiki About 43 uA per the store listing
User LED User LED on GPIO21, plus charge LED RGB LED, typically WS2812 on GPIO48
QRC price $21.49 for one board $31.99 for five boards ($6.40 per board)

Sources: Seeed wiki S3 page; Espressif S3 datasheets; TeachMeMicro; Lingflux.

The memory gap is the whole S3 story. The XIAO ESP32S3 carries the S3R8 chip with 8 MB of PSRAM and 8 MB of flash. The common S3 SuperMini carries the S3FH4R2 chip with 4 MB of flash and 2 MB of PSRAM: four times the PSRAM and twice the flash on the XIAO. PSRAM holds camera frames, display buffers, and audio at runtime, so the XIAO S3 is the board for camera work, displays, and edge AI. The SuperMini S3 still handles bigger sketches, more sensors, and small displays, but with less headroom.

Check the chip marking on any S3 SuperMini before you trust a memory figure: FH4R2 means 4 MB of flash and 2 MB of PSRAM. Run the memory check sketch in our SuperMini guide to confirm flash size and PSRAM before you write code that needs them.

The S3 boards are closer on the other rows: both have a user LED, USB OTG, and battery charging in some form. The XIAO S3 still wins on range, deep sleep, and documentation; the SuperMini S3 on price per board and breadboard use. The Sense version is the XIAO-only option, adding a detachable camera, a digital microphone, and a microSD slot on an expansion board. There is no SuperMini equivalent. Camera projects are covered in our XIAO S3 Sense guide.

Which board is better on battery power?

The XIAO is the better battery board on both chips. Every XIAO has a built-in LiPo charging circuit with BAT pads on the back: plug a LiPo in and the board charges it over USB, with no extra module. The Seeed wiki publishes board-level deep sleep figures of 44 uA for the C3 and 14 uA for the S3, and the XIAO C3 has no user LED at all, so nothing drains the cell in deep sleep. The C3 SuperMini usually has no charging circuit, so a battery build needs an external charging module, and no board-level deep sleep figure is published for the generic board. The S3 SuperMini is better here: some S3 boards have battery pads with a charger, and the listing states deep sleep around 43 uA.

One safety note: the XIAO C3 charging circuit delivers a fast charge near 370 mA, so use a battery of 370 mAh or larger unless the battery has its own protection circuit. Source: Mischianti XIAO ESP32-C3 guide.

How much does each board cost?

Prices below are the live QRC store prices. The SuperMini boards sell as packs, so the per-board price is arithmetic from the pack price.

Board QRC listing Pack price Price per board
XIAO ESP32C3, 1-pack ID 17820 $13.99 $13.99
ESP32-C3 SuperMini, 4-pack ID 19646 $22.99 $5.75
XIAO ESP32S3, 1-pack ID 17839 $21.49 $21.49
ESP32-S3 SuperMini, 5-pack ID 19649 $31.99 $6.40

The SuperMini is far cheaper per board: about $5.75 against $13.99 on the C3, and about $6.40 against $21.49 on the S3. A four-pack of C3 SuperMinis costs less than two single XIAO C3 boards, and a five-pack of S3 SuperMinis costs about one and a half XIAO S3 boards.

Prices were verified against the live SuperMini guide (updated 2026-11-21) and the batch 2 verification of the same day. The public Store API returned HTTP 429 at draft time, so re-verify every price live before publishing.

Which one should you buy?

Pick by the build, not by the brand.

Buy the XIAO ESP32C3 if the build is a battery sensor, a wearable, a BLE beacon, or a node that has to sit in another room and stay connected. The charging circuit, the external antenna, and the 44 uA deep sleep are the reasons.

Buy the ESP32-C3 SuperMini if the build is a set of cheap sensor nodes, a classroom set, or a first ESP32 project, or anything where the lowest cost per board matters most. At $5.75 per board in the 4-pack, it is the cheapest way to put WiFi and Bluetooth on a tiny board, and the blue LED makes Blink work out of the box.

Buy the XIAO ESP32S3 if the build needs memory: camera work, a display with a frame buffer, audio, edge AI, or a large sketch. The 8 MB of PSRAM and 8 MB of flash are the reasons. Buy the Sense version instead for a camera, a microphone, and a microSD slot.

Buy the ESP32-S3 SuperMini if the build needs two cores, more pins, and some PSRAM, but does not need 8 MB of it: bigger sensor builds, small displays, and multi-node projects where $6.40 per board beats $21.49. Check the chip marking for FH4R2 before relying on the PSRAM figure.

If you are still unsure, buy the C3 SuperMini 4-pack first. It is the cheapest way to learn the setup, and the steps transfer to the other boards.

What are the common mistakes?

  • Running a XIAO with no antenna. The XIAO has no built-in antenna. WiFi and Bluetooth will barely work until the included external antenna is fitted to the U.FL connector.
  • Using a SuperMini pinout on a XIAO, or the reverse. D4 is GPIO6 on the XIAO C3 and GPIO4 on the C3 SuperMini. Use the pin table for your exact board.
  • Expecting Blink to work on the XIAO C3. There is no user LED on the XIAO C3, only a charge LED. Wire an external LED before you run Blink.
  • Assuming the S3 SuperMini has 8 MB of PSRAM. The common FH4R2 version has 2 MB of PSRAM and 4 MB of flash. Check the chip marking.
  • Comparing a chip deep sleep figure against a board deep sleep figure. The bare C3 chip can sleep near 5 uA, but a finished board draws more through its regulator, LEDs, and USB circuitry. Seeed publishes board-level figures for the XIAO (44 uA C3, 14 uA S3). No equivalent figure is published for the generic SuperMini.

How do I troubleshoot a SuperMini vs XIAO problem?

The board does not appear as a USB port. Try a USB-C data cable, not a charge-only cable. Then hold BOOT, connect the cable, release BOOT, and upload Blink. Full steps are in our SuperMini guide.

The Serial Monitor is blank but the sketch runs. Set USB CDC On Boot to Enabled under Tools and re-upload. Full steps are in our SuperMini guide.

WiFi will not connect on a XIAO. Check the antenna first. If the external antenna is not fitted, fit it and test again. If it is fitted, check the connector is fully seated.

WiFi will not connect on a SuperMini. Move the board closer to the router first. Some batches have weak WiFi that improves when the transmit power is lowered in code.

Parts used in this guide

Prices and stock were verified against the live SuperMini guide (updated 2026-11-21) and the batch 2 verification of the same day. The public Store API returned HTTP 429 at draft time. Re-verify every price and stock live before publishing.

Shipped fast and securely from our secure facility in Queensbury, NY. QRC ships within the USA only.

Related guides

FAQ

What is the difference between an ESP32 SuperMini and a XIAO ESP32? Same chip, different board. The XIAO has an external U.FL antenna, a built-in LiPo charging circuit, and no user LED on the C3. The SuperMini has a ceramic antenna, usually no charging circuit, and a blue LED typically on GPIO8. Pick the XIAO for battery sensors and range, the SuperMini for the lowest cost and breadboard work. Source: Mischianti; our SuperMini guide FAQ.

Can I use the same code on a SuperMini and a XIAO? Yes, with the pin names changed. Both run the same Arduino, MicroPython, and ESP-IDF code for the same chip. The XIAO uses D0 to D10 names and the SuperMini uses GPIO numbers. Source: The Engineering Projects XIAO ESP32-C3 guide.

Which board is better for battery projects? The XIAO, on both chips. It charges a LiPo over USB with no extra parts, and Seeed publishes board-level deep sleep figures of 44 uA for the C3 and 14 uA for the S3. The C3 SuperMini usually has no charging circuit and no published deep sleep figure. Source: Seeed wiki C3 and S3 pages; Mischianti XIAO ESP32-C3 guide.

Does the XIAO need an external antenna? Yes. The XIAO has a U.FL connector only and no built-in antenna. The antenna ships in the box and must be fitted before WiFi or Bluetooth will work properly. Source: Seeed wiki S3 page; Seeed forum BLE signal thread.

Which S3 board should I buy, the SuperMini or the XIAO S3? Buy the XIAO S3 if the build needs memory: camera work, displays, audio, or large sketches. It has 8 MB of PSRAM and 8 MB of flash against 2 MB of PSRAM and 4 MB of flash on the common S3 SuperMini FH4R2 version. Buy the S3 SuperMini for two cores, more pins, and some PSRAM at $6.40 per board in the 5-pack. Check the chip marking for FH4R2 before trusting the memory figure. Source: Seeed wiki S3 page; TeachMeMicro; Lingflux.

Sources

Last updated: 2026-11-21

Change log

  • 2026-11-21: Draft created. Direct SuperMini vs XIAO comparison across the C3 and the S3: size, pins, antenna, battery, memory, and price per board. Overlap checked against live posts 15176 (SuperMini guide, one C3-only comparison section) and 18592 (XIAO four-board comparison, no SuperMini coverage). Batch 2 XIAO pinout draft not live yet at draft time, so no link to it is included. Product prices carried from the live SuperMini guide (updated 2026-11-21) and batch 2 verification of the same day; the public Store API returned HTTP 429 at draft time, so prices and stock must be re-verified live before publishing, and the slug 404 must be re-checked at publish time for the same reason.
  • 2026-11-21: Trimmed from 3,492 to 2,797 publishable words (H1 through FAQ, plain wc -w; 2,969 H1 through Last updated, Sources included). Cut one FAQ, shortened table cells and Sources lines, and trimmed prose across size, pins, C3, S3, battery, price, buy, mistakes, troubleshooting, and parts sections. No facts, prices, or safety notes changed.

XIAO ESP32 Pinout: C3, C6, S3, and C5 GPIO Tables

Every XIAO ESP32 board breaks out the same 11 GPIO pins, D0 through D10, on the same 14-pin header with 5V, GND, and 3V3. What changes is the GPIO number behind each D pin, how many pins can read analog voltages, and which pins the chip watches at boot.

This guide gives the pin table for the C3, the C6, and the C5 from the Seeed wiki pin map for each board, and points to our full S3 pinout guide for the S3. It also covers shared pins, free pins, and strapping pins. Verify every table against the Seeed wiki page for your board variant before you solder. Pin tables conflict across sources.

Which pins do all four XIAO ESP32 boards share?

The header layout is the same on all four boards. The bus positions never move: I2C is always D4 and D5, SPI is always D8, D9, and D10, and UART is always D6 and D7. What moves is the GPIO number and the analog count.

Function C3 C6 S3 C5
I2C SDA / SCL D4 / D5 D4 / D5 D4 / D5 D4 / D5
SPI SCK / MISO / MOSI D8 / D9 / D10 D8 / D9 / D10 D8 / D9 / D10 D8 / D9 / D10
UART TX / RX D6 / D7 D6 / D7 D6 / D7 D6 / D7
Analog pins on the header 4 (D0 to D3) 3 (D0 to D2) 9 (D0 to D5, D8 to D10) 1 (D0)

Sources: Seeed wiki pin maps; our S3 pinout post for the S3 row. The C3 has a charge LED only, per the Seeed C3 wiki pin map.

How do I read a XIAO pinout diagram?

Three names describe the same physical pin, and mixing them up is the most common wiring mistake on these boards.

  • D name: the printed pad name, D0 through D10. Use it in Arduino code, for example digitalWrite(D4, HIGH).
  • GPIO number: the chip pin number, for example GPIO2 or GPIO22. Use it in ESP-IDF code and in datasheets.
  • A name: the analog name, A0 through A3 on the C3, A0 through A2 on the C6, A0 on the C5. Use it with analogRead(A0).

The Seeed wiki diagram for each board shows the front and the back: the D pins and USB-C port on the front, the battery pads and JTAG test pads (MTDO, MTDI, MTCK, MTMS) on the back. Keep the Seeed wiki page for your board open while you wire. Some third party pages number the same D pads differently, and a table built for the wrong board will compile cleanly and do nothing.

What is the XIAO ESP32C3 pinout?

The C3 is the cheapest board of the four, with one catch: three of its header pins are strapping pins, so what you connect to them at reset matters. The table below follows the Seeed wiki C3 pin map.

Pad GPIO Main function Shared with
D0 GPIO2 Analog A0, ADC1_CH2 Strapping
D1 GPIO3 Analog A1, ADC1_CH3 Wake
D2 GPIO4 Analog A2, ADC1_CH4 JTAG MTMS, wake
D3 GPIO5 Analog A3, ADC2_CH0 JTAG MTDI, wake
D4 GPIO6 I2C SDA JTAG MTCK
D5 GPIO7 I2C SCL JTAG MTDO
D6 GPIO21 UART TX Console
D7 GPIO20 UART RX Console
D8 GPIO8 SPI SCK Strapping
D9 GPIO9 SPI MISO Strapping, BOOT
D10 GPIO10 SPI MOSI Flash CS
5V / GND / 3V3 – Power 5 V, GND, 3.3 V out (700 mA max per Seeed wiki)

Source: Seeed wiki C3 pin map.

D3 is the only ADC2 channel on the header, and ADC2 readings can be unreliable while WiFi is running, so use D0 to D2 (ADC1) for analog sensors when WiFi is on. Source: studiopieters C3 pinout guide. Only D0 to D3 can wake the chip from deep sleep. The C3 has no onboard antenna.

What is the XIAO ESP32C6 pinout?

The C6 is the Matter, Thread, and Zigbee board, and the friendliest to wire: none of its header pins is a strapping pin. The table below follows the Seeed wiki C6 pin map.

Pad GPIO Main function Shared with
D0 GPIO0 Analog A0, ADC LP GPIO, wake
D1 GPIO1 Analog A1, ADC LP GPIO, wake
D2 GPIO2 Analog A2, ADC LP GPIO, wake
D3 GPIO21 GPIO SDIO DATA1
D4 GPIO22 I2C SDA SDIO DATA2
D5 GPIO23 I2C SCL SDIO DATA3
D6 GPIO16 UART TX Console
D7 GPIO17 UART RX Console
D8 GPIO19 SPI SCK SDIO clock
D9 GPIO20 SPI MISO SDIO DATA0
D10 GPIO18 SPI MOSI SDIO command
5V / GND / 3V3 – Power 5 V, GND, 3.3 V out

Source: Seeed wiki C6 pin map. The chip has 7 ADC channels, but only D0, D1, and D2 are broken out as analog header pins.

The board carries both a small onboard ceramic antenna and a U.FL connector, and the choice is made in firmware through an RF switch. Pull GPIO3 low to enable the switch, then GPIO14 low selects the built-in antenna (the default) and GPIO14 high selects the external antenna. Neither GPIO is a header pin. Source: Seeed wiki C6 RF switch section. Only the low-power GPIOs, GPIO0 to GPIO7, can wake the chip from deep sleep, and the XIAO breaks out three of them.

What is the XIAO ESP32-C5 pinout?

The C5 is the newest board and the only one with dual-band WiFi, 2.4 GHz and 5 GHz. Its GPIO numbers jump around, but the bus positions are the same as the other boards. The table below follows the Seeed wiki C5 pin map.

Pad GPIO Main function Shared with
D0 GPIO1 Analog A0, ADC LP GPIO, wake
D1 GPIO0 GPIO LP GPIO
D2 GPIO25 GPIO Strapping
D3 GPIO7 GPIO SDIO DATA1, strapping
D4 GPIO23 I2C SDA –
D5 GPIO24 I2C SCL –
D6 GPIO11 UART TX –
D7 GPIO12 UART RX –
D8 GPIO8 SPI SCK –
D9 GPIO9 SPI MISO –
D10 GPIO10 SPI MOSI –
5V / GND / 3V3 – Power 5 V, GND, 3.3 V out

Source: Seeed wiki C5 pin map. The chip has 5 ADC channels, but only D0 is broken out as an analog header pin.

The battery voltage reading is built in: GPIO6 reads the battery and GPIO26 enables the measurement circuit, so you can read the cell voltage in code with no divider to solder. Source: Seeed wiki C5 battery section. The user LED is GPIO27.

What is the XIAO ESP32S3 pinout?

The S3 pinout is covered in full in our dedicated guide, Seeed XIAO ESP32S3 Pinout: GPIO, Camera, and Power, so this section is a summary only. The S3 breaks out the same 11 D pins: D0 to D5 are GPIO1 to GPIO6, D6 and D7 are GPIO43 and GPIO44 for UART, and D8 to D10 are GPIO7, GPIO8, and GPIO9 for SPI. I2C is D4 and D5, and 9 of the 11 pins can read analog voltages. The boot button is GPIO0. The Sense version adds a detachable camera and a microSD slot on an expansion board on the back, and the microSD chip select is GPIO21.

Which pins are shared with other hardware?

A pin that looks free on the header may already have a job. Check this table before you assign pins.

Shared hardware Board Pins involved What it means for your wiring
Antenna RF switch C6 GPIO3 (power), GPIO14 (select) Internal, not header pins. GPIO3 low, then GPIO14 low for onboard or high for external. Source: Seeed wiki C6.
Antenna C3 U.FL connector only No onboard antenna. Attach the external antenna or WiFi range will be poor.
Battery voltage read C5 GPIO6 (read), GPIO26 (enable) Built-in divider. Drive GPIO26 high to read the battery on GPIO6. Source: Seeed wiki C5.
Camera, mic, microSD S3 Sense only Board-to-board connector, SD CS GPIO21 On the expansion board, not the D header. See the S3 pinout guide.

Which pins are free for your project on each board?

Free means no boot-time duty, no bus duty, and no shared hardware.

The bus pins are the same on all four boards (D4/D5 I2C, D6/D7 UART, D8 to D10 SPI) and are free whenever that bus is unused.

Board Free pins, no conditions Pins that need care
C3 D1 (GPIO3), D10 (GPIO10) D0, D8, D9 (strapping); D2, D3, D4, D5 (JTAG)
C6 D0, D1, D2, D3, D4, D5, D8, D9, D10 D6, D7 (UART console)
C5 D0, D1, D4, D5, D6, D7, D8, D9, D10 D2, D3 (strapping)
S3 D0, D1, D3, D4, D5, D8, D9 D2 (strapping), D6, D7, D10 (see the S3 pinout guide)

Sources: Seeed wiki pin maps; the S3 row follows our S3 pinout post.

Which pins are strapping and boot pins on each board?

Strapping pins are read by the chip at reset to pick the boot mode. A sensor that pulls one to the wrong level at reset can stop the board from booting or accepting an upload.

Board Strapping pins on the header Boot button GPIO
C3 D0 (GPIO2), D8 (GPIO8), D9 (GPIO9) GPIO9
C6 None on the header GPIO9
C5 D2 (GPIO25), D3 (GPIO7) GPIO28
S3 D2 (GPIO3), plus GPIO0 on the BOOT button GPIO0

The C3 pins come from the Seeed wiki C3 strapping section. The Seeed wiki has no strapping section for the C6 or the C5: the C6 list (GPIO4, GPIO5, GPIO8, GPIO9, GPIO15, all internal) comes from the SolderHub C6 guide, and the C5 pins come from the ESP32-C5 datasheet via the espboards C5 page, both secondary sources. Full S3 detail is in the S3 pinout guide.

If a board stops appearing as a USB port or refuses uploads after you wire something new, check the strapping pins first. Disconnect the new wiring, confirm the board uploads again, then rewire with the strapping pin left alone at boot.

What are the common mistakes?

  • Using a pin table from the wrong board. D4 is GPIO6 on the C3, GPIO22 on the C6, GPIO5 on the S3, and GPIO23 on the C5. The D name is the same and the GPIO number is not.
  • Wiring a sensor to a strapping pin on the C3. D0, D8, and D9 decide the boot mode. A sensor that pulls one low at reset can leave the board unresponsive.
  • Expecting analog reads on every D pin. Only D0 to D3 read analog on the C3, only D0 to D2 on the C6, and only D0 on the C5. The S3 is the analog-rich board with 9 analog header pins.
  • Running the C3 with no antenna. The C3 has no onboard antenna. WiFi will barely work without the external antenna on the U.FL connector.

How do I troubleshoot a XIAO pinout problem?

The board does not appear as a USB port. Try a different USB-C cable, one that carries data, not a charge-only cable. Then try bootloader mode: on the C6, hold BOOT, connect the cable, release BOOT, and upload Blink. Source: Seeed wiki C6 bootloader section.

Uploads fail after new wiring. Disconnect the new wiring and try again. If the upload works, a strapping pin is held at the wrong level. On the C3 check D0, D8, and D9 first. On the C5 check D2 and D3. On the S3 check D2.

analogRead returns 4095 or 0 all the time. Check that the pin is an analog pin on your board. On the C5 only D0 reads analog on the header. On the C6 only D0 to D2 do. On the C3 only D0 to D3 do. Also check that the sensor output stays inside 0 to 3.3 V.

Which pins can I use for my project?

Pick the board first, then the pins. If you have not picked a board, see XIAO ESP32C3 vs C6 vs S3 vs C5: Pick the Right Board.

Project Board Pins to use
I2C sensor or OLED Any D4 SDA, D5 SCL
SPI display or SD card Any D8 SCK, D9 MISO, D10 MOSI, plus a free pin for chip select (on the C3, use D1, not D0)
Analog sensor S3 first, C3 second S3: D0 to D5, D8 to D10; C3: D0 to D2
Battery-powered sensor node C6 or C5 C6: D0 to D2 for wake and analog; C5: D0 for wake

Parts used in this guide

Prices and stock were verified live on qualityrcparts.com on 2026-11-21 through the public Store API. All four items are in stock and purchasable.

Shipped fast and securely from our secure facility in Queensbury, NY. QRC ships within the USA only.

Related guides

FAQ

How many GPIO pins does a XIAO ESP32 board have? 11, named D0 through D10, on all four boards. The header also carries 5V, GND, and 3V3. Source: Seeed wiki pin maps.

Which pins are I2C on the XIAO ESP32 boards? D4 is SDA and D5 is SCL on all four boards. Source: Seeed wiki pin maps.

Which pins are SPI on the XIAO ESP32 boards? D8 is SCK, D9 is MISO, and D10 is MOSI on all four boards. Source: Seeed wiki pin maps.

Can I use 5 volt sensors with a XIAO ESP32 board? No. All four boards run 3.3 V logic, and a voltage above 3.3 V on a GPIO pin can damage the chip. Use a level shifter. Source: Seeed wiki power sections.

Which XIAO pins are strapping pins? On the C3, D0 (GPIO2), D8 (GPIO8), and D9 (GPIO9). On the C5, D2 (GPIO25) and D3 (GPIO7). On the S3, D2 (GPIO3). On the C6, none of the header pins is a strapping pin.

Why does my XIAO ESP32C3 not boot after I wire a sensor? The usual cause is a strapping pin held at the wrong level at reset. D0, D8, and D9 decide the boot mode on the C3. Disconnect the new wiring, confirm the board boots, then move the sensor to D1 or D10.

Does the XIAO ESP32-C5 have an analog pin? Yes, one on the header: D0 (GPIO1). The chip has 5 ADC channels in total, but the others are not broken out on the header. Source: Seeed wiki C5 pin map.

Sources

Last updated: 2026-11-21

Change log

  • 2026-11-21: Draft created. Full C3, C6, and C5 pin tables from the Seeed wiki pin maps; S3 covered as a summary with a link to the dedicated S3 pinout post. Shared-pin, free-pin, and strapping tables added. No live post gives full C3, C6, or C5 pin tables, verified against posts 23363, 22718, and 18592.