How Many Wi-Fi Access Points Do I Need? AP Calculator

Get an immediate planning estimate from your area, floors, building conditions, connected devices, application bandwidth, and Wi-Fi generation. Start with the simple inputs; open Advanced mode only when you have measured radio or survey data.

Calculations run locally in your browser. This planner does not collect SSIDs, floor plans, or user data.

Basic planner

Space

Total coverage area Include all floors that need service.

Area unitResults use the same unit.

Floors The result rounds up APs per floor.

Building or environmentSets a conservative area-per-AP starting point.

Walls or obstruction densityHeavy materials reduce the assumed coverage cell.

Ceiling-height rangeHigh mounting can reduce client-level signal and placement flexibility.

Coverage typeOutdoor cells assume fewer walls but still require survey validation.

Demand

Enter peak connected devices Calculate from people

Peak associated devices All devices connected at the busy time, active or idle.

Usage profileSets busy-hour active rate and Mbps per active device.

Wi-Fi

Wi-Fi generationChanges the radio goodput default, not the environment’s range.

Future growth / design reserve (%)20% is Starlight’s default for growth and uneven loading.

Assumptions will appear here.

Advanced mode: override coverage, demand, radios, and utilization

Space and layout

Area per AP override (current area unit)Use 0 for the environment preset; otherwise enter measured/predicted coverage in the selected area unit.

RF-isolated zonesFloors, wings, rooms, aisles, or outdoor pockets needing an AP.

Layout factorReduces ideal coverage for irregular placement; preset area already includes ordinary walls.

Roaming overlap / cell shrink (%)Planning reduction only; verify overlap at the target RSSI.

Devices and applications

Simultaneously active devices (%)Associations constrain client capacity; active devices drive airtime.

Mbps per active deviceAverage busy-hour payload, not a speed-test peak.

Short-peak factorAllows demand to rise above the busy-hour average.

Associated-device limit per served radioA conservative design target, not the vendor’s maximum association table.

Served radio or band

The capacity model uses one selected client-serving radio per AP. Advertised multi-band AP speeds are not added together as client goodput.

BandChoose the band expected to carry this client group.

Channel widthWider channels increase peak rate but reduce reuse options.

Spatial streamsUse the common client capability, not only the AP maximum.

Client-generation mixOlder and low-rate clients consume more airtime.

Usable channelsAfter local rules, DFS policy, and chosen width.

Expected goodput per served radio (Mbps)Auto-populated estimate based on the selections; override if justified.

Measured-goodput override (Mbps)0 uses expected goodput. Prefer a representative busy-cell measurement.

Target radio utilization (%)Leaves airtime for contention, management traffic, and bursts.

Co-channel sharing penalty per extra AP (%)Makes channel reuse reduce modeled per-AP capacity.

Wired uplink target utilization (%)Used to recommend the per-AP Ethernet uplink class.

Results

Enter your plan details, then calculate.Coverage, associations, and airtime are checked separately.

Minimum-

Recommended-

Conservative-

Coverage-driven-

Capacity-driven-

Association-driven-

Governing constraint-

Plan assumptions

Associated devices:-

Simultaneously active devices:-

Associated / active per AP:-

Busy-hour payload per active device:-

Area per AP assumption:-

Served-radio usable throughput:-

APs per floor:-

APs per usable channel:-

Recommended AP uplink:-

Risk and sensitivity

Awaiting inputs

The range will show sensitivity to higher activity, denser coverage, and lower goodput.

Deployment validation checklist

Allocate APs by floor and RF-isolated zone.
Prefer wired backhaul; account for mesh airtime and hops.
Verify PoE budget, switch ports, uplink capacity, and cabling.
Validate channels, transmit power, roaming overlap, target RSSI/SNR, and post-install performance.

Advertisement

How to estimate how many Wi-Fi access points you need

Enter the total coverage area, number of floors, environment, and obstruction density.
Enter peak connected devices directly or calculate them from people, devices per person, and connection rate.
Choose an application profile and Wi-Fi generation, then review or override the displayed assumptions.
Calculate and compare the coverage, association, and capacity counts, then validate placement, channels, power, cabling, and RF performance before deployment.

Core formulas and no-JavaScript explanation

Associated devices: direct entry, or people × devices per person × connection rate.

Active devices: associated devices × simultaneous-active rate. Associations constrain the client target; active devices and applications drive airtime.

Busy-hour demand: active devices × Mbps per active device × short-peak factor.

Coverage APs: ceil(total area ÷ adjusted area per AP). Environment, obstruction, ceiling, indoor/outdoor selection, layout, and overlap adjust the default cell area.

Association APs: ceil(associated devices ÷ associated-device target per served radio).

Capacity APs: the smallest count whose combined served-radio goodput meets demand after target utilization and co-channel sharing. The model does not add an AP’s advertised 2.4, 5, and 6 GHz marketing rates together.

Planning range: minimum is the largest raw constraint; recommended adds the selected design reserve; conservative also tests 20% more active demand, 15% denser coverage, and 20% less radio goodput.

JavaScript is off: use the formulas above with typical starting defaults of 1,500–5,000 sq ft (140–465 sq m) per indoor AP, 30–65% simultaneously active devices, 0.1–6 Mbps average busy-hour payload per active device for ordinary office/voice/video mixes, no more than 50 associated devices per served radio, 60% target radio utilization, and 20% design reserve. These are planning defaults, not universal limits.

Application-profile assumptions

These are Starlight planning defaults for average busy-hour payload per simultaneously active device, not speed-test peaks or vendor requirements. Override them when application telemetry is available.

Profile	Active at once	Mbps / active device	Short-peak factor
Email and browsing	30%	0.5	1.2×
Cloud office work	45%	1.5	1.3×
HD video calls	65%	4	1.4×
Video streaming	50%	6	1.4×
VoIP	35%	0.1	1.2×
Scanners and IoT	25%	0.15	1.2×
Large file transfers	35%	12	1.6×
Mixed enterprise use	45%	3	1.3×

Worked Wi-Fi AP planning examples

Scenario and inputs	Active-device calculation	Counts and recommendation
Two-floor private office 30,000 sq ft; medium walls; 240 devices; mixed use; Wi-Fi 6	240 × 45% = 108 active 108 × 3 Mbps × 1.3 = 421 Mbps	Coverage 17; capacity 3; associations 5; recommend 21 (about 11/floor). Coverage wins.
Classroom wing 12,000 sq ft; 8 isolated rooms; 180 devices; HD video calls; Wi-Fi 6	180 × 65% = 117 active 117 × 4 Mbps × 1.4 = 655 Mbps	Coverage 10; capacity 5; associations 4; recommend 12 (12/floor). Coverage wins.
High-rack warehouse 90,000 sq ft; heavy obstructions; high ceiling; 90 devices; scanners/IoT; Wi-Fi 6	90 × 25% = 22.5 active 22.5 × 0.15 Mbps × 1.2 = 4.05 Mbps	Coverage 59; capacity 1; associations 2; recommend 71 (71/floor). Coverage wins.
High-density venue 50,000 sq ft outdoor; 1,200 devices; mixed use; Wi-Fi 7	1,200 × 45% = 540 active 540 × 3 Mbps × 1.3 = 2,106 Mbps	Coverage 6; capacity 12; associations 24; recommend 29 (29/floor). Associations win.

Why Wi-Fi capacity is not a simple users-per-AP number

Wi-Fi is a shared radio medium. A client with a weak signal, old radio, small packets, high retries, or a low modulation rate can consume more airtime than a nearby modern client moving the same amount of payload data. That is why this planner separates user count, active concurrency, throughput demand, AP PHY rate, usable airtime efficiency, and utilization target.

Coverage and capacity should be checked independently. Adding APs for coverage can create channel reuse and interference challenges if the transmit power and channel plan are not adjusted. Adding APs for capacity can still fail if the wired uplink, PoE budget, DHCP scope, or backhaul path cannot support the traffic.

Assumptions and references

Reviewed 14 July 2026. Revision: added environment-based coverage, per-radio goodput and channel-reuse capacity, planning ranges, and synchronized visible/schema guidance. Technical review is attributed to Starlight Robotics as the publisher; no individual credential is claimed.

Assumption	Starlight default and reasonable planning range	Basis and when to replace it
Area per AP	Environment presets from 1,500 to 7,500 sq ft before modifiers; common indoor starting band shown as 1,500–5,000 sq ft.	Starlight conservative defaults, not sourced limits. Replace with a predictive design using actual walls, antennas, mounting, power, and client requirements, then validate on site.
Cell edge and roaming	15% overlap default; FAQ cites about -67 dBm and 25 dB SNR as a common voice/mobile reference.	Cisco site-survey guidance documents -67 dBm, 25 dB SNR, and 20% overlap for its voice example. Replace with the important client/application requirements.
Channel utilization	60% planning target; 10–90% adjustable range.	Starlight default. Cisco enterprise guidance for Apple clients recommends lower utilization for latency-sensitive use. Replace with measured channel utilization, retries, and latency goals.
Channel reuse	20% modeled capacity penalty for each additional co-channel AP equivalent; adjustable 0–100%.	Starlight sensitivity model. Cisco notes that same-channel cells share available bandwidth in its industrial wireless design guidance. Replace with a predictive channel plan and measured contention.
Goodput and client mix	Estimated per served radio from generation, width, streams, band, and client mix; measured override supported.	Starlight estimate. Advertised PHY or combined multi-radio speed is not application payload. Replace with representative client-to-LAN measurements under expected signal and load.
Design reserve	20% default; 0–100% control. Conservative range also tests +20% activity, -15% cell area, and -20% goodput.	Starlight planning policy for growth and uncertainty. Replace with the organization’s growth forecast, redundancy policy, and risk tolerance.

Wi-Fi access point planning FAQs

How many Wi-Fi access points do I need?

Use the largest count required by coverage, associated-device capacity, and busy-hour airtime, then add a documented design reserve. The answer changes with walls, floors, device density, applications, channels, and measured radio performance.

How many square feet can one AP cover?

A first-pass indoor assumption is often roughly 1,500 to 5,000 square feet per AP, but dense walls, metal, high ceilings, required data rates, and client power can move the practical figure outside that range. Replace the preset with a predictive model or survey measurement when possible.

How many users can one AP support?

There is no universal users-per-AP number. Associated devices consume management resources, while active devices and their applications consume airtime; use both the association limit and per-radio goodput limit, then keep reserve for uneven distribution and retries.

How many APs per floor?

Start by dividing the recommended total across floors and round up, but calculate isolated or differently sized floors separately. Stairwells, concrete slabs, atriums, and uneven occupancy can make a simple equal split inaccurate.

Does Wi-Fi 6 or Wi-Fi 7 increase range?

Not automatically. Newer Wi-Fi generations can improve efficiency and peak capacity, but range is still constrained by frequency, transmit power, antennas, client capability, obstacles, noise, and the data rate required at the cell edge.

How do walls affect AP count?

Walls attenuate and scatter radio signals, so dense masonry, concrete, tile, metal, and foil-backed materials usually require smaller cells and more APs than an open space. Use the obstruction control as a planning adjustment and confirm it with RF measurements.

What RSSI should coverage target?

Choose a target from the requirements of the least capable important client and application. Around -67 dBm with about 25 dB SNR is a common voice and mobile-client design reference, while less demanding data-only designs may accept a weaker edge; measure both RSSI and SNR.

How much AP overlap is needed for roaming?

Overlap should be defined at the required cell-edge signal, not by circles on a floor plan. Voice guidance often uses about 15 to 20 percent overlap on different channels, but the correct amount depends on client roaming behavior, power, band, data rates, and building geometry.

Can I use mesh nodes?

Yes, where cabling is impractical, but a shared wireless backhaul consumes airtime and can reduce capacity at each hop. Prefer wired Ethernet backhaul for predictable capacity and model dedicated backhaul radios and hop count when mesh is necessary.

When is a site survey required?

Use a predictive design and on-site validation for production networks where coverage, roaming, safety, voice, location, high density, unusual materials, or business continuity matter. A calculator is suitable for budgeting and early comparison, not final AP placement or channel design.

Disclaimer

This is an infrastructure planning aid. Validate production Wi-Fi designs with vendor datasheets, local spectrum rules, a predictive design or site survey, real client mix, cabling, PoE budgets, switch capacity, and post-install measurements before relying on the AP count.