SeqBench

Sanger Trace Viewer & Clone Verification

Inspect chromatograms, compare a read with its reference, or screen a whole plate of clones.

Your files are never stored or shared

View a Sanger trace, compare a read with the sequence you expected, or screen a facility ZIP to decide which clone to grow. The chromatogram viewer opens ABIF (.ab1 / .abi) and Staden SCF traces for peak-level inspection, base-call editing and trimming; the comparison reports coverage and every difference in reference coordinates; and clone screening takes traces, pasted reads or a sequencing facility ZIP with one or more maps and returns a verdict per clone. The same page carries your sequencing data between steps instead of asking you to upload it again.

What do you need to verify?

Pick a step, or drop what the facility sent — traces, a ZIP, your map — and the page picks the step that matches.

Traces (.ab1 / .scf), a facility ZIP, your map (.dna / .gb / FASTA)or click to browse

Low, broad or overlapping peaks and low-quality stretches near the ends mark bases to trim before downstream analysis.

Got the reverse read too? Assemble them

Joins the forward and reverse reads of one insert into a consensus, without a reference, and lists every position where they disagree. A free alternative to ChromasPro's assembly.

Choose filesor drop them here

Select the forward and reverse reads together, or a whole plate: reads are paired by name (S1_27F + S1_1492R) and each sample is assembled into its own contig.

Upload traces (or paste reads) to assemble them. One read is quality-trimmed on its own; two or more are joined on their overlaps.

Which forward goes with which reverse?

Paste a plate's reads as name and length and this pairs them: a clone's forward and reverse come off the same amplicon, so their lengths are one primer offset apart and they point opposite ways. Every pair comes with the gap that justifies it, and a pair held together by length alone never scores as settled — a plate of one construct gives every read the same length.

A name and a length, separated by a tab, a comma or a space — the name may carry a direction (_F, _R, M13F). When it does not, this pairs on length alone and says so.

Double peaks? Read what the basecaller did not report

A basecaller reports one base per position and stops early. This section reads the trace for a second dye under a called base (a heterozygote or a mixed colony) and for bases still visible in the scan after base calling stopped. Both commonly make a read look wrong when the DNA is correct.

Open a trace above, and this reads what is under its base calls.

No map of the finished plasmid? Check the read against the PCR

Rebuilds the expected insert from the template and the two primers that made it, finds it in the read in either orientation, and reports identity, coverage and every mismatch. A reading frame adds a premature-stop check.

The PCR you say produced the insert

Design, edit, and verify complete constructsIt opens on the verification panel, where reads are compared with it.

How to use the Sanger Trace & Clone Verification tool

  1. 1Drop what you have (traces, a facility ZIP, your map) and the page runs the matching job: inspect trace quality, compare with a reference, or screen clones or a plate.
  2. 2Upload AB1/ABI/SCF traces or a facility ZIP; comparison and screening also accept pasted reads.
  3. 3Add the expected reference when you need coordinate-level differences or clone verdicts, one map per construct when the order mixes several.
  4. 4Review the chromatogram, coverage and cited differences, then export or continue into the next Sanger task without re-entering the read.

FAQ

Which Sanger job should I choose?

Inspect trace quality when you need to see peaks, edit calls or trim one or more traces. Compare with a reference when one read should match a known sequence and you need coverage plus coordinate-level differences. Screen clones or a plate when several reads belong to several colonies and the real question is which clone to grow up. You do not pick one on the page: traces alone open for inspection, traces with a map are compared or screened against it, and a facility ZIP goes straight to screening.

Which files can I open?

The trace viewer and comparison workflow read ABIF traces (.ab1 / .abi) and Staden SCF traces (.scf). Clone screening also accepts a sequencing facility ZIP, FASTA or FASTQ reads, while references can be GenBank, SnapGene .dna, FASTA or raw DNA, several at once when the order holds more than one construct.

How is a read-to-reference verdict decided?

Coverage is checked before identity: a clean match over too little of the requested reference is ambiguous, not a pass. With enough coverage, the read passes at 99% or higher identity with no indels; every mismatch, insertion and deletion is listed in reference coordinates for inspection against the trace.

How does plate screening know which reads belong to a clone?

It parses facility-style record names, sample names and wells, shows the confidence and reason for every grouping, and allows corrections before the run. Reads for each clone are then piled up in reference coordinates so one noisy base call is not automatically treated as a mutation.

What does the plate screen say beyond PASS or not?

With an annotated map, each difference says what it does to the gene it lands in, silent, a named residue change, a premature stop or a frameshift, so a clone whose only change is silent is listed as usable. A clone not read end to end gets the read that would cover the gap: a primer already on your map, a universal primer whose site is on the construct, or a new one designed for it. When the order mixes constructs, drop every map: each clone is judged against the map its reads belong to, and where two maps differ by too little for the reads to tell, you choose rather than the reads.

Helpful?