What Is a Private IP Address?
A private IP address is an IP address from a range reserved for use within private networks - Your home, office, or data center LAN. These addresses are defined by RFC 1918 and are not routable on the public internet. Devices with private IPs communicate with the internet through Network Address Translation (NAT) performed by your router.
RFC 1918 Private IP Ranges
| Range | CIDR Notation | Total Addresses | Common Use |
|---|---|---|---|
| 10.0.0.0 – 10.255.255.255 | 10.0.0.0/8 | 16,777,216 | Large enterprise networks, VPNs |
| 172.16.0.0 – 172.31.255.255 | 172.16.0.0/12 | 1,048,576 | Medium-sized corporate networks |
| 192.168.0.0 – 192.168.255.255 | 192.168.0.0/16 | 65,536 | Home routers (192.168.0.x / 192.168.1.x) |
| 169.254.0.0 – 169.254.255.255 | 169.254.0.0/16 | 65,536 | APIPA - Assigned when DHCP fails (not RFC 1918) |
| 127.0.0.0 – 127.255.255.255 | 127.0.0.0/8 | 16,777,216 | Loopback - Local device only (not RFC 1918) |
How NAT Bridges Private and Public Addresses
Your router holds one public IP address (assigned by your ISP) and assigns private IPs to every device on your network. When a device sends traffic to the internet, the router replaces the private source IP with its public IP, keeps a translation table of the mapping, and reverses the substitution when the response arrives. This is why multiple devices can share a single public IP.
Finding Your Private IP Address
- Windows: open Command Prompt and run
ipconfig- Look for "IPv4 Address" under your active adapter. - macOS / Linux: open Terminal and run
ip addrorifconfig- Look for "inet" entries excluding 127.0.0.1. - Android: Settings → Wi-Fi → tap your network → Advanced - Look for IP address.
- iPhone / iPad: Settings → Wi-Fi → tap the (i) next to your network - Look for IP Address.
- Your router's admin panel (usually at 192.168.1.1 or 192.168.0.1) lists all connected devices and their private IPs.
Why Private Addresses Exist
The IPv4 exhaustion problem
IPv4 provides roughly 4.3 billion addresses - Far fewer than the number of connected devices in the world. In 1996, RFC 1918 ("Address Allocation for Private Internets") set aside three blocks that anyone may reuse freely inside their own network, because those addresses never appear on the public internet. Millions of homes can all use 192.168.1.0/24 simultaneously without conflict, since each network is isolated behind its own NAT router. This reuse is one of the main reasons IPv4 has survived decades past its predicted exhaustion.
Private addressing in IPv6
IPv6 has so much address space that scarcity is not a concern, but private-style ranges still exist. Unique Local Addresses (ULA, the fc00::/7 block defined in RFC 4193) play the same role as RFC 1918 space, and every IPv6 interface also has a link-local address in fe80::/10 that is valid only on the local network segment. See IPv4 vs IPv6 for the full comparison.
How to Give a Device a Fixed Private IP
By default your router's DHCP server hands out private IPs from a pool, so a device's address can change over time. For printers, NAS boxes, or anything you port-forward to, a fixed address is more reliable. The cleanest method is a DHCP reservation set on the router:
| Step | Action |
|---|---|
| 1 | Open your router's admin panel - Usually 192.168.1.1 or 192.168.0.1 in a browser |
| 2 | Log in and find the LAN, DHCP Server, or Address Reservation section |
| 3 | Select the device from the connected-clients list (identified by its MAC address) |
| 4 | Assign it a fixed IP inside your subnet but outside the DHCP pool if possible (e.g. 192.168.1.50) |
| 5 | Save and reboot the device - It will receive the same IP on every connection from now on |
You can verify which addresses are free, and how many hosts your network supports, with the subnet calculator. The mask that defines your network's size is explained in our subnet mask FAQ.
What This Means for You
Your private IP is a local label, not a secret. Websites never see it - They see only the public IP your router presents. That has two practical consequences. First, anything you configure locally (port forwarding, printer sharing, game-console settings) uses the private address, so knowing how to find it on each device saves troubleshooting time. Second, privacy concerns about "hiding your IP" apply only to the public side: changing or masking your private IP achieves nothing externally, while a VPN changes what the outside world sees without touching your LAN addressing at all.
Frequently Asked Questions
Can two devices have the same private IP address?
Not on the same network - A duplicate private IP causes an address conflict and both devices lose connectivity until one changes. On different networks it is completely normal: your 192.168.1.10 and your neighbour's 192.168.1.10 never interact because both sit behind separate NAT routers.
Is a private IP address safer than a public one?
In one narrow sense, yes: devices with only a private IP cannot be reached directly from the internet, because RFC 1918 addresses are not routable there. The router's NAT acts as an incidental barrier to unsolicited inbound traffic. It is not a security feature by itself, though - You still need a firewall and updated devices.
Why does my private IP start with 169.254?
A 169.254.x.x address (APIPA, defined in RFC 3927) means your device asked for an IP via DHCP and got no answer, so it self-assigned a link-local address. It usually indicates a router, cable, or Wi-Fi problem - Reconnect to the network, restart the router, or renew the DHCP lease to fix it.