Y-DNA haplogroup clade finder

The Y chromosome passes from father to son almost unchanged, so the mutations it carries accumulate in a single line and define a branching tree. Placing you on that tree means reading which known branch-defining variants your file calls in the derived state and finding the deepest branch all of them agree on. This tool reads the Y-chromosome rows out of a 23andMe, AncestryDNA or MyHeritage export, or out of a whole-genome VCF from a sequencing kit, compares them against the published tree, and reports the clade you reach, how many of your markers support it, and how far the next-best branch trails.

Your paternal haplogroup is a line, not an ethnicity. It traces one path through your ancestry, your father's father's father, and says nothing about the rest of your genome, which is where almost all of your ancestry lives. Two people can share a haplogroup and differ everywhere else, and siblings of different sexes do not both carry one.

The hard limit is coverage. Consumer chips genotype a sparse, fixed set of Y positions chosen years ago, so the depth you can reach is set by which markers your file happens to contain rather than by your actual lineage. A shallow result usually means the file lacks the markers that would resolve further, not that your line stops there, and where the evidence thins out the result says so instead of guessing at a deeper branch. Only sequencing reads the whole chromosome, and a whole-genome VCF carries every Y position the sequencer covered, so it usually resolves several branches deeper than a chip export. Runs need a free, email-verified account, and the uploaded file is deleted after the analysis.

Suppose a 23andMe v5 file comes back as R-Z2103, with the branches beneath it marked untested and a map of ancient men who carried the same branch; its fold of figures says how many of your Y markers carry a branch-defining change, how many do not, and how far the next-best branch trails. Read it inside out. The terminal call means every branch-defining marker on the path from the root through R-M269 down to Z2103 that your file contains came back derived, and nothing below Z2103 was testable, not that your line ends there. A man whose actual lineage sits five branches deeper gets exactly this result from a chip that stops testing at Z2103.

The untested list is the honest half of the result and the half worth reading twice. It tells you precisely what a deeper test would resolve: if the branches below your call are dense with named subclades, dedicated Y sequencing has real information to add; if your call already sits deep on a thin branch, sequencing may add little but a private variant. The ancient-carrier map reads under the same discipline as everywhere on this site: men on your branch are evidence of a shared paternal lineage, never proof of a named forefather.

One expectation to calibrate by vendor: chips differ sharply in Y coverage, and some products carry no Y rows at all; the file check reports the Y row count before you upload anything here. A result that seems shallow for your known lineage is nearly always the chip's marker selection, resolvable by sequencing, not a genealogy problem.

The community's long-standing free options do versions of this job. YSEQ's Clade Finder places uploaded files against a tree it maintains; the venerable Morley predictor infers a haplogroup from STR values rather than SNPs, an older technique with correspondingly coarser results. This tool's differences are the tree it reads against (the same public haplotree browsable branch by branch on this site, over 109,000 named branches), the explicit untested-branch reporting, and the ancient-carrier map drawn from the AADR reference panel, with the file deleted after the run.

The step up from every chip-based tool, ours included, is dedicated sequencing: FamilyTreeDNA's Big Y and full-genome tests read the chromosome rather than a marker panel, resolve private variants, and place men into matching groups: a genuinely different product for a genuinely different budget. The honest sequence for most people: read what your existing file supports for free here, look at what remains untested, and decide whether the deeper branches matter enough to sequence. A haplogroup is one paternal thread either way; the rest of your ancestry lives in the autosomes, where the admixture and distance tools read it.