The problem OFDMA solves — and why it matters in the field
Before Wi-Fi 6, every device had to wait its turn to use the channel. One device transmits, everyone else waits. In a living room with four devices that's fine. In a conference room with 40 laptops, a hospital ward with 200 devices, or a lobby with constant foot traffic, it's a disaster — not because there isn't enough bandwidth, but because everyone is queued waiting for airtime they could be sharing.
OFDMA fixes that. Understanding how it works tells you why dense Wi-Fi feels different with Wi-Fi 6, why it breaks the way it does, and what Wi-Fi 7 builds on top of it. This is foundational knowledge for anyone designing or troubleshooting modern networks.
1Why pre-OFDMA WiFi struggled in dense environments
Pre-Wi-Fi 6 networks used OFDM — one device used the entire channel for each transmission. Small packets from 30 devices waiting to send background syncs and notifications each had to wait for a full channel access opportunity. The channel was busy, but mostly with overhead and waiting, not actual data.
"Imagine a four-lane highway that only lets one car drive at a time. The road isn't congested — it's empty most of the time — but every car still has to wait for every other car to finish before it can go. That's pre-OFDMA WiFi in a crowded room."
The result in the field: high airtime utilisation, low actual throughput, poor latency, devices that feel "slow" even though signal strength is fine. Checking signal strength wouldn't tell you anything was wrong. You'd need to look at airtime utilisation and retry rates to see the real problem.
When a dense environment performs poorly despite strong signal and low MCS retries, airtime contention is often the culprit. Knowing that OFDMA is the mechanism Wi-Fi 6 uses to address this tells you two things: whether upgrading to Wi-Fi 6 APs will actually help (it will, if the clients are Wi-Fi 6 capable), and what to look for in your AP dashboard to confirm OFDMA scheduling is actually active and working.
2Slicing the channel
OFDMA works by dividing the Wi-Fi channel into smaller frequency slices called Resource Units (RUs). Each RU is a group of subcarriers — the individual narrow frequency tones that make up the channel. The AP assigns different RUs to different devices within a single transmission slot, so multiple devices send and receive simultaneously.
In a 20 MHz Wi-Fi 6 channel, there are three RU size options:
- 106-tone RUs — the channel splits into 2 large RUs. Two devices served simultaneously. Best for devices needing sustained throughput — file transfers, video streams.
- 52-tone RUs — the channel splits into 4 medium RUs. Four devices served simultaneously. Good balance for moderate traffic — video calls, active browsing.
- 26-tone RUs — the channel splits into 9 small RUs. Up to nine devices served in one slot. Best for bursty, low-volume traffic — syncs, notifications, IoT heartbeats.
The RU size the AP chooses for a client tells you something about that client's traffic profile. An AP consistently assigning 26-tone RUs to a device suggests that device is generating small, bursty traffic — background syncs, IoT heartbeats, push notifications. If that same device suddenly starts needing large RUs but can't get them because the channel is fully allocated in 26-tone mode, you'll see latency spikes. Understanding RU allocation helps you interpret what your AP dashboard's airtime and OFDMA scheduling data is telling you.
3The DC null — the gap in the middle
Open the RU Explorer and look at the centre of any spectrum view. There's a dark gap — the DC subcarrier. Every 802.11ax AP leaves the subcarrier at the exact centre of the channel (index 0) completely silent.
This isn't a flaw or a waste — it's a hardware necessity. The radio's local oscillator leaks a small amount of energy at exactly DC (direct current — the zero-frequency point of the baseband signal). That leakage would corrupt any data sent on that subcarrier, so the spec defines it as unused.
In 26-tone mode, RU 5 sits at the centre of the channel — exactly where the DC null is. Rather than sacrificing an entire RU, the 802.11ax spec defines RU 5 as straddling the null: it uses subcarriers on both sides of the gap, skipping only the silenced ones. Click RU 5 in the Explorer's 26-tone view to confirm the index split. That's the kind of careful engineering that goes into a WiFi standard.
4How to recognise an OFDMA-related problem
OFDMA problems don't look like traditional RF problems. Signal strength can be excellent, MCS can be high, and the network can still feel sluggish in dense conditions. What you're looking for is different.
- High airtime utilisation with moderate client count — If an AP is showing 70%+ airtime utilisation with only 20–30 clients, and those clients are Wi-Fi 6 capable, OFDMA scheduling may not be functioning correctly. Check whether the AP's OFDMA mode is enabled and whether clients are associating as HE (High Efficiency) or falling back to legacy modes.
- Latency spikes under load that disappear with fewer clients — Classic airtime contention signature. Adding a 31st device to an AP that handles 30 well shouldn't cause problems if OFDMA is working — the AP can serve more devices per slot. If latency spikes at that threshold, examine whether OFDMA is actually being used or whether clients are contending for the channel in legacy OFDM mode.
- IoT devices degrading overall network performance — IoT devices generating constant small traffic (heartbeats, state updates) are exactly what 26-tone RUs are designed for. If they're instead taking full channel access opportunities in OFDM mode, they're punching above their weight in airtime terms. Wi-Fi 6 APs with OFDMA enabled handle this much more gracefully.
A hospitality client reports their hotel lobby WiFi is fine at check-in time but becomes unusable during evening peak hours when 60–80 guests are in the space. Signal strength at every test point is -55 dBm or better. The APs are 802.11ac (Wi-Fi 5). You recommend Wi-Fi 6 APs — not because the signal is weak, but because the airtime contention problem is exactly what OFDMA was designed to solve. The existing hardware doesn't have the tool to address it.
5Confirming OFDMA is actually working
Upgrading to a Wi-Fi 6 AP doesn't automatically mean OFDMA is active for all clients. Several conditions have to be met:
- The AP must support 802.11ax and have OFDMA enabled (most do by default, but verify in the configuration).
- The client must be Wi-Fi 6 (802.11ax) capable and must associate in HE mode — not fall back to legacy.
- The AP must have enough clients active simultaneously to benefit from multi-user scheduling. OFDMA for a single client is identical to OFDM.
Upgrading APs to Wi-Fi 6 while the client fleet is still predominantly Wi-Fi 5 devices. The AP can't use OFDMA with those clients — it falls back to OFDM for each legacy association. The network won't perform worse, but it won't improve the dense-environment behaviour that OFDMA was supposed to fix until the clients are also upgraded. This is why client refresh cycle matters as much as AP refresh cycle.
6What Wi-Fi 7 builds on top of OFDMA
Wi-Fi 7 (802.11be) doesn't replace OFDMA — it extends it. Everything in the RU Explorer applies directly to Wi-Fi 7. The RU structure is the same foundation. Wi-Fi 7 adds two capabilities on top:
Multi-RU (MRU): In Wi-Fi 6, each device gets exactly one RU per transmission slot. In Wi-Fi 7, a device can be assigned multiple non-contiguous RUs simultaneously — a 106-tone RU on the left half of the channel and a 26-tone RU on the right, for example. This lets the AP allocate channel capacity more efficiently when the spectrum isn't evenly utilised.
MLO (Multi-Link Operation): The most significant Wi-Fi 7 addition — a single device maintains simultaneous connections on multiple bands (2.4 GHz, 5 GHz, and 6 GHz at the same time). OFDMA operates independently on each link. The device's traffic is distributed across links dynamically. This is why Wi-Fi 7 latency is fundamentally lower — traffic can be rerouted away from a congested or interfered band in real time, without dropping the connection.
When a customer asks "what does Wi-Fi 7 actually do for me that Wi-Fi 6 doesn't?" — MLO is your answer for latency and resilience, and Multi-RU is your answer for throughput in dense environments. Both are built directly on the OFDMA foundation this lesson covers. If you understand RUs, you understand why those enhancements work the way they do.
The single most important thing to take from this lesson
Dense WiFi problems are often not signal problems. They're airtime problems. OFDMA is the mechanism Wi-Fi 6 introduced to share airtime more efficiently across many simultaneous clients. When a crowded environment performs poorly despite strong signal, the first question to ask is: are these clients actually using OFDMA? The RU Explorer shows you exactly how that sharing works at the subcarrier level — so when you see it behaving differently in the field, you understand why.