Last updated: 2026-11-22
The ESP32 DevKit V1 pinout has 30 pins in two rows of 15, with 25 usable GPIOs: 21 inputs and outputs plus 4 input-only pins. Start with GPIO 4, 13, 16, 17, 18, 19, 21, 22, 23, 25, 26, 27, 32, and 33, which have no boot role and nothing pulling them. Avoid GPIO 1 and 3, which carry USB serial. Watch the strapping pins GPIO 2, 5, 12, and 15, which decide whether the board boots. Wire analog sensors to the ADC1 pins GPIO 32, 33, 34, 35, 36, and 39, because the ADC2 pins stop working with WiFi on.
Every pin number below was checked twice, against the Espressif DevKitC V4 header tables and the DOIT board tables, and the strapping rules come from the Espressif ESP32 Series Datasheet v5.3.
Table of contents
- Which board is this guide for?
- What is the full ESP32 DevKit V1 pinout?
- Which pins are safe to use first?
- Which pins are input only?
- Which pins decide whether the board boots?
- Which pins are taken by USB and flash?
- How do the ADC pins work?
- Where are the DAC and touch pins?
- Which pins do I2C, SPI, and UART use?
- Can every pin do PWM?
- How do you power the DevKit V1?
- How do you test the pins?
- What mistakes do people make?
- Frequently asked questions
- Parts used in this guide
- In this series
- Related guides
- Sources
Which board is this guide for?
This guide is for the ESP32 DevKit V1, the 30-pin DOIT board built around an ESP32-WROOM-32 module. It carries a dual-core Xtensa LX6 chip at 240 MHz, WiFi 802.11 b/g/n at 2.4 GHz, Bluetooth 4.2 and BLE, 520 KB of SRAM, and 4 MB of SPI flash. It has a Micro-USB port, a USB-to-serial chip, an AMS1117-3.3 regulator, and EN and BOOT buttons.
Count the pins before you trust any pinout. This board has 30 pins in two rows of 15. The 38-pin ESP32-DevKitC is a different board: it breaks out the flash pins GPIO 6 to 11 and the BOOT pin GPIO 0. If your board says DevKit V1, DOIT, NodeMCU-32, or ESP32 30-pin, this guide is for your board.
Clones are everywhere, and most follow the same DOIT design. What changes is the USB-to-serial chip (CP2102 on the original, CH340 or CH9102 on clones), the module revision (WROOM-32, 32D, or 32E), and the USB connector (Micro-USB or USB-C). The GPIO numbers never change, but on rare clones the last few power pins sit in a different order, so read the silkscreen on your own board.
What is the full ESP32 DevKit V1 pinout?
Hold the board with the antenna at the top and the USB port at the bottom. The left header runs from EN to VIN, and the right header runs from D23 to 3V3. In Arduino code you always use the GPIO number: D23 is GPIO 23. VP and VN are GPIO 36 and 39, TX0 and RX0 are GPIO 1 and 3, and TX2 and RX2 are GPIO 17 and 16.
Left header, top to bottom
| Silkscreen | GPIO | Main functions | Watch out for |
|---|---|---|---|
| EN | – | Reset | Active LOW, 10k pull-up |
| VP | 36 | ADC1_CH0 | Input only, no pull-ups |
| VN | 39 | ADC1_CH3 | Input only, no pull-ups |
| D34 | 34 | ADC1_CH6 | Input only, no pull-ups |
| D35 | 35 | ADC1_CH7 | Input only, no pull-ups |
| D32 | 32 | ADC1_CH4, Touch 9 | Safe pin, ADC1 with WiFi |
| D33 | 33 | ADC1_CH5, Touch 8 | Safe pin, ADC1 with WiFi |
| D25 | 25 | ADC2_CH8, DAC1 | ADC2 stops with WiFi |
| D26 | 26 | ADC2_CH9, DAC2 | ADC2 stops with WiFi |
| D27 | 27 | ADC2_CH7, Touch 7 | ADC2 stops with WiFi |
| D14 | 14 | ADC2_CH6, Touch 6, HSPI clock | Signal at boot, avoid relays |
| D12 | 12 | ADC2_CH5, Touch 5, HSPI MISO | Strapping, must be LOW at reset |
| D13 | 13 | ADC2_CH4, Touch 4, HSPI MOSI | Safe pin |
| GND | – | Ground | Common ground |
| VIN | – | 5 V to 12 V input | About 4.7 V on USB |
Right header, top to bottom
| Silkscreen | GPIO | Main functions | Watch out for |
|---|---|---|---|
| D23 | 23 | VSPI MOSI | Safe pin |
| D22 | 22 | I2C SCL | I2C clock |
| TX0 | 1 | UART0 TX | USB serial |
| RX0 | 3 | UART0 RX | USB serial |
| D21 | 21 | I2C SDA | I2C data |
| D19 | 19 | VSPI MISO | Safe pin |
| D18 | 18 | VSPI clock | Safe pin |
| D5 | 5 | VSPI chip select | Strapping, HIGH at reset |
| TX2 | 17 | UART2 TX | Safe pin |
| RX2 | 16 | UART2 RX | Safe pin |
| D4 | 4 | ADC2_CH0, Touch 0 | ADC2 stops with WiFi |
| D2 | 2 | ADC2_CH2, Touch 2, onboard LED | Strapping, LOW or floating at reset |
| D15 | 15 | ADC2_CH3, Touch 3, HSPI chip select | Strapping, HIGH at reset |
| GND | – | Ground | Common ground |
| 3V3 | – | 3.3 V output or input | Regulator output |
Not on the headers: GPIO 0 is the BOOT button, GPIO 6 to 11 run the module SPI flash, and GPIO 37 and 38 are not bonded out.
Which pins are safe to use first?
The safest pins are the 14 GPIOs with no boot role and nothing on the board pulling them: GPIO 4, 13, 16, 17, 18, 19, 21, 22, 23, 25, 26, 27, 32, and 33. Use these first for buttons, LEDs, sensors, and relays.
GPIO 5, 14, and 15 output a signal for a moment at boot, so they suit sensors and status LEDs but not relays, motor drivers, or buzzers. GPIO 34, 35, 36, and 39 are input only. GPIO 2, 5, 12, and 15 are strapping pins, covered below. GPIO 1 and 3 carry USB serial, so avoid them for anything else. A button on GPIO 33, an LED on GPIO 23, and a sensor on GPIO 32 cannot go wrong.
Which pins are input only?
GPIO 34, 35, 36, and 39 are input only. They have no output driver, so digitalWrite does nothing on them, and they have no internal pull-up or pull-down resistors, so a floating pin reads random values. The silkscreen calls GPIO 36 VP and GPIO 39 VN.
Use these four pins for analog input and for buttons with an external resistor. They are all ADC1 pins, so they keep working with WiFi on: VP is ADC1 channel 0, VN is channel 3, D34 is channel 6, and D35 is channel 7. A button here needs a 10k pull-up to 3V3 or a 10k pull-down to ground, because INPUT_PULLUP does nothing here. Do not wire an LED, a relay, or any output to these pins.
Which pins decide whether the board boots?
Five pins decide how the ESP32 boots, and the chip reads them once at reset. After reset they work as normal pins, but the level at reset is latched until the next power cycle. Per the Espressif ESP32 Series Datasheet v5.3, they are GPIO 0, 2, 5, 12, and 15.
| Pin | Must be at reset | What it controls |
|---|---|---|
| GPIO 0 (BOOT button) | HIGH to run, LOW for download mode | Boot mode, with GPIO 2 |
| GPIO 2 (D2) | LOW or floating | Boot mode, with GPIO 0; onboard blue LED |
| GPIO 5 (D5) | HIGH | SDIO slave timing |
| GPIO 12 (D12) | LOW | Flash voltage: LOW is 3.3 V, HIGH is 1.8 V |
| GPIO 15 (D15) | HIGH | Boot log on UART0: HIGH prints, LOW silences |
GPIO 0 and GPIO 2 together select the boot mode. GPIO 0 HIGH boots from flash and runs your sketch. GPIO 0 LOW with GPIO 2 LOW means joint download boot mode, which is how the Arduino IDE uploads over USB. The DOIT schematic holds GPIO 0 HIGH, pulls GPIO 2 LOW, and pulls GPIO 5 HIGH with 10k resistors, so the board boots normally out of the box.
GPIO 12 is the one that catches people. It is the MTDI pin, and it selects the flash voltage at reset. The WROOM-32 flash runs at 3.3 V, so GPIO 12 must be LOW at reset. Pull it HIGH and the chip selects 1.8 V, and the board will not boot. Never wire a pull-up resistor or a sensor that drives HIGH to D12.
To enter download mode by hand, hold BOOT, press and release EN, then release BOOT. You rarely need to: the auto-reset circuit does it when the Arduino IDE starts an upload.
Which pins are taken by USB and flash?
GPIO 1 and GPIO 3 are UART0, the serial port wired to the USB-to-serial chip. TX0 (GPIO 1) sends the boot log and your Serial prints to the computer, and RX0 (GPIO 3) receives uploads. The USB chip shares these lines through 1k resistors, so anything else wired to TX0 or RX0 fights it. Do not use GPIO 1 or 3 for sensors, buttons, or LEDs. For a second serial port, use UART2 on TX2 and RX2 (GPIO 17 and 16), or remap UART1 to two free pins.
GPIO 6 to 11 are wired to the SPI flash chip inside the WROOM-32 module. They are not broken out on the 30-pin headers: connecting anything to a flash pin corrupts flash reads and the board will not boot.
How do the ADC pins work?
The ESP32 has two 12-bit analog to digital converters, ADC1 and ADC2, with 18 channels between them. A 12-bit reading runs from 0 to 4095. The headers carry 15 ADC pins: 6 on ADC1 and 9 on ADC2. The ADC is not linear near the rails, so readings compress near 0 V and near 3.3 V.
The rule that matters most: ADC2 stops working while WiFi is on. The WiFi driver takes over ADC2, so an analogRead on an ADC2 pin returns garbage or fails while the radio runs. ADC1 keeps working with WiFi on, so wire the sensor to an ADC1 pin when the project uses WiFi.
| ADC unit | Header pins | Channels | Works with WiFi |
|---|---|---|---|
| ADC1 | VP (36), VN (39), D34, D35, D32, D33 | CH0, CH3, CH6, CH7, CH4, CH5 | Yes |
| ADC2 | D4, D2, D15, D13, D12, D14, D27, D25, D26 | CH0, CH2, CH3, CH4, CH5, CH6, CH7, CH8, CH9 | No |
GPIO 0 is ADC2 channel 1 and GPIO 37 and 38 are ADC1 channels 1 and 2, but none of the three is on the headers.
Where are the DAC and touch pins?
The ESP32 has two 8-bit digital to analog converters, DAC1 on GPIO 25 (D25) and DAC2 on GPIO 26 (D26). An 8-bit DAC writes values from 0 to 255 and outputs a true analog voltage, not a PWM square wave. Use dacWrite in Arduino code. Both DAC pins are also ADC2 pins, so do not read them as analog inputs with WiFi on.
The ESP32 has 10 capacitive touch channels, and nine sit on the headers: T0 on D4, T2 on D2, T3 on D15, T4 on D13, T5 on D12, T6 on D14, T7 on D27, T8 on D33, and T9 on D32. T1 is GPIO 0, the BOOT button, so it is not available as a touch pin here. Read a touch pin with touchRead in Arduino code. A touch pin reads lower when a finger is near it, and the threshold depends on the wire length and the board layout, so calibrate it in your sketch.
Which pins do I2C, SPI, and UART use?
The ESP32 routes peripherals through a GPIO matrix, so I2C, SPI, and UART can move to almost any free pin. The table below gives the defaults.
| Bus | Default pins on this board | Notes |
|---|---|---|
| I2C (Wire) | SDA D21, SCL D22 | Needs pull-ups |
| VSPI | MOSI D23, MISO D19, clock D18, chip select D5 | Arduino default |
| HSPI | MOSI D13, MISO D12, clock D14, chip select D15 | Second SPI bus |
| UART0 (Serial) | TX TX0 (GPIO 1), RX RX0 (GPIO 3) | USB serial |
| UART2 | TX TX2 (GPIO 17), RX RX2 (GPIO 16) | Free second port |
| UART1 | No fixed pins | Remap to free pins |
I2C needs pull-up resistors on SDA and SCL; most sensor boards include them, but if your bus hangs, check for them first. SPI chip select is D5 for VSPI, and D5 is a strapping pin that must be HIGH at reset, so do not pull it LOW with a sensor that drives the line at boot. For HSPI the chip select is D15 and the MISO line is D12, both strapping pins, so VSPI is the safer default.
UART1 has no usable default pins here: its hardware defaults are GPIO 9 and 10, which are flash pins. For a third serial port, call Serial1.begin with explicit RX and TX pins on two safe GPIOs. In the Arduino-ESP32 core 3.x, Serial1 defaults to RX GPIO 26 and TX GPIO 27, and Serial2 defaults to RX GPIO 4 and TX GPIO 25. Set them explicitly so a core update cannot move them.
Can every pin do PWM?
Every output-capable pin on the ESP32 DevKit V1 can do PWM through the LEDC peripheral, which has 16 channels. There is no fixed list of PWM pins. Pick any pin from the safe list, attach it to an LEDC channel with ledcAttach, and set the duty. The 4 input-only pins cannot do PWM, because they cannot drive an output.
GPIO 5, 14, and 15 output a signal for a moment at boot. A sensor or a status LED on these pins is fine, but a relay, a motor driver, or a buzzer wired here can switch on briefly at every reset. If your project drives something that must stay off at boot, use a safe pin.
How do you power the DevKit V1?
The DevKit V1 takes power from exactly one source at a time: Micro-USB at 5 V, VIN at 5 V to 12 V, or 3V3 at a regulated 3.3 V. Using more than one at once can damage the board or the power supply.
USB power reaches VIN through an SS14 Schottky diode, so VIN reads about 4.7 V when the board runs from USB, and a supply on VIN cannot back-feed your computer. The AMS1117-3.3 regulator is a 1 A class part with about 1.1 V of dropout, so VIN needs at least about 4.5 V. The 3V3 pin can power small sensors and logic, but budget it at a few hundred mA.
Every pin on this board is 3.3 V logic only. No pin is 5 V tolerant. A 5 V sensor output wired straight to a GPIO pin will damage the input, so use a level shifter or a voltage divider for 5 V sensors. Never power a servo or a motor from a GPIO pin or from the 3V3 rail: they need their own power supply with a shared ground. Battery power, charging, protection, and run-time math are covered in How to Power ESP32 and Arduino Projects on LiPo Power.
How do you test the pins?
This sketch tests three pins at once: the onboard blue LED on D2, a potentiometer on D32, and a button on D33. Wire the potentiometer wiper to D32 with its ends to 3V3 and GND, and wire a push button between D33 and GND; the button needs no resistor because the sketch uses the internal pull-up on D33. Open the Serial Monitor at 115200 baud: the ADC reading on D32 runs from 0 to 4095 as you turn the pot, and the button lights the LED.
// ESP32 DevKit V1 pin test: onboard LED, ADC1 potentiometer, button.
// Arduino-ESP32 core, built-in libraries only. No extra libraries needed.
// Board: DOIT ESP32 DevKit V1, 30-pin, ESP32-WROOM-32.
// Wiring: potentiometer wiper to D32, ends to 3V3 and GND.
// push button between D33 and GND (internal pull-up, no resistor).
#include <Arduino.h>
const int LED_PIN = 2; // D2, blue onboard LED. Strapping pin, LOW or floating at boot.
const int POT_PIN = 32; // D32, ADC1_CH4. ADC1 keeps working with WiFi on.
const int BUTTON_PIN = 33; // D33, ADC1_CH5. Safe pin, internal pull-up.
void setup() {
Serial.begin(115200);
delay(1000);
pinMode(LED_PIN, OUTPUT);
pinMode(BUTTON_PIN, INPUT_PULLUP);
analogReadResolution(12); // 12-bit ADC: readings 0 to 4095.
Serial.println("ESP32 DevKit V1 pin test running.");
Serial.println("Turn the pot on D32, press the button on D33.");
}
void loop() {
int pot = analogRead(POT_PIN);
bool pressed = digitalRead(BUTTON_PIN) == LOW;
digitalWrite(LED_PIN, pressed ? HIGH : LOW);
Serial.print("D32 ADC: ");
Serial.print(pot);
Serial.print(" D33 button: ");
Serial.println(pressed ? "pressed" : "released");
delay(500);
}
The sketch uses only the built-in Arduino-ESP32 core, and it compiles with PlatformIO on esp32dev. If the upload fails, hold BOOT, press and release EN, then release BOOT to force download mode. If the Serial Monitor shows nothing, check the USB cable: a charge-only cable carries power but no data.
What mistakes do people make?
First, wiring an analog sensor to an ADC2 pin and turning on WiFi. The reading goes wrong the moment the radio starts. Wire analog sensors to the ADC1 pins VP, VN, D34, D35, D32, and D33 with WiFi on.
Second, pulling GPIO 12 HIGH at boot. D12 selects the flash voltage, and HIGH selects 1.8 V, but the WROOM-32 flash runs at 3.3 V, so the board will not boot. Keep D12 LOW at reset.
Third, using GPIO 1 and 3 for a sensor or a button. TX0 and RX0 carry USB serial, and anything wired there fights the USB chip and breaks uploads.
Fourth, wiring an output to an input-only pin. GPIO 34, 35, 36, and 39 cannot drive an LED or a relay, and a button here needs an external resistor.
Fifth, trusting the chip GPIO count instead of the board pinout. The ESP32 chip has 34 GPIOs, but this board breaks out 25. Check the board pinout before you wire anything.
Frequently asked questions
How many pins does the DevKit V1 have?
The ESP32 DevKit V1 has 30 pins in two rows of 15, with 25 usable GPIOs: 21 inputs and outputs plus 4 input-only pins (GPIO 34, 35, 36, and 39). GPIO 0 is the BOOT button, GPIO 6 to 11 run the SPI flash, and GPIO 37 and 38 are not bonded out.
Which pins are safe to use?
GPIO 4, 13, 16, 17, 18, 19, 21, 22, 23, 25, 26, 27, 32, and 33 are the safest pins: no strapping role and nothing on the board pulling them. Use these first for buttons, LEDs, sensors, and relays. Avoid GPIO 1 and 3, which carry USB serial.
What are the strapping pins?
The strapping pins are GPIO 0, 2, 5, 12, and 15, per the Espressif ESP32 Series Datasheet v5.3. At reset, GPIO 0 must be HIGH to run and LOW to enter download mode, GPIO 2 must be LOW or floating, GPIO 5 must be HIGH, GPIO 12 must be LOW for 3.3 V flash, and GPIO 15 must be HIGH to print the boot log.
Can I use ADC pins with WiFi on?
Yes, but only the ADC1 pins: VP (GPIO 36), VN (GPIO 39), D34, D35, D32, and D33. ADC2 covers D4, D2, D15, D13, D12, D14, D27, D25, and D26, and it stops working while WiFi runs. With WiFi on, wire the sensor to an ADC1 pin.
Is the DevKit V1 5 V tolerant?
No. Every pin on the ESP32 DevKit V1 is 3.3 V logic only, and no pin is 5 V tolerant. A 5 V sensor output wired straight to a GPIO pin will damage the input, so use a level shifter or a voltage divider for 5 V sensors. Power the board from USB at 5 V, from VIN at 5 V to 12 V, or from a regulated 3.3 V supply on the 3V3 pin.
Parts used in this guide
The board and the bench parts below are in stock in the store. The DevKit V1 programs over a Micro-USB data cable, so use a cable that carries data, not a charge-only cable.
ESP32 DevKit V1 Development Board, 30-Pin WROOM-32, WiFi + Bluetooth, Dual-Core – The 30-pin board in this guide.
Solderless Breadboard Kit, 2 x 830-Point + 2 x 400-Point Boards + 126 Jumper Wires – Breadboard and wires for the pin test.
Breadboard Jumper Wires 120-Piece, Male to Male, 10cm Multicolored Dupont Wire – Male to male wires for board to breadboard.
ELEGOO Dupont Jumper Wire Set 120-Piece, M-F M-M F-F Multicolored for Breadboard – Male to female, male to male, and female to female wires for sensors.
In this series
This is post 2 of 10 in the ESP32 series. The pillar is Which ESP32 Should I Buy? Pick the Right Board for Your Project. The other spokes are plain text until they publish.
- Post 1: Which ESP32 Should I Buy? (pillar).
- Post 2: ESP32 DevKit V1 (30-pin) pinout (this post).
- Post 3: ESP32-S3 DevKitC-1 pinout.
- Post 4: ESP32-CAM pinout, boot mode, and flashing.
- Post 5: ESP32-CAM troubleshooting.
- Post 6: ESP32-CAM streaming.
- Post 7: ESP32-CAM on battery.
- Post 8: ESP-NOW explained.
- Post 9: Arduino IDE vs PlatformIO vs ESP-IDF vs MicroPython.
- Post 10: ESP32 not detected over USB.
Related guides
- Which ESP32 Should I Buy? Pick the Right Board for Your Project
- How to Choose ESP32 Boards for Your Robotics Projects
- How to Pick an ESP32 SuperMini Board for Tiny Builds
- How to Power ESP32 and Arduino Projects on LiPo Power
- ESP32-S2 Mini Pinout: GPIO, USB OTG, and ADC
Sources
- Espressif ESP32 Series Datasheet v5.3 (2026-07): pin functions, strapping pins Tables 3-1, 3-3, and 3-4, ADC, DAC, touch. https://documentation.espressif.com/esp32_datasheet_en.pdf
- Espressif ESP32-DevKitC V4 Getting Started Guide: J2 and J3 header tables, power options, flash pin warning. https://documentation.espressif.com/esp-dev-kits/en/latest/esp32/esp32-devkitc/user_guide.html
- Espressif ESP-IDF GPIO and RTC GPIO docs: ADC channel map, strapping pins, ADC2 and WiFi rule, input-only pins. https://docs.espressif.com/projects/esp-idf/en/v5.2-beta1/esp32/api-reference/peripherals/gpio.html
- DeepBlueMbedded ESP32 Pinout (DevKit V1 30-Pin DOIT): DOIT header tables, schematic notes, board specs. https://deepbluembedded.com/esp32-pinout-devkit-v1-datasheet-schematic/


