Components · 11 min read

ESP32 30 Pin vs 38 Pin: Pinout, Breadboard Fit, WROOM, CP2102

ESP32 30 pin vs 38 pin: side-by-side pinout, why it won't fit a breadboard, WROOM vs WROVER, CP2102 vs CH340 and which board to pick in the Arduino IDE.

The difference between an ESP32 30 pin vs 38 pin board is smaller than it looks: both usually carry the same ESP32-WROOM-32 module, run the same code and are set up as "ESP32 Dev Module" in the Arduino IDE. The 38-pin board breaks out eight extra pins: GPIO 0, GPIO 6–11 (wired to the flash memory) and one more GND. Since the flash pins can't be used anyway, the real difference usually comes down to GPIO 0, the order of the pins on the board and how it sits on a breadboard.

ESP32 DevKit development board
ESP32 DevKit board: the WROOM module under the metal shield, a USB-to-serial chip, a 3.3 V regulator and the EN and BOOT buttons; depending on the headers along its edges it has 30 or 38 pins.

In this article we put the two pinouts side by side, explain why these boards don't fit a breadboard well and how to fix it, decode the WROOM and WROVER markings on the metal shield, show you how to tell whether your USB chip is a CP2102 or a CH340, and walk through the Arduino IDE settings step by step. At the end there's a test sketch that prints your board's chip model, flash size and PSRAM.

What's the difference between the ESP32 30-pin and 38-pin boards?

The ESP32-WROOM-32 module itself has 38 solder pads. The dev board maker decides which of them to route to the headers along the edges. Espressif's own ESP32-DevKitC and its clones offer 2×19 pins, one for every pad on the module. The DOIT ESP32 DevKit V1 and similar boards leave out the risky flash pins and GPIO 0 (the BOOT button pin) and make do with 2×15 = 30 pins. In other words, the 38-pin board isn't more powerful; it just breaks out more pads.

Feature30-pin board (DevKit V1)38-pin board (DevKitC and clones)
ModuleUsually ESP32-WROOM-32 / 32D / 32EESP32-WROOM-32 / 32E, some with WROVER
Header layout2 × 152 × 19
GPIOs broken out2532 (6 are flash pins)
GPIOs you can actually use2526
GPIO 0Not on a pin, only on the BOOT buttonAvailable as a pin
Flash pins (GPIO 6–11)NoYes (CLK, SD0–SD3, CMD), not usable
GND pins23
Power pinsVIN and 3V35V and 3V3
User LEDMost have a blue LED on GPIO 2None on Espressif's board, GPIO 2 on some clones
Arduino IDE boardESP32 Dev Module or DOIT ESP32 DEVKIT V1ESP32 Dev Module

The takeaway from the table is simple: you'll never use six of the extra pins on the 38-pin board in any project, so the only real gain is GPIO 0. That's why "more pins means a better board" doesn't hold for the ESP32. Your choice should depend not on the pin count but on your breadboard layout, the wiring diagrams you'll follow and the expansion board you plan to use.

Pinout: where is each pin on the two boards?

The table below shows the pin order from top to bottom with the antenna at the top, the USB port at the bottom and the components facing you. DevKit V1 boards label pins like "D23" or "TX2"; remember that in your code you write the GPIO number (23, 17), not the label. You can also see your board's full map in the Pinout tool.

Position30-pin left30-pin right38-pin left38-pin right
1END233V3GND
2VP (GPIO 36)D22ENGPIO 23
3VN (GPIO 39)TX0 (GPIO 1)SVP (GPIO 36)GPIO 22
4D34RX0 (GPIO 3)SVN (GPIO 39)TX (GPIO 1)
5D35D21GPIO 34RX (GPIO 3)
6D32D19GPIO 35GPIO 21
7D33D18GPIO 32GND
8D25D5GPIO 33GPIO 19
9D26TX2 (GPIO 17)GPIO 25GPIO 18
10D27RX2 (GPIO 16)GPIO 26GPIO 5
11D14D4GPIO 27GPIO 17
12D12D2GPIO 14GPIO 16
13D13D15GPIO 12GPIO 4
14GNDGNDGNDGPIO 0
15VIN3V3GPIO 13GPIO 2
16--SD2 (GPIO 9)GPIO 15
17--SD3 (GPIO 10)SD1 (GPIO 8)
18--CMD (GPIO 11)SD0 (GPIO 7)
19--5VCLK (GPIO 6)

The left sides are very similar, but the right sides aren't: the 30-pin board has GND and 3V3 in its bottom-right corner, while the 38-pin board has GPIO 0, 2, 15 and the flash pins in the same area. So if you build a diagram drawn for one board by copying "the same position" on the other, you'll wire to the wrong pins. The order can vary slightly on clones; always go by the labels printed on your board.

On the 38-pin board, the CLK, SD0, SD1, SD2, SD3 and CMD pins (GPIO 6–11) are connected to the flash memory inside the module. Hook up an LED, a button or a sensor to them and the board will crash at boot or reboot endlessly. On boards with a WROVER module, GPIO 16 and 17 are also reserved for the PSRAM, so don't use the TX2 and RX2 pins there.

The breadboard fit problem and how to solve it

A standard breadboard has five connected holes on each side of every row (a–e and f–j) with a channel in the middle. The ESP32 board straddles the channel and covers everything between its two headers. Boards with 22.86 mm (0.9 inch) between the pin rows leave one open hole on each side. Boards with 25.4 mm (1 inch) leave a single hole on one side only, and you can't plug a single wire into the pins on the other side. The width depends on the manufacturer; you'll find both widths among 30-pin and 38-pin boards, but the wide one is the most common. If you already have the board, measure the distance between the two rows of pins with a ruler; before buying, check the product dimensions.

  • Two breadboards side by side: Remove the power rail strip from the edge of one, join the two breadboards and put one row of the board's pins in each. You get five holes next to every pin; it's the easiest and cheapest fix.
  • Female-to-male jumper wires: Leave the board off the breadboard and connect directly to its pins with female-ended wires. It's quick for small tests, but the wires pop off easily.
  • Expansion board (breakout base): These bases with screw terminals, or with GND and 3V3 next to every pin, take the breadboard out of the picture entirely. They're made separately for 30-pin and 38-pin boards, so buy the one that matches your board's pin count and width.
  • Choose a narrow board: If you'll work on a breadboard a lot, choose a board with 22.86 mm between the pin rows. If the product page doesn't list that measurement, ask the seller.
If you can't remember how a breadboard is connected inside, take a look at How to Use a Breadboard first. Also remember that on long breadboards the power rails may be split in the middle; run the ESP32's 3V3 and GND to each half separately.

WROOM vs WROVER: what does the metal shield tell you?

The label on the metal-shielded module shows the model name. WROOM modules contain just the processor and flash memory. WROVER modules are a little longer and also include external RAM called PSRAM. Models with a "U" (such as WROOM-32U or WROVER-IE) have no PCB antenna; instead they have a tiny U.FL connector for an external antenna. The D or E at the end of the name shows the version of the chip inside.

ModuleChipFlashPSRAMNote
ESP32-WROOM-32ESP32-D0WDQ64 MBNoneThe first version; common on older, cheaper boards
ESP32-WROOM-32DESP32-D0WD4 MB (8 and 16 MB options exist)NoneThe most common model for years
ESP32-WROOM-32EESP32-D0WD-V34, 8 or 16 MBNoneNewer boards; V3 silicon fixes bugs in the earlier chip
ESP32-WROOM-32U / 32UESame as WROOM-32D / 32E4 MB and upNoneU.FL connector for an external antenna
ESP32-WROVER-E / IEESP32-D0WD-V34, 8 or 16 MB2 or 8 MBLonger module; GPIO 16 and 17 reserved for the PSRAM

For almost every project, like reading sensors, driving a relay, running a web server or sending Telegram alerts, a WROOM is all you need; the ESP32's 520 KB of internal RAM is plenty for that. PSRAM makes a difference for memory-hungry jobs such as camera images, graphical interfaces on large color displays or audio recording. To use the PSRAM on a WROVER board you have to turn on PSRAM: Enabled in the Arduino IDE; if it's disabled, the memory doesn't show up at all.

USB-to-serial chip: CP2102 or CH340?

The ESP32 doesn't speak USB by itself; the small chip right next to the USB port translates between it and your computer. Which chip your board has decides what name it shows up under on your computer and which driver it needs. If the marking on the chip is too small to read, look at its shape:

ChipWhat it looks likeName in WindowsUSB ID (VID:PID)Driver
CP2102 / CP2104 (Silicon Labs)Square, no legs (QFN)Silicon Labs CP210x USB to UART Bridge10C4:EA60Usually automatic; otherwise the CP210x VCP driver
CH340C / CH340G (WCH)Rectangular, legs on both sides (SOP-16)USB-SERIAL CH3401A86:7523Usually automatic; otherwise the CH341SER driver
CH9102F (WCH)Small square, no legs (QFN)USB-Enhanced-SERIAL CH91021A86:55D4CH343SER driver on older systems

On Windows, open Device Manager and look under Ports (COM & LPT); the entry that appears when you plug in the board tells you the chip. If it shows up as "Unknown device", right-click it, go to Properties > Details > Hardware Ids and compare the VID and PID with the table. Recent versions of macOS and Linux recognize most of these chips without extra drivers; the port appears as /dev/cu.usbserial-... on macOS and /dev/ttyUSB0 on Linux. On boards with a CH340G you'll see a small 12 MHz crystal next to the chip; the CH340C doesn't need one. For more on drivers and ports, see USB-to-TTL Converter.

Choosing the right board and settings in the Arduino IDE

  1. In the Boards Manager, search for esp32 and install the package by Espressif Systems. For a first-time setup, follow the steps in What Is the ESP32?.
  2. Under Tools > Board > esp32, choose ESP32 Dev Module. This option works with every 30-pin and 38-pin WROOM board.
  3. For the 30-pin board you can also choose DOIT ESP32 DEVKIT V1; the only difference is that it defines the LED_BUILTIN constant as GPIO 2.
  4. If your board has a WROVER, choose ESP32 Wrover Module, or set the PSRAM option to Enabled under ESP32 Dev Module.
  5. Pick your board's port under Tools > Port and upload. If the upload hangs at "Connecting...", hold down the BOOT button and release it once the upload starts.
Tools menu settingRecommended valueWhen to change it
Upload Speed921600115200 if uploads stop halfway
CPU Frequency240MHz (WiFi/BT)80 or 160 MHz if you need to save battery
Flash ModeQIODIO if a clone won't boot
Flash Size4MB (32Mb)The real size on 8 or 16 MB modules
Partition SchemeDefault 4MB with spiffsHuge APP (3MB No OTA) if your sketch doesn't fit
PSRAMDisabledEnabled on boards with a WROVER module

A sketch that identifies your board: model, flash and PSRAM

Instead of guessing which chip, how much flash and how much PSRAM your board has, you can ask the board itself. Upload this sketch and open the Serial Monitor at 115200 baud:

C++ (Arduino IDE)
1// Kartını tanı: yonga modeli, flaş, PSRAM ve MAC / Identify your board: chip model, flash, PSRAM and MAC
2void setup() {
3  Serial.begin(115200);
4  delay(1000);                                   // Seri Monitör'ün açılmasını bekle / wait for the Serial Monitor
5
6  Serial.printf("Yonga / Chip: %s, rev %d, %d cekirdek / cores\n",
7                ESP.getChipModel(), ESP.getChipRevision(), ESP.getChipCores());
8  Serial.printf("CPU: %lu MHz\n", (unsigned long)ESP.getCpuFreqMHz());
9  Serial.printf("Flas / Flash: %lu MB\n", (unsigned long)(ESP.getFlashChipSize() / (1024 * 1024)));
10  Serial.printf("PSRAM: %lu KB\n", (unsigned long)(ESP.getPsramSize() / 1024));   // WROOM: 0, WROVER: > 0 (PSRAM: Enabled)
11
12  uint64_t mac = ESP.getEfuseMac();              // fabrikada yazılan MAC / factory MAC
13  Serial.print("MAC: ");
14  for (int i = 0; i < 6; i++) {
15    Serial.printf("%02X", (unsigned int)((mac >> (8 * i)) & 0xFF));
16    if (i < 5) Serial.print(':');
17  }
18  Serial.println();
19}
20
21void loop() {
22}

If the output says ESP32-D0WDQ6, the module is most likely the original WROOM-32; ESP32-D0WD usually points to a WROOM-32D, and ESP32-D0WD-V3 (rev 3) to a WROOM-32E or WROVER-E. If the PSRAM line is greater than zero, your board is a WROVER, but that value only appears with the PSRAM option enabled. If the flash is larger than 4 MB, you can set Flash Size to the real value and make room for bigger programs. The MAC address helps you find your board in your router's list of connected devices.

Built-in LED and pin test

Most 30-pin DevKit V1 boards have a blue LED on GPIO 2, separate from the red power LED that stays on while the board is powered. Espressif's 38-pin DevKitC has no user LED, while some clones put one on GPIO 2 as well. The sketch below sets the safe output pins found on both boards HIGH one at a time for a second and prints which one is active to the Serial Monitor. Connect an LED to GND through a 220 Ω resistor and touch its other leg to the pins to check that the labels on your board are right.

C++ (Arduino IDE)
1// 30 ve 38 pinli kartta ortak, güvenli çıkış pinleri / safe output pins found on both 30- and 38-pin boards
2const int LED_PIN = 2;   // DevKit V1 mavi LED; "ESP32 Dev Module" seçiliyken LED_BUILTIN tanımlı değildir
3                         // DevKit V1 blue LED; LED_BUILTIN is not defined when "ESP32 Dev Module" is selected
4const int pins[] = {4, 5, 13, 14, 16, 17, 18, 19, 21, 22, 23, 25, 26, 27, 32, 33};   // WROVER'da 16 ve 17'yi sil / remove 16 and 17 on WROVER
5const int count = sizeof(pins) / sizeof(pins[0]);
6
7void setup() {
8  Serial.begin(115200);
9  pinMode(LED_PIN, OUTPUT);
10  for (int i = 0; i < count; i++) pinMode(pins[i], OUTPUT);
11}
12
13void loop() {
14  for (int i = 0; i < count; i++) {
15    Serial.printf("GPIO %d -> HIGH\n", pins[i]);  // LED + 220 Ω ile bu pini yokla / probe this pin with an LED + 220 Ω
16    digitalWrite(LED_PIN, HIGH);                  // dahili LED test sırasında yanar / onboard LED lights during the test
17    digitalWrite(pins[i], HIGH);
18    delay(1000);
19    digitalWrite(pins[i], LOW);
20    digitalWrite(LED_PIN, LOW);
21    delay(200);
22  }
23}

Which pins are safe? Same rules on both boards

PinStatusWhy?
GPIO 6–11Don't useWired to the flash; only broken out on the 38-pin board
GPIO 0Use with careConnected to the BOOT button; if it's LOW at boot, the board enters upload mode
GPIO 2Use with careMust be LOW or floating during upload; drives the built-in LED on the DevKit V1
GPIO 12Use with careIf it's HIGH at boot, 1.8 V is selected for the flash and the board won't start
GPIO 15Use with careIf it's LOW at boot, the boot messages are silenced
GPIO 1 and 3Use with careTX0 and RX0 of the USB serial connection
GPIO 34, 35, 36, 39Input onlyCan't be outputs and have no internal pull-up
GPIO 16 and 17Don't use on WROVERWired to the PSRAM on WROVER; available on WROOM (TX2 and RX2)
GPIO 4, 5, 13, 14, 18, 19, 21–23, 25–27, 32, 33SafeGeneral-purpose input and output
All of the ESP32's GPIO pins run at 3.3 V and are not 5 V tolerant. Don't connect a sensor with a 5 V output (such as the ECHO pin of the HC-SR04) directly; put a voltage divider in between. And never feed 5 V into the 3V3 pin: it's the regulator's output and goes straight to the chip.

Power pins: VIN, 5V and 3V3

The VIN pin on the 30-pin board and the 5V pin on the 38-pin board do the same job: they're tied to the USB 5 V line and feed the board's 3.3 V regulator (usually an AMS1117). To run the board without USB, you supply 5 V through this pin; the regulator needs at least about 4.5 V and gets very hot at higher voltages, so 5–6 V is the safest range. The 3V3 pin is the regulator's output, and you can power your sensors from it. Because the ESP32 draws peaks of up to 250 mA when Wi-Fi switches on, don't draw more than a few hundred mA from 3V3. Powering VIN while the USB cable is plugged in can also tie two supplies together; pick one.

If you use MicroPython

The 30-pin and 38-pin boards run the same MicroPython firmware: just flash Espressif's generic ESP32 build, or the PSRAM-enabled (SPIRAM) build for WROVER boards. In the Thonny shell, these few lines show the flash size and CPU speed, and turn on the DevKit V1's LED:

MicroPython
1import esp, machine
2
3print("Flas / Flash:", esp.flash_size() // (1024 * 1024), "MB")
4print("CPU:", machine.freq() // 1000000, "MHz")
5
6led = machine.Pin(2, machine.Pin.OUT)    # DevKit V1 dahili LED / onboard LED
7led.on()

Which one should you buy? A quick decision guide

  • For breadboard practice or teaching: get a 30-pin DevKit V1, ideally a narrow one with 22.86 mm between the pin rows; its built-in LED is handy for first tests too.
  • If the diagram or book you're following uses a specific board: buy that same board; since the pin positions differ, you won't have to translate them.
  • If you need GPIO 0 or your expansion board is a 38-pin one: choose the 38-pin board.
  • For camera, large display or audio projects: consider a board with a WROVER module, or go straight for an ESP32-CAM.
  • If you don't want driver headaches: pick a newer board with a CP2102 or CH340C and a USB-C port.
  • ESP32-S3, C3 or C6 boards: these are different chips; their pin numbers and layouts aren't compatible with the boards in this article.

Common mistakes and how to fix them

  • "LED_BUILTIN was not declared" error: this constant isn't defined when ESP32 Dev Module is selected. Write 2 instead of LED_BUILTIN, or choose DOIT ESP32 DEVKIT V1 as your board.
  • I wired it to the pin in the diagram and it doesn't work: the diagram may have been drawn for the other layout. Wire by the printed label and GPIO number, not by position.
  • The board won't boot or keeps rebooting: something may be connected to GPIO 6–11, or GPIO 12 is pulled HIGH at boot. Remove whatever is on those pins and try again.
  • The port doesn't show up: the cable may be charge-only, or the USB chip's driver is missing. Use a data cable and compare the name in Device Manager with the table.
  • "Failed to connect" error: hold BOOT as the upload starts; if it keeps happening, lower Upload Speed to 115200. More fixes are in ESP32 Failed to Connect.
  • PSRAM shows 0 on a WROVER board: the PSRAM option was left Disabled in the Tools menu; set it to Enabled and upload again.

In short, 30-pin and 38-pin ESP32 boards share the same brain; what sets them apart is where the pins are, GPIO 0 and how the board fits on your workbench. Once you've read your board's labels and confirmed them with the test sketch, you'll find the right pins whatever diagram you follow. For your first experiments, check out the ESP32 projects in the BlueGrays app for the built-in LED, an external LED, button-controlled LEDs, a traffic light, light measurement with an LDR, an I2C LCD and a Wi-Fi connection; each one walks you through the wiring diagram and the code step by step.

Frequently asked questions

Should I buy the 30-pin or the 38-pin ESP32?

If you'll be working on a breadboard and don't have a special need, the 30-pin DevKit V1 is usually more convenient and most have a built-in LED. Choose the 38-pin board if you want to use GPIO 0, have a 38-pin expansion board, or the diagram you're following was drawn for it. The processor and the code are the same on both.

Do I need to change my code for a 30-pin ESP32?

No. As long as the code uses GPIO numbers, it runs the same way on 30-pin and 38-pin boards. Just check that code written for a 38-pin board doesn't use GPIO 0 or the flash pins, because those pins aren't broken out on the 30-pin board.

What pin is the built-in LED on the ESP32 DevKit V1?

On DevKit V1 boards the blue user LED is on GPIO 2. With ESP32 Dev Module selected in the Arduino IDE, LED_BUILTIN isn't defined, so write 2 directly in your code or choose the DOIT ESP32 DEVKIT V1 board. The red LED is just a power indicator and can't be controlled.

Which board do I select in the Arduino IDE for a 38-pin ESP32?

For every board with a WROOM module, whether 30 or 38 pins, ESP32 Dev Module is all you need. If your 38-pin board has a WROVER module, select ESP32 Wrover Module or enable the PSRAM option under ESP32 Dev Module.

What is the difference between ESP32 WROOM and WROVER?

Both contain the same ESP32 chip. The WROVER adds 2 to 8 MB of PSRAM and is slightly longer, but GPIO 16 and 17 are reserved for that memory in exchange. Unless you're working on camera, large display or audio projects, a WROOM is enough.

How do I know if my ESP32 has a CP2102 or a CH340?

Look at the small chip next to the USB port: a square one with no legs is usually a CP2102, while a rectangular one with legs on both sides is a CH340. In Windows Device Manager the board shows up as "Silicon Labs CP210x" or "USB-SERIAL CH340"; in the hardware ID, 10C4 means Silicon Labs and 1A86 means WCH.

See all projects
ESP32 Built-in LED Blink
ES-4Beginner

ESP32 Built-in LED Blink

Blinking the built-in blue LED on the ESP32 DevKit V1. No external components required! The first project you should try when you buy an ESP32. GPIO 2 is connected to the built-in LED.

4.8(29)
54
LED Blink with ESP32
ES-1Beginner

LED Blink with ESP32

Teaches basic GPIO output usage with ESP32. We achieve a blinking effect by turning an LED on and off from a digital pin. ESP32 version of the classic blink project on Arduino UNO; the basic blink commands in the Arduino environment are the same, but the ESP32's pin layout and 3.3 V GPIO levels differ from those of the Arduino UNO.

4.7(37)
108
ESP32 LED Control with Push Button (Push)
ES-2Beginner

ESP32 LED Control with Push Button (Push)

The LED lights up when the button is pressed and turns off when released. Shows how the ESP32's digital input pin and internal pull-up resistor are used. The INPUT_PULLUP mode eliminates the need for an external resistor.

4.6(36)
57
ESP32 LED Control with Pushbutton (Toggle)
ES-3Beginner

ESP32 LED Control with Pushbutton (Toggle)

Each time the button is pressed the state of the LED changes: if it is on it turns off, if it is off it turns on. Classic toggle pattern. With debounce we clean up the mechanical noise of the pushbutton to ensure a single toggle with a single press.

4.6(39)
59
ESP32 Traffic Light
ES-5Beginner

ESP32 Traffic Light

Real traffic light simulation with 3 LEDs red-yellow-green. Timings close to real traffic logic: red long, yellow short, green long. Classic example of sequential GPIO control.

4.4(22)
45
Reading Light Intensity with the ESP32 LDR Module
ES-11Beginner

Reading Light Intensity with the ESP32 LDR Module

Real-time monitoring of the LDR module's raw ADC value and relative light percentage calculated from dark and light reference values in the Serial Monitor. This percentage is not a lux measurement. Teaches the module’s calibration logic. It is ideal to complete this before Project 10, as it is used to determine the threshold value.

4.6(36)
55
ESP32 I2C LCD Display (16x2)
ES-17Intermediate
Premium

ESP32 I2C LCD Display (16x2)

In this project we connect a 16x2 character LCD to the ESP32 over I2C and display text. With I2C, just 2 data pins (SDA and SCL) control the screen, instead of the 6+ pins a classic parallel connection wastes. The code prints a fixed message on the first line and a counter that goes up every second on the second. At startup an I2C scanner also prints the display's address to the Serial Monitor (usually 0x27 or 0x3F).

4.9(23)
40
ESP32 Wi-Fi STA Connection (with LCD Screen)
ES-25Advanced

ESP32 Wi-Fi STA Connection (with LCD Screen)

In this project, we connect the ESP32 to the home Wi-Fi network in Station (STA) mode in a secure, fault-tolerant manner. We store the SSID and password in a separate secrets.h file to prevent leaking to Git, set up an auto-reconnect mechanism, and display the RSSI signal level and IP address on an I2C LCD screen. The internal LED works as a status indicator. It is a production-grade connection manager.

4.4(21)
38