Audited ·Last updated 29 Jul 2026·5 citations·Tier 2·0 uses

Restriction Digest Calculator — Cut Sites and Fragment Sizes

Find every cut site in a DNA sequence and get the fragment sizes, for a linear fragment or a circular plasmid. Enter any recognition site and cut position.

Restriction Digest Calculator

Plain sequence or FASTA — headers, whitespace and line numbering are stripped, case does not matter, and U is read as T. NC-IUB ambiguity codes are accepted. Up to 50,000 bp.
Look this up for your enzyme in REBASE (version 607, 29 June 2026). You may paste it with the caret, as G^AATTC — the caret is stripped, but you must still set the cut position below. Ambiguity codes such as R and N are allowed.
How many bases of the recognition sequence lie 5′ of the top-strand cut. G^AATTC is 1; a blunt cutter such as CCC^GGG is 3; a 3′-overhang cutter such as CTGCA^G is 5. This is NOT determined by the recognition sequence alone — see the warning below.
bases
Topology
Fragment sizes
19, 16, 5
Every fragment in base pairs, largest first — the band pattern you would expect on a gel. Lists up to 40 fragments in full and summarises beyond that.
Recognition sites found
2 sites
Fragments
3
Largest fragment
19 bp
Smallest fragment
5 bp
Template length
40 bp

Background.

This restriction digest calculator finds every occurrence of a recognition sequence in your DNA and reports the fragment sizes you would expect to see on a gel. It handles linear fragments and circular plasmids separately, because the answer genuinely differs: n cuts give n+1 fragments on a linear molecule but only n on a circle, and a site that straddles the arbitrary point where you started writing out a plasmid sequence is completely invisible to a linear scan.

One thing this page deliberately does not have is a dropdown of enzyme names, and the reason is worth stating plainly. REBASE, the curated database that is the authority for recognition sequences and cut positions, was consulted while building this page — version 607, dated 29 June 2026. Two automated reads of the same REBASE file, minutes apart, returned contradictory cut positions for the same enzymes: KpnI came back once as GGTAC^C and once as G^GTACC, SmaI once as CCC^GGG and once as C^CCGGG. Those are not typographical variations. They are different cuts of the same recognition sequence, and they produce different fragment sizes. Rather than ship a table of values that could not be verified, this calculator asks you for the recognition sequence and the cut position and tells you to take both from REBASE for your specific enzyme.

That is not merely defensive. It reflects a real hazard: the recognition sequence does not determine the cut. Enzymes that recognise the same sequence are isoschizomers, and those among them that cut it at a different position are neoschizomers — so two enzymes can share a six-base site and give you different band sizes. If you look up only the sequence and assume the cut, you can be wrong without any warning. Look up both.

The one default that does ship, EcoRI at G^AATTC, is verified from peer-reviewed primary literature rather than from those failed database reads. Dugaiczyk, Boyer and Goodman's 1975 paper in the Journal of Molecular Biology describes EcoRI fragments as terminated at their 5′ ends by the single-stranded sequence pA-A-T-T-, and a 5′ AATT overhang inside the palindrome GAATTC is only possible if the top-strand cut falls immediately after the G. The calculator's test suite asserts exactly that: the four bases immediately 3′ of every cut must read AATT.

What you get is a map, not a simulation. The calculator assumes every site is cut and cut completely. It does not model Dam, Dcm or CpG methylation, which routinely blocks a site from cutting at all and explains far more surprising gels than arithmetic ever does. It does not model star activity, partial digestion, buffer or temperature compatibility for double digests, or Type IIS enzymes such as BsaI that cut a fixed distance outside their recognition sequence. It models the top-strand cut only, so it reports fragment lengths — which is what a gel measures — and makes no claim about the overhang chemistry at the ends.

What is restriction digest calculator?

A Type II restriction endonuclease binds a short, usually palindromic, DNA sequence and cuts both strands at a fixed position relative to it. EcoRI recognises GAATTC and cuts between the G and the first A on each strand, leaving a four-base 5′ AATT overhang; a blunt cutter such as one recognising CCCGGG and cutting in the middle leaves no overhang at all. Because the recognition sites are short, they occur by chance at predictable frequencies — a six-base site appears roughly once every 4⁶, or about 4,100 base pairs, in a random sequence — which is what makes restriction mapping useful.

Digesting a molecule with a single enzyme produces a set of fragments whose sizes depend on where the sites are and on whether the molecule is linear or circular. On a linear template, n cuts produce n+1 fragments, because the two ends are already free. On a closed circle, n cuts produce exactly n fragments, because the first cut only opens the circle into a line rather than separating anything. A plasmid with a single site therefore runs as one band at full length after digestion, not as two.

Enzyme names follow the convention proposed by Smith and Nathans in 1973 and revised by Roberts and colleagues in 2003: an abbreviation of the source organism's genus and species, sometimes a strain designation, and a Roman numeral distinguishing multiple enzymes from the same organism. Two enzymes recognising the same sequence are isoschizomers; if they cut it at different positions they are neoschizomers. That distinction is why a recognition sequence on its own is not enough information to predict a digest, and why this calculator takes the cut position as a separate input.

How to use this calculator.

  1. Paste your sequence. Plain text or FASTA both work — headers, whitespace, line numbering and gap characters are removed, case does not matter, and U is read as T.
  2. Look up your enzyme in REBASE (version 607, 29 June 2026) and copy BOTH the recognition sequence and the cut position. Do not assume the cut from the sequence: neoschizomers share a site and cut it differently.
  3. Enter the recognition sequence. You can paste it with the caret, as G^AATTC — the caret is stripped for matching, but you still need to set the cut position field yourself.
  4. Set the cut position: how many bases of the recognition sequence lie 5′ of the top-strand cut. G^AATTC is 1, a blunt CCC^GGG is 3, a 3′-overhang CTGCA^G is 5, and a site cut before its first base is 0.
  5. Choose the topology. Circular for a plasmid, linear for a PCR product or a gel-purified fragment. If you are unsure, try both — the difference in fragment count tells you a lot.
  6. Read the fragment sizes, largest first. That is the band pattern you would expect. Check the sum: fragment sizes always add up to the template length exactly.
  7. Sanity-check against a real gel. Bands within about 10 percent of each other will not resolve on standard agarose, and fragments under roughly 100 bp often run off the end or stain too faintly to see.
  8. If a site does not cut in the tube, suspect methylation before suspecting the map — Dam, Dcm and CpG methylation block many enzymes and are not modelled here.

The formula.

cut_i = start_i + offset · linear: n+1 fragments · circular: n fragments

The calculation is a scan followed by a set of differences. Every position where the recognition sequence matches is recorded — overlapping matches included, since a site such as AA genuinely occurs three times in AAAA. Each match at position s produces a cut after s + offset bases of the molecule, where offset is how many bases of the recognition sequence lie 5′ of the top-strand cut.

For a linear molecule the cut positions are sorted and the fragments are the gaps between them, plus the two ends: cut₁, then cut₂ − cut₁, and so on, finishing with L − cutₙ. That gives n+1 fragments from n cuts. Cuts landing exactly at position 0 or position L are discarded, because a cut at the very end of a linear molecule separates nothing — this is why the calculator never reports a zero-length fragment.

For a circular molecule the sequence is searched doubled, so a site straddling the origin is found, and cut positions are taken modulo the length. The fragments are the gaps between consecutive cuts, closing the loop with (L − cutₙ) + cut₁. That gives n fragments from n cuts. Zero cuts leave an intact circle and one cut merely linearises it, so both cases return a single fragment of the full length.

Ambiguity codes are handled conservatively. A symbol in the recognition sequence matches a template base when the template base's possible set is contained in the site symbol's set: a site R matches a template A or a template G, and a site N matches anything. The reverse does not hold — a template N is never matched by a concrete site symbol, because an unknown base is not evidence of a site.

Work through the loaded example. The 40 bp sequence AAAAGAATTCAAAAAAAAAAGAATTCAAAAAAAAAAAAAA has GAATTC starting at 0-based positions 4 and 20. With offset 1 the cuts fall after 5 and 21 bases. Treated as linear, the fragments are 5, then 21 − 5 = 16, then 40 − 21 = 19, so the gel shows three bands of 19, 16 and 5 bp, summing to 40. Treated as circular, the same two cuts give 21 − 5 = 16 and (40 − 21) + 5 = 24 — two bands, still summing to 40. Same sequence, same enzyme, different answer, which is why topology is a required input rather than an assumption.

Rounding: there is none. Every numeric output is an exact integer count of base pairs or of sites, and no floating-point arithmetic is performed anywhere in this calculator.

One limitation worth stating precisely, because it is easy to misread the output. Only the top-strand cut is modelled. Digesting the reverse complement of a sequence at the same offset is not the same operation — for a staggered enzyme it corresponds to the bottom-strand cut, which sits at (site length − offset) on the top strand, four bases away for EcoRI. For a blunt cutter, where the offset is exactly half the palindrome, the two coincide. This is why the page reports fragment lengths, which is what a gel measures, and says nothing about end chemistry.

A worked example.

Example

Take the same 40 bp sequence loaded in the widget, but treat it as a tiny closed circle rather than a linear fragment. The two GAATTC sites start at positions 4 and 20 (0-based), and with EcoRI's cut position of 1 the top-strand cuts fall after 5 and 21 bases. On a circle there are no free ends to begin with, so the two cuts produce exactly two fragments: the arc between them, 21 − 5 = 16 bp, and the arc that wraps around through the origin, (40 − 21) + 5 = 24 bp. Two bands, 24 and 16, summing to 40. Switch the topology selector to linear and the identical sequence and enzyme give three bands — 19, 16 and 5 — because the two ends of a linear molecule are already free, so n cuts yield n+1 pieces instead of n. Notice which fragment is shared: the 16 bp interior piece appears in both, because it lies between the two cuts either way. What changes is that the linear molecule's two terminal pieces, 5 and 19, are joined through the origin into a single 24 bp fragment on the circle. This is also why a plasmid with exactly one site runs as a single full-length band after digestion rather than as two bands: one cut opens a circle, it does not divide it.

sequenceAAAAGAATTCAAAAAAAAAAGAATTCAAAAAAAAAAAAAA
topologycircular
cut Offset1
recognition SiteGAATTC

Frequently asked questions.

Why is there no dropdown of enzyme names?
Because the cut positions could not be verified to the standard this site requires. REBASE, the curated database that is the governing authority, was consulted during the build — version 607, dated 29 June 2026 — but two automated reads of the same file made minutes apart returned contradictory cut positions for the same enzymes: KpnI as GGTAC^C and as G^GTACC, SmaI as CCC^GGG and as C^CCGGG, and one read returned a completely different enzyme's site under the name BglII. Those disagreements are not cosmetic; they change every fragment size in the answer. The honest response is to ship no table rather than a table that might be wrong, so the recognition sequence and cut position are inputs and you take both from REBASE for your specific enzyme. The one shipped default, EcoRI G^AATTC, comes from peer-reviewed primary literature instead: Dugaiczyk, Boyer and Goodman reported in 1975 that EcoRI fragments carry a 5′ AATT overhang, which fixes the cut after the G.
Why does my plasmid with one cut site show a single band?
Because a single cut opens a circle, it does not divide it. On a closed circular molecule there are no free ends to begin with, so n cuts produce exactly n fragments — one cut gives one linear molecule of the full plasmid length. On a linear molecule the two ends are already free, so n cuts produce n+1 fragments. This is the most common source of confusion in reading a digest, and it is why topology is a required input here rather than something the calculator guesses. It also has a practical use: linearising a plasmid with a single-cutter is exactly how you check its true size, because supercoiled circular DNA runs anomalously fast on a gel and a linear standard is the only fair comparison.
What is the difference between an isoschizomer and a neoschizomer?
Isoschizomers are different enzymes, usually from different organisms, that recognise the same DNA sequence. Neoschizomers are the subset of those that recognise the same sequence but cut it at a different position. The distinction matters enormously for this calculator, because the recognition sequence alone does not determine the fragment sizes — two enzymes sharing a six-base site can leave the cut in different places and give you different bands. It also matters for cloning, because the overhang differs: one may leave a 5′ overhang and the other a blunt end or a 3′ overhang, which changes what it will ligate to. The naming convention that makes these relationships trackable was proposed by Smith and Nathans in 1973 and revised by Roberts and colleagues in 2003. The practical rule is simple: when you look an enzyme up, copy the cut position as well as the sequence.
The gel does not match the prediction. What went wrong?
Usually not the arithmetic. The first thing to check is methylation: Dam, Dcm and CpG methylation block many restriction enzymes, and plasmid DNA prepared from a standard laboratory E. coli strain is Dam and Dcm methylated, so a site that exists in the sequence may simply not cut. This calculator does not model methylation at all. Second is incomplete digestion — too little enzyme, too short an incubation, or an inhibitory carryover from the miniprep — which produces extra bands corresponding to partially cut species. Third is gel resolution: fragments within roughly ten percent of each other will not separate on standard agarose, so two predicted bands can appear as one, and fragments under about 100 bp often run off the end or stain too faintly to see. Fourth is star activity, where an enzyme cuts at related but non-canonical sites under suboptimal buffer, glycerol or pH conditions. Only after all of those should you suspect that the sequence you pasted is not the sequence in the tube — although that does happen too.
Can I use this for BsaI, BsmBI or other Golden Gate enzymes?
No. Those are Type IIS enzymes, which recognise an asymmetric sequence and cut a fixed distance outside it — BsaI recognises GGTCTC and cuts one base downstream on the top strand and five on the bottom, generating a four-base overhang whose sequence you choose. This calculator only models Type II enzymes that cut inside their own recognition sequence, and the cut position field is constrained to lie between 0 and the length of the site, so a downstream cut cannot be expressed. It also does not model the directionality that makes Type IIS enzymes useful: because the site is asymmetric, the enzyme cuts on one side only, and the orientation of the site in your construct determines which side. Use a dedicated Golden Gate design tool for those. For the same reason, this page cannot represent enzymes that cut on both sides of their recognition site.
How does it handle ambiguity codes like N or R in the recognition sequence?
A site symbol matches a template base when the template base is one of the possibilities that symbol covers. So a site written GRATTC matches both GAATTC and GGATTC, because R means A or G, and a site of NNNNNN matches every six-base window. The reverse does not apply: an N in your template sequence is not matched by a concrete site symbol, because an unknown base is not evidence that a site is present. That is a deliberately conservative choice — it means a sequence with gaps or low-quality regions will under-report sites rather than invent them, and the fragment sizes it does report are ones you can rely on. The symbols accepted are the full NC-IUB set standardised in the 1984 recommendations: R, Y, S, W, K, M, B, D, H, V and N, in both the template and the recognition sequence.

References& sources.

  1. [1]Roberts, R. J., Vincze, T., Posfai, J. & Macelis, D. 'REBASE: a database for DNA restriction and modification: enzymes, genes and genomes.' Nucleic Acids Research 51(D1): D629–D630 (2023). doi:10.1093/nar/gkac975, PMID 36318248. Database served at rebase.neb.com; version 607, dated 29 June 2026, confirmed on retrieval 2026-07-29. Cited as the authority a reader must consult for their own enzyme's recognition sequence and cut position. Deliberately NOT used as the source of a built-in enzyme table on this page: two automated reads of the same REBASE file minutes apart returned contradictory cut positions (KpnI as GGTAC^C and as G^GTACC; SmaI as CCC^GGG and as C^CCGGG), and unverified values are not shipped.
  2. [2]Dugaiczyk, A., Boyer, H. W. & Goodman, H. M. (1975). 'Ligation of EcoRI endonuclease-generated DNA fragments into linear and circular structures.' Journal of Molecular Biology 96(1): 171–184. The primary-literature verification of the one default this page ships: EcoRI fragments are described as 'terminated at their 5′-ends by the single-stranded sequence pA-A-T-T-', which fixes the top-strand cut immediately after the G in GAATTC. Asserted as a test — the four bases 3′ of every cut must read AATT. Paywalled; listed bibliographically.
  3. [3]Roberts, R. J. et al. (2003). 'A nomenclature for restriction enzymes, DNA methyltransferases, homing endonucleases and their genes.' Nucleic Acids Research 31(7): 1805–1812. doi:10.1093/nar/gkg274. Source of the enzyme-naming convention and of the isoschizomer / neoschizomer definitions on which this page's central warning depends — that enzymes sharing a recognition sequence may cut it at different positions, so the sequence alone does not determine the fragment sizes. Open access via PubMed Central.
  4. [4]Smith, H. O. & Nathans, D. (1973). 'A suggested nomenclature for bacterial host modification and restriction systems and their enzymes.' Journal of Molecular Biology 81(3): 419–423. Independent second authority consulted as a cross-check on the naming and recognition-site conventions used here, predating and independent of REBASE's curation; the Type II model of a recognition sequence plus a fixed cleavage position, written with a caret inside the site, is established there and unchanged in the 2003 revision. Paywalled; listed bibliographically.
  5. [5]NC-IUB — Nomenclature Committee of the International Union of Biochemistry (1985). 'Nomenclature for incompletely specified bases in nucleic acid sequences: recommendations 1984.' European Journal of Biochemistry 150: 1–5, and simultaneously in Nucleic Acids Research 13: 3021–3030, Biochemical Journal 229: 281–286 and three further journals in 1986. The ambiguity alphabet accepted in both the template and the recognition sequence on this page. Read on the official IUBMB nomenclature site. Retrieved 2026-07-29.

In this category

Embed

Quanta Pro

Paid features are coming later.

  • All 682 calculators remain free
  • No billing is enabled
Coming soon