MyIPScan

How to Find Your Local IP Address

Short answer: to find your local IP address, open the network settings on your device or run the right command for your operating system. On Windows, use ipconfig. On macOS, check Network settings, list hardware ports with networksetup -listallhardwareports, then use ipconfig getifaddr en0 or the active interface name. On Linux, use ip addr. On phones, check the Wi-Fi details for the current network.

This guide explains how to find your local IP address, how to tell it apart from your public IP address, and what to do when the result looks wrong, duplicated, or unstable.

Quick answer

  • Windows: open Command Prompt and run ipconfig. Look for IPv4 Address under the active adapter.
  • macOS: open System Settings, choose Network, select Wi-Fi or Ethernet, or use networksetup -listallhardwareports before checking the active interface with ipconfig getifaddr.
  • Linux: run ip addr or hostname -I, then find the address on the active interface.
  • iPhone and Android: open Wi-Fi network details and look for IP address, router, or gateway information.
  • Router: open the router admin page and check connected devices, DHCP leases, or client list.

How to find your local IP address: 7 safe ways

  1. Use device settings first. The safest method is the normal network settings screen for the device you are using.
  2. Use command-line tools when needed. Commands are faster for troubleshooting, but use the command that matches the operating system.
  3. Check the active adapter. Wi-Fi, Ethernet, VPN, virtual machine, and mobile hotspot adapters can all show different addresses.
  4. Compare the gateway. Your router or default gateway is usually nearby in the same subnet, such as 192.168.1.1.
  5. Use the router device list. This is the best way to find printers, cameras, smart TVs, phones, and devices without screens.
  6. Separate local and public IPs. A local private address is not what most websites see.
  7. Document stable devices. Use DHCP reservations for devices that need a predictable local address.

Local IP vs public IP vs router gateway

A local IP address identifies a device inside your private network. A public IP address identifies the internet connection from the outside. A router gateway is the local address of the router that moves traffic between the local network and the internet.

Address typeCommon exampleWhere it worksWhat it is used for
Private local IPv4192.168.1.23, 10.0.0.12Inside your LANDevice-to-device traffic, printer access, router DHCP
Router gateway192.168.1.1Inside your LANDefault path from your device to other networks
Public IPAssigned by ISP, VPN, mobile carrier, or workplaceInternet-facingWhat websites and online services usually see
IPv4 link-local169.254.x.xLocal link onlyFallback when DHCP fails
IPv6 link-localfe80::Local link onlyNeighbor discovery and local IPv6 communication
IPv6 unique localfc00::/7, commonly seen as fd00::/8Private IPv6 networksInternal addressing that is not globally routed

The private IPv4 ranges used on home and office networks are defined in RFC 1918. IPv4 link-local behavior is described in RFC 3927, and IPv6 unique local addresses are described in RFC 4193.

Find your local IP address on Windows

Windows often shows several adapters, so focus on the one you are actually using. Wi-Fi, Ethernet, VPN, Hyper-V, and virtual adapters can all appear in the output.

Settings method

  1. Open Settings.
  2. Go to Network & internet.
  3. Select Wi-Fi or Ethernet.
  4. Open the connected network details and look for IPv4 address, IPv6 address, and Default gateway.

Command method

ipconfig
ipconfig /all

Look for IPv4 Address under the adapter that says connected. Microsoft documents the ipconfig command as the standard Windows tool for TCP/IP configuration details.

Find your local IP address on macOS

On macOS, the graphical network settings are usually enough. Terminal commands are useful when you need to copy the result into notes or support messages.

System Settings method

  1. Open System Settings.
  2. Choose Network.
  3. Select the active Wi-Fi or Ethernet connection.
  4. Open details and review the IP address, router, and DNS information.

Terminal method

On many Macs, Wi-Fi is en0, but the interface name can differ. List hardware ports first if you are not sure which device name is active.

# List hardware ports and device names
networksetup -listallhardwareports

# Check a common Wi-Fi interface on many Macs
ipconfig getifaddr en0

# List IPv4 addresses if the interface name differs
ifconfig | grep "inet "

If the command returns nothing, the interface name may be different, or that adapter may not have an IPv4 address. Use the Network settings screen to confirm which interface is active.

Find your local IP address on Linux

Linux distributions vary, but the modern command is usually ip. Older guides may mention ifconfig, which is not always installed by default.

ip addr
ip -4 addr show
hostname -I
ip route | grep default

Find the active interface, such as wlan0, wlp, eth0, or enp. The local IPv4 address appears after inet. The default route usually points to the router gateway.

Find your local IP address on iPhone, iPad, and Android

Mobile settings change by device version, manufacturer, and carrier, so the exact labels may vary. The safest pattern is to open the details for the Wi-Fi network you are actually using. Cellular networks usually do not expose the same local LAN address view as Wi-Fi.

iPhone and iPad

  1. Open Settings.
  2. Tap Wi-Fi.
  3. Tap the information icon next to the connected network.
  4. Look for IP address, router, subnet mask, DNS, and IPv6 entries.

Android

  1. Open Settings.
  2. Open Network & internet or the device manufacturer's equivalent network menu.
  3. Tap the connected Wi-Fi network.
  4. Open network details or advanced details and look for IP address, gateway, and DNS entries.

If you are trying how to find your local IP address on a phone for printer, TV, or casting problems, test on Wi-Fi. A mobile carrier connection may use a carrier network path that does not place the phone on the same local network as your home devices.

Use your router to find every device on the network

The router is often the most reliable place to find local addresses for devices without easy screens, including printers, cameras, game consoles, NAS devices, smart TVs, and IoT gear.

  1. Find your gateway address from your computer or phone.
  2. Open the router address in a browser, such as http://192.168.1.1 or the address shown as your default gateway. Use HTTPS if your router supports it, and do this only from your trusted local network.
  3. Sign in to the router admin page.
  4. Look for Connected devices, Clients, DHCP leases, or Device list.
  5. Match the device by name, MAC address, vendor, or connection type.

Do not change router settings just to look up an address. If you are not sure which device is which, compare the device name, manufacturer, Wi-Fi band, and last-seen time before editing anything.

When local IP addresses matter most

Knowing how to find your local IP address matters most when you are trying to reach a specific device or confirm that two devices are on the same network. The address itself is only one clue; the gateway, subnet, Wi-Fi network, and router client list often explain the issue.

  • Printer setup: a printer may disappear when its local address changes.
  • Smart TV and casting: phones and TVs usually need to be on the same local network or VLAN.
  • NAS and file sharing: stable local addresses make shares easier to map and troubleshoot.
  • Router troubleshooting: gateway, subnet, and DHCP information explain whether the device is on the expected network.
  • Security review: unknown devices in the DHCP list can reveal old phones, guest devices, cameras, or IoT equipment.
  • Remote access setup: a local IP can help configure internal access, but public exposure needs separate firewall and safety review.

How to read the result without overreacting

When people search for how to find your local IP address, they often expect one clean number. Real devices can show more than one address because they have Wi-Fi, Ethernet, VPN, Bluetooth, virtual adapters, IPv6, and temporary addresses. That does not automatically mean something is wrong.

  • Pick the active network. If you are using Wi-Fi, read the Wi-Fi adapter first. If you are plugged into Ethernet, read Ethernet first.
  • Match the gateway. Devices that need to talk locally usually share a similar gateway, such as 192.168.1.1 or 10.0.0.1.
  • Compare subnets. A laptop on 192.168.1.x and a printer on 192.168.50.x may be separated by guest Wi-Fi, VLANs, or mesh/router settings.
  • Check VPN adapters separately. A VPN can add a virtual local address that is not useful for reaching your printer or TV.
  • Use router names carefully. Device names in router lists can be old, generic, or manufacturer-based, so confirm with MAC address or recent activity when possible.

The calm approach is to write down the device address, gateway, subnet, and connection type. If those details match, local troubleshooting becomes much easier. If they do not match, the next step is usually network placement, not changing random IP settings.

Static local IPs, DHCP reservations, and when to use them

Most devices should use automatic addressing. DHCP is defined in RFC 2131, and in normal home networks the router uses DHCP to hand out local IPv4 addresses. A static local IP is useful only when a device needs a stable address and you understand the local subnet. For most homes, a DHCP reservation on the router is safer than manually typing a static address on the device.

OptionBest forMain riskPractical recommendation
Automatic DHCPPhones, laptops, tablets, guest devicesAddress can changeUse this by default
DHCP reservationPrinters, NAS, cameras, smart TVsRequires router accessBest balance for stable home devices
Manual static IPServers, lab devices, managed networksDuplicate address or wrong gatewayUse only when you control the subnet plan

Troubleshooting: no IP, duplicate IP, or 169.254 address

SymptomLikely causeWhat to check
169.254.x.xDevice did not get DHCPWi-Fi password, Ethernet cable, router DHCP, access point, reboot order
No local IPAdapter is disconnected or disabledNetwork toggle, airplane mode, cable, driver, Wi-Fi connection
Duplicate IP warningTwo devices are using the same addressRemove manual static conflict or create proper DHCP reservations
Wrong subnetGuest network, extender, VLAN, or VPN adapterCompare gateway and subnet with the device you want to reach
Printer or TV disappearedAddress changed after DHCP renewalUse router device list and consider a DHCP reservation

Security and privacy notes for local IP addresses

A local IP address is not a secret identity marker. The same private ranges are reused in homes, offices, hotels, schools, and cafes. Still, local addressing can matter for device access, router hygiene, and troubleshooting.

  • Do not expose router admin, camera, NAS, Remote Desktop, or SSH interfaces to the internet just because you found a local address.
  • Use strong Wi-Fi security and update router firmware.
  • Review unknown devices in the router client list before assuming they are attackers; names can be vague or outdated.
  • Only scan networks you own or are authorized to test.
  • Remember that your public IP, account activity, DNS, browser, and provider records are different signals from a local IP.

What to do next

If you only need the address once, copy it from device settings and stop there. If you are troubleshooting a recurring printer, TV, NAS, camera, or remote-access problem, record the device local IP, gateway, subnet, MAC address, and router lease entry. That makes future support much easier.

The practical value of learning how to find your local IP address is not memorizing a number. It is understanding which device is on which network, whether the gateway is correct, and whether the address is stable enough for the task you are trying to fix.

If you need to explain the issue to support, say exactly how to find your local IP address was checked: settings page, command line, router device list, or mobile Wi-Fi details. That small detail helps separate device problems from router DHCP, guest-network isolation, VPN adapters, and public-internet issues.

Frequently asked questions

Is my local IP address the same as my public IP address?

No. A local IP address works inside your home, office, or Wi-Fi network. A public IP address is the address websites see for your internet connection. A router usually uses NAT so many local devices can share one public IPv4 address.

What are the most common local IP address ranges?

The common private IPv4 ranges are 192.168.0.0/16, 10.0.0.0/8, and 172.16.0.0/12. IPv6 local-style addresses include link-local addresses such as fe80:: and unique local IPv6 space such as fc00::/7, commonly seen as fd00::/8.

Why does my device show a 169.254 address?

A 169.254.x.x address usually means the device assigned itself a link-local IPv4 address because DHCP did not provide a normal local address. Check Wi-Fi, Ethernet, router DHCP settings, cables, and whether the device is on the correct network.

Can someone on the internet use my local IP address to find me?

Usually, no. Local private addresses are reused on many networks and are not routed directly across the public internet. Public IP, account activity, browser signals, provider records, and timestamps matter more for external tracking.

Should I use a static local IP address?

Use a DHCP reservation on the router for printers, NAS devices, cameras, servers, or smart TVs that need a stable address. For phones and laptops, automatic DHCP is usually simpler and less error-prone.

Sources and methodology

MyIPScan tools and examples show observable browser and network signals. IP and geolocation results can be approximate, and VPN, DNS, WebRTC, IPv6, ASN, reputation, and browser checks are snapshots. A single result does not prove anonymity or every security condition. See the MyIPScan methodology and editorial policy.

This FAQ was updated using MyIPScan editorial guardrails: practical troubleshooting, careful distinction between local and public addresses, no privacy guarantees, no unsafe scanning advice, and source-backed explanations of private and link-local addressing.


About the author & editorial process

Author:

Reviewed by: MyIPScan Editorial Team

Katia Belokon writes and edits practical guides on IP addresses, browser privacy, VPN leaks, DNS, WebRTC, IPv6 and online privacy for MyIPScan.

Articles follow the MyIPScan editorial policy and methodology for clarity, factual accuracy, safety, and transparent limitations.

Contact: hello@myipscan.net