Wireless AP Density Calculator

Coverage, user capacity, and bandwidth are independent constraints that scale with completely different inputs -- coverage scales with floor area, capacity scales with concurrent user count, and bandwidth scales with per-user throughput demand. The calculator computes AP count under each constraint separately and takes the maximum, because whichever factor needs the most APs is the one that actually determines how many you must deploy; sizing for only one factor risks a design that's technically compliant on paper but fails in the constraint you ignored.

The coverage radius per AP is set by environment type because walls, furniture, and bodies absorb and reflect 2.4/5 GHz signals differently -- a classroom's dense furniture and body absorption limits usable range, while a warehouse's open sightlines and fewer obstructions let a signal carry much farther. This radius directly sets each AP's coverage area (a circle, via pi times radius squared), so the same floor area can require very different AP counts purely based on which environment type you select.

Not every registered or badged user is actively connected and pulling bandwidth at the same moment, so the calculator applies your concurrency percentage to total users before computing concurrent users, which then feeds both the capacity and bandwidth AP calculations. Setting concurrency too low undersizes the network for peak usage moments (like an all-hands meeting), while setting it too high over-provisions APs for load that never actually materializes.

The bandwidth calculation divides total demand by AP throughput to find how many APs the traffic load requires, and using an AP's advertised top speed here would badly understate the AP count needed. Real-world throughput is reduced by protocol overhead, channel contention from neighboring APs and clients, and mixed-generation client devices that can't all use the fastest available data rates, so the input asks for effective aggregate throughput specifically to avoid that trap.