The ESP32-C3 Super Mini packs a single-core 160MHz RISC-V processor, Wi-Fi, and Bluetooth LE into a footprint barely larger than a postage stamp. Because space is at an absolute premium on these ultra-compact clones, the silkscreen labels are microscopic, and the pin mapping differs drastically from the standard 30-pin ESP32 DevKit. If you are wiring this board for a production prototype or a tight enclosure, you need the exact GPIO mapping, strapping pin behaviors, and logic thresholds. Below is the definitive hardware reference.

The Complete ESP32-C3 Super Mini Pinout Reference

The standard commercial "Super Mini" variant breaks out 14 pins (7 per side). Unlike the original dual-core ESP32, the C3 variant uses a RISC-V architecture and features native USB on specific pins, which changes how you handle serial debugging and bootloading.
Physical Pin GPIO Number Silkscreen Label Primary Function ADC / PWM / Special Notes
Left 1N/A5VPower InputUSB VBUS input. Do not use as a high-current 5V output.
Left 2N/AGNDGroundCommon ground for logic and power.
Left 3N/A3V3Power OutputOnboard LDO output. Max draw ~500mA depending on LDO variant.
Left 4GPIO22General I/OADC1_CH2. Strapping pin: must be LOW for SPI flash boot.
Left 5GPIO33General I/OADC1_CH3. Analog input capable.
Left 6GPIO44General I/OADC1_CH4. Often used for I2C SDA.
Left 7GPIO55General I/OADC1_CH5. Often used for I2C SCL.
Right 1GPIO21TXUART0 TXDefault hardware serial transmit. Not routed to USB.
Right 2GPIO20RXUART0 RXDefault hardware serial receive. Not routed to USB.
Right 3GPIO1010General I/OSPI FSPICS0. Good for SPI display chip select.
Right 4GPIO99Boot / I/OStrapping pin: Pull LOW during reset to enter USB download mode.
Right 5GPIO88General I/OSPI SPICS0 / Built-in RGB LED (on some revisions).
Right 6GPIO77General I/OSPI FSPID / MOSI.
Right 7GPIO66General I/OSPI FSPICLK / SCK.

Wiring Standards & Peripheral Color Codes

When connecting the ESP32-C3 Super Mini to external sensors, relay modules, or AC mains interfaces, you must adhere to established wiring color standards. While the microcontroller itself operates at 3.3V DC, the peripherals it controls often cross into higher voltages. Misinterpreting a wire color when wiring a 5V relay module or a 120V/230V AC contactor can result in a fried RISC-V core or a severe shock hazard.
Application IEC 60446 (EU / UK / AU) NEC / US Standard Common Hobbyist / Dupont Wire
Low Voltage DC Ground (GND)Black or BlueBlackBlack
Low Voltage DC Positive (3.3V / 5V)Red or BrownRedRed
I2C Data (SDA)Yellow (Recommended)YellowOrange or Yellow
I2C Clock (SCL)Green (Recommended)GreenGreen or Blue
AC Mains Earth GroundGreen/Yellow StripeGreen or Bare CopperN/A (Never use Dupont)
AC Mains NeutralBlueWhite or GrayN/A
AC Mains Line (Hot)BrownBlack or RedN/A
Safe Interpretation for Faded or Missing Markings: The Super Mini's silkscreen is notoriously fragile and can rub off during handling or reflow soldering. If your pin labels are faded, never guess the 5V or GND pins by counting. Use a digital multimeter in continuity mode. Probe the metal shell of the USB-C connector to identify the GND pins (Left 2). Once GND is found, power the board via USB and use DC voltage mode to identify the 3V3 LDO output (Left 3) and the 5V VBUS (Left 1).

Rows Makers Get Wrong (And How to Avoid Bricking Your Board)

The ESP32-C3 is not a drop-in replacement for the original ESP32. The architecture and strapping pin behaviors are fundamentally different. Here are the specific rows from the pinout table that cause the most field failures.

1. The Missing UART-to-USB Bridge (GPIO20 / GPIO21)

Unlike the 30-pin DevKit, the Super Mini does not have an onboard CP2102 or CH340 USB-to-UART bridge chip. The USB-C port is wired directly to the ESP32-C3's native USB peripheral on GPIO18 (D-) and GPIO19 (D+), which are not broken out on the side headers. The pins labeled TX (GPIO21) and RX (GPIO20) are strictly hardware UART. If you are trying to view serial monitor output, you must use the native USB CDC interface in your code, not the hardware UART pins, unless you are wiring an external FTDI adapter.

2. The Bootloader Trap (GPIO9)

Because the board uses native USB, the Arduino IDE or ESP-IDF often fails to auto-reset the board into download mode. If your upload hangs at "Connecting...", you must manually pull GPIO9 to GND, press the reset button (or unplug/replug the USB cable), and then release GPIO9. For permanent installations, wire a 10k pull-up resistor on GPIO9 and a tactile switch to GND to act as a manual "Boot" button.

3. The 5V Pin Misconception

The pin labeled 5V is directly connected to the USB-C VBUS line. It is an input, not a robust output. While you can use it to power a single 5V I2C sensor that draws 10mA, attempting to power a 5V relay module or a strip of WS2812 LEDs from this pin will cause a brownout on the USB bus, resetting the C3 core and potentially tripping your computer's USB overcurrent protection. Always power high-current 5V peripherals from a dedicated external buck converter.

Frequently Asked Questions

What is the maximum current draw per GPIO on the ESP32-C3 Super Mini?

The absolute maximum rating per GPIO is 40mA, but Espressif strongly recommends limiting continuous current to 20mA per pin, with a total aggregate current across all GPIOs not exceeding 80mA. If you need to drive a 5V relay or a high-power MOSFET gate, use a logic-level N-channel MOSFET (like the 2N7000) or an optocoupler. Never source a relay coil directly from a C3 GPIO.

Can I use the ESP32-C3 Super Mini for deep sleep battery projects?

Yes, the ESP32-C3 silicon itself supports deep sleep currents around 5µA. However, the "Super Mini" board features an onboard 3.3V LDO voltage regulator and a USB-C power path management circuit that have a quiescent current draw of roughly 5mA to 15mA. This parasitic draw will kill a lithium cell quickly. For true ultra-low-power battery projects, you must either physically desolder the onboard LDO and feed 3.3V directly into the 3V3 pin, or switch to a bare ESP32-C3 module without the dev-board overhead.

Why does my ESP32-C3 Super Mini not show up in the Arduino IDE port list?

This is almost always caused by the native USB bootloader state. The board requires the Arduino ESP32 Core (version 2.0.14 or newer) with "USB CDC On Boot" enabled in the Tools menu. If the firmware currently on the chip has disabled USB CDC or crashed before initializing the USB stack, the PC will not enumerate the device. Hold the BOOT button (or pull GPIO9 low), plug in the USB cable, and the board will enumerate as an ESP32-C3 USB device, allowing you to flash a corrected sketch.

How noisy is the ADC on the ESP32-C3 compared to the original ESP32?

The ESP32-C3 features a 12-bit SAR ADC, but bench tests consistently show a noise floor of ±15 to ±20 LSBs when reading floating analog pins or high-impedance voltage dividers. For precision analog readings (like a load cell or NTC thermistor), you must place a 100nF ceramic capacitor directly between the analog input pin and GND to filter high-frequency RISC-V clock noise. For critical measurements, bypass the internal ADC entirely and use an external I2C ADC like the ADS1115.

For deeper architectural details on the RISC-V core and strapping pin logic thresholds, refer to the official Espressif ESP32-C3 Technical Reference Manual.