WiFi shares its spectrum with every other network in range, which means channel choice directly determines how much of that spectrum a given network actually gets to itself versus competes for. 2.4GHz and 5GHz behave quite differently here — one has barely any room to avoid overlap at all, the other has plenty but introduces its own complexity through channel bonding. This post covers the real mechanics behind both.
2.4GHz: fourteen channels, three that don't overlap
2.4GHz channels are numbered 1 through 14 (channel 14 is Japan-only and rarely relevant), spaced 5MHz apart, but each channel actually occupies roughly 22MHz of spectrum — wider than the spacing between channel numbers. The practical consequence: adjacent channels overlap significantly, and two channels need to be at least 5 apart in number to avoid overlapping at all. In the 1-13 range, only 1, 6, and 11 satisfy that spacing against each other, which is why they're universally recommended — any other combination leaves at least some overlap between your own networks, on top of whatever neighboring networks are already using.
Channel: 1 2 3 4 5 6 7 8 9 10 11 12 13
Overlaps with 1: ███ ██ ██ ██ ██
Overlaps with 6: ██ ██ ██ ██ ███ ██ ██
Overlaps with 11: ██ ██ ███ ██ ██In a dense environment, the right channel isn't necessarily one of 1, 6, or 11 by default — it's whichever of those three has the fewest neighboring networks already on it or close enough to overlap. If all three are already congested, picking the least congested of the three still beats picking arbitrarily.
5GHz: plenty of non-overlapping channels, but bonding complicates it
5GHz allocates far more total spectrum to WiFi, and its 20MHz channels are spaced cleanly enough that they don't overlap at all by default — channels 36, 40, 44, and 48, for instance, are four completely independent 20MHz channels. The complication is channel bonding: to get higher throughput, modern WiFi (802.11ac/ax) combines multiple adjacent 20MHz channels into a single wider one — 40MHz combines two, 80MHz combines four, 160MHz combines eight.
20MHz: [36] [40] [44] [48] [52] [56] [60] [64]
40MHz: [36 40] [44 48] [52 56] [60 64]
80MHz: [36 40 44 48] [52 56 60 64]
160MHz: [36 40 44 48 52 56 60 64]A network configured for 80MHz at "channel 36" is actually occupying the entire 36-40-44-48 range simultaneously, even though routers commonly just display the single anchor number. A neighboring network on "channel 44" at just 20MHz genuinely competes for part of that same spectrum, even though the two channel numbers look completely different.
Why this tool sticks to U-NII-1 and U-NII-2A
Channels 36-64 (U-NII-1 and U-NII-2A) don't require DFS (Dynamic Frequency Selection) to coexist with radar systems, which keeps their bonding behavior simple and consistent — exactly the range most consumer and enterprise access points use indoors by default. Higher 5GHz channels (100-144, 149-165) have additional regulatory constraints and less uniform grouping that vary by region, which is deliberately out of scope for a general-purpose channel planning calculation.
WiFi 6E and the new 6GHz band
WiFi 6E added an entirely new band — 6GHz — specifically to address 5GHz's growing congestion as more devices adopted wider channels. 6GHz offers considerably more spectrum than 5GHz, enough for many more non-overlapping 80MHz and even 160MHz channels simultaneously, without the DFS radar-coexistence requirements that complicate parts of 5GHz. The tradeoff is compatibility: 6GHz requires WiFi 6E or WiFi 7 hardware on both the access point and the client, and (in most regulatory regions) is currently indoor-use-only, which makes it a genuine relief valve for dense environments but not yet a universal replacement for 5GHz planning.
The real-world tradeoff: throughput vs. contention
Wider channels aren't automatically better. An 80MHz or 160MHz channel offers higher theoretical throughput, but it also needs a proportionally larger area of clear spectrum to actually deliver it — in a crowded environment (an apartment building, a dense office), a narrower 20 or 40MHz channel with less contention frequently performs more consistently in practice than a wide channel constantly sharing spectrum with several neighbors.
Seeing what's actually nearby before planning
# Windows
netsh wlan show networks mode=bssid
# macOS
system_profiler SPAirPortDataType
# Linux
nmcli -f SSID,CHAN,SIGNAL dev wifi listPlanning a channel around guesswork defeats the purpose — these commands list every network actually visible from your machine right now, along with the channel each one occupies, which is the real input a channel planning decision should be based on rather than an assumption about what neighbors might be using.
Common mistakes
- Using a 2.4GHz channel other than 1, 6, or 11 out of habit. Any other choice guarantees overlap with at least one of the standard trio.
- Assuming a 5GHz channel number represents only that one 20MHz slice. Bonded channels occupy several channel numbers at once, all of which are unavailable to other networks.
- Defaulting to the widest available bandwidth regardless of environment. Wider channels perform worse, not better, once contention exceeds what the extra spectrum can actually support.
FAQ
Why do most routers default to "Auto" channel selection if manual planning is better?
Auto mode scans for the least congested channel at setup time or periodically, which is a reasonable default for a single router in an environment without much competing WiFi. It falls short in dense environments (apartment buildings, offices with many APs) where conditions change faster than the router rescans, or in multi-AP setups where the APs need to coordinate with each other rather than each independently picking a channel that might conflict with its neighbor.
Can I just set every 2.4GHz network in my house to channel 1, 6, or 11 and call it solved?
That handles interference between your own networks, but not interference from neighboring networks you don't control — in a dense apartment building, several neighbors' routers may already occupy all three of 1, 6, and 11. In that scenario, picking the least-occupied of the three (not just any of the three) is what actually matters, which is exactly the kind of ranking a channel planning tool computes.
Why does 5GHz have so many more usable channels than 2.4GHz?
5GHz simply has far more total spectrum allocated to WiFi than 2.4GHz does, which is also why 5GHz channels don't need the same tight, overlapping spacing 2.4GHz channels do — each 5GHz 20MHz channel is spaced far enough from its neighbors to not overlap at all, unlike 2.4GHz where only three channels out of fourteen achieve that.
Does channel bonding actually double throughput when going from 40MHz to 80MHz?
In ideal, interference-free conditions, wider channels do roughly scale available throughput with bandwidth — but that's specifically the ideal case. In practice, a wider channel also means a larger area of spectrum needs to be free of competing traffic to deliver that full throughput, so the real-world gain shrinks considerably in any environment with other networks nearby.
Should I turn off my 2.4GHz radio entirely and only use 5GHz?
Only if every device that needs to connect supports 5GHz — many smart-home and IoT devices (thermostats, some smart plugs, older printers) are 2.4GHz-only, and 2.4GHz's longer range through walls remains genuinely useful for anything far from the router. Most setups keep both bands active rather than disabling either one.
Try it yourself
WiFi Channel Planner ranks 2.4GHz channels by overlap and computes 5GHz channel-bonding overlap against nearby networks, entirely in your browser.