Specificity Calculator
The formula
What the false-alarm discipline tells you
Specificity is the share of truly-negative people the test correctly clears — its ability to avoid false alarms.
Calculation: Specificity = TN ∕ (TN + FP). Enter your inputs and every substitution is shown below the result.
Reading the result
93% specificity on 1,000 healthy screens yields 70 false positives that all need confirming workups.
Rules of thumb: Confirmatory testing ≥99%; screening tolerates 90–95% with follow-up
Limitations and best practice
In low-prevalence screening even 98% specificity drowns the true cases: 20 fakes per 1000 healthy versus maybe 5 real cases.
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
Why is specificity vital for confirmatory tests?
Does raising specificity cost sensitivity?
How do prevalence and specificity interact?
Source & methodology
Standard diagnostic-accuracy definitions (STARD).
Specificity explained: formula, worked example and honest limits
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. Searchers land on a Specificity page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
Like most useful measures, Specificity is a summary, and summaries hide as much as they reveal. The companion outputs and the input table are here to reopen what the headline compressed.
It helps to separate the mechanics from the interpretation. The mechanics are fixed: Specificity = TN ∕ (TN + FP). Anyone, anywhere, entering the same inputs will get the same 93.0 %. The interpretation is where experience counts: whether 93.0 % is good, normal or alarming depends on comparisons covered below, and that is the part most articles about Specificity never explain.
Nothing below is stock text pasted around a number: the worked example computes specificity = 93.0 % from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — True negatives first, at ≈0.8 % 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 Specificity formula, explained
Here is the complete model this tool runs — Specificity = TN ∕ (TN + FP) — with each input explained below. If a competitor’s page gives you a different answer from the same inputs, this is the text that settles which of you is right.
True negatives (healthy & clear) (example value 922) is a measured number in the unit named by the label; the formula does not convert for you. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
False positives (healthy & flagged) (example value 69) is a measured number in the unit named by the label; the formula does not convert for you. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Specificity on the example inputs: the complete substitution
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: True negatives (healthy & clear), False positives (healthy & flagged). The endpoint of that chain is 93.0 % of specificity, sitting in the “Workable, but false alarms will flood downstream confirmation” band.
- Total healthy = TN + FP = 922 + 69 = 991
- Specificity = 922 ÷ 991 = 93.0%
- High specificity → few false positives → SpPIn (a Positive test rules In)
Healthy correctly cleared — 922. If your inputs change, this is usually the first companion figure to move.
Healthy falsely flagged — 69. Read next to the headline, this is the figure that shows the shape of the trade-off.
False-positive rate — 7.0 %. This is the number experienced users quote when the headline alone would mislead.
positives per 1,000 healthy screened — 69.6. This is the number experienced users quote when the headline alone would mislead.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
How far Specificity 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 Specificity, not an interpolation.
| True negatives setting | Specificity |
|---|---|
| 80 % of the example value | 91.4 % |
| 90 % of the example value | 92.3 % |
| example inputs | 93.0 % |
| 110 % of the example value | 93.6 % |
| 120 % of the example value | 94.1 % |
That spread — 91.4 % at the low end, 94.1 % at the high — is what a careful read of Specificity looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing True negatives alone; the substitution steps will follow your figures exactly.
What actually moves your Specificity
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the specificity recomputed, so the ranking below is measured rather than asserted. It is the fastest honest answer to “what matters most in Specificity?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- True negatives: ten percent up gives 93.6 %, ten percent down gives 92.3 % — ≈0.8 % of the specificity either way
- False positives (healthy & flagged) +10 % → Specificity = 92.4 % · −10 % → 93.7 % (the specificity shifts ≈0.7 %)
True negatives is the dominant lever here: ten percent either way moves the result by about 0.8 %, from 92.3 % to 93.6 %. That is where a careless figure does the most damage, so check it against a source, and treat False positives (healthy & flagged) as the second priority (≈0.7 % per ten percent). The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
What a Specificity of 93.0 % means in practice
The value above only becomes useful the moment you know what it is being measured against. On the example inputs the band reads “Workable, but false alarms will flood downstream confirmation”; your own figures place you on a different rung of the same ladder. How much of that band is luck? On True negatives alone ten percent either way covers 92.3 % to 93.6 %. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
Placing this figure in context: calculators of this kind differ less in arithmetic than in what they choose to ignore. This one keeps True negatives (healthy & clear) explicit so that the omissions are visible rather than hidden in a preset.
Why Specificity results go wrong — and how to prevent it
In low-prevalence screening even 98% specificity drowns the true cases: 20 fakes per 1000 healthy versus maybe 5 real cases. 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.
Using stale inputs. Specificity is only as current as the numbers behind it — an estimate carried over from a previous season, rate table or report quietly biases every output. Re-measure the inputs first; that single habit fixes more bad Specificity figures than any formula change.
This model has its own particular trap: True negatives carries ≈0.8 % of the response per ten percent of error, so effort spent elsewhere is largely decorative.
A final trap is presentation: reporting Specificity to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Six things to confirm before acting on Specificity
- Note the date and the inputs beside the number so the figure can be audited later.
- Verify each input against its original source document, not memory.
- Check True negatives before anything else: it is the measured dominant input, ≈0.8 % of Specificity per ten percent.
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Compare the output against one published benchmark or a colleague’s independent estimate.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
Step by step: getting a trustworthy Specificity out of this tool
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 Specificity are true negatives (healthy & clear), false positives (healthy & flagged). 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. Re-running a number costs seconds; retracting a decision costs considerably more.
Step 2 — baseline before exploration. Get one defensible Specificity on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. When in doubt, prefer the boring input: the interesting one is usually the one you misread.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. Estimates improve most when the worst case is written down in ink.
Step 4 — compute a corridor, not a point. Three runs — worst, likely, best — turn Specificity from a snapshot into a range. Plan against the pessimistic end and treat the optimistic end as the upside story. The input you reach for first is usually the one you measured longest ago.
Step 5 — record the context, not just the number. Note today’s date and the inputs alongside the 93.0 % output. Six months from now the context is what turns this figure into a trend. The point of transparency is that a reader can disagree with a specific line rather than with you.
The real-world conversations Specificity settles
Numbers earn their keep in conversations, and Specificity is no exception. In Science & Research discussions around Statistics & Data Science, this figure decides whether an option stays on the table: it converts an opinionated debate into an arithmetic one, and arithmetic is the only referee both sides accept. Most surprises in numbers are surprises about inputs, not about formulas.
Professionals in Statistics & Data Science use this style of calculation as a screening filter before spending real money or effort: a quick Specificity check eliminates weak options in minutes, and the survivors earn the deeper, slower analysis. If the answer changes your behaviour, it deserves a second run with different assumptions.
Re-running this page costs nothing and catches the slow drifts that never announce themselves. In Science & Research the expensive mistakes are rarely sudden; they are small changes in True negatives (healthy & clear) that nobody recalculated for a year. If a result feels obviously right, that is the moment to check the inputs hardest.
Specificity — frequently asked questions
What affects Specificity the most?
Specificity is driven above all by True negatives. Perturbing only that field by ten percent either way produced 93.6 % against the 93.0 % baseline — a ≈0.8 % response, while False positives (healthy & flagged) manages ≈0.7 %.
Which matters more: false positives (healthy & flagged) or true negatives?
True negatives, by a factor of about 1.1. Concretely: ten percent on True negatives is worth ≈0.8 % of Specificity, the same nudge on False positives (healthy & flagged) only ≈0.7 %. That ranking is re-computed for each page from that page’s own defaults.
What is a typical Specificity?
With the example inputs on this page the result is 93.0 %, labelled “Workable, but false alarms will flood downstream confirmation”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate Specificity by hand?
Three steps: write the formula (Specificity = TN ∕ (TN + FP)), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Specificity than any number of calculator runs.
What happens to Specificity if true negatives changes by 10 %?
On these inputs a ±10 % change in true negatives takes Specificity to 93.6 % against the 93.0 % example — around 0.8 % of the headline. The same test on every other field is in the sensitivity section.
Is the Specificity result of 93.0 % good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Specificity sit against the 93.0 % reference above, how far would a plausible input error move it (≈0.8 % per ten percent on True negatives), and what does the alternative option compute to?
What affects Specificity the most?
Sensitivity depends on where you start, but the inputs True negatives (healthy & clear) and False positives (healthy & flagged) typically move Specificity further than the rest because they enter the formula multiplicatively. If you can only measure two things well, measure those and hold the others at conservative defaults.
Is Specificity accurate?
The arithmetic is exact: Specificity = TN ∕ (TN + FP) is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 93.0 % result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Why is specificity vital for confirmatory tests?
A positive is the decision trigger; if it fires often on healthy people, every downstream action is wasted or harmful.
Does raising specificity cost sensitivity?
Usually yes — cutoffs move along the ROC; only better tests lift both.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
What the labels on this page mean
- Healthy correctly cleared
- 922 for the Specificity worked case; it sits next to the main result because it carries context the headline leaves out.
- Healthy falsely flagged
- 69 for the Specificity worked case; it sits next to the main result because it carries context the headline leaves out.
- False-positive rate
- 7.0 % in the default Specificity calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Specificity
- The primary output of this tool: 93.0 % for the default inputs, computed exactly from Specificity = TN ∕ (TN + FP).
- 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 (“Workable, but false alarms will flood downstream confirmation” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Specificity moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Where the Specificity model comes from
The model is published arithmetic implemented exactly as written: Specificity = TN ∕ (TN + FP). Source of record: Standard diagnostic-accuracy definitions (STARD). Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
Treat the output as a precise answer to the question you typed: exact arithmetic, transparent formula, published source, no hidden rounding. Nothing is smoothed, weighted or adjusted behind the scenes; where judgement enters, this page says so and names the input responsible.
What to do with your Specificity next
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.