
ESP32 Strapping Pins: Complete List for All Chip Variants
ESP32 strapping pins explained for every chip variant: ESP32, S2, S3, C3, C6, H2. Complete GPIO boot mode table, safe pin selection guide, pins to avoid, and configuration tips.
Strapping pins are fundamental to all ESP32 microcontrollers, including the original ESP32, ESP32-S2, ESP32-S3, ESP32-C3, ESP32-C6 and ESP32-H2. Today we are going to explore the strapping pins common features and functions across different ESP32 versions.
| Chip | Strapping pins | Download mode trigger | What they set |
|---|---|---|---|
| ESP32 | GPIO0, GPIO2, GPIO5, GPIO12 (MTDI), GPIO15 (MTDO) | GPIO0 LOW + GPIO2 LOW | Boot mode, flash voltage, ROM log, SDIO timing |
| ESP32-S2 | GPIO0, GPIO45, GPIO46 | GPIO0 LOW + GPIO46 LOW | Boot mode, flash voltage, ROM log |
| ESP32-S3 | GPIO0, GPIO3, GPIO45, GPIO46 | GPIO0 LOW + GPIO46 LOW | Boot mode, flash voltage, ROM log, JTAG source |
| ESP32-C3 | GPIO2, GPIO8, GPIO9 | GPIO9 LOW + GPIO8 HIGH | Boot mode, ROM log |
| ESP32-C6 | GPIO4 (MTMS), GPIO5 (MTDI), GPIO8, GPIO9, GPIO15 | GPIO9 LOW + GPIO8 HIGH | Boot mode, ROM log, SDIO timing, JTAG source |
| ESP32-H2 | GPIO8, GPIO9, GPIO25 | GPIO9 LOW + GPIO8 HIGH | Boot mode, ROM log, JTAG source |
GPIO2 on the ESP32 and GPIO46 on the S2 and S3 already sit LOW by default (internal pull-down), so on most boards holding GPIO0 or GPIO9 LOW through a reset is all it takes.
Want this offline? View the full cheatsheet (PNG)
Main Uses of Strapping Pins #
The strapping pins on ESP32 microcontrollers control these four key functions:
Understanding Strapping Pins
Strapping pins (also called bootstrap pins) are specialized GPIO pins that the ESP32 reads during boot to determine hardware configuration. During power-on or reset, the chip samples these pins and latches the values to configure:
- Boot source - Flash memory, or a download mode over UART, USB or SDIO
- Flash voltage - 3.3V or 1.8V for SPI communication (ESP32, S2 and S3 only)
- Debug routing - USB-JTAG or pad-based JTAG (S3, C6 and H2)
- ROM messages - Enable or disable boot log output
The sampling happens only once during reset: Espressif's datasheets give a hold time of at least 1 ms (ESP32) or 3 ms (the newer chips) after the chip is enabled. After that, these pins become regular GPIOs - but external components (resistors, LEDs, sensors) remain connected, so circuit design must ensure correct boot states.
Automatic Boot Mode on Modern Boards #
Most ESP32 development boards manufactured since 2018 include automatic boot mode switching using DTR/RTS signals from the USB-to-serial chip, eliminating the need to manually press BOOT and RESET buttons.
How it works: When uploading firmware, the programming software (Arduino IDE, PlatformIO, esptool) automatically:
- Controls the boot pin and RESET through transistors
- Pulls the boot pin LOW while resetting to enter download mode
- Uploads firmware via UART
- Releases the boot pin and resets again to run your program
Automatic Boot Mode
- ESP32-DevKitC V4 (Espressif official)
- NodeMCU-32S, WROOM-32 dev boards
- Boards with CP2102, CH340G, FT232 chips
- ESP32-S2/S3/C3 with native USB
Manual Buttons Required
- Bare ESP32 modules without dev board PCB
- Custom PCBs without auto-reset circuit
- Budget boards with simplified USB
- Basic USB-to-TTL adapters (no DTR/RTS)
Why strapping pins matter:
- Boot failures - Incorrect pin states are the #1 cause of "won't boot" errors. External components on wrong pins prevent startup. You can probe the pin voltage with a multimeter to confirm its state at boot.
- Firmware uploads - The boot pin must be LOW at reset to flash new code. Circuits holding it HIGH block uploads.
- Circuit design - Use series resistors (1k-10k ohm) when connecting peripherals to strapping pins to avoid boot interference.
- Pin planning - Prioritize non-strapping pins for critical hardware. Save strapping pins for non-essential features.
Which GPIO Pins Are Strapping Pins? Complete List by ESP32 Version #
Here's the complete list of strapping pins for each ESP32 version, with the level each one sits at when nothing is connected and the boot mode table from Espressif's datasheet:
ESP32 (Original) Strapping Pins5 pins
| Pin | Default | What it sets |
|---|---|---|
| GPIO0 | Pull-up (HIGH) | Boot mode |
| GPIO2 | Pull-down (LOW) | Boot mode: must be LOW or floating to enter download mode |
| GPIO5 | Pull-up (HIGH) | SDIO slave timing, together with MTDO |
| GPIO12 (MTDI) | Pull-down (LOW) | Flash voltage (VDD_SDIO): LOW = 3.3 V, HIGH = 1.8 V |
| GPIO15 (MTDO) | Pull-up (HIGH) | ROM log on U0TXD: LOW silences it; also SDIO slave timing |
| Boot mode | GPIO0 | GPIO2 |
|---|---|---|
| SPI flash boot (normal) | HIGH | Any |
| Download boot (UART, SDIO) | LOW | LOW |
The original ESP32 has no JTAG strapping pin: JTAG can only be turned off for good with the EFUSE_DISABLE_JTAG eFuse.
ESP32-S2 Strapping Pins3 pins
| Pin | Default | What it sets |
|---|---|---|
| GPIO0 | Weak pull-up (HIGH) | Boot mode |
| GPIO45 | Weak pull-down (LOW) | Flash voltage (VDD_SPI): LOW = 3.3 V, HIGH = 1.8 V |
| GPIO46 | Weak pull-down (LOW) | Boot mode, ROM log |
| Boot mode | GPIO0 | GPIO46 |
|---|---|---|
| SPI flash boot (normal) | HIGH | Any |
| Download boot (USB-OTG, UART, SPI) | LOW | LOW |
ESP32-S3 Strapping Pins4 pins
| Pin | Default | What it sets |
|---|---|---|
| GPIO0 | Weak pull-up (HIGH) | Boot mode |
| GPIO3 | Floating (no internal pull) | JTAG signal source, only once an eFuse enables it |
| GPIO45 | Weak pull-down (LOW) | Flash voltage (VDD_SPI): LOW = 3.3 V, HIGH = 1.8 V |
| GPIO46 | Weak pull-down (LOW) | Boot mode, ROM log |
| Boot mode | GPIO0 | GPIO46 |
|---|---|---|
| SPI flash boot (normal) | HIGH | Any |
| Download boot (USB-Serial-JTAG, USB-OTG, UART) | LOW | LOW |
ESP32-C3 Strapping Pins3 pins
| Pin | Default | What it sets |
|---|---|---|
| GPIO2 | Floating | Not the boot mode itself, but Espressif recommends pulling it HIGH against glitches |
| GPIO8 | Floating | Must be HIGH to enter download mode; also the ROM log |
| GPIO9 | Weak pull-up (HIGH) | Boot mode |
| Boot mode | GPIO2 | GPIO8 | GPIO9 |
|---|---|---|---|
| SPI flash boot (normal) | Any | Any | HIGH |
| Download boot (USB-Serial-JTAG, UART) | HIGH | HIGH | LOW |
ESP32-C6 Strapping Pins5 pins
| Pin | Default | What it sets |
|---|---|---|
| GPIO4 (MTMS) | Floating | SDIO slave sampling and driving clock edge, with MTDI |
| GPIO5 (MTDI) | Floating | SDIO slave sampling and driving clock edge, with MTMS |
| GPIO8 | Floating | Must be HIGH to enter download mode; also the ROM log |
| GPIO9 | Weak pull-up (HIGH) | Boot mode |
| GPIO15 | Floating (no internal pull) | JTAG signal source, only once an eFuse enables it |
| Boot mode | GPIO8 | GPIO9 |
|---|---|---|
| SPI flash boot (normal) | Any | HIGH |
| Download boot (USB-Serial-JTAG, UART, SDIO) | HIGH | LOW |
| Invalid - avoid | LOW | LOW |
ESP32-H2 Strapping Pins3 pins
| Pin | Default | What it sets |
|---|---|---|
| GPIO8 | Floating | Must be HIGH to enter download mode; also the ROM log |
| GPIO9 | Weak pull-up (HIGH) | Boot mode |
| GPIO25 | Floating (no internal pull) | JTAG signal source, only once an eFuse enables it |
| Boot mode | GPIO8 | GPIO9 |
|---|---|---|
| SPI flash boot (normal) | Any | HIGH |
| Download boot (USB-Serial-JTAG, UART) | HIGH | LOW |
Key Observations #
- The boot pin moved: GPIO0 selects the boot mode on the ESP32, S2 and S3; GPIO9 does on the C3, C6 and H2, where download mode also needs GPIO8 HIGH.
- Only the ESP32, S2 and S3 have a flash voltage strap (GPIO12 on the ESP32, GPIO45 on the S2 and S3). The C3, C6 and H2 have none.
- The JTAG source strap exists only on the S3 (GPIO3), C6 (GPIO15) and H2 (GPIO25), and the chip ignores it until an eFuse is burnt.
- The newer chips float by default: on the C3, C6 and H2 every strapping pin except GPIO9 has no internal pull, so give the ones that matter a defined level.
Common Strapping Features Across ESP32 Versions #
Strapping pins control four main hardware configurations across ESP32 variants. Here's a detailed look at each function:
Boot Mode Selection #
Determines whether the ESP32 boots into normal operation mode (to run your program) or download mode (to receive new firmware via USB/UART).
Why it's important: This is the most critical strapping pin function. Without proper boot mode control, you cannot upload firmware to your ESP32. Every time you flash new code, the chip must enter download mode first, then reset to normal mode to run the code.
| Chips | Normal boot | Download mode |
|---|---|---|
| ESP32 | GPIO0 HIGH (default) | GPIO0 LOW, GPIO2 LOW (default) |
| ESP32-S2, ESP32-S3 | GPIO0 HIGH (default) | GPIO0 LOW, GPIO46 LOW (default) |
| ESP32-C3, ESP32-C6, ESP32-H2 | GPIO9 HIGH (default) | GPIO9 LOW, GPIO8 HIGH |
Most dev boards put their "BOOT" button on the boot pin: GPIO0 on ESP32, S2 and S3 boards, GPIO9 on C3, C6 and H2 boards.
Flash Voltage Selection (VDD_SDIO / VDD_SPI)
Configures the operating voltage (1.8V or 3.3V) for the SPI flash memory chip that stores your program code and data. Some ESP32 modules support both voltage levels.
Why it's important: The voltage must match your flash chip. If the strap selects 1.8 V on a module with 3.3 V flash, the flash is underpowered and the chip fails to boot; selecting 3.3 V for 1.8 V flash runs it outside its rating. Most ESP32 modules use 3.3V flash.
| Chip | Strapping pin | Default | 1.8 V when |
|---|---|---|---|
| ESP32 | GPIO12 (MTDI), sets VDD_SDIO | Pull-down: 3.3 V | GPIO12 is HIGH at reset |
| ESP32-S2, ESP32-S3 | GPIO45, sets VDD_SPI | Pull-down: 3.3 V | GPIO45 is HIGH at reset |
An eFuse can override the pin for good: EFUSE_SDIO_FORCE with EFUSE_SDIO_TIEH on the ESP32, EFUSE_VDD_SPI_FORCE with EFUSE_VDD_SPI_TIEH on the S2 and S3. Once it is burnt, the pin's level at reset no longer matters. The C3, C6 and H2 have no flash voltage strapping pin.
On the original ESP32, MTDO (GPIO15) and GPIO5 also set the SDIO slave timing (which clock edge it samples and drives on), and the C6 does the same with MTMS (GPIO4) and MTDI (GPIO5). That only matters if the chip is an SDIO slave to a host processor.
JTAG Signal Source Control #
Determines whether JTAG debugging signals come from USB (built-in USB Serial/JTAG controller) or external debug pins (traditional JTAG pads). JTAG allows real-time debugging, breakpoints, and memory inspection.
Why it's important: Proper JTAG configuration is essential for advanced debugging with tools like OpenOCD or ESP-IDF's debugging features. It determines whether you debug via USB cable or external JTAG hardware (like J-Link or FT2232H).
Out of the box the S3, C6 and H2 use the USB Serial/JTAG controller and ignore their JTAG strapping pin. The pin only takes over after you burn the JTAG select eFuse (EFUSE_STRAP_JTAG_SEL on the S3, EFUSE_JTAG_SEL_ENABLE on the C6 and H2):
| Chip | Strapping pin | Pin HIGH | Pin LOW |
|---|---|---|---|
| ESP32-S3 | GPIO3 | USB Serial/JTAG controller | JTAG pins |
| ESP32-C6 | GPIO15 | USB Serial/JTAG controller | JTAG pins |
| ESP32-H2 | GPIO25 | USB Serial/JTAG controller | JTAG pins |
These pins have no internal pull resistor, so once the eFuse is burnt your circuit has to drive the level: a floating pin is not allowed. The ESP32, S2 and C3 have no JTAG strapping pin at all.
Note: The EFUSE_DIS_PAD_JTAG and EFUSE_DIS_USB_JTAG eFuses can permanently disable either JTAG source for security, and then the strapping pin is ignored.
JTAG Pin Name Aliases (MTDI, MTDO, MTCK, MTMS)
ESP32 datasheets and pinout diagrams use legacy JTAG signal names alongside GPIO numbers. These aliases appear frequently in IDE warnings and community discussions, and they sit on different GPIOs on each chip:
| Alias | JTAG signal | ESP32 | ESP32-S2, S3 | ESP32-C3, C6 | ESP32-H2 |
|---|---|---|---|---|---|
| MTDI | TDI (Test Data In) | GPIO12 | GPIO41 | GPIO5 | GPIO5 |
| MTDO | TDO (Test Data Out) | GPIO15 | GPIO40 | GPIO7 | GPIO3 |
| MTCK | TCK (Test Clock) | GPIO13 | GPIO39 | GPIO6 | GPIO4 |
| MTMS | TMS (Test Mode Select) | GPIO14 | GPIO42 | GPIO4 | GPIO2 |
Three of them are also strapping pins: MTDI and MTDO on the original ESP32 (flash voltage, and ROM log plus SDIO timing), and MTMS and MTDI on the C6 (SDIO timing).
ROM Boot Messages
Controls whether the ESP32's ROM bootloader prints diagnostic messages during the boot process. These messages show boot mode, flash configuration, and any boot errors.
Why it's important: ROM messages are extremely useful for debugging boot failures, but you may want to disable them in production devices to reduce power consumption, boot time, or prevent information leakage.
| Chip | Strapping pin | How it works |
|---|---|---|
| ESP32 | GPIO15 (MTDO) | HIGH (default) prints the log on U0TXD, LOW silences it |
| ESP32-S2, ESP32-S3 | GPIO46 | Ignored until EFUSE_UART_PRINT_CONTROL is burnt; the eFuse value then picks which level silences the log |
| ESP32-C3, ESP32-C6, ESP32-H2 | GPIO8 | Same scheme as the S2 and S3, with GPIO8 |
When enabled:
- See detailed boot sequence messages
- Flash size, speed, and mode information
- Error messages if boot fails
- Helps diagnose hardware or flash configuration problems
When disabled:
- Cleaner serial output (only your application's messages)
- Slightly faster boot time
- Prevents exposing internal boot information
- Preferred for production/commercial devices
Output destinations: The original ESP32 prints to UART0. The S2 prints to UART0 or UART1 (set by an eFuse). The S3, C3, C6 and H2 print to UART0 and the USB Serial/JTAG controller by default, and each can be turned off with eFuses.
Using Strapping Pins as Regular GPIO #
While strapping pins primarily serve as configuration parameters during the boot process, this doesn't mean the pins must be left alone after the initial configuration.
Once the ESP32 microcontroller has successfully initialized, these pins transform into regular GPIO (General Purpose Input/Output) pins, available for user-defined functions. However, you must be careful when manipulating these pins during and immediately after the boot phase.
Can you use strapping pins as regular GPIOs? Yes, but with important caveats:
Safe After Boot
- Read input from sensors
- Control LEDs or outputs
- Use for communication protocols (I2C, SPI)
- Any normal GPIO function
Watch Out For
- External pull-ups/downs affecting boot state
- Components that hold pins LOW/HIGH at boot
- Reset scenarios that re-check strapping pins
- Brownout conditions triggering re-boot
Design considerations:
- Use series resistors (1k-10k ohm) when connecting peripherals to strapping pins. This allows the internal pull-ups/downs to dominate during boot.
- Avoid strong pull-ups/downs that could override the ESP32's boot configuration.
- Test your design through multiple power cycles and resets to ensure consistent booting.
- Prioritize non-strapping pins for critical functions when possible.
Can I Use GPIO0, GPIO2, or GPIO12 as Output After Boot?
Yes - all strapping pins become fully general-purpose GPIOs once the chip has latched them, a few milliseconds after reset. Here's the practical guidance for the three pins people ask about most on the original ESP32:
| Pin | After boot | What to watch at reset |
|---|---|---|
| GPIO0 | Safe for input and output | Must not be held LOW at reset, or the chip enters download mode. Most boards already pull it HIGH and put the BOOT button on it; use a 1k-10k ohm series resistor for a button or LED. |
| GPIO2 | Safe for output (often the on-board LED) | Doesn't matter for a normal boot, but must be LOW or floating to enter download mode. A pull-up, or a circuit that drives it HIGH at reset, is what breaks flashing. |
| GPIO12 (MTDI) | Use with caution | The most dangerous strapping pin: HIGH at reset selects 1.8 V flash, and a module with 3.3 V flash then fails to boot. Keep it floating or LOW, or burn the flash voltage eFuse with espefuse set-flash-voltage 3.3V so its level no longer matters. |
ESPHome Strapping Pin Warnings
ESPHome checks your pins when it validates a config and prints this for any strapping pin of your chip:
WARNING GPIO2 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq/#why-am-i-getting-a-warning-about-strapping-pinsThe warning is informational - it does not mean the pin doesn't work. It fires for the same pins this guide lists (GPIO0, 2, 5, 12 and 15 on the original ESP32). The Arduino core and plain ESP-IDF print no such warning, so on those you have to know the pins yourself.
Once you have checked the circuit on that pin, silence the warning per pin with ignore_strapping_warning:
binary_sensor:
- platform: gpio
pin:
number: GPIO5
ignore_strapping_warning: true
name: "Door"- For GPIO5: safe to use after boot - suppress the warning if it's distracting
- For GPIO12: verify your module uses 3.3 V flash before driving it HIGH at reset
- For GPIO0: ensure nothing holds it LOW during power-on
ESP32 GPIO Pins to Avoid: Safe Pin Selection Guide
To revise once more, let's take a look at the strapping pins on different ESP32 versions. Strapping pins are used to set configurations such as ESP32 programming mode or specific boot behaviors.
It's important to identify ESP32 reserved pins and avoid using them as GPIO pins, as they are required during boot-up and certain operational modes. The table below provides an overview of ESP32 programming pins and ESP32 pins to avoid.
| ESP32 version | Strapping pins to avoid |
|---|---|
| ESP32 | GPIO0, GPIO2, GPIO5, GPIO12 (MTDI), GPIO15 (MTDO) |
| ESP32-S2 | GPIO0, GPIO45, GPIO46 |
| ESP32-S3 | GPIO0, GPIO3, GPIO45, GPIO46 |
| ESP32-C3 | GPIO2, GPIO8, GPIO9 |
| ESP32-C6 | GPIO4 (MTMS), GPIO5 (MTDI), GPIO8, GPIO9, GPIO15 |
| ESP32-H2 | GPIO8, GPIO9, GPIO25 |
ESP32 Strapping Pins CheatsheetPNG
ESP8266 Strapping Pins #
While this guide focuses on the ESP32 family, the ESP8266 uses a similar strapping pin concept at boot. If you're working with an ESP8266 (e.g., NodeMCU, Wemos D1 Mini), here are its three boot-critical pins:
| Pin | Required state at boot | Effect |
|---|---|---|
| GPIO0 | HIGH = normal boot, LOW = download mode | Primary boot mode control - same role as on ESP32 |
| GPIO2 | HIGH (internal pull-up) | Must be HIGH at boot - LOW causes boot failure. Don't tie it straight to VCC: the bootloader drives it as an output. Also TXD1 (second UART TX). |
| GPIO15 | LOW (external pull-down on most modules) | Must be LOW at boot - HIGH causes boot failure. Also SPI CS / HSPI CS0. |
Additional Resources #
The boot configuration chapter (Section 3) of each datasheet is the source for every table above.
Frequently asked questions
19 questionsWhat are strapping pins?
What are the ESP32 strapping pins?
What are the ESP32-S3 strapping pins?
What are the ESP32-C3 strapping pins?
What are the ESP32-C6 strapping pins?
Which ESP32 pin controls boot mode?
How do I put ESP32 in download mode?
What is GPIO0 used for in ESP32?
What pins should I avoid on ESP32?
What does 'wrong boot mode detected (0x13)' mean?
Can I use strapping pins as regular GPIO?
What is the difference between ESP32 and ESP32-S3 strapping pins?
What is ESP32 boot mode?
What does GPIO0 mean on ESP32?
What is strapping pin meaning?
Which ESP32 pins to avoid?
What are ESP32 flash pins?
What are ESP8266 strapping pins?
What does the 'GPIO is a strapping PIN' warning in ESPHome mean?
Conclusion #
In conclusion, strapping pins play an important role in the initialization and configuration of various ESP32 microcontroller versions, including ESP32-S2, ESP32-S3, ESP32-C3, ESP32-C6 and ESP32-H2. These pins serve as gatekeepers, influencing critical parameters during startup or reset, such as boot mode, voltage selection, JTAG signal source, and more.
Across different ESP32 versions, certain common strapping pins persist, each with its unique functions and default configurations. GPIO0, for instance, is the most commonly used strapping pin, which is used to select the boot mode on the ESP32, S2 and S3; on the C3, C6 and H2 that job moved to GPIO9.


