Enter available throughput
Use the practical aggregate throughput available to users, not only the advertised access-point link rate.Set per-user demand
Enter the average Mbps needed by one actively transmitting user during the peak period.Choose a utilization ceiling
Set the highest share of capacity you want normal peak traffic to consume; a lower value preserves more headroom.Review the capacity estimate
The main result is the whole-number count of simultaneous active users supported at the selected utilization ceiling.Compare the breakdown
Use usable bandwidth and reserved headroom to see how conservative the capacity target is.
WiFi Network Concurrent User Capacity Estimator
The WiFi Network Concurrent User Capacity Estimator approximates how many simultaneously active users a wireless network can support before the planned utilization limit is reached. It combines the usable network throughput with an average bandwidth demand per active user, making it useful for offices, schools, venues, cafés, and other shared WiFi environments where the number of connected devices alone does not describe actual load.
The estimate is most useful during capacity planning or when comparing an existing backhaul or WLAN design with expected peak demand. Because real WiFi throughput is affected by signal quality, channel contention, protocol overhead, device capabilities, and traffic bursts, the result should be treated as a practical planning ceiling rather than a guaranteed client count. Use measured application demand when available and leave operating headroom for short peaks.
WiFi capacity inputs
Where:
- Available throughput — aggregate usable WiFi or backhaul throughput in Mbps
- Maximum utilization — planned peak utilization as a percent
- Average bandwidth per active user — average simultaneous demand in Mbps for one active user
Assumptions: Average per-user demand is treated as steady during the peak window. The model does not separately simulate airtime contention, retries, channel overlap, roaming, or protocol overhead, so practical throughput should already reflect those effects.
What the result means
The main result is the estimated number of simultaneously active users that fit within the selected utilization ceiling.
A network may have many more associated devices than active users. Capacity should be checked against both throughput and WiFi airtime constraints.
Given:
- Available throughput: 600 Mbps
- Average active-user demand: 4 Mbps
- Maximum utilization: 70%
Calculation:
Usable bandwidth = 600 × 0.70 = 420 Mbps
Concurrent users = floor(420 ÷ 4) = 105 users
Result: 105 concurrent active users
Interpretation: At the selected ceiling, the network can plan for about 105 actively transmitting users while keeping 180 Mbps of nominal throughput outside the utilization target.
Why is concurrent user capacity lower than the number of connected devices?
Connected devices can remain idle for long periods. This estimator focuses on users transmitting at the same time, because simultaneous traffic is what consumes throughput.
What should I use for average bandwidth per user?
Use a peak-period average for the applications that matter in your environment. Measurements from similar users are better than advertised application minimums because actual demand varies by behavior and quality settings.
Should I enter the WiFi link rate shown on a device?
Usually no. Link rates are physical-layer speeds and are higher than usable application throughput; use measured or realistically modeled aggregate throughput instead.
What happens if I set utilization to 100%?
The estimator removes all planned throughput headroom. That can show a theoretical upper bound, but operating continuously near full utilization can increase delay and make bursts harder to absorb.
Does this replace access-point density planning?
No. Throughput is only one constraint. Coverage, channel reuse, client distribution, radio capabilities, interference, and airtime can limit WiFi capacity even when backhaul bandwidth is sufficient.