UniFi channel width: 20, 40, 80, 160, 320 MHz — what to set on 2.4, 5, and 6 GHz

A compact summary, before the detail. Each row is expanded in the section that follows.

The table is the short answer. The next four sections are the reasoning, band by band, plus a note on channel utilization (which is the metric that tells you whether your channel plan is actually working) and the UniFi-specific settings to change.

The spectrum

The 2.4 GHz band in the United States runs from 2.400 GHz to 2.4835 GHz — 83.5 MHz of spectrum in total. The IEEE 802.11 standard places channel centres every 5 MHz, but each channel is 20 MHz wide, which is why most channels overlap. In the US, only channels 1, 6, and 11 are far enough apart not to spectrally overlap one another. Cisco Meraki's channel planning best-practices documentation states this directly: “In the United States, channels 1 through 11 are permitted. This provides three non-overlapping channels 1, 6 and 11.”³

Why 40 MHz on 2.4 GHz is the wrong setting

A 40 MHz channel on 2.4 GHz consumes two adjacent 20 MHz channels — for example, the 40 MHz channel centred at channel 3 spans channels 1 through 5, and the 40 MHz channel centred at channel 9 spans channels 7 through 11. In a single-household-in-a-field deployment, this is fine. In any environment where another household's Wi-Fi network is within range — which is essentially every urban, suburban, and apartment-building install — bonding to 40 MHz erases the three-channel plan and forces every neighbouring network to share airtime on overlapping spectrum.

This is industry-consensus guidance. HPE Aruba Networking's deployment documentation recommends 20 MHz channel width as the default for the 2.4 GHz band in large public-venue deployments, and notes that the limited number of non-overlapping channels in the band is itself the reason.⁶ Cisco Meraki's position is the same. Ubiquiti doesn't mark 40 MHz as a hard error in the UI — it's an option — but the residential audit answer is to leave 2.4 GHz at 20 MHz.

What 2.4 GHz is actually for

Modern Wi-Fi clients have moved overwhelmingly to 5 GHz and 6 GHz for throughput-heavy work. The residential role of 2.4 GHz now is the long-tail of legacy devices: older smart-home hubs, IoT devices that don't support 5 GHz, range-extending Wi-Fi cameras, occasional outdoor coverage where 2.4 GHz's better propagation matters. The right setting is one AP — usually the central one in a multi-AP house — broadcasting 2.4 GHz at 20 MHz, with 2.4 GHz disabled on the other APs to avoid the multi-AP version of the same overlap problem.

Channel selection

Pick one of 1, 6, or 11. In a single-AP household, whichever is least congested at the install location (a Wi-Fi-Analyzer scan on a phone takes thirty seconds and resolves this immediately). In a multi-AP house where two or more APs need to carry 2.4 GHz, use 1, 6, and 11 across them — never two APs on adjacent channels.

The four sub-bands

The 5 GHz Wi-Fi band in the United States is split into four sub-bands by the FCC, commonly labelled U-NII-1 through U-NII-3 (the names come from FCC terminology and Wi-Fi industry convention; 47 CFR §15.407 sets the underlying technical rules):

• U-NII-1 — 5.150–5.250 GHz, channels 36 / 40 / 44 / 48. No DFS, indoor and outdoor permitted.
• U-NII-2A — 5.250–5.350 GHz, channels 52 / 56 / 60 / 64. DFS required.
• U-NII-2C — 5.470–5.725 GHz, channels 100 / 104 / 108 / 112 / 116 / 120 / 124 / 128 / 132 / 136 / 140 / 144. DFS required.
• U-NII-3 — 5.725–5.850 GHz, channels 149 / 153 / 157 / 161 / 165. No DFS.

That is roughly 25 non-overlapping 20 MHz channels — a comfortable amount of spectrum on paper. In practice, most of those channels are inside DFS sub-bands, which changes the picture.

What DFS actually is

DFS — Dynamic Frequency Selection — is the regulatory requirement that Wi-Fi access points sharing spectrum with weather and military radars must listen for radar pulses and immediately vacate the channel if they detect one. Cisco Meraki's documentation states the rule plainly: “APs operating on UNII-2 channels are required to use Dynamic Frequency Selection (DFS) to avoid interfering with radar signals. If an AP detects a radar signal, it must immediately stop using that channel and randomly pick a new channel.”³ The practical implications for a home network:

• A DFS channel can disappear without warning if the AP perceives a radar event — every client on that SSID has to reassociate to a new channel.
• Some client devices (especially older IoT and some cars) refuse to scan DFS channels at all, so an SSID parked on a DFS channel becomes invisible to them.
• Coastal areas near airports, weather-radar installations, and major military bases see many more false-positive DFS events than inland areas. In some neighbourhoods DFS channels are essentially unusable.

The 80 MHz vs 160 MHz decision

The 5 GHz band in the US supports several non-overlapping 80 MHz channels but only two contiguous 160 MHz blocks — channel 50 (covering channels 36–64) and channel 114 (covering channels 100–128). Both 160 MHz blocks include DFS channels. That is the spec-precise version of the rule of thumb that “160 MHz on 5 GHz always crosses DFS in the US.”

For a residential network, the practical answer is 80 MHz on 5 GHz. The reasoning:

• 80 MHz is enough to clear a few hundred Mbps per spatial stream on a modern Wi-Fi 6 client — fast enough that the wire (or the laptop's onboard radio) is the new bottleneck.
• 80 MHz gives the AP four non-overlapping channels to choose from in a multi-AP house — enough to keep adjacent APs off the same spectrum.
• 160 MHz requires accepting the DFS risk, and the uplift in real-world residential throughput rarely justifies the trade.

The case for 160 MHz on 5 GHz exists, but it's narrow: a single-AP home, no DFS-averse clients, inland, with a gigabit-plus internet plan and one or two heavy users actively pulling throughput. For anyone else, 80 MHz is the right setting.

Channel selection on 5 GHz

If DFS is workable in the neighbourhood, the residential picks at 80 MHz are channel 36 (UNII-1), channel 52 (UNII-2A, DFS), channel 100 or 116 (UNII-2C, DFS), or channel 149 (UNII-3). If DFS isn't workable — near an airport, near a coastal weather radar, or with a roster of clients that refuse DFS — then 80 MHz on channels 36 (UNII-1) or 149 (UNII-3) are the two non-DFS options. A multi-AP house with both clear non-DFS 80 MHz blocks is comfortable; a multi-AP house that needs to add a third or fourth AP without DFS has already exhausted the non-DFS spectrum and is forced onto narrower widths or accepting DFS.

How 6 GHz got opened

On 23 April 2020 the Federal Communications Commission adopted a Report and Order — FCC 20-51 — that, in the Commission's own words, “makes 1200 megahertz of spectrum available for unlicensed use in the 6 gigahertz (GHz) band (5.925-7.125 GHz).”⁴ That single decision more than doubled the spectrum available to Wi-Fi worldwide and is the regulatory foundation underneath Wi-Fi 6E (2021) and Wi-Fi 7 (2024). The 6 GHz band is divided into four sub-bands:

• U-NII-5 — 5.925–6.425 GHz (500 MHz)
• U-NII-6 — 6.425–6.525 GHz (100 MHz)
• U-NII-7 — 6.525–6.875 GHz (350 MHz)
• U-NII-8 — 6.875–7.125 GHz (250 MHz)

Crucially, there is no DFS in the 6 GHz band. The incumbents are point-to-point microwave links and fixed satellite services, not radars, and the interference-protection mechanism is a different one — Automated Frequency Coordination — that applies only to the higher-power class of 6 GHz APs (Standard Power), not to the indoor consumer class.

Three power classes

• Low Power Indoor (LPI) — the class every residential consumer 6 GHz AP falls into. No AFC required; restricted to indoor use only; lower EIRP than Standard Power. This is what the U7 Pro, U7 Pro Max, U7 Pro XGS, and similar UniFi APs ship as by default.⁴
• Standard Power (SP) — outdoor-capable 6 GHz APs that report their location to an AFC service and receive a list of allowed frequencies and power levels in return. Designed for enterprise / outdoor / building-to-building use. Operates only in U-NII-5 and U-NII-7.⁴
• Very Low Power (VLP)— added by the FCC's October 2024 expansion order, allowing small mobile devices to use 6 GHz outdoors at up to 14 dBm EIRP without AFC. Body-worn AR / VR applications and similar.⁵

Channel width on 6 GHz

Because there is so much fresh spectrum and no DFS risk to negotiate, the trade-off that constrains 5 GHz simply doesn't apply on 6 GHz. The residential answer for Wi-Fi 6E APs is 160 MHz; for Wi-Fi 7 APs the answer is 320 MHz — Wi-Fi 7's headline channel-width mode, doubling the previous maximum.

The reasons go in the right direction this time. 6 GHz has enough room for multiple non-overlapping 160 MHz channels across the four U-NII sub-bands, and channels are positioned to align with Preferred Scanning Channels — PSCs — every 80 MHz, so client discovery remains efficient regardless of the operating width.

Range trade-off

The one thing 6 GHz costs is range. The 5.925–7.125 GHz frequencies attenuate more aggressively in air and through building materials than 2.4 GHz or 5 GHz, so a 6 GHz signal that's strong in the room may not reach the next room over. The residential shape of this is: 6 GHz is the right band for the primary device in the room with the AP, and 5 GHz remains the workhorse for everything else.

What it is

Channel utilization is the fraction of time the air on a given channel is in use by any Wi-Fi traffic — yours, your neighbour's, anyone's. Wi-Fi uses a shared-medium protocol called CSMA/CA (Carrier-Sense Multiple Access with Collision Avoidance): every transmitter listens before it transmits, and if the channel is already busy, it waits. That means a neighbour's busy network directly subtracts from yours, even though the two networks are otherwise unrelated.

What the numbers mean

Industry guidance from Cisco, Aruba, and similar enterprise Wi-Fi vendors broadly treats channel utilization above roughly 50% as the point where Wi-Fi performance starts to degrade noticeably. Above 70-80%, the channel is effectively saturated — new connections fail to negotiate, voice and video calls begin to drop, and observed throughput collapses well before the PHY rate would suggest. There is no single authoritative cross-vendor threshold; the practical shape is that 30% feels great, 60% feels slow, and 80% feels broken.

What residential users see

In a UniFi installation, channel utilization is the clearest evidence of a wrongly-chosen channel width or a wrongly-chosen channel number. On a 2.4 GHz radio set to 40 MHz in a typical apartment building, the observed channel utilization frequently sits above 70% even when the home's own traffic is light — the neighbours' networks are filling the air. Dropping to 20 MHz and moving to the least congested of channels 1, 6, or 11 routinely halves the observed number.

The UniFi Network application surfaces channel utilization per radio in the AP details view, and Channel AI (introduced in UniFi Network 9.5 on 13 October 2025) explicitly uses the metric as the input to its automated planning.²

Per-radio channel and width

In the UniFi Network application, the path is UniFi Devices → [select the AP] → Settings → Radios. Each of the AP's three radios — 2.4 GHz, 5 GHz, and 6 GHz on Wi-Fi 6E / 7 hardware — exposes a Channel dropdown and a Channel Width dropdown. Auto is the default for both. The residential audit answer is to set them explicitly per the table at the top of this article: 20 MHz on 2.4 GHz, 80 MHz on 5 GHz, 160 MHz (or 320 MHz on Wi-Fi 7) on 6 GHz.

Disabling 2.4 GHz on most APs

In a multi-AP house, the cleanest residential setup is to leave 2.4 GHz enabled on a single central AP and disable the 2.4 GHz radio on the others. On each AP, under Radios → 2.4 GHz, set the radio to Disabled. This eliminates the multi-AP version of the channel-overlap problem on 2.4 GHz and consolidates legacy / IoT clients onto a single broadcaster.

Channel AI

UniFi Network 9.5, released on 13 October 2025, introduced Channel AI — Ubiquiti's automated channel-planning feature. The release blog states it gives administrators “a fast way to evaluate and improve their WiFi channel plans,” and that it “can generate a complex channel plan in a matter of minutes, rather than days of trial-and-error.”² It runs from the Insights section of the Network app and considers neighbour conditions and observed channel utilization across the whole site.

Channel AI is analogous in purpose to Cisco's Radio Resource Management (RRM) and Aruba's Adaptive Radio Management (ARM) — automated picking of channels and power levels based on what the APs can hear of one another and of neighbouring networks. For a residential home it's a reasonable starting point; it does not, however, override the band-by-band guidance in this article — if Channel AI picks 40 MHz on 2.4 GHz in a dense building, the right move is still to lock 2.4 GHz to 20 MHz.

• The “20 MHz on 2.4 GHz” guidance is industry-consensus but not vendor-uniform policy. Aruba and Cisco Meraki both recommend 20 MHz as the default for the band; UniFi permits 40 MHz as an option. The residential audit answer is 20 MHz, and the reasoning above is defensible, but a single-house-in-a-field setup is the one place where 40 MHz on 2.4 GHz can make sense.
• The “~50% channel utilization is the congestion threshold” framing is industry folklore, not a single canonical citation. Different vendors use slightly different thresholds — Aruba documentation references 50% as a useful airtime ceiling for mixed-use WLANs; community Cisco discussions tend to use 70-80% as the saturation point. The shape of the rule is the same across vendors; the exact cut-off is not standardised.
• The 6 GHz channel count is not a single number. The full 5.925–7.125 GHz band contains roughly 59 contiguous 20 MHz channels, but only U-NII-5 and U-NII-7 are usable by Standard Power devices, so the count available to a Standard Power outdoor AP is smaller. For Low Power Indoor APs — which is what every residential UniFi 6 GHz AP is — the entire band is in scope.⁴
• 5 GHz 160 MHz is not impossible — it's trade-off-laden. The two contiguous 160 MHz blocks in the US 5 GHz band (channels 50 and 114) both span DFS channels, but in some inland installations DFS events are rare enough that the trade is worth taking. Coastal areas, areas near airports, and homes with many older IoT clients should default to 80 MHz.
• Wi-Fi 7's 320 MHz mode requires both an AP and a client that support it. Setting an SSID to 320 MHz on a UniFi 7 AP does not magically speed up a Wi-Fi 6E or Wi-Fi 6 client — those clients will continue to negotiate the widest mode they support (160 MHz on Wi-Fi 6E, 80 MHz on most Wi-Fi 6). Wi-Fi 7 client support is still expanding; the residential upside today is partial.
• Per-region rules differ. Everything above describes the United States. Channels 12 and 13 are permitted in most of Europe and Japan on 2.4 GHz; the 5 GHz UNII-2C sub-band has slightly different DFS rules in the EU; the 6 GHz allocation varies — some regions opened only U-NII-5 (500 MHz rather than the full 1200 MHz). Set the UniFi console's country code correctly and trust the channel choices it offers.

None of these caveats changes the headline recommendation. 20 / 80 / 160 (or 320) MHz is the right residential default across the three bands. Channel AI is a reasonable starting point. Channel utilization is the metric that tells you whether the plan is working — and is also what an audit looks at first when the homeowner says the Wi-Fi feels slow.