Channel Width in 802.11ac

Channel width is the single 802.11ac setting that most directly trades throughput against range and coexistence. The IEEE amendment that defines 802.11ac explains its purpose as improving the wireless LAN user experience by providing significantly higher basic service set throughput, and enabling new market segments below 6 GHz, including distribution of multiple multimedia and data streams (https://standards.ieee.org/ieee/802.11ac/4473/). Wider channels are one of the main tools that make that throughput possible, and the same mechanism creates the coexistence problems operators see in dense deployments.

What does channel width mean in 802.11ac?

Channel width is how much radio spectrum a single transmission occupies. In 802.11ac, the practical options are 20, 40, 80, and 160 MHz. A 40 MHz channel uses two adjacent 20 MHz blocks, an 80 MHz channel uses four, and a 160 MHz channel uses eight. The access point and client negotiate a width both can support, then the transmitter sends one wider signal instead of several narrow ones. Wider channels carry more data per symbol period, which is why vendors advertise far higher rates with 80 MHz than with 20 MHz.

How does wider channel width increase throughput?

Throughput rises roughly in proportion to width when signal quality is good. Doubling the width doubles the number of usable subcarriers, so the same modulation and coding scheme delivers roughly twice the data rate in one transmission opportunity. Alongside 256 QAM and multiple spatial streams, wider channels are one of the levers 802.11ac uses to deliver the very high throughput the amendment was written for (https://standards.ieee.org/ieee/802.11ac/4473/). The catch is that this gain is only realised when the client has a strong, clean signal.

What happens to range and reliability as width grows?

Wider channels lose range. When the same transmit power is spread across more spectrum, energy per hertz falls, so the signal-to-noise ratio at the receiver drops at a given distance. Noise also scales with width: an 80 MHz channel collects roughly four times the noise power of a 20 MHz channel, and a 160 MHz channel roughly eight times. Clients at the cell edge often do better on 20 or 40 MHz than on 80 MHz, because a narrower channel keeps a higher modulation and coding scheme usable.

Why does channel width matter for coexistence?

Because 5 GHz spectrum is finite. An 80 MHz channel consumes four of the twenty or so non-overlapping 20 MHz blocks available in many regulatory domains, and 160 MHz consumes eight. Every wide channel leaves fewer independent channels for neighbouring access points. That pushes co-channel interference up and forces airtime sharing, so a network of wide-channel APs can deliver worse aggregate throughput than a well-planned set of narrower channels. DFS radar detection also removes entire wide blocks at once when a pulse is detected anywhere inside them.

When should you use 20, 40, 80, or 160 MHz?

A simple decision checklist helps:

• Use 20 MHz for high-density venues, IoT-heavy floors, and any environment where many APs hear each other.
• Use 40 MHz for general office coverage and for clients that sit at moderate range.
• Use 80 MHz in low-density areas, in single-AP homes and small offices, and where a clean block of spectrum is available.
• Use 160 MHz only where the spectrum is genuinely clear, typically one or two links in a small, isolated space.
• Match the AP setting to the client base. Legacy devices that do not support a width will fall back, but the AP still occupies the wider block.

Setting	Relative throughput	Noise collected	Spectrum used	Good fit
20 MHz	Baseline	Lowest	1 block	Dense offices, venues, IoT
40 MHz	About 2x	About 2x	2 blocks	General office, mixed clients
80 MHz	About 4x	About 4x	4 blocks	Low density, small sites
160 MHz	About 8x	About 8x	8 blocks	Isolated, clean spectrum only

The figures are ratios that follow from how many 20 MHz blocks each width occupies, not measured test results.

How should you plan channels in practice?

Start with a site survey rather than a default. Detect which 20 MHz blocks are actually free, then group them into the widest contiguous runs that do not collide with neighbouring APs. On a multi-AP floor, a common pattern is 20 or 40 MHz for most cells and 80 MHz for one or two cells that serve high-demand clients. If you are committing to wide channels, the surrounding architecture has to keep up: APs that saturate a 1 GbE uplink cannot pass through an 80 MHz PHY rate. Our guide on choosing 802.11ac hardware covers uplink and radio choices, and wireless planning for offices walks through coverage and capacity design.

What about 160 MHz and legacy devices?

160 MHz is where 802.11ac shares DNA with later generations. Wi-Fi 6 and Wi-Fi 7 keep 80 and 160 MHz as core widths, and Wi-Fi 7 adds 320 MHz positioning support in a later amendment (https://standards.ieee.org/ieee/802.11ac/4473/). If a network is likely to be upgraded, aligning on 80 MHz now leaves room to widen later. Legacy clients that only support 20 or 40 MHz still operate, but mixed client populations reduce the benefit of wide channels because airtime is shared. See legacy devices on 802.11ac networks for how to handle that mix.

Where can you confirm certified capability?

Wi-Fi CERTIFIED 5 is the interoperability programme associated with 802.11ac, and it exists to give buyers confidence that devices interoperate. Certification does not guarantee that a given product supports 160 MHz, however. Check the datasheet for the supported widths, then verify behaviour in the field. Regulatory limits on allowed bandwidth, transmit power, and DFS vary by country, so consult current official guidance from your national regulator before finalising channel plans. If you are weighing generations, 802.11ac vs Wi-Fi 6: what changed and 802.11ac vs Wi-Fi 7: upgrade decisions cover the trade-offs.