Back to Guides
wifi 7802.11bechannel width320mhz6ghzthroughputwirelessexplainer

WiFi 7 320 MHz Channel Width Explained: How It Doubles Throughput, Which Routers Support It, and When to Enable It

WiFi 7 doubles the maximum channel width from 160 MHz to 320 MHz — but only in the 6 GHz band. This guide explains exactly how wider channels translate to faster speeds, which routers and devices actually support 320 MHz today, and when enabling it is worth it.

WiFi 7 320 MHz Channel Width Explained: How It Doubles Throughput, Which Routers Support It, and When to Enable It
8 min read

WiFi 7 (802.11be) ships with a headline feature that sounds almost too simple: double the channel width. Previous WiFi standards topped out at 160 MHz channels; WiFi 7 pushes that ceiling to 320 MHz. Doubling the channel width effectively doubles the data pipe, so a single 320 MHz link can carry far more traffic than any WiFi 6 or WiFi 6E connection. But the full picture is more nuanced — 320 MHz operation requires the 6 GHz band, capable hardware on both ends, and local regulatory approval that not every country has granted. This guide explains the mechanics behind the spec, the real-world numbers you should actually expect, and the practical settings to look for on your router.

What Channel Width Means in WiFi

A WiFi channel is a slice of radio spectrum. When two devices communicate wirelessly, they exchange data across a defined frequency range — that range is the channel. The wider the channel, the more data can pass through it simultaneously, just as a six-lane highway moves more cars per minute than a two-lane road.

WiFi channels are assembled by bonding adjacent 20 MHz sub-channels together. A 40 MHz channel bonds two 20 MHz sub-channels; an 80 MHz channel bonds four; a 160 MHz channel bonds eight. WiFi 7’s 320 MHz channels bond sixteen 20 MHz sub-channels into a single wide pipe. Because each sub-channel carries independent data streams, doubling the channel width from 160 MHz to 320 MHz doubles the raw PHY (physical layer) data rate before any other factor is considered.

The tradeoff is spectrum: wider channels consume more of the available frequency range, leaving less room for other networks. This is why 320 MHz channels are only practical in the 6 GHz band, where there is enough spectrum to make them viable without every neighboring network colliding.

Why 320 MHz Only Works in the 6 GHz Band

The 2.4 GHz band covers roughly 83 MHz of spectrum (2,400–2,483 MHz in the U.S.). There is not room for a single 320 MHz channel, let alone multiple non-overlapping ones. The 5 GHz band provides more room — about 500 MHz across the various U-NII sub-bands — but that spectrum is already shared with radar systems and other licensed uses, which is why DFS channels and radar avoidance exist. Carving out two contiguous 160 MHz blocks in 5 GHz without colliding with DFS restrictions or neighboring networks is impractical in most real environments.

The 6 GHz band (5.925–7.125 GHz in the U.S.) was opened for unlicensed WiFi use by the FCC in April 2020 and provides 1,200 MHz of fresh spectrum — nearly 15 times the bandwidth of the 2.4 GHz band. This allows for up to three non-overlapping 320 MHz channels in the U.S., compared to just three non-overlapping 20 MHz channels on 2.4 GHz. No incumbents, no radar, no legacy interference. It is the only band wide enough to make 320 MHz channels practical in a consumer environment.

An important caveat: 6 GHz spectrum allocation varies by country. The U.S., EU, Brazil, Saudi Arabia, Chile, and South Korea have broadly opened 6 GHz for WiFi. Other regions allow only part of the band, or none at all. If you are outside the U.S. or EU, verify whether 6 GHz is available in your country before expecting 320 MHz operation.

How 320 MHz Channels Actually Double Throughput

The relationship between channel width and data rate is direct and linear at the PHY layer. Compare the theoretical single-stream data rates across WiFi generations at their maximum channel widths:

  • WiFi 5 (802.11ac), 160 MHz, 256-QAM: 866.7 Mbps per spatial stream
  • WiFi 6/6E (802.11ax), 160 MHz, 1024-QAM: 1,201 Mbps per spatial stream
  • WiFi 7 (802.11be), 320 MHz, 4096-QAM: 2,882 Mbps per spatial stream

WiFi 7’s 2,882 Mbps per-stream rate comes from two simultaneous improvements: the channel width doubles (from 160 MHz to 320 MHz), and the modulation density increases (from 1024-QAM to 4096-QAM, which squeezes 20% more data into each symbol). A tri-band WiFi 7 router with 8 spatial streams on the 6 GHz radio has a theoretical aggregate rate of roughly 23 Gbps on that band alone.

Real-world throughput is considerably lower. Consumer WiFi 7 routers deliver 2–5 Gbps of actual throughput to a single close-range client on a 320 MHz channel — still far beyond any current internet plan, but well below theoretical maximum. The gap is normal: modulation efficiency at real-world signal-to-noise ratios, protocol overhead, multi-device contention, and hardware implementation quality all reduce throughput from the headline number. Run a speed test to establish your current baseline before any hardware changes.

Preamble Puncturing: Using 320 MHz Even When Sub-Channels Are Occupied

One of WiFi 7’s most important supporting features for 320 MHz channels is preamble puncturing. In previous standards, if any of the 20 MHz sub-channels making up a wide channel was occupied by another network or detected interference, the entire wide channel had to fall back to a narrower width. A 160 MHz channel could be forced down to 80 MHz if two of its eight sub-channels were busy.

WiFi 7 solves this with preamble puncturing: the router marks occupied sub-channels in the frame preamble and simply skips transmitting on them, using the remaining sub-channels at full efficiency. A 320 MHz channel with one or two busy 20 MHz sub-channels does not have to drop to 160 MHz — it operates as 320 MHz with a small number of holes punched in it. In the dense 6 GHz environment that 2026 networks are beginning to encounter, this feature is what makes 320 MHz channels practical rather than theoretical. Our preamble puncturing explainer covers the mechanism in detail.

Which Routers Support 320 MHz Channels

Any router certified as WiFi 7 (802.11be) is required to support 320 MHz channels in the 6 GHz band. In practice, tri-band WiFi 7 routers dedicate the 6 GHz radio specifically to 320 MHz operation (for direct client connections or wireless backhaul), while the 5 GHz radio handles legacy clients at up to 160 MHz and 2.4 GHz handles IoT and older devices.

Several widely available WiFi 7 routers confirmed to support 320 MHz include:

  • TP-Link Archer BE550 (~$200): Dual-band WiFi 7 with 320 MHz support on 6 GHz. A strong entry-level WiFi 7 option for users who want 320 MHz at a lower price point. Note that as a dual-band unit, the 6 GHz radio handles both client connections and backhaul simultaneously.
  • NETGEAR Nighthawk RS700S (~$600): Tri-band WiFi 7 flagship with dedicated 6 GHz radio for 320 MHz client connections and a 10 Gbps WAN port. Supports 4×4 MIMO on the 6 GHz band for maximum throughput to WiFi 7 clients.
  • ASUS RT-BE96U (~$500): Tri-band WiFi 7 with a dedicated 6 GHz radio operating at 320 MHz and a 10 Gbps WAN port. ASUS supports 320 MHz through its standard AiProtection-enabled firmware with no additional configuration required.
  • TP-Link Archer BE900 (~$700): Quad-band WiFi 7 with two 6 GHz radios — one for 320 MHz client connections, one for 6 GHz wireless backhaul. The dual-6 GHz design delivers the highest flexibility for dense environments.
  • NETGEAR Orbi 970 Mesh System (~$1,500): WiFi 7 mesh with dedicated 320 MHz 6 GHz backhaul between nodes and a separate 6 GHz client radio. The separation prevents the backhaul from competing with client traffic on the 6 GHz band.

For a comprehensive comparison of these and other options, see our WiFi 7 home network setup guide.

Which Client Devices Can Use 320 MHz

To actually benefit from a 320 MHz channel, the connecting device must also support WiFi 7 (802.11be). A WiFi 6E laptop connecting to a WiFi 7 router will negotiate a 160 MHz connection on the 6 GHz band — it cannot use 320 MHz regardless of router capability. The same applies to WiFi 6 and WiFi 5 devices: they connect to the router’s 2.4 GHz or 5 GHz radios at their supported widths and never see the 6 GHz radio at all.

WiFi 7 clients available as of mid-2026 include:

  • Smartphones: Samsung Galaxy S24 series and later, Google Pixel 9 series, OnePlus 12 and later, Xiaomi 14 series
  • Laptops: Any laptop with an Intel WiFi 7 BE200 or BE202 module (widely available in 2024+ laptops from Dell, HP, Lenovo, ASUS, and others running Intel Core Ultra or 13th-gen+ processors). Also available as an M.2 PCIe upgrade for compatible desktops — see our WiFi 7 laptop upgrade guide.
  • Desktop upgrades: TP-Link Archer TBE550E, ASUS PCE-BE92BT, and Intel BE200 on an M.2 adapter bracket all bring 320 MHz WiFi 7 capability to desktop PCs.

MacBooks and iPads as of mid-2026 still ship with WiFi 6E radios and do not support 320 MHz. Check Apple’s technical specifications page for the latest information before assuming compatibility.

When to Enable 320 MHz — and When to Leave It Off

Most WiFi 7 routers default to automatic channel width selection, which negotiates the widest mutually supported width per connection. In this mode, WiFi 7 clients automatically get 320 MHz on the 6 GHz band, while older clients fall back to appropriate widths on 5 GHz or 2.4 GHz. For most households, the default setting is correct and requires no manual change.

Manual 320 MHz configuration makes sense in a few specific scenarios:

  • Mesh backhaul optimization: Some mesh systems default to 160 MHz wireless backhaul even on WiFi 7 hardware. Explicitly setting the 6 GHz backhaul channel to 320 MHz in the router’s advanced wireless settings can significantly increase node-to-node bandwidth for large homes with multiple mesh nodes.
  • Single-device high-throughput workloads: A workstation doing local 10 Gbps NAS transfers over WiFi, or a video editing machine pulling large files from a home server, benefits from locking to 320 MHz to prevent automatic negotiation from selecting a narrower width under momentary interference.
  • Testing and benchmarking: When measuring WiFi 7 router performance, manually fix the channel width to 320 MHz to eliminate variable channel-width negotiation from your test results.

Situations where 320 MHz is not the right choice:

  • No WiFi 7 clients: If nothing in your home supports WiFi 7, enabling 320 MHz on the router does nothing — no client can use it. The wider channel still occupies spectrum, increasing potential interference for non-WiFi-7 neighbors.
  • Countries where 6 GHz is restricted: If your local regulations only permit low-power indoor use or a narrower portion of the 6 GHz band, 320 MHz channels may not be available even if your hardware supports them. The router will fall back to the widest legally permitted width automatically.
  • Congested 6 GHz environments: In very dense apartment buildings where multiple 320 MHz WiFi 7 networks share the same three non-overlapping channels, 160 MHz or even 80 MHz channels may deliver better per-client throughput due to reduced co-channel interference. WiFi 7’s preamble puncturing mitigates this substantially, but it is not a complete solution in extremely dense deployments.

The Bottom Line

WiFi 7’s 320 MHz channel width is a genuine throughput improvement — not marketing hype — but it requires the right conditions to deliver: 6 GHz spectrum access, a WiFi 7-capable router, and a WiFi 7 client device on the other end. If all three are present, you gain a fast, low-contention connection capable of multi-gigabit speeds that no WiFi 6E setup can match. If any piece is missing, you are connecting at 160 MHz or less, and the 320 MHz spec is irrelevant to your network.

For most households upgrading in 2026, the practical path is a tri-band WiFi 7 router paired with a WiFi 7 laptop or smartphone. The router handles 320 MHz automatically once it detects a capable client, and the improvement in throughput and latency is immediately measurable with a speed test from a connected WiFi 7 device versus an older WiFi 6 device on the same network. The jump is real — especially at the distances and through the walls typical of a real home environment.

Related Articles