How To Read Sanger Sequencing

Reading Sanger sequencing data means interpreting a chromatogram (electropherogram) where four colored fluorescence peaks represent the DNA bases A, C, G, and T. The correct sequence is read from the 5' end to the 3' end by calling the peak at each position, but you must account for signal quality, mixed peaks, and trace artifacts. This guide is for molecular biology researchers, lab technicians, and bioinformatics students who need to validate clones, confirm mutations, or check PCR products using Sanger sequencing. It provides a source bounded framework using authoritative references from the NCBI Bookshelf and practical training from EMBL EBI Training.

A typical chromatogram begins with a strong signal after an initial noisy region and ends with broadening peaks. You will use the raw trace file (often .ab1) and software like FinchTV, SnapGene, or Benchling. The reading process is straightforward when the template is clean and the run is good, but you must be prepared for common pitfalls such as low quality base calls, heterozygous positions, and homopolymer stutter.

At a Glance

Core Concepts and Workflow

1. Understand the Chromatogram

The chromatogram displays a series of peaks, each representing a fluorescently labeled dideoxynucleotide that terminated the sequencing reaction. The x axis is the base position, the y axis is fluorescence intensity. The software calls a base at the highest peak for each position. According to the Galaxy Training Network, you should always visually inspect the chromatogram because base calling algorithms can make errors, especially near the beginning and end of the read.

2. Open and Inspect the Trace File

Load your .ab1 file in a trace viewer. Look for the initial ramp up region (first 20 50 bases) where peaks may be uneven , these are often unreliable. The high quality region typically follows, with evenly spaced, sharp peaks and low baseline noise. The Bioconductor package sangerseqR provides tools for programmatic quality assessment, but manual inspection remains the standard.

3. Call Bases and Score Quality

Each peak is assigned a Phred quality score. Q20 means a 1 in 100 chance of an incorrect call, Q30 means 1 in 1000. Trust bases with Q scores above 20. Many viewers color code the quality: green for good, yellow for moderate, red for poor. The NCBI Sequence Read Archive documentation notes that raw Sanger traces are often archived alongside quality values. When reading, start from the first stable peak after the primer region and stop when peaks become ambiguous or too broad.

4. Identify Heterozygous Positions (If Applicable)

In mixed templates (e.g., from a heterozygous individual or a pooled sample), you will see two overlapping peaks of similar height at the same position. The software may call the higher peak or mark it as ambiguous (e.g., N). According to a study on viral genotyping High resolution HAV genotyping, Sanger sequencing remains useful for detecting major variants, but minor variants below 20% frequency are often missed. If you see a clear double peak, record the IUPAC ambiguity code (e.g., R for A/G).

5. Read Forward and Reverse Strands

For high confidence, sequence both strands. Align the forward and reverse reads using a tool like Benchling or a local alignment. The reverse read is the reverse complement of the forward read. Mismatches between the two strands indicate either a sequencing error or a true polymorphism , you should inspect the chromatograms at those positions. The Vertebrate Genomes Project relies on Sanger finishing to resolve assembly gaps, highlighting the value of bidirectional reads.

6. Trim and Export the Final Sequence

Remove the primer regions and low quality tails. A common rule is to trim the first 20 30 bases and the last 50 100 bases. Export the consensus sequence as FASTA. For publication or submission, ensure that the quality scores are available.

Decision Criteria for Base Calling

You will encounter ambiguous situations where the software call differs from what your eye sees. Follow these guidelines:

• Check the peak shape: a sharp, symmetric peak is reliable. A shoulder on the peak or a split peak suggests an underlying mixed base or dye blob.
• Evaluate the baseline: high baseline noise (e.g., elevated signal between peaks) may cause false calls. The NCBI Bookshelf chapter on DNA sequencing notes that poor template purity or leftover primers can raise the baseline.
• Compare forward and reverse traces: if both strands show the same base call with good quality, accept it. If only one strand supports the call and the other has a gap or low quality, flag it.
• Consider the local context: repeat regions (e.g., homopolymers of AAAAA) cause peak overlay. For homopolymers longer than about 8 bases, the exact length is uncertain. Techniques like nanopore sequencing are better for long homopolymers.

Quality Checks You Must Perform

Do not rely solely on the software base call. Implement these checks:

• Visual inspection of the entire trace. Look for off scale peaks (flat topped) which indicate signal saturation and may cause miscalls.
• Confirm that the four dye channels are balanced. If one channel (e.g., G) is consistently lower, the base calls may be skewed. Use the normalization feature in your viewer.
• Check for dye blobs: these appear as sharp, narrow peaks in all channels simultaneously, often near the beginning of the trace. They are not real bases.
• Examine the trace for spurious peaks in the middle of a run that could indicate a double loading or an air bubble.
• Use a quality score threshold: discard any base with Phred score below 20 unless you have a strong reason to keep it. The Galaxy Training Network recommends a minimum average Q30 over the region of interest.

Common Mistakes When Reading Sanger Sequencing

1. Reading low quality ends. Many users try to extend the read beyond the reliable region. The last 50 bases often have broad, overlapping peaks. Stop reading when peaks become shorter than half the height of the preceding peaks.

2. Ignoring double peaks in supposedly pure samples. Double peaks can arise from PCR errors, allele dropout, or incomplete primer extension. Always consider the possibility of contamination or heterozygosity. Workflows for amplicon based NGS often include a Sanger confirmation step, and discrepancies must be resolved.

3. Confusing dye blobs with real bases. Dye blobs appear as spikes in all four channels but are not followed by a typical peak pattern. They often occur right after the primer peak. Mark them as noise and do not include them in the final sequence.

4. Not trimming the primer sites. Primers used for amplification or sequencing will appear at the start of the trace. If you do not remove them, you may inadvertently submit primer sequence as part of your target. Use the sequencing primer sequence to identify and clip the region.

5. Misaligning forward and reverse reads. When you perform a reverse complement, double check orientation. A common error is to compare forward forward instead of forward reverse complement. Use aligners that automatically handle direction.

6. Overlooking secondary structure effects. GC rich regions can cause premature termination, leading to a sudden drop in signal or a stack of overlapping peaks. The EMBL EBI Training module on sequencing troubleshooting advises using a different polymerase or adding DMSO to resolve such regions.

Limits of Interpretation

Sanger sequencing cannot resolve several situations:

• Lengths of homopolymers longer than about 8 10 bases are ambiguous because the polymerase slips. The trace shows a series of decreasing peaks after the run.
• Minor variants present at less than 15 20% frequency are not reliably detected. For mixed samples, consider using next generation sequencing or single worm approaches to capture diversity.
• Repetitive sequences or inverted repeats can cause hairpin structures that stall the polymerase, leading to abrupt stops or compression artifacts.
• Large insertions or deletions may be missed if they occur in a region where the alignment becomes impossible. The NCBI Sequence Read Archive advises that Sanger is best for sequences under 1 kb without complex repeats.
• Base calling accuracy is not uniform across the read. The first 20 bases are unreliable due to primer interference, and the last 100 bases deteriorate due to enzyme exhaustion. A study on evolutionary fusion events Evolutionary innovation through fusion used Sanger to confirm chimeric sequences, but they trimmed these regions.

Frequently Asked Questions

Q: How do I know if a peak is a true base or background noise?
A: Look at the peak height relative to the surrounding peaks. True bases are usually at least half the height of the average peak. Noise peaks are often small (< 20% of average) or appear in multiple channels. Use the quality score: a Phred score below 10 indicates almost random assignment.

Q: What should I do when my forward and reverse reads do not match?
A: Inspect the chromatograms at the mismatch positions. If one trace has a clear peak and the other has a split or low quality peak, the clear one is likely correct. If both are clean but different, you may have a true heterozygous site. If the mismatch occurs in a homopolymer, the length may be uncertain. Sequence a second clone or use a different primer.

Q: Can I rely on a single Sanger read for confirmation?
A: For simple confirmation (e.g., checking a known point mutation), a single clean read is often sufficient. However, for reporting a novel variant or for publication, you should sequence both strands from at least two independent PCR products. Sources like the EMBL EBI Training emphasize that bidirectional reads reduce error rates.

Q: Why does my trace show broad peaks halfway through the run?
A: Broad peaks usually indicate that the sequencing reaction ran out of nucleotides or that the template had secondary structure. It may also be due to salt carryover from the PCR. If the first half is high quality, trim the sequence at the point where peak resolution degrades. If the problem occurs early, repeat with a new template.

References and Further Reading

• NCBI Bookshelf , Chapter on DNA sequencing and quality assessment.
• EMBL EBI Training , Online course on Sanger sequencing analysis and troubleshooting.
• Galaxy Training Network , Tutorials for processing Sanger traces and quality control.
• Bioconductor sangerseqR package , Documentation for programmatic Sanger data analysis in R.
• NCBI Sequence Read Archive , Repository for raw Sanger trace files and metadata.
• High resolution HAV genotyping using amplicon based NGS , Discusses Sanger versus NGS for variant calling in viral samples.
• Sequencing parasite genomes, one worm at a time , Highlights Sanger finishing in genome projects.
• Performance and practicality of 16S nanopore sequencing , Compares Sanger to nanopore for bacterial identification.
• Evolutionary innovation through fusion of sequences , Uses Sanger to confirm gene chimeras.
• The Vertebrate Genomes Project Phase I , Describes Sanger in assembly validation.

Related Articles

• Protein Synthesis
• Incomplete Dominance Gene
• Cell Membrane Function Biology
• Dna Structure
• Protein Structure