{{ result.summaryHeading }}
{{ result.primaryDisplay }}
{{ result.secondaryText }}
{{ result.statusText }} {{ result.bandLabel }} {{ result.effectiveWidthLabel }} {{ result.poolLabel }}
{{ wifiChannelStageAnchor }} {{ wifiChannelStageWidthLabel }}
Enter the AP count for this band; plan one band at a time when radios differ by floor or area.
APs
Planning size slider {{ apCountRangeLabel }}
Use the same band, width, and regulatory domain that will be configured on the WLAN controller.
Choose FCC/US, ETSI/EU, or a conservative world-safe indoor pool.
Start narrow for dense designs; 2.4 GHz is planned as 20 MHz even if a wider width is selected.
Set whether 5 GHz radar-sharing channels are excluded, allowed, or deliberately preferred.
Pick row for a corridor, grid for a floor plate, or floors for a stacked multi-floor plan.
Use the naming prefix from your controller or survey notes, such as AP, Floor2, or WingA.
Keep 1 for a new plan or match an existing controller naming sequence.
Set the number of stacked floors or zones to offset when Reuse pattern is Floors.
floors
Stacked-floor slider {{ floorCountRangeLabel }}
Use this for known radar hits, neighbor conflicts, controller restrictions, or vendor-specific exclusions.
When a bonded 6 GHz block contains a Preferred Scanning Channel, use it as the primary channel.
Channel 165 is a 20 MHz-only option; it is ignored for bonded 5 GHz widths.
AP Position Primary Block Width Center Flag Reuse Copy
No AP assignments are available
The channel pool needs at least one usable block before assignments can be generated.
{{ row.apName }} {{ row.position }} {{ row.primaryChannel }} {{ row.blockLabel }} {{ row.widthLabel }} {{ row.centerFrequencyLabel }} {{ row.flagLabel }} {{ row.reuseLabel }}
Checkpoint Status Recommendation Detail Copy
{{ row.checkpoint }} {{ row.status }} {{ row.recommendation }} {{ row.detail }}
Primary Block Center Frequency Band segment Assigned APs Flag Copy
No candidate channel blocks remain
Adjust width, regulatory domain, DFS policy, or exclusions to restore the pool.
{{ row.primaryChannel }} {{ row.blockLabel }} {{ row.centerChannel }} {{ row.centerFrequencyLabel }} {{ row.segmentLabel }} {{ row.assignedCount }} {{ row.flagLabel }}
Tags: Networking, Wireless
Free Space Path-loss & RSSI Calculator Estimate free-space path loss and predicted RSSI, then compare reserve, Fresnel clearance, SNR, range, and band tradeoffs for RF links.
MAC Address Details Lookup Look up a MAC address, normalize EUI-48 or EUI-64 input, and compare vendor evidence with bit flags, privacy clues, and special-use checks.
Attenuator Pad Calculator Design a matched Pi or T attenuator pad, compare exact and preferred resistor values, and check power dissipation before choosing parts.
IP3 and SFDR Calculator Estimate IP3, IM3 clearance, and SFDR for RF two-tone tests using gain, noise bandwidth, detection margin, and clean-tone limits.
Customize
Advanced
:

Good Wi-Fi channel planning is less about finding one perfect channel and more about keeping nearby radios from competing for the same airtime. Every access point occupies part of an unlicensed band. When two close APs use the same or overlapping channel block, clients can see more retries, slower roaming, and uneven performance even though each AP is working normally.

The first planning choice is the band because each band has a different reuse problem. The 2.4 GHz band travels far but has very little clean spectrum, so most enterprise designs treat channels 1, 6, and 11 as the practical non-overlapping set. The 5 GHz band offers more channels, but many of them share spectrum with radar systems and may require Dynamic Frequency Selection (DFS). The 6 GHz band adds much more capacity for compatible Wi-Fi 6E and Wi-Fi 7 clients, yet availability, power class, indoor or outdoor use, and Automated Frequency Coordination (AFC) rules vary by country and device class.

Wi-Fi channel width sketch showing narrow channels with more reuse choices and wide bonded blocks with fewer choices.

Channel width is the next tradeoff. A 20 MHz block gives up headline speed but creates more non-overlapping choices for reuse. A 40, 80, 160, or 320 MHz block bonds neighboring 20 MHz channels together, so the same spectrum produces fewer independent blocks. Wide channels can be useful for low-density areas and modern clients, but they become fragile when many access points must fit into the same building.

Regulatory profiles and controller country codes matter because Wi-Fi is not a single worldwide channel list. A channel that appears in a planning note may be unavailable on a specific AP model, restricted to indoor use, tied to lower power, unavailable outdoors, or removed by firmware after the country is set. DFS adds another operational caution: a 5 GHz AP may have to move when radar is detected, and clients that dislike DFS channels can slow down roaming even when the channel is legal.

Channel plans also separate a candidate pool from an actual deployment. A candidate pool answers which blocks are available after the selected band, width, region, DFS stance, and exclusions are applied. Deployment still depends on the controller's country code, AP firmware, device class, local RF scan, neighboring WLANs, and whether the controller should keep managing channels dynamically after the first plan is drafted.

Band Planning strength Common caution
2.4 GHz Longer reach and broad client support. Only a few practical non-overlapping channels, so dense designs reuse quickly.
5 GHz More channels and mature client support. DFS availability, radar events, and regional rules can remove large parts of the pool.
6 GHz Large clean pool for newer clients. Country support, AFC or power-class rules, and client discovery behavior must be verified.

A channel plan is a starting point for a survey, controller configuration, or static override discussion. It cannot prove that airtime will be clean, that neighbors will stay quiet, or that every client will support the chosen band and width. Good deployment work still checks measured channel utilization, adjacent-channel noise, radar history, AP transmit power, antenna layout, and the controller's own radio resource management behavior.

How to Use This Tool:

Plan one radio band at a time so the channel pool, width, and AP count match the radios you intend to configure.

  1. Set Access points to the number of APs or radios that need assignments for the selected band. If the value is outside the supported range, the planner limits it to a readable table size.
  2. Choose Band, Regulatory domain, and Channel width. The summary updates with the effective width, and 2.4 GHz is reduced to 20 MHz because wider bonding is not useful for this plan.
  3. For 5 GHz, choose a DFS policy. Avoid DFS for stability-sensitive WLANs, allow it when the site can use the extra spectrum, or select DFS-only when you are intentionally checking the radar-sharing pool.
  4. Pick a Reuse pattern that resembles the layout: row for a corridor, grid for a floor plate, or floors for a stacked building. Use Floors in Advanced when the floors pattern is selected.
  5. Use Advanced fields for AP naming, the first AP number, excluded channel numbers or ranges, 6 GHz PSC preference, and 5 GHz channel 165. Invalid exclusion tokens are ignored and listed in Planning notes.
  6. Review AP Channel Assignments, Planning Brief, Channel Load Chart, and Candidate Channel Pool. Copy or download the table, chart, or JSON outputs only after the status and planning notes match your design intent.

Interpreting Results:

The first thing to check is whether the channel pool is ready or blocked. A ready result means at least one candidate block survived the band, width, regulatory profile, DFS policy, and exclusion filters. A blocked result means the planner cannot assign APs until you lower the width, allow more channels, change the domain profile, or remove exclusions.

Reuse pressure is the main judgment cue. Unique assignment means no block is reused. Light reuse means the busiest block has two APs. Managed reuse covers three to four APs on the busiest block, and heavy reuse means more than four APs share one block. Those labels are planning warnings, not measured RF guarantees.

A block label such as 38[36] means the bonded block is centered on channel 38 and uses channel 36 as the primary channel. The Flag column distinguishes DFS, non-DFS, PSC, and standard blocks, while the Planning Brief explains why a pool shrank or why a width choice needs extra care.

Do not treat a clean assignment table as deployment approval. Verify the controller country code, AP firmware, client support, indoor or outdoor mode, local RF scan, neighboring WLANs, and any 6 GHz AFC or power-class requirement before locking static channels.

Technical Details:

Wi-Fi channel planning starts by converting band rules into candidate channel blocks. Each block has a primary channel used by clients, a center channel used to describe the bonded block, a center frequency, and one or more 20 MHz member channels. Filters then remove blocks that do not match the selected band, width, region, DFS stance, or manual exclusions.

For bonded channels, the center channel is the midpoint of the member channel list. The exclusion check is intentionally broad: a block is removed when the excluded value matches its primary channel, center channel, or any bonded 20 MHz member channel. This prevents a range such as 52-64 from leaving behind an 80 MHz block that still uses those channels internally.

Formula Core:

Channel frequency labels use the standard 5 MHz channel-number spacing for the displayed band.

f2.4 = 2407+5c MHz, except channel 14 uses 2484 MHz f5 = 5000+5c MHz f6 = 5950+5c MHz

In the formula, c is the channel number used for the displayed primary or center channel. For example, a 5 GHz 40 MHz block labeled 38[36] has a center frequency of 5000 + 5 x 38 = 5190 MHz, while the primary channel 36 corresponds to 5180 MHz.

Rule Core:

Band Pool construction Boundary behavior
2.4 GHz Uses channels 1, 6, and 11 as 20 MHz blocks. Requested widths above 20 MHz are normalized to 20 MHz and reported in Planning notes.
5 GHz Builds 20, 40, 80, or 160 MHz blocks from supported U-NII channel groups. 320 MHz has no practical 5 GHz block here. DFS policy can remove, allow, or require channels 52 through 144.
6 GHz Builds 20, 40, 80, 160, or 320 MHz blocks from the selected indoor planning profile. When PSC preference is enabled, a block that contains a Preferred Scanning Channel uses that channel as primary.

Regulatory profiles are practical planning profiles, not legal certificates. The FCC / US indoor profile keeps the broad 5 GHz and 6 GHz starting pool. The ETSI / EU indoor profile is narrower for 5 GHz high channels and uses a lower 6 GHz planning pool. The world-safe profile is more conservative and removes channel 144 from the 5 GHz plan.

Mechanism How it is calculated What to verify
Row pattern Access points rotate through the candidate pool in sequence. Use for corridors or linear areas where AP order follows a simple path.
Grid pattern Rows and columns are derived from the AP count, with each row offset through the pool. Check that the generated R and C positions roughly match the real floor plate.
Floors pattern The AP list is split across the selected number of floors, with each floor offset through the pool. Confirm AP counts per floor before copying the assignments to a controller.
Maximum APs assigned to one block Reuse pressure label Planning meaning
0No poolNo AP assignment can be produced.
1Unique assignmentEvery assigned AP has its own channel block.
2Light reuseThe busiest block is reused once.
3 to 4Managed reuseSeveral APs share the busiest block, so spacing and power settings matter.
More than 4Heavy reuseThe pool is tight for the AP count and should be reconsidered before production use.

The calculation is deterministic. The same AP count, band, width, domain profile, DFS policy, layout pattern, exclusions, PSC setting, and channel 165 setting produce the same assignment order until those inputs change.

Accuracy Notes:

The planner is useful for first-pass channel allocation, survey preparation, and controller handoff notes. It does not measure airtime or confirm that a channel is legal for a specific product in a specific country.

  • AP firmware, controller country code, device class, and indoor or outdoor mode remain authoritative for allowed channels.
  • DFS channels can change after radar detection, so a static 5 GHz plan needs operational history and monitoring.
  • 6 GHz plans must be checked against local adoption, client capability, power class, and AFC requirements where they apply.
  • Neighbor networks, AP power, antenna placement, wall loss, and client distribution can make a tidy channel rotation perform poorly.

Worked Examples:

Scenario Inputs Expected result What it means
Open office 5 GHz draft 12 access points, 5 GHz, FCC / US indoor, 40 MHz, avoid DFS, grid pattern. Channel pool shows four non-DFS 40 MHz blocks, and Reuse pressure is Managed reuse. The plan is usable for a first pass, but 12 APs over four blocks means placement and power tuning still matter.
Small 2.4 GHz overlay 6 access points, 2.4 GHz, 40 MHz requested, row pattern. Planning notes report 40 MHz normalized to 20 MHz, and AP assignments rotate through channels 1, 6, and 11. Each practical 2.4 GHz channel is reused twice, so the result should be treated as a sparse compatibility overlay, not a high-capacity design.
Blocked 5 GHz width 8 access points, 5 GHz, 320 MHz, any DFS policy. Channel pool is blocked, AP Channel Assignments is empty, and Planning notes explain that 5 GHz has no practical 320 MHz block. Choose 20, 40, 80, or 160 MHz for 5 GHz, or move the 320 MHz check to 6 GHz where supported.
6 GHz PSC preference 10 access points, 6 GHz, 80 MHz, FCC / US indoor, Prefer 6 GHz PSC primaries enabled. Candidate Channel Pool marks blocks that use PSC primaries, and Planning Brief reports the PSC block count. PSC primaries can reduce discovery work for compatible clients, but the AP model, country setting, and client support still need confirmation.

FAQ:

Does a ready channel pool mean the plan is legal to deploy?

No. Ready means the selected planning profile still has candidate blocks. The AP, controller, country code, device class, and local regulations decide what can actually be used.

Why did avoiding DFS remove so many 5 GHz choices?

The DFS filter removes blocks that include channels 52 through 144. Wider 5 GHz blocks often include DFS members, so avoiding DFS can shrink the pool quickly.

What should I do when no candidate channel blocks remain?

Check Planning notes, then reduce Channel width, allow DFS if appropriate, change the Regulatory domain, remove stale Excluded channels, or move a 320 MHz plan from 5 GHz to 6 GHz.

Why are excluded channels matched against bonded blocks?

A bonded block can contain several 20 MHz member channels. Matching primary, center, and member channels prevents a block from surviving when it still touches an excluded channel.

Do my AP names and exclusions leave the browser for calculation?

The channel plan is calculated in the browser. AP names, exclusions, and generated assignments are not submitted to a planning service by this calculator.

Should I disable controller radio resource management after using this?

Not by default. Use the assignments as a planning draft or comparison point, then decide whether static channels, partial constraints, or controller-managed channels fit the measured site.

Glossary:

Channel block
A 20, 40, 80, 160, or 320 MHz planning unit made from one or more 20 MHz channels.
Primary channel
The channel a client uses as the main reference inside a bonded block.
Center channel
The midpoint channel used to label a bonded block and calculate its center frequency.
DFS
Dynamic Frequency Selection, a radar-protection requirement that affects many 5 GHz channels.
PSC
Preferred Scanning Channel, a 6 GHz primary channel that can make network discovery more efficient for compatible clients.
Reuse pressure
The maximum number of access points assigned to the same channel block.
AFC
Automated Frequency Coordination, a system used in some 6 GHz operation modes to protect incumbent users.

References: