WiFi signal strength, SNR, noise, and channel overlap explained

WiFi troubleshooting gets sloppy when every problem is described as “weak signal.” Weak signal is real, but many bad wireless experiences come from a combination of signal strength, noise, signal to noise ratio, same/overlapping channel contention, channel width, roaming, AP placement, and client behavior.

This guide explains the RF terms that matter when interpreting a WiFi survey or heatmap report.

Signal strength and dBm

Signal strength is commonly expressed in dBm. In WiFi, dBm values are usually negative. A value closer to zero is stronger, so minus 45 dBm is stronger than minus 75 dBm. dBm is useful in reports because RSSI can be handled differently by adapter vendors, while dBm is a more consistent and human-readable way to express signal strength.

Avoid one universal signal promise for every project. A warehouse scanner, voice/video office, guest WiFi lobby, and high density classroom can have different requirements. Signal is only one layer.

RSSI vs dBm

RSSI means Received Signal Strength Indicator. It is common, but not standardized across every adapter/vendor. Some tools convert RSSI into dBm like values; others use internal scales. For survey deliverables, dBm is easier for technical readers to compare across reports.

dBm is logarithmic

A dB scale is not linear. Small looking changes can matter:

This is why RF reports need interpretation. A few dB may or may not matter depending on noise, clients, application needs, and margin.

Noise and interference

Noise is unwanted RF energy in the environment. If noise is high, a client may struggle even when desired signal looks acceptable. This is why “coverage looks fine” can still produce bad performance.

Noise/interference contributors can include other wireless systems, same or overlapping WiFi channel behavior, non WiFi RF sources, industrial equipment, and environmental conditions. A spectrum analysis workflow may be needed when suspected non WiFi interference is part of the problem. Ekahau describes heatmap/interference views and Sidekick 2 spectrum analysis capability, but the survey still needs the right objective and interpretation.

SNR formula

SNR compares the desired signal to the background noise. Higher SNR generally means the receiver can distinguish the WiFi signal more clearly from the noise floor.

The basic formula is:

SNR dB equals signal dBm minus noise dBm

Example:

minus 65 dBm signal minus (minus 95 dBm noise) = 30 dB SNR

A signal strength only heatmap can hide SNR problems. If signal is acceptable but the noise floor is also high, the device may still have poor usable margin.

What each RF layer proves

Channel overlap and contention

WiFi is a shared medium. APs and clients using the same channel must share airtime. That is not automatically bad; WiFi is designed to coordinate channel access. But poor channel planning can create excessive contention and inconsistent performance.

Ekahau’s design material describes channel interference views that identify areas where APs compete on the same or overlapping channels. Ekahau heatmap material also references co channel interference and other noise that can affect performance. The practical takeaway is conservative: review AP placement, channel reuse, channel width, and transmit power together. Do not solve every problem by adding APs.

Adjacent/overlapping channel issues

In 2.4 GHz, overlapping channel use is especially easy to create. The common planning rule is to avoid partially overlapping channels where possible. In North America, channels 1, 6, and 11 are commonly used as non-overlapping 20 MHz choices for 2.4 GHz planning.

That does not mean 2.4 GHz is always the answer. It means if legacy devices require 2.4 GHz, the channel plan must be deliberate.

Channel width tradeoffs

Wider channels can increase potential throughput, but they also consume more spectrum and can reduce the number of clean reuse opportunities. Practical guidance:

• 2.4 GHz: keep planning conservative; 20 MHz channels are usually the practical baseline.
• 5 GHz: 20/40/80 MHz decisions depend on density, AP count, DFS policy, client support, and throughput requirements.
• 6 GHz: more spectrum can help, but only clients that support 6 GHz benefit; validate requirements before designing around it.

Ekahau channel planning material supports planning channels, avoiding interference, and adjusting plans to the environment. Treat channel width as a design decision, not a bigger is always better setting.

Why heatmap colors can mislead

A green area may still fail if:

• noise is high
• channel reuse is poor
• APs are overloaded
• roaming boundaries are badly placed
• clients are on the wrong band
• the critical device has a weak radio or poor roaming behavior
• application sessions time out during movement
• the walked path did not match the real user path

This is why PacketScout’s WiFi heatmap services and survey reports should pair visuals with interpretation.

Field diagnosis examples

Green signal map, bad SNR

Signal is acceptable, but the noise floor is elevated. The next step is to inspect noise/interference sources, channel behavior, and whether spectrum analysis is needed.

Strong AP signal, scanner drops

The scanner may have different roaming behavior, band support, antenna performance, or application timeout behavior than the survey device. In a warehouse, compare RF results to actual pick paths and device models.

More APs made the network worse

Adding APs can improve capacity or coverage when justified. It can also create extra contention, poor channel reuse, and roaming confusion if power/channel planning is not reviewed.

Non WiFi interference suspected

If WiFi measurements show suspicious noise/interference patterns, spectrum analysis may be needed. Sidekick 2’s stated capabilities can support deeper measurement, but the workflow still needs interpretation.

How RF analysis turns into recommendations

Good survey analysis can lead to different actions:

• move APs closer to critical areas
• add APs where coverage or capacity requires it
• reduce transmit power where overlap/roaming is poor
• change channels or channel widths
• remove or disable unnecessary radios
• investigate non WiFi interference
• validate device specific behavior
• re survey affected areas after changes

For warehouse specific interpretation, read Warehouse WiFi Design Best Practices. For a basic heatmap primer, read What Is a WiFi Heatmap?.

Troubleshooting decision tree

Use a simple decision tree when reading RF results:

1. Signal weak in the complaint area? Check AP placement, mounting, obstruction, band, and whether the area was actually walked.
2. Signal acceptable but SNR poor? Look for elevated noise/interference, overlapping channels, or environmental RF issues.
3. Signal and SNR acceptable but users still complain? Review channel reuse, AP load, roaming boundaries, client capability, and application behavior.
4. Only one device type fails? Treat it as a client/workflow issue until proven otherwise. Compare scanner/phone/laptop behavior.
5. Problems follow movement? Review roaming path, AP overlap, power levels, and application session tolerance.
6. Problems follow time of day or operations? Check density, dock activity, machinery, inventory state, or temporary interference.

This approach keeps the report from jumping straight from “complaint” to “add APs.”

Co channel contention vs adjacent channel interference

Do not treat every channel problem as the same failure. Two APs on the same channel create co channel contention: the devices can usually hear each other and take turns using the medium. That may be slow, but it is at least polite. Adjacent channel interference is different. Overlapping channels can raise noise and corrupt frames because devices may not decode each other cleanly enough to coordinate.

For report language, separate the two ideas:

This is why a survey should not stop at “signal is green.” If the same map also shows poor SNR, high channel utilization, or overlapping channel pressure, the fix may be channel/power planning rather than more APs.

Typical design targets by application

Targets are not standards and should not be promised blindly, but practical designs need starting points. A PacketScout report can use target bands like this as a scoping and validation aid, then adjust for the actual client/application requirements:

The exact numbers should be tuned to the project. A scanner fleet, VoIP handset, laptop, tablet, and guest phone do not behave the same way.

Airtime and channel utilization

A network can have acceptable signal and still perform poorly if the channel is busy. WiFi is a shared medium. Every client, AP, retry, beacon, management frame, and low rate device consumes airtime. Adding an AP can help if it improves cell sizing and reuse; it can hurt if it adds more contention on the same channel.

Look for airtime clues in controller data and survey interpretation:

• high channel utilization during business hours
• high retry percentages
• clients stuck at low data rates
• too many APs heard at similar strength in the same area
• wide channels in a dense AP plan
• legacy 2.4 GHz devices consuming airtime
• scanner or voice clients roaming late and transmitting at weak rates

The practical recommendation should connect the symptom to the cause. “Add two APs” is weak. “Reduce 2.4 GHz contention, tighten 5 GHz cell overlap, move the aisle AP below the obstruction line, and validate scanner roaming on the receiving path” is useful.

WiFi 6E and WiFi 7 RF notes

WiFi 6E and WiFi 7 make channel planning more interesting because 6 GHz adds cleaner spectrum for compatible clients. That does not remove the need for measurement. 6 GHz propagation, client support, channel width, and AP placement still need validation by zone.

For 2026 style survey work, add these checks:

• separate 2.4 GHz, 5 GHz, and 6 GHz heatmap layers
• identify which client groups can actually use 6 GHz or WiFi 7 features
• avoid assuming 80/160/320 MHz channels are always appropriate
• review Preferred Scanning Channel behavior where relevant
• confirm whether the design relies on Multi Link Operation, and whether clients support it
• keep a fallback plan for older 5 GHz and 2.4 GHz devices

The field report should say where the modern features help and where classic RF fundamentals still control the design.

FAQ

Is stronger WiFi signal always better?

No. Stronger is not always better if it creates poor roaming, unnecessary overlap, or more contention. The goal is the right signal, SNR, channel plan, and capacity for the environment.

What is SNR in WiFi?

SNR is the difference between the desired signal and background noise. Example: minus 65 dBm signal minus minus 95 dBm noise equals 30 dB SNR.

Can a heatmap show channel overlap?

Many survey/design tools can visualize channel related behavior, but overlap must be interpreted with AP placement, band use, client requirements, channel width, and transmit power.

Does a green heatmap prove the network is good?

No. A green signal map can still hide poor SNR, noisy RF, bad channel reuse, overloaded APs, roaming issues, or client specific limitations.

Utilization and retry numbers worth a closer look

Signal and SNR still matter, but airtime tells you whether the channel has room to breathe. These readings deserve a closer look during review:

These are not pass or fail numbers. They are the readings that justify a closer look before recommending hardware.