DNA Replication Fork: Molecular Machinery Visualized

simulator intermediate ~10 min
Loading simulation...
~300 errors per 3 billion bp at 10⁻⁷ error rate

At an error rate of 10⁻⁷ per base pair, replicating the 3 billion bp human genome introduces approximately 300 errors. Mismatch repair corrects most of these, reducing the final mutation rate to about 10⁻⁹ per bp per cell division.

Formula

Errors per genome = genome_size × 10^(error_rate_exponent)
Replication time = genome_size / (fork_speed × num_origins × 3600) hours

The Molecular Copier

Every time a human cell divides, it must copy 3.2 billion base pairs of DNA with near-perfect accuracy — a task equivalent to copying the entire Encyclopedia Britannica with fewer than one typo. This is accomplished by an elegant molecular machine centered on the replication fork, where the double helix is unwound and both strands are simultaneously copied by a coordinated team of enzymes.

Anatomy of the Replication Fork

Helicase (yellow in the simulation) unwinds the double helix by breaking hydrogen bonds between complementary bases. Single-strand binding proteins coat the exposed single strands to prevent reannealing. Primase (green) synthesizes short RNA primers that provide the 3'-OH group DNA polymerase needs to begin synthesis. DNA polymerase III (cyan on the leading strand, red segments on the lagging strand) then extends these primers by adding complementary deoxynucleotides.

Leading vs Lagging Strand

Because DNA polymerase can only add nucleotides in the 5' to 3' direction, the two strands of the fork are replicated differently. The leading strand — oriented toward the fork — is synthesized continuously as one long polymer. The lagging strand — oriented away from the fork — must be synthesized discontinuously as short Okazaki fragments (1000–2000 bp in prokaryotes, 100–200 bp in eukaryotes), each requiring its own RNA primer. DNA ligase then seals the gaps between fragments.

Error Correction and Fidelity

DNA polymerase achieves remarkable accuracy through a three-tier system. First, the geometric selection of the active site favors correct base pairing (error rate ~10⁻⁴). Second, the 3' to 5' exonuclease proofreading domain immediately removes mismatched bases (improving to ~10⁻⁷). Third, post-replication mismatch repair proteins scan newly synthesized DNA and correct remaining errors (final rate ~10⁻⁹ to 10⁻¹⁰). Adjust the error rate in this simulation to see how each level of correction impacts genome-wide mutation counts.

FAQ

How does DNA replication work?

DNA replication begins when helicase unwinds the double helix at the replication fork. Single-strand binding proteins stabilize the separated strands. Primase synthesizes short RNA primers, and DNA polymerase III extends them, adding complementary nucleotides. The leading strand is synthesized continuously; the lagging strand is made in short Okazaki fragments that are later joined by DNA ligase.

Why is there a leading and lagging strand?

DNA polymerase can only synthesize in the 5' to 3' direction. The leading strand runs toward the fork, so it can be copied continuously. The lagging strand runs away from the fork, so it must be copied in short segments (Okazaki fragments) that are synthesized backward and then ligated together.

How accurate is DNA replication?

DNA polymerase has an intrinsic error rate of about 10⁻⁵ per base pair. Built-in 3' to 5' proofreading exonuclease activity improves this to ~10⁻⁷. Post-replication mismatch repair further reduces it to ~10⁻⁹ to 10⁻¹⁰, meaning roughly 0.1–1 error per human genome per cell division.

How long does it take to replicate the human genome?

Each replication fork moves at about 50 bp/s in human cells (much slower than the 1000 bp/s in bacteria). However, human chromosomes have thousands of replication origins that fire simultaneously, allowing the entire 3 billion bp genome to be copied in approximately 8 hours during S phase.

Sources

Embed

<iframe src="https://homo-deus.com/lab/genetics/dna-replication/embed" width="100%" height="400" frameborder="0"></iframe>
View source on GitHub