RSSI Calculator
The formula
What the wi-fi snr tells you
The number that actually decides Wi-Fi speed — signal above the noise floor — translated to negotiable MCS and PHY rate.
Calculation: SNR = RSSI − noise; required SNR per MCS from 802.11 tables; usable = highest MCS under SNR. Enter your inputs and every substitution is shown below the result.
Reading the result
RSSI alone is vanity; a −60 dBm signal in a −70 dBm noise floor is worse than −75 dBm in −95. Engineers plan in SNR.
Rules of thumb: Design floors: 25 dB SNR for voice/video cells, 15 dB for general office, 10 dB minimum coverage edge.
Limitations and best practice
Noise floor includes your neighbouring BSS traffic — in apartments the interference term is ~10× thermal noise, and channel planning, not power, recovers it.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
What is a realistic noise floor?
Can I improve RSSI and still fail?
Source & methodology
MCS SNR thresholds from IEEE 802.11 reference receivers; Wi-Fi Alliance voice design target −67 dBm / 25 dB SNR.
RSSI: what this tool answers
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. There are plenty of pages about RSSI; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
There is a habit that separates people who get useful answers from Networks & Storage numbers: they decide what question the figure answers before they compute it. RSSI answers “Signal-to-noise ratio?” — and nothing else, which is precisely why the result is trustworthy.
In plain terms, RSSI answers the question "Signal-to-noise ratio?". The measurement matters because it converts a situation that feels complicated — several inputs pulling in different directions — into a single number you can act on. Within Technology & Computing, Networks & Storage is the context where this figure is quoted most often, and professionals treat it as a first-pass screen rather than a verdict.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to signal-to-noise ratio = 23.0 dB on the default inputs, and the sensitivity section ranks the inputs that move the result — Noise floor first, at ≈37.0 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.
The RSSI formula, explained
One formula, published in full: SNR = RSSI − noise; required SNR per MCS from 802.11 tables; usable = highest MCS under SNR. Anything you can read, you can reproduce in a spreadsheet, and that reproducibility is the whole point of printing it rather than hiding it behind a button.
Measured RSSI (dBm) (example value -62) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Noise floor (dBm) (example value -85) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Client radio capability (example value Up to 256-QAM) is a choice rather than a quantity — pick the option that matches your situation, because the calculation path branches here. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
A fully worked RSSI example
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Measured RSSI (dBm), Noise floor (dBm), Client radio capability. The computed signal-to-noise ratio comes out at 23.0 dB, which the interpretation band labels “Amber — mid MCS, fine for work”.
- SNR = -62 − (-85) = 23.0 dB
- 802.11 MCS tables need 10 dB for MCS2 up to 34 dB for MCS9
- Highest sustainable at this SNR ⇒ MCS 5 (capped by client class)
- Rule of thumb: −3 dB of SNR halves your robust modulation options
Link quality (SNR mapped to %) — 51.4%. This is the number experienced users quote when the headline alone would mislead.
Negotiable MCS index — 5. This is the number experienced users quote when the headline alone would mislead.
Expected single-stream PHY — 140 Mbps. This is the number experienced users quote when the headline alone would mislead.
SNR margin to 25 dB (voice target) — -2.0 dB. Compare it against the main result of 23.0 dB before drawing conclusions.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
How far RSSI can reasonably move
Single-point answers invite false confidence, so the same engine was run across a band around the input that matters most here. Each row is a full recalculation of RSSI, not an interpolation.
| Noise floor setting | Signal-to-noise ratio |
|---|---|
| 80 % of the example value | 6.0 dB |
| 90 % of the example value | 14.5 dB |
| example inputs | 23.0 dB |
| 110 % of the example value | 31.5 dB |
| 120 % of the example value | 40.0 dB |
The corridor runs from 6.0 dB to 40.0 dB across that band — which is the range worth planning inside rather than the single 23.0 dB point estimate. Reproduce it in the form above by editing Noise floor alone; the substitution steps will follow your figures exactly.
Sensitivity: which inputs change RSSI the most
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the signal-to-noise ratio recomputed, so the ranking below is measured rather than asserted. Read it as a map of where RSSI is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- Noise floor +10 % → RSSI = 31.5 dB · −10 % → 14.5 dB (the signal-to-noise ratio shifts ≈37.0 %)
- Measured RSSI: ten percent up gives 16.8 dB, ten percent down gives 29.2 dB — ≈27.0 % of the signal-to-noise ratio either way
Noise floor is the dominant lever here: ten percent either way moves the result by about 37.0 %, from 14.5 dB to 31.5 dB. Spend your verification effort there first, and treat Measured RSSI as the second priority (≈27.0 % per ten percent). Everything below that can stay approximate, which is a licence to stop chasing data that would not change the decision.
Interpreting the RSSI verdict
Nobody acts on a bare figure — they act on a figure with a comparison attached. The verdict attached to the default calculation — “Amber — mid MCS, fine for work” — is one band on a ladder your own figure may sit somewhere else on. How much of that band is luck? On Noise floor alone ten percent either way covers 14.5 dB to 31.5 dB. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
In Technology & Computing, RSSI is one instrument in an orchestra: on its own it is a number, next to Link quality (SNR mapped to %) and Negotiable MCS index it becomes a diagnosis. The tools linked above exist so the headline never has to carry that weight alone.
The errors that quietly break an RSSI figure
Noise floor includes your neighbouring BSS traffic — in apartments the interference term is ~10× thermal noise, and channel planning, not power, recovers it. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Comparing an RSSI computed here with a figure from another source that uses different conventions. Same name, different denominator — the disagreement is usually in the definitions, not the data.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Noise floor dominating — a careful figure there beats false precision everywhere else.
The subtlest error is answering the wrong question precisely. Confirm that signal-to-noise ratio is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
Before you trust your RSSI: a short checklist
- Validate inputs against a live measurement, not datasheet peak figures.
- Verify each input against its original source document, not memory.
- Check Noise floor before anything else: it is the measured dominant input, ≈37.0 % of RSSI per ten percent.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Note the date and the inputs beside the number so the figure can be audited later.
- Run the ±10 % stress on the top two levers and check that your conclusion survives both.
A routine for decision-grade RSSI
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — start from evidence. The inputs behind RSSI are measured rssi (dbm), noise floor (dbm), client radio capability. Write them down with their source next to each one; if you cannot name where a figure came from, that is the input most likely to be wrong. The point of transparency is that a reader can disagree with a specific line rather than with you.
Step 2 — compute the version you would not be embarrassed by. If a stranger audited your inputs, which set would you hand over? Enter that set, read the result, and treat everything else as upside. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Step 3 — measure what deserves measuring. The ranked levers above tell you where a careful figure pays off. Everything else can stay approximate, which is a licence to stop hunting for data you do not need. When in doubt, prefer the boring input: the interesting one is usually the one you misread.
Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. If a result feels obviously right, that is the moment to check the inputs hardest.
Step 5 — record the context, not just the number. Note today’s date and the inputs alongside the 23.0 dB output. Six months from now the context is what turns this figure into a trend. A result worth acting on survives having its two shakiest inputs halved.
Who actually uses RSSI — and when
Most Networks & Storage disagreements are arithmetic disagreements in disguise. When Signal-to-noise ratio of 23.0 dB sits on the table with its working shown, the conversation stops being about who sounds more confident and starts being about which input is wrong. Estimates improve most when the worst case is written down in ink.
The audience for this page is people who need one trustworthy number before their next decision. In professional Networks & Storage practice the pattern is always the same — screen with RSSI, then invest slow analysis only in whatever survives the screen. The inputs are the part of the work that nobody else can do for you.
Treat RSSI like a smoke alarm rather than a painting — its value is in being tested periodically, not in being admired once. Compare the calculation to the rough guess you arrived with, and ask why they differ.
The questions that come up most about RSSI
What affects RSSI the most?
RSSI is driven above all by Noise floor. Perturbing only that field by ten percent either way produced 31.5 dB against the 23.0 dB baseline — a ≈37.0 % response, while Measured RSSI manages ≈27.0 %.
Which matters more: measured rssi or noise floor?
Noise floor, by a factor of about 1.4. Concretely: ten percent on Noise floor is worth ≈37.0 % of RSSI, the same nudge on Measured RSSI only ≈27.0 %. That ranking is re-computed for each page from that page’s own defaults.
What is a typical RSSI?
On the worked example above RSSI comes out at 23.0 dB. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate RSSI by hand?
SNR = RSSI − noise; required SNR per MCS from 802.11 tables; usable = highest MCS under SNR is the entire method. Work the inputs in that order — SNR = -62 − (-85) = 23.0 dB — and you will reach 23.0 dB on the default figures, the same number this tool prints.
What happens to RSSI if noise floor changes by 10 %?
On these inputs a ±10 % change in noise floor takes RSSI to 31.5 dB against the 23.0 dB example — around 37.0 % of the headline. The same test on every other field is in the sensitivity section.
Is the RSSI result of 23.0 dB good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own RSSI sit against the 23.0 dB reference above, how far would a plausible input error move it (≈37.0 % per ten percent on Noise floor), and what does the alternative option compute to?
How often should I check RSSI?
Whenever an input changes by more than a few percent, and otherwise on the rhythm of your decisions — before a purchase, a review, a renewal. RSSI is a snapshot, not a subscription; stale snapshots are the most common silent error in Technology & Computing planning.
Which model does RSSI use?
The stated formula: SNR = RSSI − noise; required SNR per MCS from 802.11 tables; usable = highest MCS under SNR. It is the same arithmetic the vendor calculators and standards documents implement; differences appear only where vendors tune hidden coefficients, which the pitfall section above flags.
What is a realistic noise floor?
Thermal is −96 dBm in a 20 MHz channel; real offices measure −85 to −75 once neighbours are counted.
Can I improve RSSI and still fail?
Yes — moving a client closer raises both signal and its own interference footprint; re-scan the floor after every change.
Do I need an account to use this RSSI calculator?
No, and no data leaves the tab. The engine runs in the page itself, which is why the worked example, the bands and the sensitivity ranking all respond instantly to your keystrokes.
Glossary for RSSI
- Link quality (SNR mapped to %)
- 51.4% in the default RSSI calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Negotiable MCS index
- 5 on the example inputs — a companion figure printed beside the headline of RSSI so that no result is read in isolation.
- Expected single-stream PHY
- 140 Mbps on the example inputs — a companion figure printed beside the headline of RSSI so that no result is read in isolation.
- Signal-to-noise ratio
- The primary output of this tool: 23.0 dB for the default inputs, computed exactly from SNR = RSSI − noise; required SNR per MCS from 802.11 tables; usable = highest MCS under SNR.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The interpretation attached to a result (“Amber — mid MCS, fine for work” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the RSSI moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Methodology, sources and limits
The model is published arithmetic implemented exactly as written: SNR = RSSI − noise; required SNR per MCS from 802.11 tables; usable = highest MCS under SNR. Source of record: MCS SNR thresholds from IEEE 802.11 reference receivers; Wi-Fi Alliance voice design target −67 dBm / 25 dB SNR. Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
Treat the output as a precise answer to the question you typed: exact arithmetic, transparent formula, published source, no hidden rounding. The sensitivity table above is part of that promise rather than a bonus: it lets you see how much of the result depends on how carefully you measured.
Next steps after the calculation
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
The audience here is people who need one trustworthy number before their next decision. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.