ESP32 Dev Board Pinout Reference: WROOM, S3, and Strapping Pins

The standard 30-pin ESP32-WROOM-32E dev board features 25 usable GPIOs, 3.3V logic (strictly not 5V tolerant), and specific strapping pins that dictate boot modes. Whether you are wiring an I2C sensor or debugging a boot loop, the exact pin behavior matters. Below is the complete pinout reference, followed by the critical edge cases that brick boards and halt projects.

The Standard 30-Pin ESP32 Dev Board Pinout Table

This table maps the ubiquitous 30-pin DevKit V1 layout (often sold by HiLetgo, NodeMCU, or generic brands in 2026). Note that while the physical board has 30 pins, the underlying Espressif ESP32-WROOM-32E datasheet exposes 34 physical GPIO pads, some of which are not broken out to the headers.

Note: Pins 16-18 and 20-22 (GPIO6-11) are connected to the internal SPI flash on the WROOM module. ESP-IDF documentation explicitly warns against using these for external peripherals, as doing so will crash the chip or corrupt the firmware.

Rows People Get Wrong: Strapping Pins and 5V Hazards

The most common reasons an ESP32 dev board fails to boot or permanently dies trace back to misinterpreting three specific rows in the table above.

The Strapping Pins (GPIO0, GPIO2, GPIO12, GPIO15)

During the reset sequence, the ESP32 samples these pins to determine its boot mode and flash voltage. If you wire a sensor or relay directly to these pins without considering their boot state, the chip will hang.

• GPIO12 (MTDI): This is the most dangerous strapping pin for beginners. It selects the flash voltage. If GPIO12 is pulled HIGH during boot, the ESP32 expects a 1.8V flash chip. Since the WROOM-32E uses a 3.3V flash, pulling GPIO12 high will cause a brownout or permanent flash corruption. Rule: Never wire external pull-up resistors to GPIO12.
• GPIO0 & GPIO2: These dictate the boot mode (Flash vs. Download). GPIO2 has an onboard LED on most DevKits. If you connect a low-impedance load to GPIO2 that pulls it HIGH, the chip will fail to enter the UART bootloader when you press the flash button.
• GPIO15: Controls boot log output. If pulled HIGH, it outputs SDIO debug logs, which can interfere with standard UART communication if you are multiplexing pins.

Input-Only Pins (GPIO34, 35, 36, 39)

These pins lack internal pull-up or pull-down resistors and cannot be configured as outputs. If you try to drive an LED from GPIO34, nothing will happen. Furthermore, because they lack internal pull-ups, reading a button on these pins requires an external 10kΩ resistor to 3.3V, otherwise the pin will float and trigger phantom interrupts.

Peripheral Wiring Color Codes: IEC vs NEC vs Old UK

When wiring external sensors to the ESP32's I2C, SPI, or UART buses, maintaining a consistent wire color scheme prevents catastrophic cross-wiring. While data lines (SDA, SCL, MOSI, MISO) generally follow universal hobbyist conventions (Yellow/Orange for data, Green for clock), the power and ground wiring colors vary drastically by regional electrical standards.

When building enclosures or running wire harnesses from the ESP32 to external terminal blocks, align your DC low-voltage colors with your region's governing standard to ensure safe interpretation by other technicians.

Which standard applies to you? If you are building a consumer product for the European market, you must adhere to IEC standards where Blue is strictly reserved for the grounded/negative conductor. If you are wiring a control panel in the US under NFPA 79, Blue is often used for DC control circuits, but Black remains the standard for DC common (GND). Never mix IEC Blue (GND) with US Black (GND) in the same harness without clear labeling, as a European technician will assume the Black wire is a live AC phase.

Safe Interpretation When Silkscreen Markings Are Faded

Cheap clone boards from overseas marketplaces frequently suffer from rubbed-off silkscreen, misprinted pin labels, or completely blank PCBs. Guessing the pinout by looking at adjacent boards is a reliable way to short the 5V rail to a GPIO. Here is the bench-tested procedure to safely map an unmarked ESP32 dev board.

Step 1: Identify the Power and Ground Rails

Do not plug the board into USB yet. Set your multimeter to continuity mode (the diode/beep setting).

1. Locate the large metal shielding can (the WROOM module). The metal can is tied to GND. Probe the can with your black lead.
2. Use the red lead to test the header pins. The pins that beep are your GND pins. Mark them with a silver paint pen.
3. Locate the AMS1117-3.3 voltage regulator (a small SOT-223 package near the USB port). Pin 3 (or the large tab) is the 3.3V output. Trace the continuity from the tab to the header pins to find your 3V3 pin.

Step 2: Locate the EN and Boot Pins

The EN (Enable) pin is almost always routed through a 10kΩ pull-up resistor to the 3.3V rail, and a 100nF capacitor to GND. If you have a component view, find the capacitor tied to the EN button; the trace leading to the header is your EN pin. Similarly, the GPIO0 pin is routed to the 'BOOT' tactile switch. Tracing the switch leg will reliably identify GPIO0, giving you a fixed reference point to count the remaining pins against the standard 30-pin layout.

Step 3: Verify with a Safe Power-Up

Once GND, 3V3, and 5V are identified and marked, power the board via USB. Use the multimeter in DC voltage mode to verify the 3V3 pin reads between 3.25V and 3.35V. If it reads 5V, the board has a catastrophic regulator failure or a non-standard pinout—discard it immediately to protect your sensors.

Bench Tip: When mapping faded boards, write the GPIO numbers directly on the plastic header shroud using a fine-tip white paint marker. Silkscreen wears off, but paint on the black plastic housing survives years of plugging and unplugging jumper wires.