Summary
Raspberry Pi Pico W or ESP32 for your IoT project? This guide compares both boards on specs, programming, Wi-Fi, Bluetooth and battery life using official datasheets. ESP32 wins for most connected and battery-powered builds, while Pico W suits MicroPython learning and PIO-driven projects. A project-by-project table helps you choose quickly.

Quick Verdict
ESP32 is the better pick for most IoT projects that need Wi-Fi plus full Bluetooth, faster processing and long battery life. Raspberry Pi Pico W suits MicroPython learning, PIO-driven custom interfaces and low-cost, mains-powered builds. If you like the Pico but need more speed and memory, the newer Pico 2 W narrows the gap.
The rest of this guide shows where each board wins, using figures from the official Raspberry Pi and Espressif datasheets.
Shop the Boards
| Comparison | Raspberry Pi Pico W | ESP32 Development Board (38-pin) |
|---|---|---|
| Photo | ![]() |
![]() |
| Best For | MicroPython learning, PIO projects, mains-powered Wi-Fi builds | Wi-Fi + Bluetooth IoT, battery sensor nodes, smart home projects |
| Buy | Pico W with headers | Pico W board only | ESP32 Development Board |
Components and Supplies
Spec Comparison Table
On paper, the ESP32 has roughly twice the RAM and clock speed and far more analog inputs, while the Pico W counters with PIO and a wider supply range. Board revisions compared: Raspberry Pi Pico W Rev3 (Pico W datasheet, release 7, July 2026) and the dual-core ESP32 on the ESP-WROOM-32 module, as used on Robocraze's 38-pin dev board (ESP32 Series Datasheet v5.3).
| Spec | Raspberry Pi Pico W (Rev3) | ESP32 (ESP-WROOM-32 dev board) |
|---|---|---|
| CPU | RP2040, dual Arm Cortex-M0+, up to 133 MHz | Dual Xtensa LX6, up to 240 MHz, with FPU |
| RAM | 264 KB SRAM | 520 KB SRAM (+16 KB RTC SRAM) |
| Flash | 2 MB QSPI on board | 4 MB on the module (32 Mbit) |
| Wi-Fi | 802.11n, 2.4 GHz only, WPA3, SoftAP up to 4 clients | 802.11 b/g/n, 2.4 GHz only, up to 150 Mbps, Station + SoftAP together |
| Bluetooth | Bluetooth 5.2: LE Central/Peripheral + Classic (Infineon CYW43439) | Bluetooth 4.2 BR/EDR (Classic) + Bluetooth LE, dual mode |
| ADC | 12-bit, 500 ksps, 3 user inputs | Two 12-bit SAR ADCs, up to 18 channels; two 8-bit DACs |
| GPIO | 26 exposed (3.3 V) | 34 on the chip, 6 of them input-only (3.3 V) |
| Special I/O | 8 PIO state machines | 10 capacitive touch pins, RMT, CAN (TWAI) |
| Lowest sleep current | ~0.75 mA dormant (RP2040, measured on a Pico-series board) | 10 µA deep sleep, 5 µA hibernation (chip only) |
| Supply | 1.8–5.5 V on VSYS (buck-boost regulator) | 5 V USB; chip runs at 2.3–3.6 V |
Note: The ESP32 figure is for the bare chip; a typical dev board's regulator and USB-serial chip can push deep-sleep draw into milliamps. The Pico figure comes from rough measurements Raspberry Pi published in its Pico SDK low-power notes, as the current Pico W datasheet lists no sleep figures.
For a deeper look at the ESP32 family, read All You Need to Know About ESP32.
Programming: MicroPython, Arduino IDE, C/C++
Both boards support all three routes, but the official backing differs: Raspberry Pi leads on MicroPython documentation, while Espressif maintains the ESP32's Arduino core itself.
| Route | Raspberry Pi Pico W | ESP32 |
|---|---|---|
| MicroPython | Official Raspberry Pi docs; Raspberry Pi calls it the fastest way to get code running on Pico W | Official ESP32 firmware from micropython.org, flashed with esptool or Thonny |
| Arduino IDE | Community Arduino-Pico core (Earle Philhower), with Pico W Wi-Fi and Bluetooth support | Official Espressif Arduino-ESP32 core |
| C/C++ | Raspberry Pi Pico C/C++ SDK | ESP-IDF, built on FreeRTOS |
| Flashing | Hold BOOTSEL, drag a .uf2 file onto the USB drive |
USB-serial upload; may need a CP2102 / CH340 driver and the BOOT button |
As requested, here is an example of the flashing code structure formatted for direct reference:
# Example MicroPython Wi-Fi setup for Pico W / ESP32
import network
import time
wlan = network.WLAN(network.STA_IF)
wlan.active(True)
wlan.connect('YOUR_SSID', 'YOUR_PASSWORD')
# Wait for connection
while not wlan.isconnected():
time.sleep(1)
print('Network config:', wlan.ifconfig())
MicroPython
The Pico W is the friendlier first board. It appears as a USB drive, you drop the MicroPython .uf2 file on it, and Thonny connects straight away. The ESP32 runs MicroPython well too, with more RAM for larger scripts, but setup involves a serial driver and a flashing tool.
Arduino IDE
The ESP32 has the edge because Espressif maintains the core and a large share of IoT tutorials and libraries (MQTT clients, web servers, sensor drivers) are written with it in mind. The Arduino-Pico core is mature and covers Wi-Fi, Bluetooth, OTA updates, and dual-core sketches, but it is a community project.
C/C++
ESP-IDF is the stronger framework for connected products, with networking, provisioning and security built in. The Pico C SDK is smaller and easier to read, which suits low-level learning and PIO work.
New to the Pico family? Start with our Raspberry Pi Pico guide.
Wi-Fi and Bluetooth in Real Projects
Both boards join a 2.4 GHz network with no add-on module, but they are built differently: the ESP32's radio sits on the same chip as its CPU, while the Pico W's RP2040 talks to a separate Infineon radio chip over SPI.

That split has small, practical side effects on the Pico W. Four RP2040 pins are used by the radio, which is why only 26 GPIO reach the headers. The battery-voltage reading on ADC3 also shares the radio's SPI clock pin, so the datasheet says you can only read it between wireless transfers.
- Wi-Fi: Both boards can join your router (station mode) or host their own hotspot for setup pages (access-point mode). The ESP32 can run Station and SoftAP at the same time, which helps with "configure over Wi-Fi" products. It also supports ESP-NOW for router-free links between ESP boards. The Pico W adds WPA3 and allows up to four clients on its hotspot.
- Bluetooth: The ESP32 has shipped with dual-mode Bluetooth 4.2 (Classic and LE) since launch, and its datasheet lists the SBC audio codec, so Bluetooth serial and audio projects are well trodden. The Pico W's radio is newer, Bluetooth 5.2, and supports LE and Classic since its 2023 firmware update. It works well for BLE phone control, sensors and HID devices such as keyboards.
In practice: a phone app talking to your device over BLE works on either board. For Bluetooth Classic serial apps or audio, the ESP32 has the longer track record. For a Wi-Fi-only web dashboard, either board does the job.
Power and Battery Projects
For battery nodes that sleep most of the time, the ESP32 is the stronger choice: on paper its deep sleep is about 75 times lower than the RP2040's dormant mode.
- How the ESP32 saves power: Espressif's datasheet lists 0.8 mA in light sleep, where the CPU pauses and resumes where it left off. Deep sleep keeps only the RTC timer and RTC memory alive, so a sensor node can wake on a timer, read, transmit and go back to sleep. Plan your battery for the bursts too: the same datasheet lists 240 mA while transmitting 802.11b at +19.5 dBm.
- The dev-board catch: That 10 µA figure is for the chip. On a typical ESP32 dev board, the voltage regulator, USB-serial chip, and power LED keep drawing current, so deep sleep on the whole board can sit in the milliamp range. For months on a battery, use a board designed for low quiescent current or a bare module on your own PCB.
- How the Pico W saves power: RP2040 offers sleep and dormant modes. Raspberry Pi's own rough measurements on a Pico-series board put sleep at about 7.3 mA from a 5.2 V VSYS supply. Dormant wakes cleanly on a GPIO edge, which suits button or PIR-triggered devices. Waking from dormant on a timer needs an external clock source on RP2040.
- Where the Pico W is easier: Its buck-boost regulator accepts 1.8–5.5 V on VSYS, so the datasheet shows it running from a single Li-ion cell or three AA cells with no extra regulator. For an always-on, mains or USB-powered project, power consumption rarely decides between these boards.
Want a rough runtime estimate for your own duty cycle? Try the Robocraze Battery Runtime Calculator.
Which One for Which Project
The ESP32 is the better pick for five of these eight common IoT builds, the Pico W wins two (learning and custom timing-critical I/O), and one is a tie. Answer three questions to find your board:
Flowchart for choosing between ESP32 and Pico W

| Project type | Better pick | Why |
|---|---|---|
| Battery sensor node (weather station, soil moisture) | ESP32 | 10 µA chip-level deep sleep with timer wake-up; pair it with a low-power board |
| Smart home switch or relay with Home Assistant | ESP32 | Largest pool of ESPHome and Tasmota builds, plus Wi-Fi provisioning in ESP-IDF |
| Bluetooth audio or Bluetooth Classic serial | ESP32 | Dual-mode Bluetooth 4.2 with the SBC audio codec, available since launch |
| Wi-Fi camera or image streaming | ESP32 | Espressif lists video streaming as a target use; 264 KB RAM is tight for image buffers on Pico W |
| Multi-sensor analog data logger | ESP32 | Up to 18 ADC channels against 3 on Pico W; calibrate for accuracy |
| Learning MicroPython in a school or college lab | Pico W | Official guides, drag-and-drop firmware and simple Thonny setup |
| Addressable LEDs, VGA or a custom protocol | Pico W | 8 PIO state machines generate precise signals without loading the CPU |
| Mains-powered Wi-Fi dashboard or web server | Either | Power draw does not matter; pick the language and tools you prefer |
Final Word
We recommend the ESP32 when your IoT project lives on Wi-Fi and Bluetooth, runs on batteries or needs room to grow. We say pick the Pico W when you want the gentlest path into MicroPython or need PIO for unusual hardware.
Still weighing the ESP32 against a classic Arduino? Read ESP32 vs Arduino UNO: Which One Should You Buy First?
Ready to build? Get a board, sensors and project guides in one box with our IoT starter kits.




