ESP32 Dev Module Pinout: 30-Pin vs 38-Pin Reference & GPIO Map

When you select "ESP32 Dev Module" in the Arduino IDE, you are not selecting a single physical board. You are selecting a generic board definition that maps to dozens of physical clones, primarily the 30-pin DevKit V1 and the 38-pin NodeMCU-32S. The most common baseline is the 30-pin ESP32-WROOM-32 DevKit V1. Below is the exact physical pinout and GPIO capability map for this standard, followed by critical hardware variants and wiring standards.

1. The Master ESP32 Dev Module Pinout Table (30-Pin DevKit V1)

This table maps the physical header pins (left and right sides, USB port facing down) to the internal ESP32-WROOM-32 GPIO numbers and their specific peripheral capabilities. Use this as your primary bench reference.

Rows People Get Wrong: Strapping Pins and ADC2

The most common bench failures with the ESP32 come from misinterpreting three specific rows in the table above:

• The ADC2 / WiFi Conflict: Pins mapped to ADC2 (GPIO 0, 2, 4, 12, 13, 14, 15, 25, 26, 27) share hardware resources with the WiFi radio. If your sketch initializes WiFi.begin(), any analogRead() calls on these pins will fail and return garbage data. Fix: Always use ADC1 pins (GPIO 32-39) for analog sensors in IoT projects.
• GPIO 12 (The Boot Killer): GPIO 12 is a strapping pin that determines the flash voltage. If an external circuit pulls GPIO 12 HIGH during power-on, the ESP32 expects a 1.8V SPI flash chip. Since 99% of DevKit modules use 3.3V flash, the boot will fail with a continuous reset loop. Fix: Never use GPIO 12 for inputs with external pull-up resistors.
• GPIO 34-39 (Input Only): These pins lack output drivers and internal pull-up/pull-down resistors. If you try to use them with a push-button, you must provide an external 10kΩ pull-up resistor to 3.3V.

2. Hardware Variants and DC Wiring Color Standards

The "Dev Module" definition covers multiple physical layouts. Before wiring external sensors, you must identify your physical variant and apply the correct DC wiring color standards for your region.

DC Sensor Wiring Color Codes: IEC vs. US/NEC

When wiring external 3.3V DC sensors to your ESP32, the wire colors you choose should match the standard recognized in your region to prevent catastrophic reverse-polarity faults on the bench.

• IEC 60446 (Europe / UK / International): For DC circuits, Brown is positive (3.3V), Blue is negative/ground (GND), and Green/Yellow is protective earth (not used on ESP32). Signal wires are typically Black or Grey.
• US / NEC Practice (North America): While the NEC primarily governs AC mains, standard US DC electronics practice uses Red for positive (3.3V/5V), Black for negative/ground (GND), and Yellow/White for signals.

Bench Rule: If you are mixing sensor modules from different regions, always verify the VCC/GND pinout on the sensor's silkscreen before applying power. Many cheap clone sensors swap the VCC and GND pins compared to the original Adafruit/SparkFun designs, which will instantly destroy the ESP32's 3.3V regulator.

3. Safe Interpretation When Silkscreen Markings Are Faded

Cheap clone boards from bulk AliExpress orders frequently suffer from faded, misaligned, or entirely missing silkscreen pin labels. If you cannot read the GPIO numbers on the PCB, do not guess. Use this systematic bench procedure to safely map the board.

Step 1: Identify Power and Ground via Continuity

Set your multimeter to continuity mode (the diode/beep setting). With the board unpowered:

1. Touch the black probe to the metal shield of the USB connector (this is your known ground).
2. Probe the header pins with the red probe. Any pin that beeps is a GND pin. On a 30-pin board, you should find exactly two GND pins (Left 13, Right 6).
3. The pin directly adjacent to the GND pin on the outer edge is almost always the 5V (VIN) pin.
4. The pin on the opposite outer edge is the 3V3 output.

Step 2: Map Unknown GPIOs via Software Toggling

Once power and ground are identified, plug the board into your PC. Upload the following "Pin Mapper" sketch. This code sequentially pulses every available GPIO HIGH for 2 seconds, allowing you to identify the physical pin using a logic probe, an LED with a 330Ω resistor, or a multimeter set to DC voltage.

// ESP32 Pin Mapper - Identifies physical pins via sequential 3.3V output
// Use a multimeter or LED+resistor to probe headers while this runs.

void setup() {
  Serial.begin(115200);
  Serial.println("ESP32 Pin Mapper Started. Probing pins...");
  
  // Array of safe-to-test GPIOs (Excludes strapping/input-only pins)
  int testPins[] = {4, 5, 13, 14, 15, 16, 17, 18, 19, 21, 22, 23, 25, 26, 27, 32, 33};
  int pinCount = sizeof(testPins) / sizeof(testPins[0]);

  for (int i = 0; i < pinCount; i++) {
    pinMode(testPins[i], OUTPUT);
  }
}

void loop() {
  int testPins[] = {4, 5, 13, 14, 15, 16, 17, 18, 19, 21, 22, 23, 25, 26, 27, 32, 33};
  int pinCount = sizeof(testPins) / sizeof(testPins[0]);

  for (int i = 0; i < pinCount; i++) {
    Serial.print("Pulsing GPIO ");
    Serial.println(testPins[i]);
    
    digitalWrite(testPins[i], HIGH);
    delay(2000); // 2 seconds to probe the physical header
    digitalWrite(testPins[i], LOW);
    delay(500);  // Brief gap between pins
  }
  
  Serial.println("Cycle complete. Restarting...");
  delay(3000);
}

By combining the continuity test for power rails and the software toggling for data lines, you can reliably map any unmarked ESP32 clone without risking a short circuit. For deeper architectural details on the ESP32's internal multiplexing, always refer to the official Espressif ESP32 Datasheet and the community-maintained ESP32 GPIO Reference Guide.