Dam and Dcm Methylation: Why One Enzyme in a Digest Will Not Cut
8 min read · Updated November 11, 2026
One enzyme in a double digest cuts and the other does not, in a buffer where both are supposed to be at 100%. The instinct is to blame the buffer, then the enzyme, then the DNA. The usual answer is none of those: the site was methylated by the strain the plasmid was grown in.
The reason this misleads is that the blocking is not a property of the enzyme alone. It depends on the bases flanking the recognition site, so the same enzyme cuts one construct and not another.
The two methylases a standard prep carries
E. coli K-12 strains used for cloning are dam+ and dcm+. Dam methylates the adenine in GATC; Dcm methylates the inner cytosine in CCWGG (CCAGG and CCTGG). Neither is a rare event — GATC is a four-base site, so it occurs roughly every 256 bp by chance, and a plasmid carries dozens.
A restriction site is blocked when it overlaps one of those methylated bases. Not when it is near one, and not when it contains the motif as a subsequence — the methyl group has to sit on a base inside the recognition sequence.
Worked: XbaI, blocked or not depending on its neighbours
XbaI recognises TCTAGA, which contains no GATC. On the sequence AAATCTAGATCAAA it is nevertheless blocked, because the flanking bases complete a GATC that overlaps the site: TCTAGA is at position 4 and GATC at position 8, sharing the GA. The methylation check reports XbaI blocked at position 4, one of one site.
Change one flanking base and the verdict flips. On AAATCTAGAAAA the XbaI site is still there and there is no GATC anywhere, so the same enzyme on the same site with the same buffer is reported as one site, zero blocked.
Worth knowing which tool says what: the site scanner below finds recognition sites and reports their positions, and does not model methylation at all. The blocked-or-not verdict comes from the cloning troubleshooter and the workbench's enzyme panel, which take the strain the DNA was prepared from as an input. A site list showing XbaI present is not a statement that XbaI will cut.
That is the whole phenomenon in two sequences, and it explains the symptom that makes methylation so confusing: an enzyme that worked on last month's construct fails on this month's, with no change to the protocol.
The enzymes worth knowing by name
In the curated reaction table here, nine enzymes are blocked by one of the two methylases. Dam blocks XbaI, ClaI, BspEI, TaqI and MboI. Dcm blocks StuI, ApaI, FseI and ScrFI. Several are also blocked by CpG methylation, which is a third, separate mechanism that matters for DNA from mammalian sources rather than from E. coli.
The GATC isoschizomers are the case that catches people because the names look interchangeable and the requirements are opposite. MboI and DpnII are blocked by Dam methylation — they need an unmethylated GATC. DpnI requires a methylated GATC and is used precisely because it destroys the methylated template after site-directed mutagenesis while leaving the unmethylated PCR product. Sau3AI cuts GATC regardless of adenine methylation, though it is blocked by cytosine methylation inside the site.
DpnI is deliberately not offered as an ordinary restriction enzyme in SeqBench, because a model with no methylation state would either pretend it cuts everything or pretend it cuts nothing. It is named in the enzyme resolver with that reason attached, which is the honest output.
Proving it rather than assuming it
The cheap test is to digest the same DNA with an enzyme you know is insensitive — EcoRI, BamHI, HindIII are not blocked by either methylase — in the same tube. If that enzyme cuts and the suspect one does not, the DNA and the reaction are fine and the site is the problem.
The definitive fix is to prepare the plasmid from a dam−/dcm− strain. It is a different prep, not a different buffer, and it costs a transformation and a miniprep. Repeating the digest with more enzyme, more time, or a fresh tube will not change the outcome if the methyl group is on the base.
Sequencing the region is the third option, and it settles the other half of the question: whether the site you expected is even there. A site that was assumed rather than scanned is the other common reason a digest gives fewer bands than predicted, and it produces the identical gel.
What the scan cannot see
- The strain the DNA actually came from. The scan applies a rule; it does not know whether your prep was dam+.
- Other modifications — CpG methylation from a mammalian source, or a phage-specific base — beyond the two motifs modelled here.
- Partial digestion. A blocked site gives no cut in that site; every site uncut is a different failure and points at the reaction rather than the sequence.
- Star activity, which produces extra cuts rather than missing ones and is a buffer and glycerol problem.
FAQ
Why did one enzyme in my double digest not cut at all?
Check methylation before the buffer. Plasmid from a standard dam+/dcm+ strain is methylated at GATC and CCWGG, and a recognition site overlapping either is blocked regardless of how good the reaction is. XbaI, ClaI, BspEI, TaqI and MboI are Dam-blocked here; StuI, ApaI, FseI and ScrFI are Dcm-blocked.
Why does XbaI cut one plasmid and not another?
Because Dam blocking is context-dependent. XbaI's TCTAGA contains no GATC, so it is blocked only when the flanking bases complete one. The same site in a different sequence context is not blocked at all.
How do I get around Dam methylation?
Prepare the plasmid from a dam−/dcm− strain. That removes the methyl groups, which is the only fix; more enzyme, a longer incubation or a different buffer cannot cut a methylated base.
What is the difference between DpnI, DpnII, MboI and Sau3AI?
All four recognise GATC and they differ in what they require. DpnI needs the site methylated, which is why it removes the template after mutagenesis. MboI and DpnII need it unmethylated and are blocked by Dam. Sau3AI cuts regardless of adenine methylation but is blocked by cytosine methylation within the site.
Related references
Common restriction enzymes: recognition sites, cut positions, NEB buffer activity, star activity and an interactive double-digest buffer finder.
Nucleotide ambiguity codes and their complements.
Selection markers, mechanisms and working concentrations for cloning.