Arduino vs ESP32 vs Raspberry Pi for robots
Which board should be the brain of my robot?
The short answer
Start on an Arduino Uno if you have never flashed a board; move to an ESP32 once your robot needs to talk to a phone, a server or another robot; add a Raspberry Pi (or a Jetson) only when you need a camera, a map or ROS 2 — and keep a microcontroller underneath it driving the motors.
These are three different kinds of computer. The Uno R4 is a 48 MHz microcontroller that runs one program, bare-metal, with 5 V pins — the most forgiving board to learn on. The ESP32 is a 240 MHz dual-core microcontroller with Wi-Fi and Bluetooth built in, for a few dollars more. The Raspberry Pi 5 is a Linux computer with up to 16 GB of RAM: it runs ROS 2 and vision models but is not a real-time controller.
| Aspect | Arduino Uno R4 | ESP32 | Raspberry Pi 5 | Edge |
|---|---|---|---|---|
| What it is | Microcontroller board: Renesas RA4M1, Arm Cortex-M4 at 48 MHz | Microcontroller SoC: dual-core Xtensa LX6 at up to 240 MHz | Single-board computer: quad-core Arm Cortex-A76 at 2.4 GHz | Even |
| Memory | 32 KB SRAM, 256 KB flash — enough for motor logic, not for images | 520 KB SRAM, 4 MB flash on a typical DevKitC — room for a web server and FreeRTOS tasks | 1–16 GB LPDDR4X, storage on microSD or NVMe — runs a full OS | Raspberry |
| Connectivity | None on the Minima (the Uno R4 WiFi adds a radio); UART, I²C, SPI and CAN on board | Wi-Fi 802.11 b/g/n and Bluetooth 4.2 (BR/EDR + LE) on the chip | Gigabit Ethernet, dual-band Wi-Fi, Bluetooth 5, USB 3, PCIe | Raspberry |
| GPIO voltage | 5 V logic — drives most hobby sensors and motor drivers directly | 3.3 V logic — 5 V sensors need a level shifter or a divider | 3.3 V logic on the 40-pin header; a wrong wire can kill the board | Arduino |
| Analog inputs | 6 inputs, up to 14-bit, plus a 12-bit DAC | Up to 18 ADC channels at 12-bit (two are unusable while Wi-Fi is on) | None — add an external ADC chip for any analog sensor | Arduino |
| Real-time behaviour | Bare metal: one loop, microsecond-predictable timing — ideal for PID and PWM | ESP-IDF runs FreeRTOS: predictable tasks, but the Wi-Fi stack competes for one core | Linux: scheduling jitter of milliseconds; not for closing a motor loop | Arduino |
| Power | Tens of milliamps at 5 V; runs for days from a battery pack; VIN 6–24 V | Hundreds of mA when the radio transmits; a ULP co-processor runs while the cores sleep, so battery projects are possible | Peak about 12 W; the official 5 V 5 A (25 W) supply is recommended — a serious battery budget | Arduino |
| Price (official store, late 2026) | Uno R4 Minima $20 (store-usa.arduino.cc) | ESP32-DevKitC about $10; bare modules less | Pi 5 from $45 (1 GB) to $145 (16 GB) after the Dec 2025 price change; add a PSU, card and cooler | ESP32 |
| Can it run ROS 2? | No. micro-ROS lists only the Portenta H7 among Arduino boards; the Uno has too little RAM | Yes, as a micro-ROS client over UART or Wi-Fi UDP — it publishes topics to a ROS 2 agent on a bigger computer | Yes, natively: Ubuntu 24.04 arm64 is a Tier 1 ROS 2 Jazzy platform with binary packages | Raspberry |
| Typical robot role | Motor control, encoders, line-following, obstacle avoidance — the reflexes | Connected sensors, telemetry, phone-controlled robots, the bridge between a Pi and the motors | Vision, SLAM, Nav2, speech, the ROS 2 graph — the planning brain | Even |
| Programming | Arduino IDE, C/C++; the largest beginner library ecosystem in hobby electronics | Arduino IDE, ESP-IDF (C), MicroPython; more setup, more options | Any language — Python first; a full desktop if you plug in a monitor | Even |
| Best first board for a beginner | Yes. 5 V tolerance, instant feedback, and every tutorial on the internet was written for it | Second board. Worth it the moment a project needs a network | Not as a first robot controller — it is a computer, and you still need a microcontroller for the motors | Arduino |
Choose Arduino Uno R4 when…
- It is your first robot and you want to blink an LED, read a sensor and spin a motor within an hour.
- The robot has no need to talk to anything — a line-follower, a sumo bot, a servo arm.
- You are driving 5 V sensors or modules and do not want to think about level shifting.
- Timing matters more than throughput: PWM, encoder counting, a PID loop.
Choose ESP32 when…
- The robot needs Wi-Fi or Bluetooth: phone control, telemetry, a web dashboard, OTA updates.
- You want micro-ROS so a microcontroller can appear as a node in a ROS 2 graph.
- Budget is the tightest constraint — a whole dev board for the price of a sensor.
- You are ready for 3.3 V logic and a slightly fussier toolchain.
Choose Raspberry Pi 5 when…
- The robot needs a camera, a lidar map, Nav2 or any neural network.
- You want to learn ROS 2 on real hardware without a laptop strapped to the chassis.
- The project is a Linux project (SSH, Python, Docker) that happens to have wheels.
- You accept a bigger battery, a cooler, and a microcontroller underneath for the motors.
Plain English. Free. Unsubscribe in one click.
Read next
Sources
- Arduino — UNO R4 Minima documentation and tech specs
- Arduino Store (USA) — UNO R4 Minima
- Espressif — ESP32 series datasheet
- Raspberry Pi — Introducing Raspberry Pi 5
- CNX Software — Raspberry Pi 5 1 GB launched, Dec 2025 price list
- micro-ROS — Supported hardware
- REP 2000 — ROS 2 releases and target platforms
Updated 2026-11-09 · All comparisons