Finding the IP address of a Raspberry Pi is one of the first practical tasks you may need to complete after setting it up. Whether you want to connect over SSH, access a web server, manage Home Assistant, or troubleshoot a network issue, the Pi’s IP address tells you where it is on your local network. The safest and most reliable method depends on whether you already have access to the Raspberry Pi, whether it is running headless, and what equipment you can access on the same network.
TLDR: The easiest way to find a Raspberry Pi’s IP address is to check your router’s connected devices list or use the command hostname -I directly on the Pi. If the Pi is headless, you can scan your network from another computer using tools such as arp, ping, or nmap. For long-term reliability, reserve a fixed IP address for the Raspberry Pi in your router’s settings.
Contents
Why the Raspberry Pi IP Address Matters
An IP address is the network location assigned to your Raspberry Pi. On most home and office networks, this is a private address such as 192.168.1.42, 192.168.0.25, or 10.0.0.15. You use this address when connecting to the Pi from another device, for example with SSH, VNC, a browser-based dashboard, or file sharing.
In many cases, the IP address is assigned automatically by your router using DHCP. That means it can change after a reboot, router restart, or network reconfiguration. This is normal, but it can be inconvenient if you depend on the Pi for regular services. The methods below will help you find the current address and, where appropriate, make it easier to identify in the future.
Method 1: Use the Raspberry Pi Itself
If you have a monitor and keyboard connected to the Raspberry Pi, or you already have terminal access, this is the most direct method.
- Open a terminal on the Raspberry Pi.
- Type the following command:
hostname -I - Press Enter.
The command will display one or more IP addresses. In most simple networks, the first address shown is the one you need. For example, you may see something like 192.168.1.34. If both Wi-Fi and Ethernet are connected, you may see more than one address. In that case, choose the one associated with the network interface you intend to use.
You can also use a more detailed command:
ip addr
This shows information for each network interface. Look for wlan0 if the Pi is connected by Wi-Fi, or eth0 if it is connected by Ethernet. The relevant line usually contains inet followed by the IP address.
Method 2: Check Your Router’s Device List
For a headless Raspberry Pi, checking the router is often the most reliable option. Your router assigns addresses to devices, so it usually keeps a list of connected clients.
- Open a browser on a computer or phone connected to the same network.
- Enter your router’s address, often
192.168.1.1,192.168.0.1, or10.0.0.1. - Sign in using the router administrator credentials.
- Look for a section called Connected Devices, DHCP Clients, LAN Devices, or Network Map.
- Find an entry named raspberrypi, raspberrypi.local, or a custom hostname you set during installation.
The router list should show the IP address and often the MAC address. If several unknown devices appear, disconnect and reconnect the Raspberry Pi, then refresh the list. The device that appears or updates is likely to be the Pi.
This method is particularly trustworthy because it relies on the router’s own assignment records. However, router interfaces vary widely, so the exact menu names may differ.
Method 3: Try the Local Hostname
Many Raspberry Pi installations support local hostname resolution. Instead of typing the numeric IP address, you may be able to connect using:
raspberrypi.local
For example, if SSH is enabled, try:
ssh pi@raspberrypi.local
On newer Raspberry Pi OS installations, the username may not be pi, because recent setup tools require you to create your own user. Replace pi with the username you configured.
This method uses multicast DNS, often called mDNS. It works well on many home networks, especially with macOS, Linux, and Windows systems that support the required discovery service. If it does not work, it does not necessarily mean the Pi is offline; it may simply mean that hostname discovery is not functioning on your device or network.
Method 4: Scan the Network from Another Computer
If you cannot access the router and do not have a display connected to the Pi, you can scan the local network. This should only be done on networks you own or are authorized to manage.
On Linux or macOS, you can start with:
arp -a
This lists devices your computer has recently seen on the local network. Look for unfamiliar hostnames or addresses that may belong to the Raspberry Pi. You can also use ping to test likely addresses.
A more systematic option is nmap, a respected network scanning tool. For example, if your computer’s IP address is 192.168.1.20, your network is often in the range 192.168.1.0/24. You could run:
nmap -sn 192.168.1.0/24
This performs a basic discovery scan and lists active devices. Raspberry Pi devices may appear with a hostname, or the MAC address vendor may indicate Raspberry Pi Foundation or Raspberry Pi Trading. If the hostname is not shown, compare the results with your router, device labels, or by temporarily unplugging the Pi and scanning again.
Method 5: Use a Mobile Network Scanner
Several reputable mobile apps can scan your local network and show connected devices. These apps are convenient if you do not want to use command-line tools. Connect your phone to the same Wi-Fi network as the Raspberry Pi, run a scan, and look for a device named raspberrypi or a similar hostname.
Be cautious with unknown apps. A network scanner can see sensitive information about devices on your LAN, so use well-reviewed tools from trusted sources and avoid granting unnecessary permissions. For professional or security-sensitive environments, router logs and administrator-approved tools are preferable.
Ethernet Versus Wi-Fi
If your Raspberry Pi is connected by both Ethernet and Wi-Fi, it may have two IP addresses. This can lead to confusion when one address works and another does not. Ethernet interfaces usually appear as eth0, while wireless interfaces usually appear as wlan0.
For stable services, Ethernet is generally preferable because it is less affected by wireless signal strength and interference. If you must use Wi-Fi, place the Pi where it has a strong signal and avoid networks with client isolation enabled, because that feature may prevent other devices from reaching it.
Make the Address Easier to Find Next Time
Once you have found the Raspberry Pi’s IP address, consider creating a DHCP reservation in your router. This tells the router to give the same IP address to the Pi every time it connects. It is usually better than manually configuring a static IP on the Pi because the router remains the central authority for address management.
To create a reservation, find the Raspberry Pi in your router’s connected devices list, then look for an option such as Reserve IP, Address Reservation, or Static Lease. Choose an address within your local network but outside any conflicting range, if your router requires that level of detail.
Troubleshooting Common Problems
- The Pi does not appear on the network: Confirm it is powered properly and that the SD card or storage device has a valid operating system.
- Wi-Fi was configured but no address appears: Check the SSID, password, country setting, and wireless signal strength.
- SSH does not work: The IP address may be correct, but SSH may not be enabled or the firewall may block access.
- The address changed: This is common with DHCP. Use a router reservation to prevent it.
- You see multiple addresses: Identify whether you are using Ethernet or Wi-Fi, then choose the matching interface address.
In most situations, the fastest path is to run hostname -I if you can access the Pi, or check the router’s connected device list if you cannot. Network scanning is useful when those options are unavailable, but it should be done carefully and only on authorized networks. Once you identify the Raspberry Pi, reserving its IP address will save time and reduce connection problems in the future.
