How to change IP address on macOS
Use this when your main need is the exact navigation inside macOS settings.
macOS network workflow
How to switch between DHCP and static IP on Mac
On macOS, you switch between DHCP and static IP in the adapter's IPv4 settings. The actual clicks are easy. The hard part is doing it repeatedly without forgetting which static values worked and how to get back to a clean DHCP baseline. IPChange helps when this becomes a recurring workflow rather than a one-off change.
The simple switching workflow
- Keep one known-good DHCP fallback ready before you move to any manual setup.
- Confirm the target static IP, mask, gateway and DNS for the environment you are entering.
- Apply the static setup and verify the connection you actually need.
- When the task is done, switch back to DHCP or to another saved working profile.
The risk is usually not the first switch to static IP. The risk is forgetting the exact path back to normal after several client, router or lab changes.
When DHCP is the right return state
- You are leaving a client or router maintenance environment.
- You are returning to home, office or normal managed Wi-Fi.
- You no longer need fixed gateway or DNS values from a narrow local setup.
- You want the Mac to follow whatever the network provides automatically.
When static IP still makes sense
| Need | Why static still matters | What to watch |
|---|---|---|
| Router or firewall access | The device expects a known local range. | Confirm the right mask and avoid stale gateway or DNS. |
| Lab or demo work | The environment may not have DHCP at all. | Keep a known rollback path when you leave the lab. |
| Repeatable customer setup | You need the same values every visit. | Save the exact working combination instead of trusting memory. |
Why repeated switching becomes messy
- You remember the IP but forget the mask or gateway.
- One customer's DNS gets left behind in another environment.
- You rebuild the same static setup over and over instead of reusing it.
- Your DHCP fallback is not clearly separated from temporary maintenance setups.
Where IPChange helps
- Save DHCP as an explicit fallback profile.
- Keep static setups named by client, router or lab.
- Switch between known-good profiles instead of retyping values.
- Keep aliases, local static and full static workflows in one place.
FAQ
Is the macOS UI enough for switching between DHCP and static IP?
Yes for occasional changes. The pain starts when the same transitions repeat often and you need to remember multiple working setups.
Should DHCP be saved as a profile too?
Yes. DHCP is often the most important safe state because it gives you a clean reset after static maintenance work.
Can an alias replace static switching?
Sometimes. If you only need one extra local address and want to keep the main setup, an alias may be enough.
Related pages
How to switch between network profiles on Mac
Use this when the repeated switching is really a profile management problem across multiple environments.