Double Digest Buffer Finder - Two Restriction Enzymes, One Tube
Pick two restriction enzymes and get the single buffer that runs both, each enzyme's activity in every buffer, and a straight answer on when to digest sequentially instead.
🌐 Nothing you paste is logged or stored — every tool is also callable via REST & MCP, and in bulk from the batch tools
Choose two restriction enzymes and get the buffer to use, chosen on the worse of the two activities rather than the average - because the enzyme that under-performs is the one that leaves your plasmid uncut and your ligation full of background. The full activity table for every buffer is shown, not just the winner, so you can see how much you give up by using a buffer you already have on the bench. Incubation temperatures are checked separately from buffer compatibility, since two enzymes can share a buffer and still disagree by 10 degrees, and that is a different problem with a different fix. Where no single condition works well enough, the answer is a sequential digest with a cleanup in between, and the tool says so plainly instead of recommending a compromise buffer that half-cuts. Activity figures come from NEB's own current product pages, audited against them in 2026 rather than transcribed from an older compatibility chart.
Working on a whole construct rather than one pair of enzymes? Open SeqStudio — the full editor, with live feature annotation, plasmid maps, restriction and primer panels, undo/redo, multi-document tabs and GenBank / SnapGene import and export.
How to use the Double Digest Buffer tool
- 1Pick your two enzymes from the list. Only enzymes with published reaction data are offered, since a recommendation without activity figures behind it would be a guess.
- 2Read the recommended buffer and the worse enzyme's activity in it - that figure, not the better one, is what decides whether the digest goes to completion.
- 3Check the temperature row. Enzymes that share a buffer but not an optimum need the lower temperature and a longer incubation, or a sequential digest.
- 4If the answer is sequential, cut with one enzyme in its own buffer, clean up on a column or beads, then cut with the second.
Frequently asked questions
Why is the buffer chosen on the worse enzyme's activity?
Because a double digest fails asymmetrically. If one enzyme runs at 100% and the other at 25%, the reaction is limited by the 25% enzyme: you get linearised plasmid instead of the two-cut fragment you wanted, and after ligation that shows up as a lawn of colonies carrying re-ligated vector. Averaging the two activities would hide exactly the enzyme that causes that, so the recommendation is made on the minimum and the minimum is what the headline figure reports.
What activity is good enough?
As a working rule, 75% or more for both enzymes is comfortable, 50-75% works with a longer incubation or more enzyme, and below 50% is where a sequential digest becomes the better use of an afternoon. The table colours the figures on those bands. These are practical thresholds rather than a vendor guarantee - a 50% enzyme cutting a supercoiled plasmid at a site near another feature can behave worse than the number suggests.
The enzymes share a buffer but the temperatures differ. What do I do?
Digest at the lower of the two temperatures for longer, or digest sequentially. An enzyme run below its optimum is slower but usually still specific; run above its optimum it can lose specificity or die. The tool reports the two temperatures separately from the buffer verdict precisely because they are different failure modes, and a shared buffer does not rescue a 10-degree gap.
Why does a dash appear instead of an activity figure?
Because NEB does not publish a figure for that enzyme in that buffer. A dash is not zero and should not be read as one - it means the number is unknown, so the tool declines to recommend that buffer rather than assuming a value. If the only dash-free option is a poor one, that is genuine information about how well characterised the pair is.
Does this tell me whether the enzymes cut my sequence?
No, and it deliberately stays out of that question. This answers the buffer and temperature question for a pair of enzymes; whether those enzymes have sites in your plasmid, how far apart they are, and whether the resulting fragments will resolve on a gel are separate questions answered by the restriction-sites, double-digest fragment and virtual-gel tools. Keeping them separate means the buffer answer does not require you to paste a sequence.
What about star activity and methylation?
Neither is modelled here. Some enzymes cut at degenerate sites under sub-optimal conditions - exactly the conditions a compromise buffer creates - and some are blocked by Dam or Dcm methylation in the strain you grew the plasmid in. Both are real reasons a digest with a good activity score still fails, and both are outside what a buffer table can tell you. Notes flagged in the results call them out where the reaction data records them.
Where do the numbers come from?
From NEB's current product pages for each enzyme, checked against them directly rather than copied from a legacy compatibility chart - an audit in 2026 found 57 corrections between the older chart values and the current published ones, including cases where the modern rNEBuffer figures differ from the classic four-buffer values people still quote. The high-fidelity and standard versions of the same enzyme are not interchangeable and are listed separately where both exist.
Is my data stored, and can I run this from code?
There is nothing to store - the input is two enzyme names. double_digest is also callable from the REST API and the MCP server, which is the practical way to check a whole plate of planned digests at once rather than one pair at a time.
More
Related tools
Summarise and validate FASTA or FASTQ: counts, N50, GC, quality.
Convert between mass, moles, molarity and copy number for DNA/RNA.
Turn a 3:1 insert-to-vector molar ratio into the microlitres you actually pipette, for one insert or a whole multi-fragment assembly.