Azure Biosystems
A step-by-step qPCR troubleshooting guide covering common problems such as high Cq values, no amplification, primer-dimers, contamination, and poor efficiency, with practical fixes for reliable results.
Quantitative PCR (qPCR) is a highly sensitive and widely used technique for applications such as gene expression analysis, pathogen detection, genotyping, and copy-number analysis. However, that sensitivity also makes qPCR prone to errors. Small issues in pipetting, reagent quality, template integrity, or assay design can lead to inconsistent or misleading results.
The good news is that most qPCR problems leave recognizable signatures in controls, amplification curves, melt curves, or standard curves. This step-by-step qPCR troubleshooting guide explains how to diagnose common issues, including no amplification, high Cq values, nonspecific products, and poor efficiency, and how to apply targeted fixes quickly and systematically.
Workflow at a glance: Controls → Curves → Melt → Efficiency → Sample → Fix one variable. Systematic troubleshooting leads to reliable qPCR data.
Controls are the most informative diagnostic in qPCR. Before interpreting unknowns, evaluate every control well. The pattern of passing and failing controls often narrows the problem to a specific class of issues before deeper analysis is needed.
An NTC is a reaction containing every component of the master mix except the nucleic acid template; nuclease-free water is added in place of sample. A properly performing NTC should show no amplification, or amplification only at very late cycles (typically Cq > 38) and lack a clear exponential phase or specific melt peak. If the NTC amplifies with a defined Cq and a clean melt peak, you have one of two problems.
Practical example: A user running a SYBR Green assay for GAPDH sees the NTC cross threshold at Cq 32 with a melt peak at 72°C, while the intended amplicon melts at 84°C. The 72°C peak is the signature of primer-dimers, not contamination. The fix is to lower primer concentrations from 500 nM to 200–300 nM, raise the annealing temperature by 1–2°C, or redesign the primers using a tool such as Primer-BLAST with a stricter ΔG cutoff for self- and hetero-dimers.
If contamination is the culprit, decontaminate the workspace by wiping benches and pipettes with 10% bleach followed by 70% ethanol, replace shared aliquots of water and master mix, dedicate a set of pipettes to pre-PCR setup, and physically separate template handling from amplification. Rerun the NTC alongside fresh reagents to confirm the source has been eliminated.
A positive control is a sample known to amplify successfully under the assay conditions, often a plasmid standard, a synthetic gBlock, a previously validated cDNA pool, or genomic DNA at a defined concentration. If the positive control fails to amplify or amplifies very late, the unknowns cannot be trusted, and the problem is almost always technical rather than biological.
Walk through the components systematically:
Azure Cielo note: On the Azure Cielo, excitation and emission are directed into each well via in-well optics, eliminating the need for a passive reference dye (e.g., ROX) to normalize path-length variation. This allows that channel to be used as an additional detection channel on the Cielo 6 and reduces the likelihood that a failed positive control is due to an optical artifact. Confirm that the selected detection channel matches the assay chemistry, that the polymerase activation step is included in the run protocol, and that the correct plate type and seal are specified.
In two-step or one-step RT-qPCR, the no-RT control is the same RNA sample run through the reverse transcription step with the reverse transcriptase enzyme omitted. It tests whether the signal in your unknowns is coming from cDNA, as intended, or from contaminating genomic DNA in the RNA prep. If the no-RT control amplifies, your RNA is contaminated with genomic DNA and your gene-expression measurements will be inflated by an unknown amount.
Two complementary fixes are widely used:
Once the controls behave as expected, turn to the shape of the amplification curve. A textbook curve has a flat baseline, a clean exponential phase that crosses threshold within the linear range of the assay (typically Cq 15–30 for moderate-abundance targets), and a clear plateau. Deviations from this ideal curve typically fall into three categories: no amplification, high or late Cq values, and inconsistent replicates.
When no measurable fluorescence increase is observed, check basic setup before concluding the target is absent.
A Cq that drifts later than expected indicates that the reaction is starting from a much smaller pool of amplifiable template than intended. Several causes are common.
Technical replicates should typically agree within ~0.5 Cq for routine assays and ~0.25 Cq for high-precision work. Larger variation usually reflects technical variability rather than biology.
When using intercalating dyes such as SYBR Green or EvaGreen, all double-stranded DNA fluoresces, including nonspecific products. The melt curve is therefore essential for confirming that the observed signal originates from the intended amplicon.
A single, narrow peak at the expected melting temperature (typically between 78 and 88°C for amplicons of 70–200 bp) indicates good specificity. The Cq values for that sample can be trusted and the analysis can proceed. As a sanity check, compare the observed Tm against the predicted Tm from a tool such as uMELT; differences of more than 2–3°C across replicates suggest a contamination, mispriming, or instrument calibration issue worth investigating.
Azure Cielo note: High data density is advantageous for melt analysis: the Azure Cielo records on the order of 100,000 data points per well per run, generating finely resolved −dF/dT melt curves. Subtle shoulders or secondary peaks—often indicative of low-level mispriming—are easier to detect than on instruments that collect fewer data points during melt acquisition, providing an early warning of specificity issues before they begin to affect quantification.
Two or more peaks indicate that the polymerase produced more than one amplicon. The most common causes are mispriming on related sequences, amplification of a pseudogene or paralog, or formation of a secondary product at high cycle number. Either fix the specificity or accept that SYBR Green is not appropriate for this target and switch to a hydrolysis-probe assay, which only fluoresces when the probe sequence is correctly cleaved.
Specificity fixes worth trying first:
A peak well below the expected amplicon Tm, often between 65 and 75°C, is the classic signature of primer-dimers. Because primer-dimers are short (typically 30–60 bp), they melt at lower temperatures than even small amplicons. Primer-dimers compete with the intended target for reagents, suppress true signal at low template inputs, and are particularly problematic in NTCs and dilute samples.
To address primer-dimers: reduce primer concentration to 100–200 nM, raise the annealing temperature in 1°C steps, shorten the extension time slightly to disfavor short products, and, if the problem persists, redesign the primers with stricter dimer-formation criteria. As a last resort, switch to a probe-based chemistry, which is insensitive to primer-dimer formation because the probe must hybridize to the intended amplicon to produce signal.
Azure Cielo note: When migrating from SYBR Green to a probe chemistry, the Azure Cielo 6 offers a practical advantage: with no ROX channel needed for normalization, all six fluorescence channels are available for actual targets. The Cielo 6 supports SYBR Green/EvaGreen, FAM, VIC/JOE/HEX/CAL Fluor 540, CAL Fluor Orange 560, ROX/TAMRA (as a target dye), TEX615, Quasar 670/CAL Fluor Red 610, Cy5, and Cy5.5/Quasar 705, which means a six-plex hydrolysis-probe assay is achievable without giving up a channel to a passive reference.
Amplification efficiency reflects how closely the reaction approaches ideal doubling each cycle. It is determined from a standard curve by plotting Cq versus log(template concentration). A slope of −3.32 corresponds to 100% efficiency.
Acceptable assays typically fall within 90–110% efficiency (slopes ~ −3.10 to −3.58), with R² ≥ 0.98 in accordance with MIQE guidelines.
An assay in this range can be used for absolute quantification with a standard curve, for relative quantification using the ΔΔCq method (which assumes 100% efficiency), or for Pfaffl-corrected ratios when the reference and target assays have similar but not identical efficiencies. Document the slope, intercept, R², and dynamic range alongside the assay metadata so future runs can be benchmarked against the validated baseline.
Efficiency below 90% suggests inhibition, suboptimal primers, or a flawed reaction setup. Efficiency above 110% almost always points to the same problems in disguise: nonspecific products, primer-dimers, or pipetting artifacts that compress the dilution series at the low end. Both extremes invalidate quantitative comparisons until corrected.
Diagnostic actions, in order:
Even a perfectly designed assay cannot rescue a poor sample. Sample quality should be assessed before the assay is ever loaded, but it is also worth revisiting whenever results look anomalous. Three attributes matter most: concentration, integrity, and freedom from inhibitors and unwanted nucleic acids.
If quality checks pass, proceed to data interpretation with confidence.
If any of the following are present, fix the sample before fixing the assay:
Document each sample's QC results alongside its qPCR data. When a result looks wrong months later, the QC trail is often the fastest path to diagnosis.
The final and most important step is also the most often skipped under deadline pressure. Once you have identified a likely cause, change a single variable, rerun the assay with all controls in place, and confirm that the fix produced the expected change. Changing two or three things at once may resolve the symptom, but it leaves you without a defensible explanation, and it sets up the next failure when one of those changes silently breaks something else.
Keep a troubleshooting log that records the failure mode observed, the hypothesized cause, the single change made, and the outcome. This log becomes the institutional memory of the lab and dramatically shortens the time required to resolve future failures. Tools as simple as a shared spreadsheet or as structured as an electronic lab notebook entry work equally well; what matters is that the change-and-result pairs are preserved in a searchable form.
Azure Cielo note: Instrument-side automation can shorten the documentation loop. The Azure Cielo can deliver completed run files automatically by email at the end of a run, and supports data export over Wi-Fi, Ethernet, or USB, so the run archive can be attached to the troubleshooting log while conditions are still fresh in mind. Cielo Manager’s run history also preserves the exact protocol, plate layout, and dye assignments used, which is invaluable when a fix has to be defended weeks later in a manuscript or quality record.
Use this matrix as an at-the-bench summary. It distills the workflow into the fastest path from observed symptom to a focused first action.
| Symptom | Most Likely Cause | First Action |
|---|---|---|
| NTC amplifies with low-T melt peak | Primer-dimers | Lower primer conc., raise annealing T, redesign primers |
| NTC amplifies with on-target melt peak | Reagent or workspace contamination | Decontaminate workspace, replace reagents, separate setup areas |
| Positive control fails | Master mix, primer, polymerase, template, or instrument issue | Walk through each component; verify cycling protocol |
| No-RT control amplifies | Genomic DNA contamination of RNA | DNase treatment; redesign primers across exon junctions |
| No amplification (no Cq) | Missing component, wrong cycling, no template | Verify master mix, template, cycling, primers |
| High Cq / late amplification (Cq > 30–35) | Low input, inhibitors, poor RT, weak primers | Re-quantify input, test for inhibition, check RT |
| Inconsistent replicates (ΔCq > 0.5) | Pipetting, mixing, plate setup, edge effects | Use appropriate pipettes, spin plate, increase replicates |
| Multiple melt peaks | Nonspecific amplification | Optimize annealing T, redesign primers, consider probe assay |
| Efficiency outside 90–110% | Inhibitors, primer issues, suboptimal conditions | Run standard curve, test inhibitors, optimize conditions |
| Degraded sample / poor QC | Sample handling or extraction problem | Re-extract, repurify, store properly in single-use aliquots |
qPCR rewards disciplined workflows. The same sequence that enables efficient troubleshooting (controls, curves, melt, efficiency, sample, then a single targeted fix), also ensures reproducibility across experiments and users.
When controls are verified first, melt and efficiency data are recorded alongside Cq values, and only one variable is changed at a time, sources of variability become traceable and correctable.
Reliable qPCR is not the result of luck, it is the result of a consistent, well-documented process.
Remember the sequence: CONTROLS → CURVES → MELT → EFFICIENCY → SAMPLE → FIX ONE VARIABLE.
NEED HELP WITH YOUR qPCR AND DON’T KNOW WHERE TO BEGIN?
| Title | Link |
|---|---|
RELATED BLOG POSTS ON qPCR…
In the pursuit of modern drug discovery, the industry’s most significant challenges often lie with proteins that are structurally dynamic or elusive—the so-called “undruggable” targets
Real-time PCR (qPCR) is the bedrock of molecular biology, offering precise measurement of nucleic acids. But before you hit ‘Run’ on your Azure Cielo Real-Time PCR
Real-time PCR (qPCR) has long been an indispensable tool in the life sciences, widely celebrated for its speed, sensitivity, and quantitative precision in gene expression
