Your Mac gets its IP address automatically over DHCP by default, and for everyday browsing there's usually no need to change that. But if you need to connect to a NAS or a network printer, or want other devices on your LAN to reliably reach this Mac, a fixed IP address is more convenient.
Different macOS versions put the settings in slightly different places — especially since Ventura, when System Settings got a redesign. Below are three approaches: the graphical interface, terminal commands, and a router-side reservation — plus how to verify everything afterward.

Don't just copy an IP address you found online. Different home or office networks can use different subnets, and a wrong gateway or subnet mask can leave you with no connection at all.
Open System Settings on your Mac, go to Network, select the Wi-Fi or Ethernet connection you're using, then click TCP/IP under Details.
Note down your current IP address, subnet mask, and router address. For example:
• IP address: 192.168.1.23
• Subnet mask: 255.255.255.0
• Router: 192.168.1.1
If your network uses that subnet mask, 192.168.1.88 is a reasonable address to try — but first make sure nothing else is using it, and ideally pick one outside the router's DHCP range.
It's also worth separating the LAN IP from the public IP. What macOS shows in network settings is usually your local address, while websites see your public egress address. To check your current public IP, run an IP lookup with ToDetect to see your egress IP, location, and ISP.
On newer versions of macOS you can do this straight in System Settings — no extra software required.
• Click the Apple menu and open System Settings.
• Go to Network and select the Wi-Fi or Ethernet connection you're currently on.
• Click Details and find TCP/IP.
• Change Configure IPv4 from Using DHCP to Manually.
• Enter the IP address, subnet mask, and router address you prepared.
• Click OK to save.
Staying with the example network above, you'd enter:
• IP address: 192.168.1.88
• Subnet mask: 255.255.255.0
• Router: 192.168.1.1
Then go into DNS settings and check that a working DNS server is still listed. If you need to add one, 223.5.5.5 or 119.29.29.29 will do.
These addresses are just examples. If your company network has specified parameters, use whatever your network administrator gives you.
On macOS Monterey and earlier, the path is System Preferences → Network → select the connection → Advanced → TCP/IP. Set Configure IPv4 to Manually, fill in the values, and click Apply.
If you're comfortable on the command line, you can set a static IP with networksetup, which ships with macOS. Open Terminal and run the commands below in order.
| Action | Terminal command |
|---|---|
| List network service names | networksetup -listallnetworkservices |
| Set a static IP | sudo networksetup -setmanual "Wi-Fi" 192.168.1.88 255.255.255.0 192.168.1.1 |
| Set DNS servers | sudo networksetup -setdnsservers "Wi-Fi" 223.5.5.5 119.29.29.29 |
| Switch back to DHCP | sudo networksetup -setdhcp "Wi-Fi" |
| Restore automatic DNS | sudo networksetup -setdnsservers "Wi-Fi" Empty |
In the table, 192.168.1.88 is an example static IP, 255.255.255.0 is the subnet mask, and 192.168.1.1 is the gateway — adjust them to match your own network.
If you're on Ethernet, replace "Wi-Fi" with the network service name listed by the system. When you go back to automatic addressing, it's best to restore both the DHCP and DNS settings.
If all you want is for your Mac to get the same address every time it joins your home Wi-Fi, the router's DHCP reservation feature is usually the better fit.
Open your router's admin page and look for "DHCP reservation," "static address assignment," or something similar, then bind the Mac's current Wi-Fi MAC address to the IP you want.
That way the Mac still gets its address automatically over DHCP, and you don't have to keep reconfiguring it when you connect to other networks.
One thing to watch: some Macs use a private Wi-Fi address per network. When you set up the binding, make sure the MAC address your router sees is the one actually in use.
First, go back to the TCP/IP page and confirm the manual address has taken effect.
Then open Terminal and test whether the gateway responds: ping -c 4 192.168.1.1
If you get a normal response, test DNS resolution: nslookup apple.com
If the gateway responds but domain names won't resolve, focus your attention on the DNS settings.
You can also run a public IP check on ToDetect to verify that your current egress IP, location, and ISP match expectations.
Worth noting: successfully setting a LAN static IP doesn't mean your public IP will change. A public IP lookup tells you about your internet egress — it's no substitute for local connectivity testing.
• Can't reach the gateway: Check that the IP address, subnet mask, and router address are correct, and that the Mac and gateway are on a network that can talk to each other.
• IP address conflict: Another device may already be using that address. Check what the router has already handed out and pick an unused IP.
• Gateway reachable but pages won't load: Test external IP connectivity first, then check DNS — don't assume every network problem is a name resolution issue.
• No internet after switching Wi-Fi networks: A manual configuration may not apply to the new network. Restore DHCP, or configure each network separately.
A static IP itself won't raise or lower your bandwidth. But a wrong gateway, DNS, or network configuration can affect how the connection actually performs.
No. LAN addresses and public egress addresses are configured at different layers, and whether your public IP stays the same depends on your service provider.
Yes. They're separate network services, and each can use either a manual IP or DHCP.
If you carry your MacBook between different networks often, DHCP reservation on the router is usually the better choice. If your network explicitly requires manual configuration, use the parameters you're given.
Setting a static IP on a Mac isn't complicated. The keys are confirming your network parameters up front, avoiding address conflicts, and checking the gateway and DNS after your changes. As for public egress details, verify them separately with an IP lookup tool — and don't confuse LAN configuration with public IP testing.
Efficiently solve multi-account management, environment isolation, and account security