Why Won't My Mac Connect to Wi-Fi? Common Causes and How to Fix Them
Few things are more frustrating than a Mac that refuses to connect to Wi-Fi — especially when every other device on the same network works fine. The good news is that most Mac Wi-Fi problems follow recognizable patterns, and understanding those patterns makes troubleshooting far more effective than restarting and hoping for the best.
What's Actually Happening When Your Mac Won't Connect
Your Mac connects to Wi-Fi through a layered process: the wireless hardware (Wi-Fi chip) detects available networks, macOS networking software negotiates the connection, your router assigns an IP address via DHCP, and finally traffic routes out to the internet. A failure at any one of these layers produces the same symptom — no connection — but requires a completely different fix.
This is why "Wi-Fi not working" can mean a dozen different things depending on where the breakdown is happening.
The Most Common Causes
1. A Stale or Corrupted Network Configuration
macOS stores saved Wi-Fi network profiles, and these can become corrupted or outdated — especially after a macOS update or a router change. Your Mac thinks it knows how to connect, but the stored credentials or settings no longer match what the network expects.
What to try: Forget the network entirely (go to System Settings → Wi-Fi → the network name → Forget This Network), then reconnect from scratch by entering the password manually.
2. IP Address Conflicts or DHCP Failures
Every device on your network needs a unique IP address, assigned automatically by your router's DHCP server. Sometimes a Mac gets stuck with an expired lease, a conflicting address, or fails to receive one at all — which means it connects to Wi-Fi but can't actually communicate on the network.
You'll often see this as "Connected" in your Wi-Fi menu but no internet access, or an IP address starting with 169.254.x.x (a self-assigned address, which signals a DHCP failure).
What to try: Go to System Settings → Network → Wi-Fi → Details → TCP/IP and click Renew DHCP Lease.
3. DNS Problems
Even with a valid IP address, your Mac might struggle to resolve domain names — translating URLs like google.com into the actual server addresses it needs to reach. DNS failures usually look like pages that won't load even though the connection appears active.
What to try: Switch your DNS to a public resolver like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) temporarily to see if that resolves the issue.
4. Router or Modem Issues
The problem isn't always on your Mac. Routers can get overloaded, develop firmware bugs, or simply need a reset. If multiple devices are having trouble, or if the connection drops regularly at certain times of day, the router itself is the more likely culprit.
What to try: Power-cycle your router and modem — unplug both for 30 seconds, restart the modem first, wait for it to fully come online, then restart the router.
5. Wi-Fi Interference and Signal Problems 📶
2.4 GHz and 5 GHz are the two main Wi-Fi bands. The 2.4 GHz band travels farther but is more congested; the 5 GHz band is faster and less crowded but has shorter range. If your Mac is connecting to the wrong band for its location — or if there's heavy interference from neighboring networks, microwaves, or Bluetooth devices — you can get an unstable or unusable connection even with full signal bars.
macOS sometimes holds onto a weak or congested connection rather than switching to a better one.
6. macOS Software or Driver Issues
After major macOS updates, Wi-Fi behavior occasionally changes — sometimes for the worse. Apple's wireless drivers and network stack can develop bugs that affect certain hardware configurations. Symptoms tend to be intermittent disconnections, slow speeds, or complete failure on specific networks.
What to try: Check if other users are reporting the same issue after a recent update. A supplemental update from Apple often addresses these within weeks.
7. Hardware Problems
If none of the software fixes work, the Wi-Fi hardware itself may be at fault. This could be a failing Wi-Fi card, a loose antenna connection (more common after a drop or repair), or in some cases, a known hardware defect. Apple has issued repair programs for specific Mac models with documented Wi-Fi issues — worth checking if your machine is older.
Factors That Affect Which Fix Works for You
| Variable | Why It Matters |
|---|---|
| macOS version | Bugs introduced in specific releases affect certain fixes |
| Mac model and age | Older hardware may have different failure modes |
| Router brand/firmware | Some routers handle macOS DHCP/DNS differently |
| Network type (home, office, public) | Authentication methods and security settings vary |
| Distance from router | Determines whether band-switching helps |
| Recent changes (update, move, new router) | Often points directly to the cause |
A Logical Order for Troubleshooting
Rather than trying fixes at random, working through the stack methodically saves time:
- Confirm the router is the problem or isn't — check other devices
- Restart Mac and router — clears transient software states
- Forget and rejoin the network — eliminates corrupted profiles
- Renew DHCP lease — fixes IP assignment issues
- Check DNS settings — resolves name resolution failures
- Create a new Network Location (System Settings → Network → Location dropdown) — resets network configuration cleanly
- Delete Wi-Fi preference files — deeper config reset for persistent issues
- Boot into Safe Mode — tests whether third-party software is interfering
- Run Apple Diagnostics — checks for hardware faults
What Makes This Harder to Diagnose Than It Looks
The same symptom — "won't connect" — can come from completely different layers of the system. A fix that works immediately on one Mac may do nothing for another with what looks like an identical problem, because the underlying cause is different.
macOS version, router firmware, network environment, and even how long the Mac has been in use all shift which solutions are most likely to work. Two people with the same Mac model on the same network can have different experiences after the same update.
That's what makes a blanket fix impossible — the details of your specific setup determine which part of that stack actually broke, and that's the piece only you can see from where you're sitting.