Choosing a controller: ESP32 is a family, not a chip

"ESP32" is a name shared by a family of chips, not one specific part. The classic ESP32, S2, C3 and S3 differ on Bluetooth, USB, DAC, Ethernet and camera support - and three of those are presence-versus-absence differences, not fast-versus-slow ones. So the right order is fix the control frequency first, then the interfaces you cannot live without, and only then read the spec table. After the first two questions, one or two parts usually remain.

The short answer

There is no better chip, only the one whose weak spot does not kill you. Ask three questions in order: how fast must the control loop be; which interfaces are non-negotiable (classic Bluetooth, Ethernet, analog output); do you need USB and imaging. The first two eliminate candidates; the third only adds. Reading the spec table last keeps you from paying for compute you will not use - and from missing an interface that is simply absent.C

Last verified: 2026-11-19. Every figure here comes from Espressif's official chip comparison table and the ESP32-S3 product page (grade A). A datasheet value is not your board's measured value; see section 5 for where they diverge.

1. One table: the official differences across four generations

This table answers one question: which capability exists on this generation and not that one. Read it horizontally, not vertically - find the row you cannot do without, then see who has a tick.A

CapabilityESP32 (classic)ESP32-S2ESP32-C3ESP32-S3
Launched2016202020202020
Core / clockDual- or single-core Xtensa LX6, 240 MHzSingle-core Xtensa LX7, 240 MHzSingle-core RISC-V, 160 MHzDual-core Xtensa LX7, 240 MHz
On-chip SRAM520 KB320 KB400 KB512 KB
On-chip ROM448 KB128 KB384 KB384 KB
BluetoothClassic v4.2 (BR/EDR) + BLENoneBLE 5.0 onlyBLE 5.0 only
USB OTGNoneYesNoneYes
DAC (analog out)2 x 8-bit2 x 8-bitNoneNone
Ethernet MACYesNoneNoneNone
Camera interfaceYesYesNoneYes
LCD interfaceYesYesNoneYes
GPIOs34432245
ADC channels2 x 12-bit, 18 ch2 x 12-bit, 20 ch2 x 12-bit, 6 ch2 x 12-bit, 20 ch
External RAM ceiling8 MB1 GBNot supported1 GB
Unique acceleration---Vector (SIMD) instructions, used by the official ESP-DSP and ESP-NN libraries

Source: Espressif's official chip series comparison and the ESP32-S3 product page, retrieved 2026-11-19. Values are chip-level datasheet figures and exclude module and board differences.A

The row most people misread

The S3 has 512 KB of on-chip SRAM - 8 KB less than the classic part's 520 KB. "The S3 has more memory" refers to the external PSRAM it can address (octal, higher bandwidth), not to on-chip memory. These are two separate budgets: on-chip memory decides how complex a bare-metal program can be, external memory decides how many image frames you can buffer.

2. Three hard edges: present versus absent

Most wrong choices are not about compute - they are about an interface that simply is not there. All three below are yes/no. No amount of software makes up for them.A

Edge one: Bluetooth audio or legacy serial means the classic part only

The classic ESP32 has BR/EDR (classic Bluetooth). The S2 has no Bluetooth at all; the C3 and S3 have Bluetooth Low Energy (5.0) only. So Bluetooth speakers, Bluetooth headsets, and SPP serial bridges to older equipment cannot be built on an S3 - the protocol layer is not in the stack, and that is not a performance question. Conversely, for BLE sensors, BLE HID keyboards or beacons, the S3 is the better side of the family.A

Edge two: analog output or a wired network means the classic part

The two 8-bit DACs exist only on the classic ESP32 and the S2; the Ethernet MAC exists only on the classic ESP32. So "output an analog voltage or simple audio straight from the MCU" and "plug in a network cable" both need extra parts on an S3: a DAC chip or PWM filtering for the first, an external PHY for the second.A

Edge three: screens, cameras or USB device roles rule out the C3

The C3 is the cheapest generation (22 GPIOs, 6 ADC channels, no USB OTG, no camera or LCD interface) and fits a minimal node with one sensor and one radio. The moment you need a colour display, a camera, or to present the board as a USB keyboard, thumb drive or virtual serial port, the C3 is out; you move to the S2 or S3 - and between those two the S3 has more GPIOs (45 versus 43) and a second core.A

3. When an ESP32 should not be on the board at all

One hard constraint

For a hard real-time loop at the 1 kHz level - current loop, torque loop, multi-joint synchronisation - do not use an MCU with a radio. Not because it lacks compute: a 240 MHz dual-core part runs a 1 kHz PID loop with room to spare. Because the jitter comes from places you do not control: Wi-Fi and Bluetooth radio interrupts, cache misses on flash reads, and protocol-stack scheduling all cut into the loop. The control loop belongs on the chip with no radio and no general-purpose OS.C

The practical reading of that constraint: in such a system the ESP32 is a co-processor - telemetry, status reporting, phone-side debugging, OTA, non-real-time commands to the main controller. Keep the loop on the controller with hardware timers and a deterministic bus, leave the radio to the ESP32. Two chips doing what each is good at beats one chip doing both badly.C

You do not need a clock-rate table to apply this. Ask one question: how much jitter can my control loop tolerate in the worst case? If the answer is "tens of microseconds", this is not ESP32 territory; if it is "a few milliseconds", the ESP32 is entirely adequate.C

4. Reading the part number: N8R8 matters more than "S3"

On a module, the suffix after the family name decides which tier you actually get; "ESP32-S3" alone is not enough. Take ESP32-S3-WROOM-1-N8R8: N8 = 8 MB flash, R8 = 8 MB PSRAM (an R with no number means no PSRAM). Within the same "S3", N4R2 and N16R8 are different machines in terms of what they can run:A

N4 / N8 / N16Flash size (4 / 8 / 16 MB): how much firmware and filesystem you can carry A
R2 / R8PSRAM size (2 / 8 MB): whether you can buffer image and display frames A
No RNo PSRAM: forget cameras and colour displays on this part A

One hands-on detail worth knowing: many S3 development boards carry two Type-C ports - one wired to the chip's own USB (usable as a device), one wired to an on-board USB-to-serial bridge (flashing and logs only). A good share of "it will not flash" reports are the wrong port; check which one you plugged into first.C

5. Scope, evidence grades and sources

Every figure here is a chip-level datasheet value (grade A), not a measurement of the board in your hand. The gap between the two comes from three places, each worth one question before you buy:C

Source of differenceWhat it looks likeGrade
Module choiceSame S3 family; PSRAM present or not, flash size, PCB or external antenna - all decided by the suffixA
Board designPower delivery, number of USB ports, and how many of the broken-out GPIOs are actually usable (some are taken by flash and PSRAM)C
Batch and clonesThird-party clone boards may differ from the reference design in component choice; we do not verify each one here and will not repeat rumours as conclusionsC

No prices here. Module and board prices move with channel, volume and exchange rate; a single point figure is wrong within a day. For price benchmarks, see the cost index.

Related

Last updated 2026-11-19. Sources: Espressif official chip series comparison and ESP32-S3 product page.