Shuttle Vector vs Cloning Backbone: Two Replicons or One Job

A shuttle vector versus a cloning backbone is a dual-replicon claim, not a nicer multiple-cloning site. A cloning backbone is built to propagate and manipulate DNA in one practical host, usually E. coli. A shuttle is that job plus a second, host-specific origin — and usually a second selectable marker — so the same file can be grown in a second species. The label is an architecture. It is not a host list.

What a Shuttle Vector Is — and What a Cloning Backbone Is

Addgene’s shuttle-vector 101 starts from a shared fact: replication machinery is host-specific. An E. coli ori is not a yeast ARS. A one-host cloning backbone accepts that limit and does all the cloning where transformation is cheap. A shuttle spends extra sequence to keep a second replicon on the same molecule.

That is category plus purpose. The audience is anyone moving a construct from a fast bacterial host into yeast, another bacterium, or a mammalian production system. The purpose is to clone first, then transfer the same DNA. It is not a quality ranking of the MCS.

Two Origins, Two Ways to Keep the Plasmid

Addgene’s usual architecture is four objects: an origin and a selectable marker for each host. Yeast shuttles add an ARS, often a CEN, and an auxotrophic marker such as URA3 on top of a bacterial ori and bla or another antibiotic cassette. The E. coli side still looks like ordinary cloning. The second side is the claim that the other host will recognize the second ori and the second marker.

One magical ori that “just works everywhere” is a different vocabulary. That vocabulary is broad host range. A shuttle still names two hosts. A broad-host-range claim names a set of bacteria that one replicon is said to serve. Mixing the words hides which experiment you still owe.

Shuttle Is Not Broad Host Range and Not an Expression Upgrade

Addgene splits the words on purpose. Broad-host-range plasmids, in the usual lab sense, are multi-bacterial replication claims, often with a history in natural plasmids. Shuttles are engineered lab tools and may cross kingdoms. The three-part BHR test — transfer, replication, persistence — already lives on the broad-host-range page. This page does not rewrite it.

Promoters, tags, and whether the backbone is a cloning vector or an expression vector live on the feature page. Copy number inside one ColE1-family pair lives on the pBR322 versus pUC page.

A Common Example, Not a Universal Host List

Addgene notes that almost all commonly used S. cerevisiae vectors are shuttles. That is the textbook case: clone and sequence in E. coli, then transform yeast. Many mammalian constructs also keep a bacterial ori so the file can be prepped as a plasmid. Viral-production “shuttle” or transfer vectors are a related but distinct delivery story. One yeast example does not license a table of every plant or mammal host.

The Second Origin Is Still a Claim

The annotation is a claim. Persistence in the second host still has to be tested. After both replicons are named, a map such as ZettaGene is one place to see them together. Seeing two ori labels is not proof the second host will keep the plasmid. The takeaway is the dual-replicon architecture — and the refusal to treat shuttle, BHR, and expression as synonyms.

Frequently Asked Questions

What makes a plasmid a shuttle vector rather than a cloning backbone?

A second, host-specific replicon and usually a second marker. One E. coli ori is a cloning backbone.

Is a shuttle vector the same thing as a broad-host-range vector?

Not in the usual lab vocabulary. BHR is a multi-bacterial replication claim; shuttles are engineered lab tools and may cross kingdoms. The BHR test lives on its own page.