Skip to content

Best WiFi Channel for Mac: How to Find and Switch

/ 11 min read
macos wifi networking troubleshooting

Slow WiFi with fast internet is usually not your internet.

It is congestion. Your router picked a channel, three neighbors picked the same one, and now all four networks take turns talking over each other. The speed test still shows your full plan when it manages to get a word in. The video call still stutters.

This is fixable in about ten minutes, and it costs nothing.

The short answer

2.4 GHz in the US: use channel 1, 6, or 11. Nothing else.

5 GHz in the US: use 36, 40, 44, or 48 if you want a connection that never drops. Use 149 through 165 if you want the same reliability with more range outdoors. The channels in between work well and are usually emptier, but they carry a catch worth understanding before you pick one.

Everything below is why, and how to check what you are actually on.

Why only three channels on 2.4 GHz

The 2.4 GHz band has 11 usable channels in the US. That sounds like eleven choices. It is three.

Channels are numbered 5 MHz apart, but each one is about 22 MHz wide. Channel 2 overlaps channel 1 and channel 3 and channel 4. Two networks on channels 1 and 3 do not politely share, they interfere, and both get slower than if they had picked the same channel and taken turns properly.

To not overlap, two channels need roughly 25 MHz between them. In a band that only goes to 11, exactly one set works: 1, 6, and 11.

If a neighbor is parked on channel 3, the useful move is not to find a gap next to them. It is to pick whichever of 1, 6, or 11 has the least traffic and accept the partial overlap.

Channels 12 and 13 exist, and if you look at a Mac’s supported channel list you may see them. That list reflects the region your Mac thinks it is in, not what your router may legally use. In the US, the FCC allows 1 through 11. Channel 14 is not permitted at all.

Find the channel your Mac is on

The fast way: Option-click the WiFi icon

Hold Option and click the WiFi icon in your menu bar. The menu expands to show your current channel, signal strength (RSSI), noise, PHY mode, and the BSSID of the access point you are attached to.

No Terminal, no install. This is the right answer for most people.

The Terminal way

If you want the numbers as text, or you want the full neighbor scan:

system_profiler SPAirPortDataType

Under Current Network Information you get your channel, band, and channel width in one line:

Channel: 60 (5GHz, 80MHz)
Signal / Noise: -64 dBm / -94 dBm
PHY Mode: 802.11ax
Country Code: US

Keep scrolling and you reach Other Local Wi-Fi Networks, which lists every network your Mac can hear along with the channel and width each one is using. That is your site survey, free, no sudo, no download.

A warning about older guides

Most WiFi articles written before 2024 tell you to run something like airport -I or airport -s from deep inside a private framework path.

That binary no longer exists. Apple deprecated it and then removed it in macOS 14.4. On the Mac I am writing this on (macOS 26.5, build 25F71), the path returns No such file or directory, and a recursive search of the framework turns up only a sandbox profile. If a guide hands you that command, the guide has not been touched in over two years, and you should weigh the rest of its advice accordingly.

The modern equivalents are system_profiler SPAirPortDataType (works as a normal user) and wdutil info (requires sudo, so it will prompt for your password). Wireless Diagnostics, in the Option-click menu, is the graphical version.

Read the survey and pick

Run system_profiler SPAirPortDataType, scroll to the neighbor list, and count how many networks sit on each channel.

Run it three times. I ran it three times in a row from my desk while writing this and got 20, then 33, then 36 networks. The scan accumulates as the radio hears more beacons, so a single run under-reports, and the emptiest channel in run one may not be empty at all.

What stayed consistent across all three runs is the part you can act on. On 2.4 GHz the traffic clustered on channels 1, 2, and 11. On 5 GHz it clustered on 44, 48, 100, 157, and 161. Nothing was on 36, 40, 149, or 165 in any run, and those are the four I would choose between.

That is the whole decision. Count across a few scans, then move to the channel that is consistently quiet.

Two things worth weighing beyond the count:

  • Signal strength matters more than emptiness. A crowded channel from an access point in the next room usually beats an empty one from three rooms away. RSSI closer to zero is stronger. Around -50 dBm is excellent, -67 dBm is the usual floor for smooth video, and past -75 dBm you are in trouble regardless of which channel you chose.
  • Noise floor tells you if the problem is even WiFi. The gap between signal and noise is your signal-to-noise ratio. In the reading above, -64 dBm signal against a -94 dBm noise floor is a 30 dB margin, which is healthy. If your noise floor is high (say -80 dBm), something non-WiFi in your home is generating interference, and no channel change will fix it. Microwave ovens, older cordless phones, and some baby monitors all sit in the 2.4 GHz band.

The 5 GHz catch nobody mentions

5 GHz has far more channels, and most of them are empty. There is a reason the empty ones are empty.

Channels 52 through 64 and 100 through 144 are DFS channels, shared with weather and military radar. Regulators let WiFi use them on one condition: the moment radar is detected, the network has to get off that channel within ten seconds. Before a router may transmit on a DFS channel at all, it has to listen for one to two minutes to confirm the channel is clear.

In practice, that means a DFS channel can be perfectly fast for weeks and then drop your video call without warning, because an aircraft passed within range of your router. When it happens the router has to sit out the listening period before it can come back.

If you live near an airport, a coastline, or a military installation, avoid DFS entirely. The non-DFS US 5 GHz channels are 36, 40, 44, 48 at the low end and 149 through 165 at the high end.

I want to be precise about one thing: the ten-second vacate rule and the listening period are regulatory requirements, and the dropped-call experience follows from them. Apple does not publish a document describing how macOS behaves during a radar eviction, so treat the user-facing symptom as a well-founded inference rather than a documented Apple behavior.

Channel width

Wider channels carry more data and tolerate less interference. Apple’s own router guidance is specific:

  • 2.4 GHz: 20 MHz. Not 40. A 40 MHz channel on 2.4 GHz eats most of the band and interferes with everything around it, including your other devices.
  • 5 GHz and 6 GHz: Auto, or leave all widths enabled.

If your router offers “20/40/80 MHz auto” on 5 GHz, take it.

Change it on the router, not the Mac

Your Mac does not choose the channel. It follows whatever the access point advertises. The setting lives in your router’s admin page, usually at 192.168.1.1 or 192.168.0.1 in a browser, under Wireless or WiFi settings, listed as Channel.

Set it, save, and let the router restart. Your Mac will reconnect on the new channel. Confirm with Option-click.

One caveat that catches people: many mesh systems and ISP-supplied routers hide the channel setting entirely, or override it. If you cannot find it, that is usually deliberate, and the auto-selection is what you get.

Apple says leave it on Auto

Worth stating plainly, because it contradicts half of this article: Apple’s published recommendation for routers is to set the channel to Auto and let the router pick.

That advice is right for most homes. Modern routers re-scan and re-select periodically, and a router watching its own environment continuously will usually beat a human who set a channel once in 2023 and forgot.

Manual selection earns its keep in two situations. First, when auto-selection keeps landing you on a congested channel, which happens in dense apartment buildings where every router runs the same algorithm and they all reach the same conclusion. Second, when auto keeps parking you on a DFS channel and you are getting periodic unexplained drops.

Check the survey first. If your channel is already clear, the channel is not your problem.

When the channel is not the problem

Changing channels fixes congestion. It does not fix:

  • Distance and walls. Signal below -75 dBm needs a better router position or a mesh node, not a different channel.
  • A slow plan or a busy uplink. Run a wired speed test to separate the WiFi from the internet.
  • Band steering confusion. If your 2.4 and 5 GHz networks have different names, devices get stuck on the slower one. Apple recommends giving all bands the same name for exactly this reason.
  • Old hardware. A device that only speaks 802.11n is going to be slow on any channel, and on some routers it drags the whole network down.

Watching it over time

The awkward part of channel tuning is that the survey is a snapshot. Your neighbor’s router reboots at 3am, lands on your channel, and your afternoon calls get worse for reasons you cannot see. Running system_profiler once tells you about right now.

That is the gap Signal Peek fills. It keeps RSSI, noise, SNR, and the current channel in your menu bar, so a change in conditions is something you notice rather than something you rediscover a week later during a bad call. It is $2.99, one time, no subscription.

If you would rather not install anything, a note in your calendar to re-run the survey every few months does most of the same work.

FAQ

What is the best WiFi channel for a Mac specifically?

There is no Mac-specific answer. The Mac follows the access point. The best channel is whichever of 1, 6, or 11 (on 2.4 GHz) or the non-DFS 5 GHz channels is least crowded where you live, and that is a property of your neighborhood, not your computer.

Is 5 GHz always better than 2.4 GHz?

Not always. 5 GHz is faster and much less crowded, but it passes through walls poorly. 2.4 GHz travels further. In a small apartment, use 5 GHz. In a house with thick walls, 2.4 GHz may be the only band that reaches the far bedroom.

Why does my Mac show channels 12 and 13?

Because it is reporting the channels legal in the region it detects, not the channels your router should use. Mine reports a Country Code of VN and lists 1 through 13. A Mac in the US reports US and lists 1 through 11.

Why does networksetup -getairportnetwork en1 say I am not associated?

It is unreliable on current macOS. On the machine I tested, it reported no association at the same moment system_profiler reported a healthy connection on channel 60. Use system_profiler SPAirPortDataType instead.

Do I need 6 GHz?

Only if you have it. 6 GHz (WiFi 6E) needs both a 6E router and a Mac from 2023 or later, and it is not available in every region. When both ends support it, it is the emptiest band by a wide margin, because almost nothing is on it yet.

How often should I change my channel?

Almost never, if you set it well once and your neighbors are stable. Re-check when something changes: you move, your speed degrades noticeably, or you start getting drops that were not there before.

The short version

Option-click the WiFi icon and note your channel. Run system_profiler SPAirPortDataType and count what your neighbors are on. If your channel is crowded, move to 1, 6, or 11 on 2.4 GHz, or to 36 through 48 on 5 GHz. Set 2.4 GHz width to 20 MHz. Ignore any guide that tells you to run airport, because that command has been gone since macOS 14.4.

If your channel was already clear, the problem is somewhere else, and you have saved yourself from tuning the wrong thing.