Gateway vs Gibson Assembly: When Each Method Actually Wins
Gateway vs Gibson Assembly: When Each Method Actually Wins
You have an insert and a destination, and you can clone it with Gateway or with Gibson. Both are mature methods, both work, and both have specific situations where the other is the wrong choice. The decision is not "which is better" — it is "what does this particular project need."
This comparison walks through the criteria that actually drive the choice in practice: number of destination vectors, scar tolerance, reagent cost, time to first clone, library scale, and whether you need ccdB-tolerant strains around. By the end you should know which method to default to for your next cloning project, and which one to switch to when the default does not fit.
The short answer first
- Pick Gateway when you need to shuttle the same insert into many destination vectors over months or years (one entry clone, many downstream uses).
- Pick Gibson when you are building a single construct, especially one with custom junctions or no convenient restriction sites, and you do not want att-site scars at the boundaries.
- Pick neither — pick Golden Gate — when you are doing modular multi-part assembly with a standardized library of parts.
The rest of this post is the long answer, organized around the criteria that flip the decision.
How Gateway cloning and Gibson assembly actually work
Gateway in one paragraph
Gateway is a two-step recombination system based on bacteriophage lambda integration. In the BP reaction, BP Clonase recombines a PCR product flanked by attB sites with a donor vector carrying attP sites, producing an entry clone (insert flanked by attL sites). In the LR reaction, LR Clonase recombines the entry clone with a destination vector (attR sites and a ccdB selection cassette), producing the final expression clone with the insert flanked by 21–25 bp attB scars. The entry clone is the asset — once you have it, you can shuttle it into any Gateway-compatible destination vector with a 1-hour LR reaction.
Gibson in one paragraph
Gibson Assembly is a single-tube isothermal reaction at 50°C using T5 exonuclease, a high-fidelity polymerase, and Taq ligase. The exonuclease chews back 5′ ends to expose complementary single-stranded overhangs (15–40 bp, designed into your primers); fragments anneal at the overlaps; polymerase fills gaps; ligase seals nicks. The result is a scarless, seamless assembly of any DNA fragments you give it — backbone plus one or more inserts — provided the overlaps are designed correctly.
Criterion 1: Number of downstream destinations
This is the criterion that decides the call for most working labs.
- One destination, done: Gibson wins. The overhead of making a Gateway entry clone is wasted if you never use it again.
- Two to four destinations: it is a toss-up. The Gateway entry clone pays for itself if you actually use it, but if two of the destinations end up unused (and they often do), Gibson would have been cheaper.
- Five or more destinations over a year or more: Gateway wins clearly. The 1-hour LR reaction is faster, the success rate at LR is very high, and the entry clone is a reusable asset other lab members can use.
The classic Gateway use case is: you have a gene, and you want to express it as a GFP fusion, a His-tagged version, a yeast two-hybrid bait, a CRISPR donor template, and a lentiviral construct. The same entry clone goes into all five destination vectors with five 1-hour LR reactions. With Gibson, you would design five sets of primers and run five PCR-and-assembly workflows.
Criterion 2: Junction scars and reading frame
Gateway leaves att-site scars at both ends of the insert. The attB1 scar is approximately 25 bp, attB2 is approximately 21 bp. In most destination vectors the scars sit in-frame with N- or C-terminal tags, adding 7–8 amino acids of unstructured linker to the protein. For many applications this is invisible. For others it is a real problem:
- Crystallography and structural studies: the att scars add disordered residues that can interfere with crystal packing. Many structural biologists avoid Gateway for this reason.
- Native N- or C-terminus required: you can put the att sites in the 5′ or 3′ UTR rather than in-frame, but then your destination vectors need matching UTR-style att sites — not the standard offering.
- Small peptides: a 7-amino-acid scar is a big fraction of a 30-residue peptide.
- Functional studies sensitive to N-terminal context: signal sequences, secretion peptides, and some PTM sites depend on exact N-terminus.
Gibson is scarless by design. The fragment ends are exactly what you put in your primers. If you need a clean N-terminus or a wild-type junction, Gibson is correct.
Criterion 3: Cost per clone
Both methods have fixed reagent costs and per-reaction costs. The break-even depends on how many constructs you make per year.
- Gibson: NEBuilder HiFi or homemade Gibson master mix. NEBuilder at list price is roughly $10–15 per reaction; homemade master mix is well under $1 per reaction if you have the enzymes. PCR primers with overhang tails are an extra ~$10–25 per primer pair.
- Gateway: BP and LR Clonase are notably more expensive — roughly $25–40 per reaction at list price for BP, similar for LR. The attB-tailed primers for the initial BP add ~$10–25. Destination vectors must be purchased or obtained (most academic labs use the Andrew Phillips or Hartley collections, freely available, but commercial destinations are pricey).
List prices change; the relative ordering does not. Gateway is more expensive per reaction. The economics flip when you amortize an entry clone across many LR reactions — the BP cost is paid once.
Criterion 4: ccdB and the host strain headache
Gateway donor and destination vectors carry the ccdB gene as a negative selection — uncut donor or destination plasmid expresses ccdB and kills the bacterial host, so only successful recombinants grow up. ccdB has two consequences:
- You need a ccdB-resistant strain (DB3.1, ccdB Survival, One Shot ccdB Survival 2 T1R) to propagate uncut donor or destination plasmids. Standard DH5α or Stbl3 will not grow them.
- Don't grow up Gateway destination plasmids in your standard cloning strain — you will get either no colonies or a population of mutants that have lost ccdB and will give massive background in the LR reaction.
Gibson has none of this. You can grow up backbone and insert in DH5α, do the assembly, transform into NEB Stable or DH5α, and screen.
Criterion 5: Time to first clone
For a single new construct, end-to-end:
- Gibson: design primers (30 min), order primers (1–3 days), PCR (3–4 hours including a gel), assembly (1 hour), transform (overnight), pick and screen (1 day), miniprep and verify (1 day). Roughly 4–6 days total.
- Gateway, first time with this insert: design attB primers (30 min), order (1–3 days), PCR (4 hours), BP reaction (1–16 hours), transform (overnight), pick and screen entry clones (1 day), miniprep (1 day), LR reaction (1 hour), transform (overnight), pick expression clones (1 day), miniprep (1 day). Roughly 6–9 days total, plus an extra round of screening.
- Gateway, subsequent destinations: LR reaction (1 hour) + transform + screen + miniprep. Roughly 2–3 days.
Gibson is faster for the first clone. Gateway pulls ahead on the second, third, and fourth destination.
Criterion 6: Library scale and library cloning
Both methods can be done at library scale, but they have different sweet spots:
- Gateway is the historical default for ORFeome libraries — thousands of entry clones, each shuttled into a panel of destinations. The Hartley lab, MGC, and ORFeome consortia generated huge entry clone libraries that are still in use.
- Gibson scales for one-off complex assemblies — multi-fragment constructs that combine elements from different sources — but the per-clone optimization is higher.
- For pooled library screens (mutagenesis libraries, gRNA libraries) the modern default is Golden Gate, not Gibson or Gateway. The directional 4-bp overhangs and one-pot cycling reaction give better library coverage and less bias than either Gateway or Gibson at scale.
Side-by-side summary
| Criterion | Gateway | Gibson |
|---|---|---|
| Junction scars | ~21–25 bp att scars at each end | Scarless |
| Cost per single clone | Higher (BP + LR Clonase) | Lower (master mix) |
| Cost across many destinations | Lower (amortized BP) | Higher (one assembly per destination) |
| First-clone speed | 6–9 days | 4–6 days |
| Speed for additional destinations | 2–3 days each | Same as first clone each time |
| Multi-fragment assembly | Mostly single-fragment | 2–5 fragments routine |
| Vector ecosystem | Limited to Gateway-compatible destinations | Any backbone |
| Host-strain requirements | Needs ccdB-resistant strain for donors | Standard cloning strain |
| Reusability of intermediate | Entry clone shuttles to many destinations | Each assembly is one-off |
Verdict by use case
- "I'm building one expression construct for a specific experiment." Gibson. The Gateway entry-clone overhead is not worth paying.
- "I'm characterizing a new gene and will need it in five different vectors over the next year." Gateway. Make the entry clone, then run LR reactions as the experiments come up.
- "I'm building a complex multi-fragment construct with custom junctions." Gibson. Multi-fragment Gateway is awkward; Gibson handles 2–5 fragments natively. Golden Gate is the alternative for 4+ standardized parts.
- "I need a clean N-terminus for structural work." Gibson. The Gateway att-site scars often defeat crystal formation.
- "I'm building a screening library of thousands of variants." Neither — use Golden Gate at library scale.
- "My lab already has a Gateway destination collection and a routine workflow." Gateway. Don't switch methods just because Gibson is newer; established workflows have value.
Picking the method is the cheap part. Picking it for the right reasons — the destinations you actually need, the scars you can actually tolerate, the strain headache you actually have time for — is what separates a one-week project from a one-month one.
For either method, the design step is the same in spirit: get the overlaps right, get the reading frame right, check that nothing in your insert collides with the assembly chemistry. A tool like PlasmidStudio validates primer overlaps, checks for internal Type IIS sites if you're also considering Golden Gate, and runs the design-health checks (terminators, frame, Kozak) that catch the mistakes you would otherwise discover at miniprep.
Try PlasmidStudio
AI-assisted plasmid design with automated validation. Start free — $0 to sign up.
Get started free