How to Find the IP Address of Your Raspberry Pi

Whether you're setting up a headless server, running a home automation project, or just getting started with your Pi for the first time, knowing its IP address is the essential first step to connecting remotely. The good news: there are several reliable ways to find it. The right method depends on how your Pi is configured and what tools you have available.

Why Your Raspberry Pi's IP Address Matters

When you connect a Raspberry Pi to your network — via Ethernet or Wi-Fi — your router assigns it an IP address, typically something like 192.168.1.x or 10.0.0.x. This address is how other devices on your network (your laptop, phone, desktop) locate and communicate with the Pi.

If you're using a monitor and keyboard directly connected to the Pi, finding the IP is straightforward. If you're running it headless (no display attached), you'll need to find the address through other means before you can SSH in or open a browser-based interface.

Method 1: Check Directly on the Raspberry Pi

If you have a monitor and keyboard connected, this is the fastest path.

Open a terminal and run:

hostname -I 

This returns the Pi's current IP address on the local network. You may see multiple addresses if the Pi is connected to both Ethernet and Wi-Fi simultaneously — the first one listed is typically the primary connection.

Alternatively, run:

ip addr show 

This gives more detail, including which network interface (eth0 for Ethernet, wlan0 for Wi-Fi) each address belongs to.

Method 2: Log Into Your Router

Every device connected to your network is listed in your router's DHCP client table. This is one of the most reliable methods, especially for headless setups.

1. Open a browser and navigate to your router's admin page — commonly 192.168.1.1 or 192.168.0.1
2. Log in with your router credentials (often printed on the router itself)
3. Look for a section labeled Connected Devices, DHCP Clients, or Device List
4. Find the entry with the hostname raspberrypi (or whatever you've named it)

The IP address listed there is what you need. 🔍

One caveat: routers from different manufacturers organize this differently. Some bury the DHCP table several menus deep. If you can't locate it, check your router's manual or support page.

Method 3: Use a Network Scanner

If router access isn't convenient, a network scanning tool can discover all devices on your local network, including the Pi.

Popular options include:

With nmap, you can scan your entire subnet from a terminal:

nmap -sn 192.168.1.0/24 

Replace the IP range with your own network's subnet. Your Pi will appear in the results, often identified by its hostname or by a MAC address prefix associated with the Raspberry Pi Foundation.

Method 4: Use mDNS / Bonjour (raspberrypi.local)

Modern versions of Raspberry Pi OS support mDNS (multicast DNS), which means you may be able to reach your Pi by hostname without knowing its IP at all.

From another computer on the same network, try:

ping raspberrypi.local 

If it responds, the IP address will appear in the ping output. On Windows, mDNS support requires Bonjour to be installed (it typically comes with iTunes or Apple devices). On macOS and Linux, it works natively.

This method is particularly useful during initial setup — you can SSH directly using raspberrypi.local as the address without hunting for the IP first.

Method 5: Check the SD Card Before First Boot

If you haven't booted the Pi yet and used Raspberry Pi Imager to write your OS, you may have configured Wi-Fi and SSH during the imaging process. In that case, the Pi will connect to your network automatically on first boot and appear in your router's device list.

Some users add a file called ssh (no extension) to the boot partition of the SD card to enable SSH by default on older versions of Raspberry Pi OS. Once connected, any of the methods above will reveal the address.

Variables That Affect Which Method Works Best 🛠️

Not every method works in every situation. A few factors shape which approach is most practical:

• Headless vs. display-connected: Without a monitor, Methods 2–4 become your primary options
• OS version: Older Raspberry Pi OS builds may not support mDNS out of the box
• Network type: On some corporate or managed networks, mDNS is blocked and router access is restricted
• Multiple Pis on the same network: Hostname-based methods like raspberrypi.local can conflict if you haven't renamed each device
• Static vs. dynamic IP: If you haven't assigned a static IP to your Pi, its address can change after a reboot or router restart — something worth planning for if you connect to it regularly

A Note on Static IP Assignment

For most ongoing projects, it's worth reserving a static IP for your Pi through your router's DHCP reservation feature. This ties the Pi's MAC address to a fixed IP, so you always know where to find it without re-scanning. The process varies by router brand, but it's generally found in the same DHCP settings section where you first located the Pi's address.

Whether that's worth doing depends entirely on how you're using your Pi, how often you connect to it, and how your network is set up — which only you can assess based on your own situation.