How to Read a Plasmid Map (and the GenBank Format Behind It)
6 min read · Updated July 10, 2026
Every plasmid map crams a lot of information into one circle: backbone size, origin of replication, resistance marker, promoter, insert, tags and restriction sites, usually drawn as arrows around a ring. Most maps you see in a paper, a vendor catalog or a viewer you ran yourself are just a rendering of an underlying GenBank record, and once you can read that record you can read any map. This guide walks through the parts of a plasmid map, the GenBank format that encodes them, and a practical order for checking a new construct before you use it.
What a plasmid map actually shows
A plasmid map is a diagram of a construct's backbone size plus its functional parts, drawn to scale around a circle, or along a line for constructs too large to read comfortably as a circle.
Genes and promoters are drawn as arrows so you can see which strand they sit on and which direction they are transcribed. An arrow pointing away from a promoter, rather than into it, is one of the fastest ways to spot a construct that will not express as intended.
At minimum, a usable map should show the following:
- An origin of replication (ori), which sets copy number and host range
- A selectable marker, usually an antibiotic-resistance gene
- A promoter driving the gene or insert of interest
- The gene or insert itself
- Any fusion tags attached to the insert
- Restriction sites, either a full digest or just the ones relevant to cloning
The origin of replication sets copy number and compatibility
Check the ori before anything else, because it determines both how many copies of the plasmid a cell carries and which other plasmids it can tolerate at the same time. A pUC-type ori gives high copy number, which is convenient for miniprep yield but can stress a cell if the encoded protein is toxic at high dose. A p15A-type ori gives a lower copy number and is commonly paired with a pUC-type plasmid in the same cell precisely because the two origins do not compete for the same replication machinery. If you are setting up a co-expression system with two plasmids, that ori compatibility matters as much as the antibiotic markers do.
The GenBank record behind the map
Nearly every plasmid map you will open, whether from a vendor, a lab collection, or a viewer you ran yourself, is a rendering of a GenBank flat file (.gb or .gbk), the standard machine-readable format for annotated DNA sequences. The file opens with a LOCUS line giving the name, length in base pairs, molecule type, topology (circular or linear) and a modification date, for example:
LOCUS pMYPLASMID 4821 bp DNA circular 14-NOV-2023
That is followed by DEFINITION, a plain-text description of the construct, then ACCESSION and VERSION identifiers, then SOURCE and ORGANISM lines noting where the backbone or an inserted piece originated. Everything after those header lines is the FEATURES table, which is where the actual content of the map lives.
Reading the FEATURES table
Each entry in FEATURES names a feature type, such as source, gene, CDS, promoter, rep_origin or misc_feature, followed by a location and a set of qualifiers. Locations are base-pair ranges: 1..720 for a feature on the forward strand, or complement(500..800) for one on the reverse strand, which is what tells a viewer to draw that arrow pointing the other way. Qualifiers such as /gene, /product, /label and /note carry the human-readable name that actually shows up on the map. A rep_origin or misc_feature with no /label just renders as an unnamed box, which is the most common reason a map looks less informative than the underlying sequence actually is.
After the last feature, an ORIGIN section prints the raw sequence in numbered 60-base-per-line blocks, and the record ends with a line containing only //.
A practical order for checking a new construct
When you open a map you have not seen before, checking things in a fixed order is faster than reading every feature top to bottom:
- Total size and ori, which sets copy number and tells you whether the plasmid is compatible with anything else you are co-transforming
- Selectable marker, to confirm it matches the antibiotic you actually plan to select on
- Multiple cloning site or insert boundaries, to find exactly where the insert starts and ends relative to the promoter
- Reading frame at fusion junctions: check that a tag fusion does not introduce a frameshift. An in-frame fusion on the map does not guarantee an in-frame fusion in the actual construct if a base was added or dropped during cloning, so confirm against the sequence itself, not just the diagram.
Where a viewer helps
Parsing LOCUS lines, FEATURES tables and complement() locations by eye is doable but slow, especially on a plasmid someone else built. Plasmid Viewer renders a circular or linear map with restriction sites directly from your sequence, so you see the layout without manually stepping through the flat file.
If you are starting from a GenBank record rather than a raw sequence, GenBank Viewer shows the same information as an annotated map alongside a feature table. Plasmid Annotator auto-detects promoters, tags, origins and resistance markers by matching your sequence against a library of known parts, which is useful when you have inherited a construct with thin or missing annotation and do not want to identify every feature by eye.
Frequently asked questions
What does complement mean in a GenBank file?
It means the feature is encoded on the reverse strand. A location like complement(500..800) tells a viewer to draw that gene or promoter as an arrow pointing toward lower coordinates instead of higher ones.
What is the difference between a high-copy and low-copy plasmid origin?
A high-copy origin such as a pUC-type ori lets the plasmid replicate to many more copies per cell, which boosts miniprep yield, while a low-copy origin such as a p15A-type ori keeps copy number down, which is often preferred for toxic proteins or for running two compatible plasmids in the same cell.
Why does a feature on my plasmid map have no label?
The feature is present in the FEATURES table but lacks a /label, /gene, or /product qualifier, so the viewer has nothing to display except the feature type. This is common with rep_origin and misc_feature entries in loosely annotated files.
How do I know if my fusion tag is in frame?
Check that the number of bases between the start of your gene and the tag is a multiple of three with no insertion or deletion at the junction. A map showing both features next to each other does not confirm the frame, only the raw sequence coordinates do.
Related references
Reference table of common cloning and protein expression vectors with backbone size, origin of replication, copy number, selection marker, promoter and fusion tags.
Common restriction enzymes: recognition sites, cut positions, NEB buffer activity, star activity and an interactive double-digest buffer finder.
Selection markers, mechanisms and working concentrations for cloning.