Blog
ESP32 Button: Wiring, Debounce, Hold
Buttons are the first input most ESP32 projects get and the second-biggest source of “why doesn’t this work” posts — usually the wiring is fine and the debounce is missing. Wiring, the BOOT button, and how to read presses without glitches.
How to Connect a Button to ESP32?
One leg to a GPIO, one to GND, internal pull-up in code: pinMode(4, INPUT_PULLUP). That’s the whole circuit — no resistor, no 3.3V wire; the pull-up keeps the pin high until the button shorts it low. How to connect a button to esp32 this way is the standard answer, and it has worked on every variant I’ve used, DevKit V1 to C3 Super Mini.
How to Connect Button to ESP32?
Same circuit, second phrasing: GPIO to one leg, GND to the other, INPUT_PULLUP in code. Long press, short press, double click — none changes the wiring, only the firmware. If the pin reads randomly when untouched, the pull-up isn’t enabled — the #1 mistake in the wild. Wiring examples show the same layout across boards.
How to Connect Push Button to ESP32?
For a momentary push button, leg orientation matters: the four pins connect in pairs, so use opposite legs — typically pins 1 and 4 — or it never closes the circuit. Wire GPIO and GND on those two. LED push buttons need their own series resistor.
Where Is the Boot Button on ESP32?
On a dev kit, look next to the USB connector: a small button labeled BOOT, IO0, or just “0” — some boards print FLASH. DevKit V1 and WROOM DevKits keep both buttons in the same corner.
What Pin Is the Boot Button Attached to for ESP32?
GPIO0, always. The BOOT button shorts GPIO0 to GND, and because GPIO0 is a strapping pin the chip samples it at reset to choose between normal boot and download mode. That dual role is why holding BOOT during a reset enables uploads. What pin is the boot button attached to for esp32 is one of the few facts identical across variants.
How to Check for Button Press on ESP32?
Read the pin and watch for a change: digitalRead() in loop(), or attachInterrupt() with a flag. With INPUT_PULLUP, released reads HIGH and pressed LOW, so the naive test is digitalRead(4) == LOW. The same ten lines ignoring contact bounce will double-fire — the simulator is a fast way to test the logic before hardware arrives.
How to Debounce a Button on ESP32?
Ignore state changes for 20–50 ms after the first edge. Bounce2 does it in two lines, or track millis() yourself: if (millis() – lastPress > 30) accept the press. Contacts bounce for milliseconds; on my ESP32-S3 a 20 ms window fixed a button that fired twice per press, and 50 ms is a safe default depending on your switch. Our debounce write-up has the code.
What does holding the BOOT button do while the program runs?
Holding it during normal operation ties GPIO0 low — harmless for most sketches, but anything else on GPIO0 misreads, and flashing tools get confused if you hold it at reset.
Can I reuse the BOOT button as a regular input in my project?
Yes — after boot it’s just a GPIO0 button with an internal pull-up; plenty of projects use it for a “factory reset” or programming mode. Don’t press it during reset or you’ll land in download mode by accident; GPIO0 pulls high at boot, so the input starts in a defined state. The strapping trade-off is the price of a free button.
How do I know my button wiring is correct before writing code?
Measure it: with the pull-up enabled the pin reads HIGH, and shorting the button reads LOW; a Serial.println() in a bare loop shows the state live. If the pin never changes, suspect the opposite-leg wiring from question three. This two-minute test isolates hardware from software, and it mostly works even on dodgy breadboards.
Press a Button, Watch It Bounce — In Your Browser
The humblest input, with the classic wart visible:
- Button + LED on ESP32-C3 — hold-to-light with feedback:
ESP32-C3 Button+LED ready
Hold button to light LED
Button pressed!
Button pressed!Two lines for what felt like one press? That is contact bounce — and the reason the debounce patterns in this FAQ exist. Toggle fast in the simulator and you can see the duplicate events the way an oscilloscope would show the ringing, then reason about why a 20 ms window fixes it.