How to Read Button Press on Raspberry Pi Using GPIO

To read a button press on Raspberry Pi, connect the button to a GPIO pin and ground, then use Python's RPi.GPIO library to detect the button state by setting the pin as input with a pull-up resistor. When the button is pressed, the input reads LOW (0), and when released, it reads HIGH (1).

Syntax

Use the RPi.GPIO library to set up the GPIO pin connected to the button as an input with an internal pull-up resistor. Then read the pin state to detect button presses.

• GPIO.setmode(GPIO.BCM): Use Broadcom pin numbering.
• GPIO.setup(pin_number, GPIO.IN, pull_up_down=GPIO.PUD_UP): Set pin as input with pull-up resistor.
• GPIO.input(pin_number): Read the current state of the pin.

python

import RPi.GPIO as GPIO

GPIO.setmode(GPIO.BCM)  # Use BCM pin numbering
GPIO.setup(18, GPIO.IN, pull_up_down=GPIO.PUD_UP)  # Set GPIO18 as input with pull-up

button_state = GPIO.input(18)  # Read button state
print(button_state)  # 1 means not pressed, 0 means pressed

Output

1

Example

This example shows how to detect a button press on GPIO pin 18. It prints "Button Pressed!" when the button is pressed and "Button Released" when it is not pressed.

python

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.IN, pull_up_down=GPIO.PUD_UP)

try:
    while True:
        if GPIO.input(18) == GPIO.LOW:  # Button pressed
            print("Button Pressed!")
        else:
            print("Button Released")
        time.sleep(0.2)  # Delay to avoid flooding output
except KeyboardInterrupt:
    GPIO.cleanup()  # Clean up GPIO on Ctrl+C

Output

Button Released
Button Released
Button Pressed!
Button Pressed!
Button Released
...

Common Pitfalls

• Not using pull-up or pull-down resistors: Without them, the input pin can float and give random readings.
• Wrong pin numbering mode: Mixing BCM and BOARD numbering causes wrong pin reads.
• Not cleaning up GPIO: Forgetting GPIO.cleanup() can cause warnings on next run.
• Ignoring button debounce: Mechanical buttons can cause multiple rapid signals; adding software debounce or hardware capacitor helps.

python

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
# Wrong: Missing pull_up_down causes floating input
GPIO.setup(18, GPIO.IN)  # No pull-up resistor

try:
    while True:
        if GPIO.input(18) == GPIO.LOW:
            print("Button Pressed")
        time.sleep(0.2)
except KeyboardInterrupt:
    GPIO.cleanup()

Quick Reference

Remember these key points when reading button presses on Raspberry Pi:

• Use GPIO.setmode(GPIO.BCM) for pin numbering.
• Set button pin as input with GPIO.PUD_UP to enable internal pull-up resistor.
• Button pressed reads as GPIO.LOW (0), released reads as GPIO.HIGH (1).
• Use GPIO.cleanup() to reset pins after your program ends.
• Add debounce logic if button presses are noisy.

Key Takeaways

Always use internal pull-up or pull-down resistors to avoid floating inputs.

Button press reads as LOW (0) when using pull-up resistor configuration.

Use BCM pin numbering consistently to avoid confusion.

Call GPIO.cleanup() to reset pins after your program finishes.

Consider debounce handling to prevent multiple triggers from one press.