Blog 2026-05-15
Module Selection · Generation Thinking
TL;DR. Pick a WiFi module generation by answering four questions — bandwidth you genuinely need, client density per radio, power budget, and infrastructure already in place — then match, not maximise. The newest generation is rarely the right answer; the classic overbuy traps (density you don’t have, no 6 GHz peer, upstream-limited designs) drive most overspend.
The newest standard is rarely the right answer for a given product. This guide breaks the decision into the four variables that actually decide it — bandwidth, client density, power, and infrastructure — and names the mistakes that drive teams to overspend.
Every few years a fresh Wi-Fi generation shows up with a bigger headline number, and with it comes a familiar rush to put the newest chip in everything. The honest view is different: the “best” generation is the one that matches your real-world load, your client population, and your power and cost envelope. This guide walks the four decision axes and then the common traps.
| Capability | Wi-Fi 5 (ac) | Wi-Fi 6 (ax) | Wi-Fi 6E (ax 6 GHz) | Wi-Fi 7 (be) |
|---|---|---|---|---|
| Max channel width | 160 MHz | 160 MHz | 160 MHz | 320 MHz |
| Max modulation | 256-QAM | 1024-QAM | 1024-QAM | 4096-QAM |
| OFDMA | No | DL + UL | DL + UL | Enhanced |
| MU-MIMO | DL only | DL + UL | DL + UL | Enhanced |
| Multi-link (MLO) | No | No | No | Yes |
| 6 GHz band | No | No | Yes | Yes |
| Theoretical peak | 3.5 Gbps | 9.6 Gbps | 9.6 Gbps | 46 Gbps |
| Real-world 2×2 throughput | 200–500 Mbps | 400–900 Mbps | 500–1200 Mbps | 800–3000+ Mbps |
| Typical module draw (2×2) | 0.9–1.2 W | 1.5–2.5 W | 2.0–3.5 W | 2.0–6.5 W |
| Best-fit client density | < 20 / AP | 20–60 / AP | 30–80+ / AP | 30–100+ / AP |
Two columns deserve a closer look. Wi-Fi 6E’s value is not protocol efficiency — it is spectrum: a clean, uncongested 6 GHz band to offload dense traffic. Wi-Fi 7’s 46 Gbps headline is a stack of maximums almost no client device reaches; its real benefit arrives through multi-link operation and wide channels, on an ecosystem that has to catch up first.
Start with how much throughput one client actually needs, sustained:
It is easy to read that list and reach for the top option, but bandwidth is not free. Each step up in generation brings higher module cost, higher power draw, and more thermal engineering. The discipline is to ask what the sustained per-client need is, not the burst-peak number a spec sheet quotes. A camera that streams a few Mbps for hours will never touch a multi-gig throughput figure, so the bandwidth axis by itself will not justify a Wi-Fi 7 module. It only starts to justify one when you are per-client-squeezed or aggregation-limited.
OFDMA and multi-user MIMO only earn their cost when there are enough clients to multiplex. Below the thresholds, they are dead weight:
Density is the axis where Wi-Fi 6 and later generations genuinely earn their keep, because OFDMA lets one radio serve many low-rate clients in parallel instead of serially competing for airtime. If your product is an access point in a classroom, an auditorium, or a dense office, this is the reason to move up the ladder. If your product is a single client or a sensor network with a handful of nodes, the density benefits are largely irrelevant to you. Know which side of this axis you sit on before the axis gets a vote.
For battery-powered or sealed devices, generation choice is a power decision:
There are two separate budgets to reconcile here, and teams often conflate them. The average budget decides battery life, while the peak budget decides power supply sizing and thermal headroom. A Wi-Fi 7 module that draws 6 W in a burst is not just a battery-line concern — it is a supply-and-heat concern for a sealed, passively cooled enclosure. If the product runs on a coin cell or a modest PoE budget, the generation choice may be decided by the power axis alone, regardless of how much bandwidth is on the table.
Your client module is only as good as the access point it talks to:
Infrastructure is the axis most often ignored on a datasheet. It is easy to see a fast new module and forget that the network on the other side of the radio determines what is actually achievable. A widely repeated field reality is the “AP gap”: a product that ships the fastest radio the market offers, only to be throttled by an upgrade path or a wired spine that cannot carry its ambition. Mapping the full path — host bus, radio, access point, and wired uplink — before committing keeps the bottleneck from being the most expensive component in the design.
Rather than sampling the four axes informally, run them in a fixed order so none gets skipped:
Only after those four numbers exist do you look at the table and pick the lowest generation that satisfies all four at once. That “lowest acceptable” instinct is the entire trick: people almost never fail by picking something too old, and almost always overspend by chasing the headline. For a companion deep-dive into the fuller selection discipline, the 8-field enterprise selection guide extends this into a complete checklist.
Two checks belong alongside the four axes, because a module is not only a radio — it is a thermal and mechanical part.
Neither check is exotic, but together they catch the most expensive late-stage failures: a board that cannot cool its radio, and a module that cannot be laid out where the product needs it. Do both on paper before you commit silicon to a schematic.
If you are moving up a generation for the first time, the newest terms can mislead. Multi-link operation in Wi-Fi 7 lets a device use more than one band at once, which is genuinely new and useful for latency and resilience — but it requires a Wi-Fi 7 access point and matching client support. OFDMA, first shipping in Wi-Fi 6, is what makes dense networks efficient by carving a channel into sub-carriers shared by many clients. Understanding these mechanisms — rather than treating each new number as “more speed” — is the difference between a purchase driven by need and one driven by a spec sheet. A deeper look at the newest generation’s real-world behaviour is in the Wi-Fi 7 explained guide.
A recurring source of bad decisions is comparing your next product against a marketing peak that almost no real deployment reaches. Understanding the gap between the advertised number and a sustainable field number prevents months of disappointment:
| Reality check | What it means for your decision |
|---|---|
| Peak is 160/320 MHz, max QAM, perfect RF, few interferers | Almost no client negotiates this; it is a ceiling, not a promise. |
| High QAM needs 30–35 dB SNR | Only short, clean links sustain it; real links drop to lower modulation over distance. |
| Aggregate throughput divides across clients | A “9.6 Gbps” AP shares that across everyone on the radio. |
| Protocol overhead is several percent to tens of percent | TCP-friendly throughput is well below the PHY-rate headline. |
| Wired uplink caps everything | Multi-gig is only as real as the 2.5G/5G/10G port behind it. |
The practical rule: divide marketing peaks by 2–4 and you are roughly where a good real deployment lands, and divide further under dense or noisy conditions. If a decision hinges on a number you can only enjoy in a lab, treat that number as a warning rather than a justification. For a deeper treatment of the throughput question across MIMO configurations, the MIMO guide walks the stream counts and their honest client capacity.
To make the four axes concrete, run three very different products through the procedure and see where each lands:
| Product | Bandwidth | Density | Power | Infrastructure | Suggested choice |
|---|---|---|---|---|---|
| Battery door sensor | < 100 kbps | 1 client | Tiny; sleep dominates | Any modern AP | Wi-Fi 5 / 6 low-power |
| HD surveillance camera | 2–10 Mbps | 1 client | PoE available | Site AP 5 GHz | Wi-Fi 5 or 6 |
| Office access point | Aggregating many | 40–80 clients | Moderate PoE | AP + wired gigabit+ | Wi-Fi 6E / 7 |
Notice that only the access-point product justifies moving up the ladder, and it does so because of the density axis — not because any single client needs more speed. The sensor stays on an old, lean module because anything newer adds cost and power without serving its ten-second-a-day job. The camera sits comfortably on Wi-Fi 5/6 because its per-client bandwidth is small and stable. Most products in the world look like the first two; very few actually look like the third, and acting accordingly is the whole point of a decision procedure.
Beneath the four axes sits a lifecycle consideration that a single table hides: the cost and certification burden that travels with the generation choice, and how long you are committing to supply it.
Adding these to the decision often tips a borderline case toward the lower generation: the increment in bandwidth you do not need is then paid for in certification and per-unit cost you definitely feel. A module that satisfies the four axes and keeps the lifecycle lean is worth more than the one with the better headline.
Before a module becomes a schematic, validate the choice instead of trusting the datasheet. A short validation plan catches the failures that paper decisions miss:
Validation is where “the right generation in theory” becomes “the right module on the board.” It is also where the cost axes quietly resurface: a module that looks great on paper but throttles in your box, or cannot hold a connection to your installed AP fleet, is a design error no datasheet will confess.
Because 6 GHz access is the single biggest reason to move to 6E or 7, it deserves its own decision check. The band is not globally available, and where it is approved the rules differ:
| Region | 6 GHz band | Approach | Key check |
|---|---|---|---|
| United States | 5925–7125 MHz | Tiered (low-power indoor; standard-power with AFC) | Confirm the intended power tier and indoor/outdoor limits. |
| European Union | 5945–6425 MHz | Lower 6 GHz for indoor low-power | Upper 6 GHz (6425–7125 MHz) not yet approved for Wi-Fi at time of writing. |
| Canada / Japan / others | Varies | Progressing to lower or full band | Confirm per-country tables before committing. |
| China, India, parts of Southeast Asia | Not yet approved for Wi-Fi | — | A 6E/7 module ships but runs only on 5 GHz in these markets. |
The lesson is concrete: if your target market has no 6 GHz, a 6E/7 module is a tri-band part running as a dual-band one — you buy the premium and the certification cost without gaining the spectrum. If you ship one product globally, the decision gets harder, because a single SKU must behave acceptably in both 6 GHz and 5 GHz-only regions. Running the regulation check early, market by market, is what keeps a “future-proof” module from becoming a permanently throttled one.
When the four axes feel overwhelming, fall back to a two-variable quadrant that captures most decisions: density on one axis and per-client bandwidth on the other.
This quadrant is not a substitute for the full procedure — it intentionally leaves out power and infrastructure, both of which can veto a choice — but it is a useful first filter. A team that places itself in the top-left box and still buys a Wi-Fi 7 module has almost certainly drifted back to headline-chasing. Run the quadrant, then run the full four-axis pass to confirm.
A decision that is right for a design starting today may be wrong for one shipping in two years, simply because the ecosystem moves. Factor the timing of your launch into the generation choice:
Timing is a soft axis, but it can out-rank a hard one. A module chosen purely on today’s spec sheet — with no thought for the APs, clients, and spectrum your product will meet at launch — is a gamble that headlines rarely reward. The roadmap question ties the four axes to the moment your product actually reaches users, which is the moment that pays the bills.
A generation choice is only as good as the RF chain it feeds. Antenna count, PCB layout, and platform impedance quietly override every axis in this guide if they are wrong:
Treat the antenna and layout pass as part of the generation decision rather than an afterthought. It is the difference between the number on the datasheet and the number your user actually gets, and that is the only number that matters at the end of the project.
For balance, name the cases where the newest generation is the honest answer rather than an indulgence. These are narrow but real, and recognising them avoids the opposite failure — underbuying for a workload that genuinely needs it:
The keynote of this whole guide is that these are exceptional, not typical, cases. If your product genuinely lives in one of them, Wi-Fi 7 is not overengineering — it is the correct call, and the four-axis procedure will show it. Most teams, however, will find their workload sits in the large majority that does not need it, and buy with that knowledge instead of against it.
Run four decision axes in order: (1) sustained per-client bandwidth, (2) client density per access point, (3) power budget (average and peak), and (4) the infrastructure path end to end. Then pick the lowest generation that satisfies all four at once. The instinct to choose the smallest acceptable part is the entire trick — overspending by chasing the headline is the common failure.
Under 200 Mbps sustained, Wi-Fi 5 is usually right and cheapest. 600 Mbps–1.5 Gbps points to Wi-Fi 6 or 6E. Over 3 Gbps, only Wi-Fi 7 with MLO and 320 MHz works. For density: below ~15 clients per AP, OFDMA gives nothing meaningful; 15–40 favours Wi-Fi 6; 40–80 favours 6E; 80+ favours Wi-Fi 7.
No — this is the single most common 6E error. Without a 6E access point, the 6 GHz band is simply unreachable, so you pay the tri-band premium for nothing. Also check regulation: if 6 GHz is not approved in your target markets (e.g. China, India, parts of Southeast Asia), a 6E/7 module just runs on 5 GHz.
Marketing peaks assume 160/320 MHz, max QAM, perfect RF and few interferers — almost no client negotiates this. High QAM needs 30–35 dB SNR (short, clean links only), aggregate throughput divides across clients, protocol overhead eats a few to tens of percent, and the wired uplink caps everything. Divide marketing peaks by 2–4 for a good real deployment.
A Wi-Fi 5 module draws about 0.9–1.2 W active; Wi-Fi 6 about 1.5–2.5 W; Wi-Fi 7 with MLO about 4.5–6.5 W. For idle devices, sleep current dominates and Wi-Fi 5 sleeps leaner. For constantly transmitting devices, Wi-Fi 6/6E’s better per-bit efficiency can offset higher active draw. A Wi-Fi 7 module pulling 6 W in a burst is a supply-and-heat concern for sealed enclosures.
Table values are directional reference figures from typical deployments; exact numbers depend on chipset, firmware, channel width, and environment. Regulatory rules for the 6 GHz band differ by market and should always be confirmed before committing.