You search "best microcontroller for beginners" and get three different answers.

Most people just buy whichever board their favorite tutorial used. Then the sensor array needs more pins than the board has, or the chassis is too small to hold it, or a 5 volt signal meets a 3.3 volt pin and something on the bench stops working. None of that is bad luck. It is the board not matching the build.

This post sorts the Nano, the Uno and the ESP32 by what actually decides it for a line follower: voltage, pins and size, not which one has the most tutorials.

If you are stuck on this before you have even ordered a kit, our community has made this call for a dozen different builds already, so ask before you buy anything.

Nano, Uno and ESP32 in one line each

The Uno is the full-size board most tutorials teach on. It runs an ATmega328P chip at 16 MHz, works at 5 volts, and gives you 14 digital pins and 6 analog pins, per Arduino's own board comparison.

The Nano runs the same chip, at the same 16 MHz and 5 volts, in a board about a tenth the size, with 8 analog pins instead of 6.

The ESP32 is a different animal. It is a dual-core chip that clocks up to 240 MHz, with Wi-Fi and Bluetooth built in, but its pins read 3.3 volts, not 5.

None of the three is better in general. They are built for different jobs, and a line follower only cares about two of those differences: voltage and size.

Five volts versus three point three: the mismatch that kills a pin

Logic voltage is the level a pin reads as "on." Wire a 5 volt signal into a pin built for 3.3, and you risk more than a wrong reading. You can damage the pin for good.

Techgeeks' own carrier board, the Robot Carrier Board, regulates everything on it to 5 volts, which is what the Nano and Uno run at natively. The ESP32 runs at 3.3, so pairing it with a 5 volt board means adding a level shifter or a voltage divider first, not just plugging it in.

Sensors vary. The ARC8 sensor array happens to accept anywhere from 3.3 to 5 volts, so it works with any of the three boards without extra parts. Not every module is that forgiving, and your motor driver usually isn't. Check the datasheet before you assume.

Everyone wires something straight into a pin at least once before reading it. Do that with an ESP32 and a 5 volt line, and the pin might not read anything again. Budget for the level shifter before you budget for the board.

How many analog pins your sensor array actually needs

An 8-channel sensor array like the ARC8 needs 8 pins that can read analog voltage, ADC pins for short, one per channel. The Uno only has 6, so wiring all 8 channels runs it short by two. The Nano's 8 pins cover it exactly.

A 16-channel array like the ARC16 does not need 16 physical ADC pins. It multiplexes all sixteen channels through a handful of pins on the sensor board itself, so it reads fine on a Nano's 8 analog inputs. It also needs a steady 5 volts to run, and its output swings across that same 0 to 5 volt range, so feeding it into an ESP32's ADC needs a voltage divider on the signal line, not just a level shifter on the power rail.

Pin count only bites you with simple, unmultiplexed sensors. Check your specific array before assuming you're short.

The size problem nobody mentions

An Uno is roughly the size of a credit card and a half. A Nano is roughly the size of a stick of gum. On a breadboard, neither matters. Mounted on a race-ready chassis with a battery, two motors and a sensor array up front, that difference decides whether the board fits at all.

This is exactly why the Robot Carrier Board is built around a Nano and not an Uno. A carrier board's entire job is a small footprint, and a full-size Uno would defeat that before the first screw goes in.

Clock speed and memory: does a line follower actually need it

The ESP32 runs up to 15 times faster than the Nano or Uno's 16 MHz, with far more memory alongside it. None of that speed shows up in a basic line-following loop. Reading a sensor array and adjusting two motors on a fixed timer is a job the Nano finishes with room to spare. When a lap time is slow, the chip is almost never the reason. Sensor placement and tuning usually are, as the ESP32's own documentation makes clear it was designed for heavier connected workloads, not faster GPIO toggling.

The ESP32's extra power earns its place when you add something the Nano cannot do at all: logging sensor data over Wi-Fi, syncing with a phone app, or processing a camera feed. For a first build running a standard IR array, that need hasn't shown up yet.

Which one to buy, for what you're actually building

Conclusion

For a first line follower with a standard sensor array, the Nano wins because it matches the voltage and the mounting space of everything else in the build, not because it's the fastest chip on this list. The Uno teaches identical code on a friendlier, bigger board if you want practice before you commit to a chassis. The ESP32 is a specialist for wireless features you probably haven't needed yet, not a default choice for a first build.

Now that you know what the pins and the voltage actually decide, which of the three matches the build you already have in mind?

If that's a Nano, the Mark 1 Line Following Robot kit ships with the pins and the voltage already sorted, so your first week goes to tuning, not to converting logic levels.