Back to Bands & Frequencies
Spectrum Engineering

Frequency Overlap & Coexistence Guide

In unlicensed spectrum, nobody owns a private channel. When smart plugs drop offline, LoRa packets vanish into thin air, or Wi-Fi HaLow video stutters, invisible co-channel collisions are almost always the cause. This guide and interactive spectrum map show exactly how protocols overlap—and how to plan clean channels.

Interactive Spectrum Map

Frequency Overlap & Coexistence Visualizer

Protocol Layer Toggles:
2.4 GHz ISM band (2400–2483.5 MHz): protocol channel overlap Wi-Fi channels 1, 6 and 11 are centred at 2412, 2437 and 2462 MHz. Zigbee/Thread channels 11–26 sit underneath them; channels 15, 20, 25 and 26 are marked as safe. Bluetooth LE advertising channels 37, 38 and 39 sit at the band edges and between Wi-Fi 1 and 6, and microwave-oven noise is centred near 2450 MHz. Microwave Oven Noise Wi-Fi Ch 1 2412 MHz Wi-Fi Ch 6 2437 MHz Wi-Fi Ch 11 2462 MHz 11 12 13 14 15 ★ 16 17 18 19 20 ★ 21 22 23 24 25 ★ 26 ★ Adv 37 Adv 38 Adv 39 2400 2410 2420 2430 2440 2450 2460 2470 2480 2485 MHz

Hover or Tap Any Channel in the Spectrum Map

Frequency: —
Protocol: Select a channel above
Overlap: Inspect which systems share this frequency space.
Field Recommendation: —

01 · The 2.4 GHz Battleground (2400 – 2483.5 MHz)

The 2.4 GHz ISM band is only 83.5 MHz wide, yet it is simultaneously shared by high-bandwidth Wi-Fi routers, low-power Zigbee/Thread mesh networks, Bluetooth peripherals, and unshielded microwave ovens.

The Non-Overlapping Wi-Fi Rule (1, 6, 11)

A standard 2.4 GHz Wi-Fi channel requires roughly 20 to 22 MHz of spectral width to accommodate its OFDM or DSSS carrier roll-off. Because channel centers are spaced only 5 MHz apart, adjacent channels trample each other:

  • Channel 1 (2412 MHz): Extends from 2401 to 2423 MHz.
  • Channel 6 (2437 MHz): Extends from 2426 to 2448 MHz.
  • Channel 11 (2462 MHz): Extends from 2451 to 2473 MHz.
  • Why Intermediate Channels Fail: Setting an AP to Channel 2, 3, 4, or 5 causes bidirectional packet collisions with both Channel 1 and Channel 6, generating continuous retransmissions without 802.11 clear-channel coordination.
  • The 40 MHz Trap: Enabling 40 MHz channel bonding in 2.4 GHz consumes two-thirds of the entire band (e.g. Ch 1 + 5 or Ch 6 + 10), guaranteeing collisions with every smart home device in the house. Always lock 2.4 GHz Wi-Fi to 20 MHz.

Zigbee & Thread (IEEE 802.15.4) Channel Selection

IEEE 802.15.4 divides 2.4 GHz into 16 channels numbered 11 through 26, each 2 MHz wide with 5 MHz spacing. Because Zigbee transmits at low power (+0 to +10 dBm) compared to home Wi-Fi (+20 to +30 dBm), Wi-Fi can easily drown out Zigbee packets:

Zigbee ChannelCenter FreqWi-Fi 1/6/11 RelationshipCoexistence RatingField Guidance
Ch 11–142405 – 2420 MHzWi-Fi Channel 1High CollisionSevere packet drops during Wi-Fi video streaming or large downloads.
Ch 152425 MHzBetween Wi-Fi Ch 1 & Ch 6Safe Null ★EXCELLENT: Sits cleanly in the 5 MHz spectral null between Wi-Fi 1 and 6.
Ch 16–192430 – 2445 MHzWi-Fi Channel 6High CollisionDirectly inside Wi-Fi Channel 6 energy envelope. Avoid.
Ch 202450 MHzBetween Wi-Fi Ch 6 & Ch 11Guard Null (Watch Microwave)Clear of Wi-Fi 6 and 11, but directly in the 2450 MHz microwave oven noise path.
Ch 21–242455 – 2470 MHzWi-Fi Channel 11High CollisionDirectly inside Wi-Fi Channel 11 energy envelope. Avoid.
Ch 252475 MHzAbove Wi-Fi Channel 11Best Safe Channel ★★★GOLD STANDARD: Completely clear of standard Wi-Fi channels 1, 6, and 11. Full TX power.
Ch 262480 MHzUpper Band EdgeClear Band (Reduced Power)Zero Wi-Fi collision. Note: In North America, FCC band-edge rules force some transceivers to reduce power.

The Zigbee Channel 25 vs 26 Dilemma in North America

While Zigbee Channel 26 sits completely outside standard Wi-Fi, it borders the FCC band edge at 2483.5 MHz. To pass FCC out-of-band emissions testing, many commercial transceivers (including Silicon Labs and TI chips) automatically clamp transmit power on Channel 26 down to +3 dBm or lower. Channel 25 (2475 MHz) avoids Wi-Fi Channel 11 while retaining full +19 dBm transmit power, making it the safest choice across the Americas.

Why Bluetooth LE Survives in 2.4 GHz

Bluetooth uses 40 channels spaced 2 MHz apart. It survives the Wi-Fi onslaught through two distinct mechanisms:

  • Dedicated Advertising Channels: The three primary beaconing and pairing channels (Ch 37 @ 2402 MHz, Ch 38 @ 2426 MHz, and Ch 39 @ 2480 MHz) were intentionally engineered into the gaps between Wi-Fi channels 1, 6, and 11.
  • Adaptive Frequency Hopping (AFH): For active connections, Bluetooth hops up to 1,600 times per second across 37 data channels. If it detects packets colliding with an active Wi-Fi channel, it dynamically marks those frequencies as “bad” and restricts hopping to clean spectrum.

02 · 915 MHz Sub-1GHz Coexistence (902 – 928 MHz)

In North America, the 902–928 MHz band (ITU Region 2) provides 26 MHz of shared spectrum. Unlike European ETSI bands (which mandate polite 1% duty cycles), FCC Part 15 allows continuous high-power transmission (up to 1 W conducted / 4 W EIRP) using frequency hopping or digital modulation.

The LoRa vs. Wi-Fi HaLow Conflict

LoRa transceivers (such as Meshtastic nodes and Helium hotspots) send low-power, narrowband (125 kHz) chirp signals. Wi-Fi HaLow (802.11ah) transmits high-power, wideband (2 MHz, 4 MHz, or 8 MHz) OFDM carriers.

Because Meshtastic and LoRaWAN gateways default to US915 Sub-Band 2 (903.9 to 905.3 MHz), enabling the wrong Wi-Fi HaLow channel will completely swamp the local LoRa noise floor:

Wi-Fi HaLow ChannelCenter FreqLoRa / Z-Wave OverlapCoexistence StatusField Engineering Recommendation
HaLow Ch 2 (2 MHz)903.0 MHzLoRa Sub-Band 1 & Sub-Band 2 edgeSevere OverlapDo not use if running Meshtastic or LoRaWAN Sub-band 2 nearby.
HaLow Ch 6 (2 MHz)905.0 MHzLoRa Sub-Band 2 (Meshtastic 903.9–905.3 MHz)Fatal OverlapDirect collision with primary Meshtastic and Helium default channels.
HaLow Ch 8 (4 MHz)906.0 MHzLoRa Sub-Band 2 top edge & Meshtastic default 906.875 MHzFatal OverlapNEVER enable 4 MHz Ch 8 on sites with LoRa hardware.
HaLow Ch 14 (2 MHz)909.0 MHzZ-Wave Classic US (908.4 MHz)Z-Wave OverlapKeep separated from Z-Wave smart home controllers.
HaLow Ch 30 (2 MHz)917.0 MHzNone (Clear of LoRa SB 2 & Z-Wave)Safe Channel ★Excellent choice for long-range IP cameras running alongside LoRa.
HaLow Ch 32 (4 MHz)918.0 MHzNone (Z-Wave 916 MHz & ZWLR 920 MHz only at its edges)Best 4 MHz Choice ★★★Delivers 10+ Mbps video backhaul, clear of all LoRa uplinks.
HaLow Ch 34 (2 MHz)919.0 MHzNone (Clear of LoRa SB 2 & Z-Wave)Best 2 MHz Choice ★★★GOLD STANDARD: The cleanest 2-MHz HaLow channel for coexisting with off-grid LoRa.
HaLow Ch 38 (2 MHz)921.0 MHzNone (Above ZWLR 920 MHz)Safe Channel ★Clear upper-band operation.

03 · Field Coexistence Cheat Sheet & Golden Setups

Tested channel pairings for common multi-radio installations:

Smart Home Automation (2.4 GHz + Sub-1GHz)

Wi-Fi Channel Plan: Wi-Fi AP on Channel 1 (2412 MHz) and Channel 6 (2437 MHz) @ 20 MHz width only.
IoT Channel Plan: Zigbee / Thread Coordinator fixed on Channel 25 (2475 MHz). Z-Wave on 908.4 / 916.0 MHz.
Why it works: Wi-Fi handles heavy household streaming while Zigbee operates in the virgin spectrum above Wi-Fi Ch 11. Z-Wave operates in sub-1GHz with zero 2.4 GHz contention.

Long-Range Field Station (HaLow Video + LoRa Mesh)

Wi-Fi Channel Plan: Wi-Fi HaLow AP set to 2 MHz Channel 34 (919.0 MHz) or 4 MHz Channel 32 (918.0 MHz).
IoT Channel Plan: Meshtastic / LoRaWAN operating on US915 Sub-band 2 (903.9–905.3 MHz).
Why it works: 14+ MHz frequency separation between LoRa uplinks and HaLow carrier protects sensitive LoRa receiver LNAs while passing 5+ Mbps video.

Dense Urban Sensor Cluster (Zero 2.4 GHz Footprint)

Wi-Fi Channel Plan: Household Wi-Fi strictly limited to 5 GHz and 6 GHz UNII channels.
IoT Channel Plan: All telemetry mapped to 915 MHz LoRa or Z-Wave Long Range (912 MHz).
Why it works: Completely frees 2.4 GHz spectrum from IoT traffic. Critical in multi-tenant MDUs where 2.4 GHz noise floors regularly exceed -65 dBm.

04 · Physical & Hardware Mitigation Techniques

Channel separation in software is only half the battle. When multiple antennas are mounted within centimeters of each other on a tower, roof mast, or smart home hub, transmitters generate strong out-of-band RF fields that overload the receiver’s Low Noise Amplifier (LNA):

1. Vertical Antenna Stacking

Standard omnidirectional vertical dipoles have a deep radiation null directly above and below their tips. Mounting antennas vertically in line on the same mast provides 30 to 40 dB of isolation compared to mounting them horizontally side-by-side.

2. Minimum Physical Distance

Keep high-power transmitters (+30 dBm Wi-Fi HaLow or ZWLR) at least 1 to 2 meters away from sensitive LoRa gateway antennas. Receiver frontends can be desensitized even when operating on separate frequencies if input power exceeds -10 dBm.

3. Sub-Band Cavity & SAW Filters

On dense radio towers, install a tuned SAW or cavity bandpass filter between the antenna and the LoRa transceiver. A sharp filter centered on 904 MHz strips away out-of-band energy from upper-band HaLow carriers before it reaches the receiver silicon.

Site search