False Positive (FP)
Last reviewed
Apr 6, 2026
Sources
14 citations
Review status
Source-backed
Revision
v2 · 3,721 words
Improve this article
Add missing citations, update stale details, or suggest a clearer explanation.
Suggest edit
CtrlK
Last reviewed
Apr 6, 2026
Sources
14 citations
Review status
Source-backed
Revision
v2 · 3,721 words
Add missing citations, update stale details, or suggest a clearer explanation.
A false positive (FP), also known as a Type I error, occurs when a classification model incorrectly predicts the positive class for a sample that actually belongs to the negative class. In other words, the model raises a "false alarm" by indicating the presence of a condition, event, or attribute that is not actually there. False positives are one of the four possible outcomes in binary classification, alongside true positives, true negatives, and false negatives.
The concept originates from statistical hypothesis testing, where Jerzy Neyman and Egon Pearson formalized the notion of Type I and Type II errors in their 1933 paper on the theory of testing statistical hypotheses. A Type I error (false positive) corresponds to rejecting a null hypothesis that is actually true, while a Type II error (false negative) corresponds to failing to reject a null hypothesis that is actually false. This framework has since been adopted across machine learning, medical diagnostics, information security, and many other fields.
Imagine you have a smoke detector in your kitchen. Its job is to beep whenever there is a fire. But sometimes, when you are just making toast, the smoke detector goes off even though there is no fire at all. That is a false positive. The detector said "yes, there is a fire!" but it was wrong. There was no fire, just some toast smoke.
In machine learning, computers try to sort things into groups, like deciding whether an email is spam or not spam. A false positive is when the computer says "this is spam!" but the email was actually a normal message from your friend. The computer made a mistake by saying "yes" when the real answer was "no."
A confusion matrix is a table that summarizes the performance of a classification model by comparing predicted labels against actual labels. For binary classification, it contains four cells.
| Predicted positive | Predicted negative | |
|---|---|---|
| Actually positive | True positive (TP) | False negative (FN) |
| Actually negative | False positive (FP) | True negative (TN) |
The false positive cell sits at the intersection of "actually negative" (the row) and "predicted positive" (the column). It counts the number of negative samples that the model incorrectly labeled as positive.
Given a binary classifier that assigns each input to either the positive class or the negative class:
A false positive is any sample that belongs to N (actually negative) but also belongs to PP (predicted positive):
FP = N ∩ PP
The count of false positives is typically denoted as FP and is used in the calculation of multiple evaluation metrics.
False positives appear directly or indirectly in the formulas of many classification metrics. The following table summarizes the most common ones.
| Metric | Formula | What it measures | Effect of false positives |
|---|---|---|---|
| Accuracy | (TP + TN) / (TP + TN + FP + FN) | Overall fraction of correct predictions | More FPs decrease accuracy |
| Precision (positive predictive value) | TP / (TP + FP) | Fraction of positive predictions that are correct | More FPs directly decrease precision |
| Recall (sensitivity, true positive rate) | TP / (TP + FN) | Fraction of actual positives correctly identified | FPs do not appear in the formula, so recall is unaffected |
| Specificity (true negative rate) | TN / (TN + FP) | Fraction of actual negatives correctly identified | More FPs directly decrease specificity |
| False positive rate (FPR, fall-out) | FP / (FP + TN) | Fraction of actual negatives incorrectly classified as positive | More FPs directly increase FPR |
| False discovery rate (FDR) | FP / (FP + TP) | Fraction of positive predictions that are incorrect | More FPs directly increase FDR |
| F1 score | 2 × (Precision × Recall) / (Precision + Recall) | Harmonic mean of precision and recall | More FPs decrease precision, which decreases F1 |
The false positive rate (FPR), sometimes called the fall-out rate or the probability of false alarm, measures the proportion of actual negatives that were incorrectly classified as positive:
FPR = FP / (FP + TN)
FPR ranges from 0 to 1. A perfect classifier has an FPR of 0, meaning it never raises a false alarm. FPR is the complement of specificity (FPR = 1 - specificity). This metric serves as the x-axis of the Receiver Operating Characteristic (ROC) curve, where it is plotted against the true positive rate (y-axis) at various classification thresholds. The area under the ROC curve (AUC) summarizes the model's ability to distinguish between classes across all threshold settings, with an AUC of 0.5 indicating random guessing and 1.0 indicating perfect separation.
Precision answers the question: "Of all the samples my model labeled as positive, how many were actually positive?" Because FP appears in the denominator of the precision formula (TP / (TP + FP)), every false positive reduces precision. In applications where false alarms carry high costs, precision becomes the primary metric to optimize.
The false discovery rate (FDR) is the complement of precision (FDR = 1 - Precision = FP / (FP + TP)). It directly quantifies the proportion of positive predictions that are wrong.
False positives and false negatives represent two fundamentally different types of classification errors. Understanding the distinction is important because the relative cost of each error varies by application.
| Aspect | False positive (Type I error) | False negative (Type II error) |
|---|---|---|
| What happened | Model predicted positive, but the sample is actually negative | Model predicted negative, but the sample is actually positive |
| Common analogy | False alarm | Missed detection |
| Statistical name | Type I error (alpha error) | Type II error (beta error) |
| Effect on precision | Decreases precision | No direct effect |
| Effect on recall | No direct effect | Decreases recall |
| Effect on specificity | Decreases specificity | No direct effect |
| Effect on sensitivity | No direct effect | Decreases sensitivity |
In some domains, a false positive carries greater consequences than a missed detection:
In most probabilistic classifiers, such as logistic regression or neural networks, the model outputs a continuous score (often a probability) that is then compared against a classification threshold to produce a binary prediction. The default threshold is typically 0.5, but adjusting it allows practitioners to control the balance between false positives and false negatives.
This inverse relationship is known as the precision-recall tradeoff. The optimal threshold depends on the relative costs of false positives and false negatives in the specific application. Tools for selecting a threshold include:
One of the most counterintuitive aspects of false positives is the base rate fallacy (also called the false positive paradox). When the condition being tested for is rare, even a highly accurate test can produce more false positives than true positives in absolute numbers.
Consider a disease that affects 1 in 10,000 people. A test for this disease has 99% sensitivity (it correctly identifies 99% of people who have the disease) and 99% specificity (it correctly identifies 99% of people who do not have the disease). If the test is administered to 1,000,000 people:
| Group | Count | Test result |
|---|---|---|
| People with the disease | 100 | 99 test positive (true positives), 1 tests negative (false negative) |
| People without the disease | 999,900 | 9,999 test positive (false positives), 989,901 test negative (true negatives) |
Out of 10,098 total positive results (99 true positives + 9,999 false positives), only 99 are genuine. That means a person who tests positive has roughly a 0.98% chance of actually having the disease, despite the test being 99% accurate in both sensitivity and specificity.
This result follows directly from Bayes' theorem. The positive predictive value (PPV) depends not just on the test's accuracy but also on the prevalence (base rate) of the condition. When prevalence is very low, even a small FPR applied to a vast number of true negatives produces a large absolute count of false positives.
The base rate fallacy has practical consequences in machine learning. Models deployed for rare-event detection (such as anomaly detection, fraud screening, or disease diagnostics) can achieve high accuracy while still generating an overwhelming number of false positives. Evaluating such models with precision, PPV, and FPR is more informative than using accuracy alone.
False positives arise from a variety of sources during model development and deployment.
Overfitting occurs when a model learns noise, outliers, or coincidental patterns in the training data rather than the underlying signal. An overfit model may memorize spurious correlations that cause it to predict the positive class for samples that happen to share superficial similarities with positive training examples. The result is increased false positives (and often increased false negatives as well) on unseen data.
When the training set contains far more samples of one class than the other (a class imbalance), the model may develop a bias. Paradoxically, an aggressive attempt to compensate for imbalance, such as heavy oversampling of the minority class or extreme cost weighting, can push the model to over-predict the positive class and generate more false positives.
If the training labels contain errors (for example, negative samples incorrectly labeled as positive), the model learns incorrect decision boundaries. These boundary errors persist at inference time, producing false positives for samples near the boundary.
When the input features do not capture enough information to distinguish between positive and negative classes, the model cannot make reliable predictions. Missing domain-specific features or using overly generic features increases the likelihood of false positives.
As discussed above, using a threshold that is too low causes the model to predict positive more often than warranted, increasing false positives.
When the data distribution at deployment differs from the distribution during training, the model's learned decision boundary may no longer be valid. Inputs that would have been correctly classified as negative during training may be misclassified as positive under the new distribution.
Several strategies can help reduce the false positive rate of a classification model.
| Technique | Description | Tradeoff |
|---|---|---|
| Threshold tuning | Raise the classification threshold to require higher confidence before predicting positive | Reduces false positives but may increase false negatives |
| Feature engineering | Add or refine features that better separate positive from negative samples | Requires domain knowledge and additional data |
| Regularization | Apply L1 or L2 penalties to prevent overfitting and reduce reliance on noisy features | May slightly reduce model expressiveness |
| Cross-validation | Use k-fold or stratified cross-validation to detect overfitting and select hyperparameters that generalize | Increases training time |
| Ensemble methods | Combine predictions from multiple models (bagging, boosting, stacking) to reduce variance | Increases computational cost and complexity |
| Cost-sensitive learning | Assign a higher misclassification cost to false positives in the loss function, forcing the model to be more cautious about positive predictions | May increase false negatives |
| Resampling strategies | Use undersampling of the majority class or careful oversampling (such as SMOTE) to balance the dataset without over-correcting | Over-aggressive resampling can introduce its own biases |
| Calibration | Apply post-hoc calibration (Platt scaling, isotonic regression) so that predicted probabilities better reflect true class probabilities | Requires a held-out calibration set |
| Multi-stage classifiers | Use a high-recall first stage followed by a high-precision second stage, filtering out false positives in the refinement step | Adds latency and system complexity |
| Human-in-the-loop review | Route borderline predictions to human reviewers for final judgment | Adds cost and latency; not scalable for all applications |
False positives have distinct impacts depending on the domain. The following sections examine several areas where false positives present significant challenges.
In medical testing, a false positive occurs when a healthy patient receives a positive test result for a disease they do not have. This can lead to:
Mammography screening for breast cancer provides a well-studied example. Studies have shown that approximately 50% of women who undergo annual screening over a 10-year period will receive at least one false positive result. While each individual mammogram has high specificity, the cumulative probability of a false positive over many screenings is substantial. Despite these drawbacks, screening programs are maintained because the cost of a false negative (missing an actual cancer) is considered much greater.
Fraud detection systems in banking and e-commerce flag transactions that appear suspicious. False positives in this context mean that legitimate transactions are declined or frozen. The financial impact is substantial:
These numbers illustrate that overly aggressive fraud prevention, while reducing actual fraud, can destroy more revenue through lost legitimate sales than the fraud itself would have caused.
Spam filters classify incoming emails as either spam or legitimate ("ham"). A false positive occurs when a legitimate email is incorrectly routed to the spam folder. For businesses, missed emails can mean lost sales opportunities, delayed responses to clients, or ignored legal notices. Most modern spam filters allow users to review their spam folders and mark false positives, which feeds back into the model to reduce future errors.
Intrusion detection systems (IDS) and security information and event management (SIEM) platforms generate alerts when they detect potentially malicious activity on a network. False positives in security systems result in:
False positives in facial recognition systems can lead to wrongful identification, detention, and even arrest of innocent individuals. Research from the National Institute of Standards and Technology (NIST) has shown that many facial recognition algorithms exhibit higher false positive rates for certain demographic groups. A 2018 study titled "Gender Shades" found that the error rate for lighter-skinned men was 0.8%, compared to 34.7% for darker-skinned women. Multiple cases of wrongful arrest based on facial recognition false matches have been documented in the United States, with all known cases involving Black individuals.
Object detection systems in computer vision applications, including autonomous vehicles and surveillance systems, can produce false positives by detecting objects that are not actually present. In autonomous driving, a false positive (for example, detecting a pedestrian where there is none) may cause the vehicle to brake suddenly and unnecessarily, potentially causing accidents or traffic disruptions.
In natural language processing tasks such as sentiment analysis or named entity recognition, false positives occur when the model incorrectly identifies a sentiment, entity, or intent. For example, a content moderation system may flag a benign comment as toxic (false positive), leading to unnecessary censorship and user frustration.
While the concept of a false positive is most straightforward in binary classification, it extends to multi-class settings. In multi-class classification, each class can be treated as a one-vs-rest binary problem. A false positive for class A occurs when a sample that does not belong to class A is predicted as belonging to class A. The confusion matrix generalizes from a 2x2 table to an N x N table (where N is the number of classes), and false positives for each class are summed across the corresponding column, excluding the diagonal cell.
The statistical foundations of false positives trace back to the early 20th century. Ronald Fisher introduced the concept of significance testing and p-values in the 1920s, establishing a framework for making decisions under uncertainty. Jerzy Neyman and Egon Pearson built on this work in the late 1920s and early 1930s, formalizing the distinction between Type I errors (false positives) and Type II errors (false negatives). Their 1933 paper introduced the Neyman-Pearson lemma, which provides the most powerful test at a given significance level (the maximum acceptable Type I error rate, denoted alpha).
The term "false positive" itself became widely used in medical screening and diagnostics during the mid-20th century, and later migrated into signal detection theory, radar systems, information retrieval, and eventually machine learning. The concept of the ROC curve was originally developed during World War II for analyzing radar signals, where distinguishing enemy aircraft (true positives) from noise (false positives) was a life-or-death problem.
| Formula | Expression |
|---|---|
| False positive count | FP = Number of negative samples predicted as positive |
| False positive rate (FPR) | FP / (FP + TN) |
| Specificity | TN / (TN + FP) = 1 - FPR |
| Precision (PPV) | TP / (TP + FP) |
| False discovery rate (FDR) | FP / (FP + TP) = 1 - Precision |
| F1 score | 2 × (Precision × Recall) / (Precision + Recall) |
| Positive predictive value (PPV) via Bayes | (Sensitivity × Prevalence) / ((Sensitivity × Prevalence) + (FPR × (1 - Prevalence))) |