redzilla
All tools
Wireless

WiFi Airtime & Capacity

Define the clients (PHY rate and demand) and I compute the airtime each one consumes, the cell total and whether it saturates. See why a slow client hogs the medium (airtime fairness).

Cell clients

Each row is a WiFi client. Set its PHY rate (Mbps, the one negotiated with the AP) and its actual traffic demand (Mbps). The airtime it consumes is demand / (PHY × efficiency).

typical a/g/n 802.11 overhead
redzilla.cl — wifi-airtime
 

Total cell airtime

0% of the air 0%

Total airtime
Cell state
Airtime hog
Airtime
Free
State

Per-client breakdown

Client PHY Demand Airtime Real throughput
How it is computed · airtime, saturation and the slow client

1. For each client, the airtime (fraction of air time it occupies) is airtime = demand(Mbps) / (PHY(Mbps) × efficiency). Efficiency (MACeff) accounts for 802.11 overhead: preambles, ACKs, contention and inter-frame spaces. Typically 0.65 on a/g/n, up to 0.75 on ax thanks to OFDMA; in crowded 2.4 GHz it drops to ~0.5.

2. The cell's total airtime is the sum of all of them: total = Σ airtime_i. The air is a shared resource, so only 100% is available.

3. If total ≤ 100% the cell does not saturate: every client gets its demand and some airtime is left free. If total > 100% the cell saturates: there is not enough air and each client's real throughput is scaled by 1/total (proportional to demand).

4. Slow-client effect: a client at a low PHY rate consumes a lot of airtime even with modest demand. E.g. 5 Mbps at 6 Mbps PHY5/(6×0.65) = 128%, it alone saturates the cell. That client hogs the medium and slows everyone down (which is why raising its rate or moving it off the channel helps).

5. Simplified model: it does not include retransmissions, real collisions, MU-MIMO or aggregation (A-MPDU). It is meant to show the airtime-fairness dynamics, not as an exact capacity figure.

Runs locally in your browser · no sign-up · nothing leaves your browser

How it works

The tool models a WiFi cell as what it really is: a shared medium where only 100% of the air time exists. You define each client with its negotiated PHY rate (Mbps) and its actual traffic demand (Mbps), plus an adjustable MAC efficiency (40–90%), and it computes the airtime fraction each one consumes, the cell total, whether the cell saturates and the real throughput left for every client.

The per-client formula is airtime = demand / (PHY × efficiency). MAC efficiency discounts the IEEE 802.11 overhead (preambles, ACKs, contention, interframe spaces): 65% is typical for a/g/n, up to 75% on 802.11ax thanks to OFDMA, and around 50% on congested 2.4 GHz. Total airtime is the sum over all clients; above 100% the cell is saturated and each client throughput is cut by 1/total. It is a simplified model (no retransmissions, MU-MIMO or A-MPDU aggregation), built to show the dynamics of airtime fairness.

Example: two fast clients and one slow camera (65% efficiency)

  1. Laptop at 433 Mbps PHY demanding 50 Mbps: 50 / (433 × 0.65) ≈ 17.8% of the air. Phone at 433 Mbps demanding 30 Mbps: 10.7%.
  2. Legacy camera at 6 Mbps PHY asking for only 5 Mbps: 5 / (6 × 0.65) = 128.2% — it alone needs more air than exists.
  3. Total airtime: 156.6% > 100% → saturated cell. Real throughput scales by 1/1.57: the laptop gets ~31.9 Mbps, the phone ~19.2 and the camera ~3.2.

Frequently asked questions

Why does one slow client drag down the whole WiFi network?
Because the air is shared in time, not in megabits. A client that negotiates a low PHY rate takes far longer to transmit each byte, so even with a modest demand it hogs a large share of the airtime and leaves little for everyone else. In the example, a camera at 6 Mbps PHY asking for 5 Mbps consumes 128% of the air on its own and saturates the entire cell.
What is MAC efficiency and why do I never reach the PHY rate?
The PHY rate is the modulation speed, but the 802.11 protocol spends time on preambles, ACKs, medium contention and interframe spaces. That is why useful throughput is usually 50–75% of PHY: around 65% on a/g/n, up to 75% on 802.11ax with OFDMA and near 50% on congested 2.4 GHz. The slider in the tool adjusts that factor.
How many clients can a WiFi access point support?
It depends on airtime, not on a fixed number. A client at 433 Mbps PHY demanding 10 Mbps takes about 3.6% of the air at 65% efficiency, so roughly 28 clients of that profile would fill the cell. With slow clients or higher demands the figure plummets: that is why you should size against your worst client, not the average one.
What exactly happens when the cell saturates?
When the airtime sum exceeds 100%, the model cuts every client throughput by the factor 1/total, which is a demand-proportional split. In practice the degradation also includes retransmissions and collisions the model does not simulate, so reality tends to be worse. Everything runs in your browser, with no data sent to any server.
Was this tool useful?
Disclaimer We take great care to keep every tool accurate and review it thoroughly; even so, we can't guarantee it is free of errors or take responsibility for how the results are used. We recommend double-checking anything critical.
Found an error? Let us know →