Map Your Dead Zones: Heatmap Apps and Room-by-Room Testing

You do not need a heatmap to fix most Wi-Fi problems. You do need numbers. A heatmap is simply the most legible way to record them, and the free analyzer apps get you most of the way there. Here is what to install, what to measure, and what the readings mean.

What you are actually measuring

There are two numbers, and confusing them is the most common mistake.

• Signal strength (RSSI), in dBm. How loudly your device can hear the router. Always negative; closer to zero is stronger. This tells you about coverage.
• Throughput, in Mbps. How much data actually gets through, measured by a speed test. This tells you whether the link is usable.

You need both, because they come apart in a diagnostically useful way. A strong signal with terrible throughput means congestion or interference — adding hardware will not help, and the interference page is where to go. A weak signal with terrible throughput means coverage, and hardware is the answer.

The practical target is −67 dBm or better in every room you care about. That figure is the conventional floor for reliable real-time traffic such as a video call, and it is a far more useful design goal than any coverage claim printed on a box.

The apps worth using

On Android: a Wi-Fi analyzer

Android exposes the full Wi-Fi scan API to apps, so the analyzer category is genuinely useful here. Any reputable analyzer will show you every network in range, its channel, its width and its signal strength, updating live as you walk. That channel view is the single most valuable screen: it shows you immediately whether your 2.4 GHz channel is stacked with five neighbors.

On iOS: AirPort Utility, or a laptop

Apple restricts third-party apps from reading Wi-Fi signal data, which is why the iOS analyzer apps are so thin. The workaround is Apple's own AirPort Utility: install it, then turn on the Wi-Fi Scanner switch inside the iOS Settings app under the AirPort Utility entry. You then get a live scan with RSSI values. It is clunky and it works.

On a Mac, holding Option while clicking the Wi-Fi menu shows RSSI and channel directly, with no app at all. On Windows, netsh wlan show interfaces in a terminal reports signal as a percentage.

Actual heatmap software

True heatmapping — where you load a floor plan and walk a route, and the app paints coverage onto the plan — is a paid desktop category aimed at installers. It is genuinely excellent and almost always overkill for one house. If you are wiring a large or awkward building and want to do it once rather than twice, a trial license for an evening is money well spent. Otherwise a list of rooms and two numbers per room is enough.

How to run the test properly

1. Reboot the router first and give it five minutes. Otherwise you are measuring months of accumulated drift rather than the house.
2. Use one device for the whole walkaround. Devices differ more than rooms do.
3. Record three things per room: signal strength, which band you are on, and a speed test result. The band matters — a good reading on 2.4 GHz and nothing on 5 GHz is a very different situation from a good reading on both.
4. Measure at use height and use position. On the sofa, at the desk, in bed. A reading taken standing in a doorway is a reading of the doorway.
5. Walk the boundaries. Stand on one side of a suspect wall, then the other. A ten-to-twenty decibel drop across one wall identifies your obstacle precisely.
6. Repeat the worst room at 9pm. If it is dramatically worse in the evening, you have a congestion problem on top of, or instead of, a coverage problem.

Reading your results

Once you have the table, the interpretation is mechanical. A smooth taper with distance means you need coverage further out, which is a mesh sizing question. A cliff edge at one wall means you need to get past that wall, which may mean a wired option rather than a wireless one. Strong signal with poor speed means congestion. And if the numbers are fine everywhere but the experience is not, the problem is likely the router itself dropping clients rather than failing to reach them — that is a different page.

Whatever you conclude, you now have a before number. When you install the fix, walk the same route again. If the bad room did not improve, the fix was wrong and you can return it while you still can.