SeqBench

Plasmid Annotator: Detect Features on a Map

Detection of promoters, tags, origins and markers, with optional deep feature scan.

Paste a plasmid or DNA sequence to auto-annotate it. The instant quick scan matches a bundled library of short signature sequences on both strands, identifying promoters, operators, RBS and Kozak sites, affinity tags, origins of replication, resistance markers and MCS clusters. The deep scan is the thorough pass: it searches pLannotate's full feature databases instead of the signature list, recovers variants and truncated fragments the signature library misses, and reports a percent identity and reference coverage for every hit so a weak match can be judged. Either way, detected features are drawn on a circular and linear plasmid map online, with a table of type, coordinates, strand and length.

0 bp

▸Display: circular + linear · “My construct”

Which backbone is it?

Screens the sequence against curated cloning, expression and BAC backbones, and checks for chimeras.

Paste a plasmid above, and this screens it against the curated vector set.

Both at once, and what neither explains

Recognized features crossed with backbone identity, and the regions neither accounts for.

Paste a plasmid above, and this crosses its annotation with its backbone. Works best on a complete plasmid: a partial read matches a backbone over less of its length and inflates the unexplained regions.

What do I plate it on?

Reports the antibiotic the resistance markers select for, the host and copy number the origin implies, and the hazards worth knowing before you grow it.

Paste a plasmid above to read its markers and origins.

Repeats that could delete part of the plasmid

Direct repeats that let the cell recombine, the stretch each pair would lose, and the shortened molecule that is left.

Paste a sequence above to search it.

Design, edit, and verify complete constructsIt opens on its feature table, where the annotation can be edited.

How to use the Plasmid Annotator tool

  1. 1Paste a plasmid or DNA sequence into the "DNA sequence" box, or click one of the two examples: "Load example" for a 3 kb plasmid with an insert, "Tag & promoter example" for a short construct carrying T7, lac, RBS, His6, FLAG and an MCS. The quick scan reruns automatically a moment after you stop typing.
  2. 2Click "Run deep scan" to search pLannotate's full databases instead. It takes a few seconds; the "Quick scan" / "Deep scan" toggle compares the two result sets.
  3. 3Set a "Construct name" and pick "Circular + linear", "Circular only" or "Linear only" from the View dropdown.
  4. 4Read the summary tiles and the colored type chips, then check the features table for each hit's type, start, end, strand and length. Deep-scan rows also show percent identity, reference coverage, source database, and "partial" or "crosses origin" badges. Click a row to select that feature on the map.
  5. 5With a circular view showing, save the map from the Figure button as SVG, PNG or PDF, or press Share to copy a link that reopens the same construct.

FAQ

Which features can the Plasmid Auto-Annotator detect?

It looks for common cloning elements using short signature sequences: promoters (T7, T3, SP6, lac, tac, araBAD, CMV, EF-1a, SV40), the lac operator and CAP site, Shine-Dalgarno and Kozak sequences, affinity/epitope tags (His6, FLAG, HA, Myc, Strep-II, V5, T7), origins of replication (ColE1/pMB1, f1, SV40), antibiotic-resistance markers (AmpR/bla, KanR, CmR, TetR), universal sequencing primers (M13, T7) and a pUC-style multiple cloning site.

How does detection work — is it exhaustive?

There are two scans. The quick scan matches a short, characteristic signature (roughly 50 bp or less) on both strands, tolerating IUPAC ambiguity codes; because the library is curated and the signatures are short, variants, synonymous codon choices and anything outside the library will not be recognized. Treat it as a fast first pass. The deep scan runs BLAST, DIAMOND and Infernal against pLannotate's full databases, so it finds variants and partial features the signature library misses; because it reports imperfect matches too, check the percent identity column before trusting a low-scoring hit.

Does it scan both DNA strands?

Yes. Every signature is searched on the forward strand and as its reverse complement, so features encoded on the antisense strand are reported with forward-strand coordinates and a minus (reverse) strand label.

What is the deep scan, and how is it different?

Instead of matching short signatures, the deep scan aligns your sequence against pLannotate's full feature databases (common features, Swiss-Prot, FPbase and Rfam), cross-referenced against roughly 195,000 Addgene-deposited plasmids. On pUC19 it recovers features the quick scan has no entry for at all, such as the RNAI transcript, the bom site and the rop coding sequence. It takes a few seconds rather than being instant.

Why does a deep-scan feature show less than 100% identity, or a "partial" badge?

Deep scan reports imperfect and truncated matches rather than only exact hits, which is what lets it recognize engineered variants. Identity is the percent match over the aligned region; coverage is how much of the reference feature is present, and a "partial" badge means only part of it is. A hit at 99-100% identity with full coverage is a confident call; one in the 60-70s may be a distant homolog rather than the named feature, so treat it as a lead to check, not a conclusion.

Is there a limit on the deep scan?

Yes. Deep scan runs a multi-second database search on a shared service, so it is capped at 150,000 bp per sequence, which covers every plasmid, including large expression constructs, and takes in cosmids, fosmids and large viral genomes as well, and it is rate limited per user. Normal interactive use will not reach the limit; if it does, the error states how long to wait, and the quick scan stays available and unmetered. The sequence must also be A, C, G, T or N: other IUPAC ambiguity codes are rejected rather than silently dropped, because the search engines discard them and every reported coordinate after such a base would be shifted.

Helpful?