How to Find Your Raspberry Pi IP Address (All Methods Explained)

Whether you're setting up a headless server, running a home automation project, or just trying to SSH in for the first time, knowing your Raspberry Pi's IP address is a fundamental networking task. The good news: there are several reliable ways to find it, and the right method depends entirely on your current setup.

Why Your Raspberry Pi Needs an IP Address

Every device connected to a network gets assigned an IP address — a unique numerical label that allows other devices to communicate with it. Your Raspberry Pi is no different. When it connects to your router via Ethernet or Wi-Fi, your router's DHCP server automatically assigns it a local IP address (typically in a range like 192.168.1.x or 10.0.0.x).

The challenge is that this address isn't printed anywhere obvious. If you have a monitor plugged in, it's straightforward. If you're running headless (no display), you need other approaches.

Method 1: Check the Terminal Directly on Your Pi 🖥️

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

Open a terminal and run:

hostname -I 

This returns the Pi's current IP address(es) on the local network. It's simple, accurate, and works across all recent versions of Raspberry Pi OS.

You can also use:

ip addr show 

This gives more detail — including which network interface (eth0 for Ethernet, wlan0 for Wi-Fi) holds which address. Useful when your Pi is connected to both.

Method 2: Log Into Your Router's Admin Panel

Your router keeps a list of every device it's currently serving an IP address to via DHCP. This is one of the most reliable methods when you don't have direct access to the Pi.

General steps:

1. Open a browser and navigate to your router's admin address (commonly 192.168.1.1 or 192.168.0.1)
2. Log in with your router credentials
3. Find the section labeled DHCP clients, Connected Devices, or LAN clients
4. Look for a device named raspberrypi (the default hostname) or identify it by MAC address

The interface varies significantly between router brands and firmware versions, so exact navigation steps depend on your hardware.

Method 3: Scan Your Network with a Tool

Network scanning tools discover all active devices on your local network. This is particularly useful for headless setups.

Common options:

When scanning, look for a device with a hostname like raspberrypi or a MAC address prefix associated with the Raspberry Pi Foundation (B8:27:EB, DC:A6:32, or E4:5F:01 depending on the model generation).

The /24 in the nmap command tells it to scan all 256 addresses in that subnet — adjust the base address to match your network range.

Method 4: Use mDNS / Bonjour (Access by Hostname)

Recent versions of Raspberry Pi OS support mDNS (multicast DNS), which means you can often reach your Pi by its hostname instead of its IP address. By default, this resolves as:

raspberrypi.local 

So instead of finding the IP, you'd SSH with:

ssh [email protected] 

Important caveats: This works reliably on macOS and Linux. On Windows, it requires Bonjour (installed automatically with iTunes or Apple's Bonjour Print Services) or a recent version of Windows 10/11 which has built-in mDNS support. It also stops working if you've changed the Pi's hostname or if your network has mDNS filtering enabled.

Method 5: Pre-Configure a Static IP Address

If you're constantly needing to track down your Pi's address, setting a static IP eliminates the problem entirely. There are two main approaches:

• DHCP reservation at the router level — You tell your router to always assign the same IP to your Pi's MAC address. No changes needed on the Pi itself.
• Static IP configured on the Pi — You manually set a fixed IP in the Pi's network configuration files. This works independently of the router but requires more careful setup to avoid address conflicts.

Static IPs make sense for servers, always-on projects, and anything you access frequently. They add a small layer of network management overhead but save significant time over repeated IP hunting.

The Variables That Affect Which Method Works for You 🔧

Not every method works in every scenario. What determines your best path:

• Headless vs. display-connected setup — Direct terminal access is only possible if you have a screen
• Operating system on your scanning device — nmap behavior and mDNS support vary between Windows, macOS, and Linux
• Router model and firmware — Admin panel layout and DHCP client visibility differ widely
• Pi OS version — Older Raspbian versions may not have mDNS enabled by default
• Network configuration — Corporate or managed networks may block DHCP browsing or mDNS traffic
• Number of Pis on the network — Multiple devices with default hostnames creates ambiguity

A home setup with one Pi running current Raspberry Pi OS on a standard consumer router is the easiest scenario. A headless Pi on a managed office network, or one with a customized hostname, requires more deliberate steps.

When the IP Address Keeps Changing

If your Pi's IP keeps shifting between sessions, that's standard DHCP behavior — leases expire and addresses can get reassigned. The long-term fix is either a DHCP reservation or a static IP configuration. Which approach fits better depends on whether you control the router and how comfortable you are editing network config files directly on the Pi.

The method that works cleanly for one person's home lab may be completely unavailable in another person's setup — which is why understanding all the options first puts you in a much stronger position to choose.