How to Fix Sticky WiFi on a Mac: macOS Roaming Settings, Preferred Network Order, and Airport Adapter Tricks for Multi-AP Homes

In a single-router home, your Mac’s WiFi behavior is invisible — there’s only one access point to connect to. But in a multi-AP home with a mesh system or several standalone access points sharing the same SSID, Macs reveal a frustrating trait: they hold on to a weaker access point long after a better one is available. This “sticky client” behavior is built into macOS by design, and understanding exactly how it works is the first step to fixing it.

Why Macs Are Sticky: The Roaming Thresholds

macOS uses a conservative two-condition rule before initiating a roam to a different access point on the same network. Both conditions must be true simultaneously:

• The current access point’s RSSI must drop to –75 dBm or weaker
• The candidate access point must have an RSSI at least 12 dB stronger than the current one

In practice this means your MacBook can be sitting at –73 dBm on a distant AP — video calls stuttering, downloads crawling — while a mesh node three feet away broadcasting –55 dBm is completely ignored. macOS won’t trigger a roam because the current RSSI hasn’t crossed the –75 dBm floor. Apple designed this threshold to prevent constant “roaming storms” where devices ping-pong between APs as the user walks around, but it errs heavily on the side of staying put.

There is no user-accessible slider or System Settings control to change these threshold values. Apple does not expose them in the GUI.

Apple Silicon vs Intel Mac: Roaming Protocol Support

Before adjusting any settings, it’s worth knowing what your Mac’s WiFi chipset can actually do, because the answer differs significantly between generations.

• Mac with Apple Silicon (M1 and later): Supports 802.11k (neighbor reports), 802.11r (fast BSS transition), and 802.11v (BSS transition management). All three roaming-assist protocols are available when the network enables them.
• Intel-based Mac: Supports 802.11k and 802.11v but does not support 802.11r. Fast BSS transition — the protocol that dramatically reduces re-authentication time when switching APs — is unavailable regardless of router configuration.

This distinction matters when you’re troubleshooting an Intel MacBook that roams poorly on a mesh system with 802.11r enabled. The router’s fast roaming feature simply isn’t being used by the Mac, even if every other device on the network benefits from it.

What the Router Needs to Enable Proper Mac Roaming

For an Apple Silicon Mac to use all three roaming protocols, the access point must have the following enabled:

• 802.11k (Neighbor Reports): Lets the Mac request a list of nearby APs with their channel and RSSI data, so it already has candidates ready when a roam is needed. Reduces the scan time before a handoff.
• 802.11r (Fast BSS Transition): Allows the Mac to re-authenticate to a new AP without going through a full 4-way WPA handshake. Cuts handoff time from 50–200 ms down to under 20 ms. Required for seamless roaming during VoIP calls and video conferences.
• 802.11v (BSS Transition Management): Gives the AP the ability to proactively suggest that the Mac move to a better AP — essentially a server-side nudge to get sticky clients moving.
• 802.11w (Protected Management Frames / PMF): Required by the 802.11r specification. 802.11r will not activate without PMF enabled on the SSID. Most modern routers and mesh systems enable PMF automatically when 802.11r is turned on, but if fast roaming seems non-functional, check that PMF is set to “Required” or “Optional” on the SSID.

On most mesh systems — eero, TP-Link Deco, ASUS ZenWiFi, and Netgear Orbi — these protocols are enabled by default and cannot be individually toggled. On standalone access points running OpenWrt, DD-WRT, or Ubiquiti UniFi, you can verify and enable each protocol explicitly in the wireless settings. For a deeper look at how 802.11r cuts handoff latency, see our 802.11r fast BSS transition guide.

Fixing Preferred Network Order in macOS

macOS maintains a list of known WiFi networks and connects to them in a stored priority order. In earlier macOS versions you could drag networks in the preferred list to re-order them. That drag interface was removed in macOS Ventura (macOS 13) and has not returned as of macOS Sequoia.

The current workaround is to rebuild the preferred list in the order you want:

1. Open System Settings → Wi-Fi
2. Click the three-dot menu (…) next to each network you want to de-prioritize and select Forget This Network
3. Re-join the networks in your preferred priority order — the most recently joined network moves to the top

This matters most when you have separate SSIDs for different bands or different routers. If your home has both a mesh SSID and an older standalone router SSID, macOS will join whichever it learned most recently unless you re-order them.

You can also use the Network Service Order panel (System Settings → Network → click the three-dot menu next to a service → Set Service Order) to control which network interface — Ethernet, WiFi, VPN — takes priority overall, though this does not control which SSID is preferred within WiFi itself.

The Airport Utility Command: joinMode=Strongest

macOS includes a private command-line tool — the airport binary — that can change how the WiFi driver selects APs when multiple options are available. The relevant command is:

sudo /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport prefs joinMode=Strongest

Setting joinMode=Strongest instructs the WiFi driver to always prefer the AP with the best current RSSI, rather than the default behavior of staying with whatever AP it is already associated to. Other available values include Automatic (default), Preferred, Ranked, and Recent.

Important caveats: The airport binary is part of a private framework and is not officially supported by Apple. Its availability varies across macOS versions — it is present on many Intel Macs running Monterey and Ventura, and on some Apple Silicon systems, but Apple has begun removing it from newer macOS builds. Before relying on this command, verify the binary exists at the path above. Also note that joinMode=Strongest can increase roaming frequency, which causes brief interruptions during handoffs — it’s most useful for stationary Macs that are simply too far from the router and stuck on a weaker AP, not for roaming users who would experience more frequent disconnections.

When to Manually Trigger a Roam

If you just need a one-time fix without changing persistent settings, the fastest method is to toggle WiFi off and back on. This forces a fresh AP scan and association, and macOS will connect to whichever AP is strongest at that moment. On a MacBook with the menu bar WiFi icon visible, hold Option and click the WiFi icon to see the RSSI, channel, and BSSID of the currently connected AP — this is the fastest way to confirm which node you’re actually connected to and whether it’s the right one.

For a more surgical approach without dropping the connection entirely, you can use the airport tool to disassociate from the current BSSID: sudo airport -z. The Mac will then re-associate to the strongest available AP with the matching SSID.

The Most Reliable Long-Term Fix

The combination that produces the best Mac roaming behavior in a multi-AP home is:

• A mesh system with 802.11k, 802.11r, and 802.11v enabled (most modern mesh systems handle this automatically)
• A Mac with Apple Silicon to take advantage of all three protocols
• Mesh nodes placed so that RSSI overlap between nodes is 15–20 dB — enough that the candidate AP always clears the 12 dB advantage threshold before the Mac drops below –75 dBm on the current one
• PMF enabled on the SSID to allow 802.11r to function

Proper node placement is the most underappreciated fix. If nodes are too far apart, your Mac will be at –60 dBm on the current node before the next node is even in range at –72 dBm — not enough of a gap to trigger a roam. Tightening node spacing so the handoff zone falls at –65 to –70 dBm on the departing node — where the arriving node is already at –50 to –55 dBm — gives macOS the signal advantage it needs to roam cleanly. For guidance on where to put mesh nodes, see our mesh node placement guide. If sticky-client issues affect other device types beyond Mac, our WiFi client roaming aggressiveness guide covers the AP-side and client-side settings for Windows, Android, and iOS as well.