Ancestrify
All stories

mtdna

By Ancestrify
6 min read

Maternal haplogroup explained: what your mtDNA means

What a maternal (mtDNA) haplogroup is, how the tree is built, what H, U5, K, T2 and the other common branches tell you, why most chip kits resolve to a broad branch, and what a haplogroup can and cannot say about ancestry.

mtdnahaplogroupguideancient-dna

  1. What mitochondrial DNA is
  2. How the tree is named
  3. The common West Eurasian branches
  4. Why your result is probably broad
  5. What a maternal haplogroup can and cannot tell you
  6. Reading a haplogroup map honestly
  7. Putting it beside the autosomal picture
  8. References

Your maternal haplogroup is the one ancestry result that follows a single, unbroken line: your mother, her mother, her mother, back through every generation to a woman who lived tens of thousands of years ago. It is also the ancestry result most often over-interpreted. This guide explains what the label means, what the common branches are, why yours is probably broader than you hoped, and what it can honestly tell you.

If you want the practical steps first — exporting a raw file and getting a free call — they are in How to find your mtDNA haplogroup. This article is about what the answer means once you have it.

What mitochondrial DNA is#

Mitochondria are the energy-producing structures inside every cell, and they carry a tiny genome of their own — 16,569 base pairs, against three billion in the nucleus. It is inherited from the egg, so everyone, male and female, carries their mother's mitochondrial DNA; only women pass it on. It does not recombine, so it is copied intact, picking up an occasional mutation that every maternal descendant then inherits.

Those mutations form a tree. Every branch is defined by the mutations shared by everyone below it, and a haplogroup is simply the name of a branch. The reference sequence against which mutations are counted is the revised Cambridge Reference Sequence (Andrews et al., 1999); the tree itself is maintained as PhyloTree (van Oven & Kayser, 2009).

How the tree is named#

Haplogroup names encode the tree's structure: a letter for a major branch, then alternating numbers and letters for each division below it. H is a major branch; H1 is one of its children; H1a a child of that; H1a1 the next level down. Two people in H1a1 share a more recent maternal ancestor than two people who are merely both H. The deeper the name, the more recent the shared ancestor and the more specific the geography.

The oldest branches — L0 through L6 — are African, and every non-African lineage descends from L3 through two branches, M and N, that left Africa around 60,000 years ago. Within N, the branch R gave rise to most of the West Eurasian lineages people in Europe and the Near East carry today.

The common West Eurasian branches#

Rough characterisations from the published literature, not identities:

  • H — the most common haplogroup in Europe, carried by roughly four in ten Europeans, and spread widely across the Near East and North Africa. Ancient DNA shows it was present in Palaeolithic Europe but expanded greatly with and after the Neolithic. H1 and H3 are its largest sub-branches in western Europe.
  • U5 — the signature lineage of Europe's Mesolithic hunter-gatherers; most WHG individuals sequenced belong to U5. It survives at modest frequency everywhere in Europe and is highest around the Baltic. See Hunter-gatherer ancestry.
  • U4 and U2 — likewise ancient in Europe; U4 is common among Eastern Hunter-Gatherers and in steppe-related populations.
  • K — a branch of U8, common in the Near East and Europe, well represented among Anatolian and early European Neolithic farmers, and strongly associated with Ashkenazi maternal lineages.
  • T and J — both associated with the Neolithic spread from Anatolia and the Near East; T2 and J1c are the common European sub-branches. See Neolithic farmer ancestry.
  • HV, V and X — smaller branches; V is notable in northern Iberia and among the Saami; X2 has a scattered distribution from the Near East to North America.
  • I and W — low-frequency branches present across Europe and West Asia since prehistory.

None of these is "the Celtic haplogroup" or "the Viking haplogroup". Every one is found across many populations, and a branch's frequency in a region says something about population history, not about any individual's identity.

Why your result is probably broad#

Consumer chips read a few thousand mitochondrial positions at most — far fewer than the 16,569 in the full sequence — so a chip-based call can usually place you on a major branch (H, U5, K, T2) and sometimes one or two levels below, but rarely further. That is the correct result at the resolution the data supports, not a failure. A full mitochondrial sequence, which some whole-genome products include, resolves to the leaf.

Our free mtDNA Haplogroup Finder reads your raw file against the reference sequence and reports the branch it can support, the variants that supported it, the ones it ruled out and the branches below it the file could not test. The maternal haplogroup is also a €10 add-on to the qpAdm analysis, where it comes with a map of ancient individuals who carried the same lineage — and a placement the file cannot support is refused rather than sold. The full maternal tree, every named branch with its defining mutations and tester counts by country, is browsable free in the mtDNA haplotree browser.

What a maternal haplogroup can and cannot tell you#

It can tell you which branch of the maternal tree your one matrilineal line sits on, roughly where and when that branch arose, and which ancient individuals carried it — the ancient-DNA literature now includes thousands of dated mitochondrial genomes, which is how we know U5 was Mesolithic and K arrived with farmers.

It cannot tell you your ancestry. Ten generations back you have up to 1,024 ancestors; mtDNA traces one of them. Two siblings share it exactly and may have very different autosomal ancestry from their father's side; two strangers in H1 share a maternal ancestor thousands of years ago and nothing else in particular. A haplogroup is not a percentage, not an ethnicity, and not evidence about any ancestor beyond the one line it follows.

It is also not a match. Sharing a haplogroup with an ancient individual on a map means your maternal lines meet somewhere above both of you on the tree — often tens of thousands of years above. It does not mean that individual was related to you in any meaningful genealogical sense, and we never describe it that way.

Reading a haplogroup map honestly#

The maternal add-on and the free finder both show a map of published ancient individuals who carried your branch. Read it as a distribution, not a trail. If your branch is H1 and the map shows Neolithic farmers in Iberia, Bronze Age burials in Britain and medieval graves in Poland, the correct conclusion is "H1 was widespread across Europe for six thousand years" — not that your line travelled that route, and not that any pin on the map is a person you descend from in any sense stronger than sharing a branch. The map is most informative when a branch is rare and its ancient carriers cluster tightly in one region and period; for a common branch like H or U5, the map is a portrait of the branch, not of you.

Putting it beside the autosomal picture#

The right way to use a maternal haplogroup is as one line drawn on top of the whole-genome picture. The autosomal analyses — qpAdm on a raw file, or a Global25 analysis on coordinates — describe all your ancestry as a mixture; the haplogroup adds a single deep thread through it. The paternal equivalent, for men, is the Y-DNA haplogroup — see How to find your Y-DNA haplogroup. The terms are in the glossary.

From €29.99 · one-time
The tested version of this question
A qpAdm model composed, run and checked by hand against AADR v66, published with its p-value, every source's standard error and z-score, and the full right set, so the result can be argued with.
See the qpAdm analysis

References#

  • Andrews, R. M. et al. (1999). Reanalysis and revision of the Cambridge reference sequence for human mitochondrial DNA. Nature Genetics, 23, 147.
  • van Oven, M. & Kayser, M. (2009). Updated comprehensive phylogenetic tree of global human mitochondrial DNA variation. Human Mutation, 30(2), E386–E394.
  • Bramanti, B. et al. (2009). Genetic discontinuity between local hunter-gatherers and central Europe's first farmers. Science, 326, 137–140.
  • Posth, C. et al. (2016). Pleistocene mitochondrial genomes suggest a single major dispersal of non-Africans and a Late Glacial population turnover in Europe. Current Biology, 26, 827–833.

Related posts

How to find your mtDNA haplogroup from your raw DNA file
How to find your mtDNA haplogroup from your raw DNA file

What mitochondrial DNA records, how to get a free maternal haplogroup call from a 23andMe, AncestryDNA or MyHeritage export, why most chip kits resolve to a broad branch, and how to explore the maternal tree afterwards.

6 min read
Ancient vs modern admixture calculators: which reference panel answers your question
Ancient vs modern admixture calculators: which reference panel answers your question

A calculator against modern populations answers 'who do I resemble today'; one against dated ancient samples answers 'which deep ancestries formed me'. Mixing up the two produces the classic misreadings.

3 min read
qpAdm analysis tutorial: from a raw DNA file to a model with a p-value
qpAdm analysis tutorial: from a raw DNA file to a model with a p-value

A step-by-step qpAdm tutorial: check your raw file, merge it into AADR v66, choose sources and outgroups, run it in the browser or in R, and read the result.

14 min read
Back to all stories
Ancestrify

Combining cutting-edge genomic science with rich historical records to map your ancestry across generations and continents.


© 2026 Ancestrify. All rights reserved. · Ancestrify is a trading name of Andi Thomaj, a sole trader registered in Tiranë, Albania · NUIS M61725001N
Card payments processed by POK Payments (RPay Ltd)VISAMASTERCARD