mtDNA Haplogroup Predictor

Estimates a mitochondrial haplogroup from the small set of MT positions incidentally included on autosomal test chips — for narrowing down match theories, not a replacement for full mtDNA sequencing.

Read this first: autosomal chips were not designed to sequence mtDNA, so coverage is a sparse, incomplete sample of the ~16,569 base mitochondrial genome. 23andMe (older exports, roughly pre-2024) is the most reliable source of usable MT calls. AncestryDNA's current chip (2019 onward) also includes a few hundred MT positions and can work here too, but coverage is thinner and results are noticeably less certain — treat an AncestryDNA-only call as a rough lead, and cross-check it if you can. FamilyTreeDNA Family Finder exports include MT probe rows, but in practice the chip frequently fails to call a genotype at any of them — every FTDNA file we've tested came back with zero usable calls, so don't be surprised if yours does too. MyHeritage raw exports contain no mtDNA positions at all and cannot be used here, nor can older/pre-2019 AncestryDNA exports. Even with good coverage, results are typically a broad haplogroup call, not the fine subclade resolution you'd get from a dedicated mtDNA Full Sequence test. Your file is processed entirely in this browser tab — nothing is uploaded anywhere.

Click to choose a raw DNA file

or drag it here — .txt or .csv, any of the formats below

23andMe AncestryDNA (limited, 2019+ chip) FTDNA (often no-called) MyHeritage (no MT data)

—

0Markers confirmed

0MT positions tested

0Tree depth reached

Other candidates at similar depth

How this works

Your file's MT (mitochondrial) rows are read locally in your browser and compared against PhyloTree Build 17, the standard rCRS-referenced mitochondrial phylogeny (the same tree HaploGrep and James Lick's mthap use), containing 5,435 haplogroups and their defining mutations. The tool walks the tree from the root, descending into any branch whose defining markers are confirmed by your file and never contradicted by a tested position, stopping at the deepest point your file's coverage can support. "Confirmed" markers are ones your file actually tested and matched; the gap between confirmed and total reflects positions the chip simply never queried — not evidence against them.