WiFi 5 GHz Channel Bonding Explained: How 40, 80, and 160 MHz Channel Widths Affect Speed, Range, and Interference

Your router probably defaults to “20/40/80 MHz Auto” and most people never touch it. But channel width — also called channel bonding — is one of the few router settings that has a direct, measurable impact on real-world throughput. Set it too narrow and you leave peak speed on the table. Set it too wide and you amplify interference, shrink effective range, and force your router onto radar-sharing channels that can drop your connection without warning. Here’s exactly what each width does and which setting belongs in your home.

What Is Channel Bonding?

The 5 GHz band is divided into 20 MHz-wide channels — the fundamental unit of WiFi spectrum. Channel bonding combines adjacent 20 MHz channels into a single, wider logical channel. A 40 MHz channel bonds two 20 MHz channels together; an 80 MHz channel bonds four; a 160 MHz channel bonds eight. The wider the bond, the more data can travel in a single transmission.

Speed scales roughly linearly with width: going from 20 MHz to 40 MHz doubles the theoretical maximum data rate. From 40 MHz to 80 MHz doubles it again. And from 80 MHz to 160 MHz doubles it once more. A 2×2 WiFi 6 device on a single 20 MHz channel maxes out at about 287 Mbps link rate. The same device on 160 MHz can hit 2,401 Mbps. The catch is that wider channels come with significant trade-offs in range, interference, and channel availability.

How Each Width Performs in Practice

20 MHz

Twenty megahertz is the smallest option and the most interference-resistant. It occupies only one channel, so it can find a clean slice of spectrum even in dense apartment buildings with dozens of competing networks. Range is maximized because the transmit power is concentrated in a narrow band rather than spread thin. The cost is pure throughput: 20 MHz caps a 2×2 WiFi 6 connection at 287 Mbps link rate, which is plenty for web browsing and video calls but a bottleneck for local file transfers or 4K streaming over WiFi from a NAS. Use 20 MHz only on the 2.4 GHz band, where it is essential — on the 5 GHz band, 20 MHz is excessively conservative for nearly every home environment.

40 MHz

Forty megahertz bonds two adjacent 20 MHz channels and roughly doubles throughput to around 570 Mbps maximum link rate for a 2×2 client. It was the default for WiFi 5 (802.11ac) and remains a solid choice for 5 GHz in congested environments where 80 MHz picks up too much interference. On the 5 GHz band, there are enough non-DFS channels to run 40 MHz without triggering radar avoidance on most routers. If your building is packed with WiFi networks and 80 MHz seems unstable, dropping to 40 MHz is a reasonable compromise.

80 MHz

Eighty megahertz is the most common 5 GHz setting for modern routers and the best balance of speed and reliability for most homes. It bonds four 20 MHz channels and supports link rates of 867 Mbps (WiFi 5, 1×1) to 2,402 Mbps (WiFi 6, 4×4). In practice, a typical 2×2 WiFi 6 laptop on 80 MHz achieves 1,201 Mbps link rate and real-world TCP throughput of 700–900 Mbps under good conditions. The 5 GHz band has enough spectrum to fit three non-overlapping 80 MHz channels in the UNII-1 through UNII-3 blocks, which means 80 MHz can still find a channel that doesn’t overlap with a specific neighbor’s network in many suburban environments. This is why nearly every WiFi 5 and WiFi 6 router defaults here.

160 MHz

One hundred sixty megahertz doubles 80 MHz throughput on paper — a 2×2 WiFi 6 device reaches 2,401 Mbps link rate — but it comes with significant practical constraints on the 5 GHz band. The entire 5 GHz spectrum usable by consumer routers can only fit two non-overlapping 160 MHz channels, and both of them span DFS channels. DFS (Dynamic Frequency Selection) is a regulatory requirement: when a router detects radar signals (from weather stations, aircraft systems, or military installations) on a DFS channel, it must vacate immediately and remain silent for 30 minutes. Affected users see a brief connection drop or a forced fallback to 80 MHz — unpredictable in timing and location-dependent in frequency. Real-world file transfer testing shows speeds jumping from 100–120 MB/s on 80 MHz to 190–220 MB/s on 160 MHz when conditions are ideal. Whether those conditions hold — no DFS radar events, no overlapping neighbor network, and a device that actually supports 160 MHz — determines whether 160 MHz delivers on its promise.

Device Compatibility for 160 MHz

Not every client device supports 160 MHz on the 5 GHz band, and the list of devices that do has important gaps. Many older iPhone models (pre-iPhone 14) cap out at 80 MHz. Android phones vary widely by chipset: Qualcomm Snapdragon flagships generally support 160 MHz; budget and mid-range models often do not. On the laptop side, most Intel Wi-Fi 6 (AX200, AX210) adapters support 160 MHz on 5 GHz when the driver is configured correctly, but check Windows Device Manager under the adapter’s advanced properties to confirm the setting is available. If a device connects at 80 MHz even when your router is set to 160 MHz, the device is the limiting factor and the wider channel provides no benefit for that connection. See our client upgrade guide for a rundown of which devices support which maximum widths.

The Noise Floor Problem

Wider channels increase the noise floor. Every doubling of channel width adds roughly 3 dB of thermal noise power. Compared to a 20 MHz channel, an 80 MHz channel raises the noise floor by 6 dB, and a 160 MHz channel raises it by 9 dB. In practice, this means the signal-to-noise ratio (SNR) at a given distance is worse on wider channels. A device that connects cleanly at −65 dBm signal on 80 MHz might drop link rate significantly on 160 MHz because the noise floor rose enough to push SNR below the threshold required for the highest MCS rates. If your client is more than a room away from the router, 80 MHz may actually deliver more consistent throughput than 160 MHz because it holds its MCS rate more reliably at moderate signal levels. Our SNR explainer digs into the dBm numbers in detail.

Channel Bonding and Interference in Dense Environments

In an apartment building or dense neighborhood, wider channels magnify interference. An 80 MHz channel overlaps with four 20 MHz channels; a 160 MHz channel overlaps with eight. Every neighbor running WiFi on any of those overlapping channels becomes a source of co-channel or adjacent-channel interference. Running the WiFi analyzer app on your phone before changing channel width is a worthwhile 2-minute investment: if the 5 GHz spectrum is saturated with a dozen or more networks in your building, dropping from 80 MHz to 40 MHz can actually improve real-world throughput by reducing the interference you pick up. For a full guide on diagnosing and resolving crowded-channel problems, see our piece on fixing WiFi congestion in shared apartments.

How to Change Channel Width on Common Routers

TP-Link (Archer series)

Log into the admin panel at 192.168.0.1, navigate to Wireless › Wireless Settings › 5 GHz, and find the Channel Width dropdown. Options typically include Auto (20/40/80), 80 MHz, 40 MHz, and 20 MHz. Select 80 MHz for the most predictable behavior.

ASUS routers

Go to Wireless › Professional › 5 GHz tab and locate the Control Channel and Channel Bandwidth settings. ASUS exposes both 160 MHz and 80+80 MHz options on supported models. Note that 80+80 MHz uses two non-contiguous 80 MHz blocks, which avoids DFS channels on some configurations but is less widely supported by client devices than a contiguous 160 MHz channel.

Netgear Nighthawk / Orbi

In the admin UI at 192.168.1.1, go to Advanced › Advanced Setup › Wireless Settings. Select the 5 GHz band and adjust the Mode or Channel Width option. Older Nighthawk models show the channel width as part of the mode selection (e.g., “Up to 1733 Mbps” corresponds to 80 MHz).

eero

eero does not expose manual channel width settings to end users. The system automatically selects channel widths based on real-time conditions, which is one reason eero routers rarely match the peak throughput benchmarks of manually configured competitors but tend to maintain consistent performance over time.

Which Width Should You Use?

For the vast majority of home networks, 80 MHz on the 5 GHz band is the right setting. It delivers three to four times the throughput of 40 MHz, uses DFS channels only partially (leaving non-DFS options available), and is supported by virtually every 5 GHz-capable client device manufactured since 2016. Save 160 MHz for specific high-throughput use cases: local file transfers to a NAS, wireless 4K video editing, or a home environment where you have verified no neighbors are competing on the same spectrum. If you’re seeing inconsistent performance after setting 160 MHz, DFS radar interference is the most common culprit — check your router’s system logs for “DFS event” or “channel switch” entries to confirm. For a step-by-step guide on reading those logs, see our piece on how to read router system logs. Once your router settings are dialed in, run a speed test to confirm you’re getting the throughput you’re paying for.