ESP32 Mini Pinout Reference: C3 SuperMini & D1 Mini Mapping

The term "ESP32 Mini" is ambiguous in the 2026 embedded landscape. It almost always refers to either the ESP32-C3 SuperMini (the current ultra-compact, low-cost favorite) or the older Wemos D1 Mini ESP32 (the shield-compatible format). The complete ESP32 Mini pinout for the dominant C3 SuperMini variant is detailed in the master table below. If you are using the D1 Mini shield format, refer to the variant notes in Section 3.

The Master ESP32 Mini Pinout Table (C3 SuperMini)

This table maps the physical headers on the standard 2025/2026 revision ESP32-C3 SuperMini boards to their internal GPIO numbers, default peripheral functions, and hardware limits. The C3 is a single-core RISC-V chip, meaning pin multiplexing is highly flexible, but default boot behaviors still apply.

Rows People Get Wrong & Faded Silk Recovery

When working with budget clone boards, silkscreen ink frequently rubs off, and pin mappings are often misinterpreted. Here is how to navigate the most common failure points.

The Strapping Pin Traps (GPIO 2, 8, and 9)

The most common reason an ESP32-C3 SuperMini fails to boot or enters an infinite reset loop is improper handling of strapping pins. Unlike the classic dual-core ESP32, the C3 uses GPIO 2, 8, and 9 to determine boot mode.

• GPIO 2: Must be LOW during reset to boot from SPI flash. If you wire a pull-up resistor or a sensor that drives this pin HIGH at startup, the chip will enter download mode and your code will not run.
• GPIO 8: Controls the ROM message printout. If pulled LOW, it suppresses boot logs. This is generally safe but can make debugging bare-metal crashes difficult.
• GPIO 9: Must be HIGH to boot from SPI flash. If your circuit pulls this LOW (e.g., an active-low button wired directly without a pull-up), the board will halt at the bootloader.

Safe Interpretation When Markings are Faded

If you have a bare "Mini" board with no legible silkscreen, do not guess the power pins. Applying 5V to a GPIO will instantly destroy the RISC-V core. Use this multimeter recovery sequence:

1. Find GND: Set your multimeter to continuity mode. Place the black probe on the metal shield of the USB-C connector. Probe the header pins with the red probe. The pin that beeps (reads < 1 ohm) is GND.
2. Find 5V: Plug the board into a USB power source (do not connect any loads). Set the meter to DC Voltage. Black probe on your identified GND. The pin reading 4.8V to 5.2V is your 5V input.
3. Find 3V3: With the black probe still on GND, the pin reading 3.2V to 3.4V is the regulated 3V3 output. On most SuperMini layouts, this is physically adjacent to the GND pin on the opposite header bank from 5V.

IEC Standards vs. Manufacturer Silk Screens

Understanding the gap between international electrical standards and what cheap dev board manufacturers actually print is critical for designing reliable schematics and wiring harnesses.

DC Wiring Colors: IEC 60445 vs. De-Facto Hobbyist

Under IEC 60445 standards, the standard colors for DC power circuits are Brown for the positive pole, Grey for the negative pole, and Blue for the midpoint. However, the embedded manufacturing sector universally ignores this for low-voltage logic boards.

On your ESP32 Mini, you will encounter the de-facto US/hobbyist standard: Red for VCC (3V3 or 5V) and Black for GND. When designing a custom wiring harness for a C3 SuperMini in an industrial enclosure, you must label your wires explicitly. If you hand an IEC-trained European electrician a brown wire and tell them it is "Ground" because the dev board manual said so, you will create a dangerous misinterpretation. Always use Green-Yellow for chassis earth, and stick to Black for logic GND in DC systems to avoid cross-standard confusion.

Schematic Symbols: IEC 80000-6 vs. US Style

When reading the official Espressif ESP32-C3 datasheet and reference schematics, you will notice a mix of symbol standards. Espressif typically uses the US-style Ground symbol (three descending horizontal lines) for logic GND, whereas the strict IEC 80000-6 standard prefers a single horizontal line with a downward-pointing arrow, or a specific earth electrode symbol for protective earth. When drafting your own KiCad or Altium schematics for an ESP32 Mini carrier board, ensure your GND symbols clearly differentiate between Logic GND (US style is acceptable and widely understood) and Protective Earth (must use the IEC earth symbol).

Hardware Edge Cases and the D1 Mini Variant

Not all "Mini" boards are created equal. If your ESP32 Mini has two rows of 8 pins and is designed to accept stacked shields, you are likely holding a Wemos D1 Mini ESP32, not a C3 SuperMini.

The D1 Mini ESP32 Pinout Shift

The D1 Mini ESP32 uses the classic dual-core ESP32 (usually a WROOM-32 module) and maps pins to match the original ESP8266 D1 Mini shield layout. The physical pin labeled "D1" on a D1 Mini ESP32 is actually GPIO 5, whereas "D1" on an ESP8266 is GPIO 5 as well, but the underlying architecture is entirely different. If you are porting code from an ESP8266 D1 Mini to an ESP32 D1 Mini, you must remap the ADC pins, as the ESP32 ADC is non-linear and requires calibration, unlike the simpler 10-bit ADC on the older chips.

The SuperMini Voltage Regulator Flaw

A critical hardware edge case on the 2024-2026 revisions of the ESP32-C3 SuperMini is the onboard LDO (Low Dropout Regulator). While the 5V pin can theoretically pass 500mA from the USB port, the onboard 3.3V LDO is typically a generic SOT-23 package rated for 500mA on paper. In practice, without adequate copper pours on the PCB to act as a heatsink, the LDO will thermally throttle and drop the 3V3 rail if you draw more than 150mA to 200mA continuously.

By respecting the strapping pin states, verifying power rails with a meter when silkscreens fail, and understanding the thermal limits of the miniaturized LDO, you can reliably deploy the ESP32 Mini in both bench prototypes and permanent field installations.