A PCR result boils down to whether the target DNA or RNA was amplified enough to produce a detectable signal: if it was, the result is positive; if it wasn’t, the result is negative. But the raw data you get from a real-time (quantitative) PCR run is more nuanced than a simple yes or no. The amplification curve, the cycle threshold value, and the behavior of your controls all contribute to whether a result is trustworthy, and misreading any one of them can lead to a wrong call.
What the Amplification Curve Actually Shows
When you look at a real-time PCR readout, you’re seeing a graph of fluorescence intensity plotted against cycle number. At the start of the run, the amount of target product is so tiny that the fluorescence signal sits buried in background noise, creating a flat baseline. As the reaction progresses and the target doubles with each cycle, the fluorescence begins to rise exponentially, then eventually tapers off as reagents get used up and the reaction plateaus.
A positive sample produces the classic S-shaped (sigmoidal) curve: flat baseline, steep rise, then a leveling-off at the top. A negative sample stays flat throughout, never climbing above the background noise. If you see that characteristic upward sweep, target was present. If the line stays flat from cycle 1 through the final cycle, no target was detected.
That plateau at the top of the curve is not a sign that anything went wrong. It simply means the reaction ran out of fresh reagents, so the amount of product stopped increasing. The useful information lives in the steep middle portion of the curve, not at the endpoints.
Understanding the Ct Value
The cycle threshold (Ct) value, sometimes written as Cq, is the cycle number at which the fluorescence signal first crosses a set threshold above baseline noise. Think of it as the answer to the question: how many rounds of doubling did it take before we could clearly see the target? Lower Ct values mean there was more target in the sample to begin with, because fewer cycles were needed to reach a detectable level. Higher Ct values mean less starting material, because the reaction had to run longer before enough product accumulated to be seen.
In infectious disease testing, this inverse relationship between Ct and target quantity is especially useful. A Ct of 15 generally indicates a sample loaded with the pathogen, while a Ct of 35 might indicate only trace amounts.
Reading a Positive Result
A result is called positive when the amplification curve crosses the fluorescence threshold within the assay’s defined cycle range. In most diagnostic settings, that range is somewhere between cycle 1 and cycle 40 or 45, depending on the protocol. A strong positive has a low Ct, meaning the curve rises early and steeply. A weak positive has a high Ct, meaning the curve rises late and the signal is modest.
Both are technically positive, but the practical meaning can differ. A patient with a Ct of 18 on a SARS-CoV-2 test likely has a high viral load, while someone with a Ct of 37 might be at the tail end of an infection, carrying residual genetic material that isn’t necessarily infectious. This is why some labs report Ct values alongside the positive/negative call, and why clinicians sometimes factor the Ct into treatment decisions.
Keep in mind that Ct values are not perfectly standardized across different instruments, reagent kits, or labs. A Ct of 25 on one platform does not automatically mean the same thing as a Ct of 25 on another. Differences in how the threshold is set, how efficiently the primers amplify, and even pipetting variation can all shift the number.
Reading a Negative Result
A negative result means no amplification curve appeared: the fluorescence stayed at baseline through the entire run. In a well-controlled assay, this means the target nucleic acid was not present in the sample, or at least was present below the test’s limit of detection.
A negative result is only as trustworthy as the controls that accompany it. If the controls behaved properly, you can be reasonably confident the negative is real. If the controls misbehaved, you may have a false negative on your hands, and the run may need to be repeated. We’ll get into what that looks like shortly.
It’s also worth noting that a negative PCR result doesn’t always mean “no infection” or “no pathogen present.” The sample might have been collected too early or too late in the course of illness, the swab might not have picked up enough material, or the nucleic acid might have degraded before it reached the lab. Pre-analytical factors like these sit outside the PCR instrument’s ability to detect, but they affect the result all the same.
Why Controls Are Non-Negotiable
Every reliable PCR run includes at least two types of controls: a positive control and a negative control. These aren’t optional extras. They’re the internal checks that tell you whether the chemistry worked and whether the workspace was clean.
Positive Controls
A positive control is a sample known to contain the target. It goes through the entire PCR process alongside your unknown samples. If the positive control amplifies and produces a curve with the expected Ct range, you know the reagents, the thermal cycler, and the detection system all functioned properly. If the positive control fails to amplify, something went wrong with the run itself, and none of the results from that batch can be trusted, including any negatives.
Negative Controls
A negative control, often called a no-template control (NTC), contains everything the reaction needs except the target nucleic acid. Usually it’s just water or buffer added in place of a sample. It should stay flat throughout the run. If it amplifies, that’s a red flag for contamination: stray DNA or RNA got into the reaction, and any positive results in the batch are now suspect. False positives caused by contamination, whether from amplicon carryover, cross-contamination between specimens during processing, technical errors, or mislabeling, are a real concern in high-throughput labs.
Internal Controls and the Problem of Inhibition
Beyond the positive and negative controls that sit in their own reaction wells, many assays also include an internal control (IC) spiked directly into each patient sample. The internal control is a separate nucleic acid target, unrelated to the pathogen being tested, that gets co-amplified in the same tube. Its job is to confirm that the extraction and amplification steps worked for that specific sample.
This matters because some clinical specimens contain substances that interfere with PCR. Hemoglobin, mucus, certain preservatives, and other compounds can inhibit the enzymes that drive amplification, causing the reaction to fail even when the target is present. If the internal control amplifies normally, you know inhibition wasn’t a problem. If the internal control fails or shows a much higher Ct than expected, the sample likely contained inhibitors, and a negative result for the pathogen target cannot be trusted.
How common is inhibition? A large retrospective analysis of over 386,000 clinical specimens found an overall inhibition rate below one percent for most sample types. Urine and formalin-fixed tissue were exceptions, showing higher rates of inhibition.
The Trouble With Late Amplification
Some of the hardest calls in PCR interpretation involve curves that rise very late in the run, at cycle 35 or beyond. These late signals generate high Ct values and sit in a gray zone. They could represent genuine low-level positives, or they could be artifacts: primer dimers, nonspecific amplification, or trace contamination that only becomes visible after many rounds of doubling.
Setting a reliable Ct cut-off to distinguish real positives from noise is a well-studied problem. Researchers have evaluated methods based on probability of detection and statistical approaches to determine below which Ct value a late result can reliably be considered a true positive. No single universal cut-off exists; it depends on the assay, the target, and the specimen type. Labs validate their own cut-offs during assay development, and results near the boundary often get flagged for repeat testing or additional confirmation.
In clinical virology, this gray zone has practical consequences. During the COVID-19 pandemic, comparisons between standard quantitative PCR and more sensitive digital PCR showed that among samples with very low viral loads, standard PCR missed a meaningful fraction of positives. Out of samples with fewer than about 20 copies per test, barely half were detected by standard quantitative PCR, while digital PCR caught all of them. This doesn’t mean standard PCR is unreliable for most purposes, but it highlights that sensitivity has limits, and those limits live in the high-Ct zone.
Melt Curve Analysis
Some PCR assays, particularly those using SYBR Green dye rather than sequence-specific probes, include a melt curve step after amplification. The instrument gradually raises the temperature while monitoring fluorescence. As the double-stranded PCR product “melts” apart into single strands, the dye releases and fluorescence drops. The temperature at which this happens, the melting temperature (Tm), is specific to the product’s length and sequence.
When you look at a melt curve plot, you want to see a single sharp peak at the expected Tm. That tells you the reaction produced one specific product. If you see multiple peaks, or a peak at an unexpected temperature, something else was amplified alongside or instead of the intended target. Primer dimers, which are short fragments formed when primers bind to each other instead of the target, typically show up as a small peak at a lower Tm than the real product.
Melt curve analysis is especially important in SYBR Green assays because the dye binds to any double-stranded DNA, not just the target. Without probes to provide specificity, the melt curve is your main tool for confirming that a positive signal is actually your target and not an artifact. One study developing a SYBR Green-based multiplex assay for SARS-CoV-2 found that optimizing primer conditions and using melt curve analysis was the primary method for filtering out nonspecific amplification.
Multiplex Assays and Reading Multiple Targets at Once
Multiplex PCR runs detect two or more targets in a single reaction tube by using different primer sets, each paired with a probe labeled with a distinct fluorescent dye. A respiratory panel, for example, might test for influenza A, influenza B, RSV, and SARS-CoV-2 simultaneously. Each target gets its own color channel, and the software separates the signals.
Reading multiplex results means checking each channel independently. You might see amplification in the influenza A channel but not the others, giving you a positive for flu and negatives for the rest. The internal control usually occupies its own channel as well, so you can verify that all four channels were technically capable of detecting signal.
The main complication is spectral overlap between dyes. Fluorescent dyes don’t emit light at a single wavelength; they produce a spread of color that can bleed into neighboring detection channels. Instruments correct for this mathematically using what’s called color compensation, where the machine uses the known emission profile of each pure dye to subtract bleed-through from adjacent channels. If this correction isn’t calibrated properly, a strong signal in one channel can create a ghost signal in another, potentially causing a false positive call for a target that isn’t actually present.
Pre-Analytical Factors That Change Results
A PCR instrument can only analyze what it receives. If the sample was degraded, improperly stored, or poorly collected before it ever reached the lab, even a flawless PCR run will give a misleading result. These upstream issues, collectively called pre-analytical variables, are some of the most common reasons for discrepancies between PCR results and clinical reality.
Sample collection technique matters. A nasopharyngeal swab that barely touched the nostril won’t pick up the same amount of viral material as one properly inserted to the correct depth. Timing matters too: collecting a respiratory sample too early in an infection, before viral shedding peaks, can produce a false negative.
Storage and transport conditions are another layer. Nucleic acids, particularly RNA, degrade over time and with heat. Research on COVID-19 swab transport devices found that viral RNA remained stable at room temperature for up to 96 hours in most systems, but exposure to higher temperatures caused significant drops in detectable RNA in several of the devices tested. Saliva samples showed a similar pattern, with most devices preserving RNA at room temperature but at least one failing at elevated temperatures.
Even DNA, which is more chemically stable than RNA, is affected. A study examining blood samples found that storage duration and the DNA extraction method used could influence genomic DNA integrity enough that the same blood sample produced different PCR results depending on how it was processed. This is why standardized collection, transport, and processing protocols exist, and why deviations from them are documented.
What the Software Is Doing Behind the Scenes
Most people reading PCR results interact with software that has already made several automated decisions. The software sets the fluorescence threshold, determines where the baseline ends, calculates the Ct value, and often makes the positive/negative call. These aren’t always straightforward calculations, and different software packages can produce different Ct values from the same raw data.
The threshold line, for instance, is sometimes set automatically by the software based on statistical analysis of the baseline noise, and sometimes set manually by the operator. Moving the threshold even slightly up or down shifts every Ct value in the run. For samples in the gray zone near the cut-off, this shift can change the call from positive to negative or vice versa. Variability in how thresholds are set, along with differences in PCR efficiency and starting material quantity, are recognized sources of inconsistency in reported Ct values across studies and laboratories.
If you’re reviewing results from a clinical lab, the positive/negative call has typically been validated during assay development and is more reliable than the raw Ct number. If you’re running your own assays in a research setting, understanding that the software’s defaults aren’t sacred, and that manual review of borderline calls is standard practice, will save you from over-interpreting ambiguous data.
When PCR Moves Outside the Clinic
PCR isn’t limited to diagnosing infections in individual patients. Environmental and public health applications, like wastewater surveillance, use PCR to monitor pathogen levels in entire communities. During the COVID-19 pandemic, wastewater-based epidemiology became a major tool for tracking trends in infection before clinical case counts caught up.
Reading wastewater PCR results requires a different interpretive framework than clinical results. You’re not asking “is this person infected?” but rather “how much viral genetic material is present in the sewage, and what does that imply about infection levels in the population?” The relationship between measured genome copies in wastewater and actual clinical cases is influenced by many factors: sewer system transit time, water temperature, UV exposure, the presence of disinfectants, and even the microbial community in the sewage. Longer transit times stretch out the signal over time, and viral RNA degrades at different rates depending on environmental conditions.
A rising Ct trend in wastewater samples (meaning less target detected per sample) might reflect a genuine decline in community infections, or it might reflect warmer weather accelerating RNA degradation in the sewer. This is why wastewater PCR data is typically interpreted as a trend over weeks rather than a snapshot, and why it’s used alongside clinical testing data rather than as a replacement.
Digital PCR and How It Differs
Standard quantitative PCR gives you a Ct value and a relative sense of how much target was present. Digital PCR takes a fundamentally different approach: it partitions the sample into thousands or millions of tiny individual reactions, each containing either zero or one (or a few) copies of the target. After amplification, each partition is scored as simply positive or negative based on its fluorescence, and statistical counting gives you an absolute number of target molecules in the original sample.
Because digital PCR counts molecules directly rather than relying on the exponential amplification curve, it doesn’t produce a Ct value at all. Instead, it gives a concentration, usually in copies per microliter. This makes it less susceptible to the efficiency variations and threshold-setting issues that complicate quantitative PCR interpretation. Setting the fluorescence threshold that separates positive from negative partitions still matters, but the math is more forgiving because you’re making a binary call on thousands of individual data points rather than trying to pinpoint where a single curve crosses a line.
Digital PCR’s main advantage shows up at the low end of detection. As the COVID-19 comparison study demonstrated, digital PCR achieved a 100 percent detection rate on confirmed positive samples, compared to about 93 percent for standard quantitative PCR, with the discrepancies concentrated in samples carrying very low viral loads. For routine high-load clinical samples, the two methods largely agree. Digital PCR tends to be reserved for situations where absolute quantification or detection of very rare targets matters, such as monitoring minimal residual disease in cancer patients or quantifying gene-edited organisms in food products.