
The Two Numbers That Open Every Cousin Relationship
Genealogists reduce every cousin question to two integers. These are the shared ancestor’s generation distance and the cousin’s generation offset. You never calculate cousinship through yourself or your parents. You only calculate it through a common ancestor who sits above both of you in the pedigree chart.
Find that shared ancestor first. On a standard pedigree chart, locate the person who appears in both your direct line and your cousin’s direct line. That ancestor might be a grandparent, a great-grandparent, or someone six generations back. The chart position determines everything else.
The first number counts how many generations separate you from that common ancestor. Subtract one, and you have the cousin degree. If your grandmother is the shared ancestor, you’re two generations away. 2 minus 1 equals 1, making you first cousins with anyone else who shares that grandmother.
The second number measures the difference between your generation count and your cousin’s. A zero difference means simple cousinship; a positive difference adds “removed” to the title. Your grandmother’s sister’s grandchild sits three generations from her while you sit two. That one-generation gap makes them your first cousin once removed.
Colloquial usage has muddied these definitions for centuries. Many families call any distant relative a “third cousin” without consulting charts. Legal documents and probate records from 19th-century New England show clerks applying the same mathematical formula we use today. Draw your own pedigree chart on paper tonight. Mark yourself at the bottom, work upward to any shared ancestor, then count down to the cousin in question. The two numbers will name themselves.
The quick-reference chart lists first cousin (grandparent, 0 gap), second cousin (great-grandparent, 0 gap), third cousin (great-great-grandparent. 0 gap), first cousin once removed (grandparent, 1 gap), second cousin once removed (great-grandparent, 1 gap), and third cousin twice removed (great-great-grandparent, 2 gap).
The Two-Number Code, Decoded
That pencil-and-paper exercise reveals the system’s elegance. It counts the generations between each person and the shared ancestor, minus one. Two people who both trace to a great-grandparent are second cousins. The shared ancestor sits three generations up for each of them.
Removal numbers handle the asymmetry. When your cousin’s path to that ancestor is longer than yours, the difference becomes “once removed” or “twice removed.” Your grandmother’s first cousin shares your great-great-grandparents but stands one generation closer to them. That makes them your first cousin twice removed.
The math works backward too. Count from either person up to the shared ancestor, subtract one from the smaller number for the degree, and take the absolute difference for removal. A 1910 United States Census household listing Elias Whitfield, age 52, with six children offers a concrete test. Identify two descendants in different branches, count generations, and the relationship names itself.
Colloquial usage has muddied these definitions for decades. Many families call any distant relation a “third cousin” without counting a single generation. The pedigree chart on your wall is the corrective. It converts vague familiarity into a precise genealogical coordinate. Your next step: pull a census record from FamilySearch and map two branches of one household onto paper tonight.
Walking Sarah’s Line Back to Elias
Let’s make the count concrete. Sarah starts with herself, then climbs: her father (generation 1), grandfather (2), great-grandfather (3), and finally Elias and Ruth Whitfield at generation 4. Margaret’s branch climbs the same ladder on a parallel rung. Both share the Whitfields as their third great-grandparents.
Count the generations between each cousin and that common pair. Four steps for Sarah, four for Margaret. Equal distance means no “removed” qualifier; the shared ancestor sits three generations above both of their parents, which yields exactly “third cousin.”
Why Colloquial Usage Muddy the Waters
Nineteenth-century family Bibles often labeled anyone outside the immediate household as “cousin,” regardless of actual degree. That shorthand was social, not genealogical. A probate record from Perry County, Ohio might list “cousin Margaret” without specifying whether she was first or fourth. The term carried no precision.
That historical looseness explains why so many modern family stories insist on inaccurate labels. Your grandmother’s note about “Cousin Margaret from Ohio” may point to a genuine connection. But only a verified pedigree chart can tell you whether she was a third cousin or something more distant. Count your own generations tonight using FamilySearch’s free tree view against your grandparent’s records. The numbers will settle what memory cannot.
That archive-first logic applies just as fiercely once the tree is built. FamilySearch’s free tree model lets any registered user edit anyone’s ancestor profile. That generous design has spawned documented edit wars over disputed parentage on popular lines.
Ancestry’s private tree system solves that chaos with a tiered permission ladder: Viewer, Editor, and Manager roles. A viewer can browse your great-great-grandparents Elias and Ruth Whitfield without altering a single date. An editor can add census citations but not delete branches. The manager alone controls invites and merges.
MyHeritage matches Ancestry’s basic tri-level structure but adds an important safeguard for distant kin: merge requests require explicit confirmation from both parties. When Sarah in Ohio connects with Margaret’s granddaughter in Oregon, neither side unilaterally absorbs the other’s work. Each conflicting birth year or marriage date surfaces as a side-by-side comparison box before anything finalizes.
FamilyTreeDNA takes a different route entirely. Its family tree builder lacks granular permissions, defaulting to full visibility for any logged-in relative who shares your surname or mitochondrial DNA match list. FamilySearch occupies the most permissive end of the spectrum. Its one-world-tree philosophy means your third-cousin discovery becomes instantly editable by a stranger in Utah who never met your grandmother. That trade-off is accurate for collaboration volume, dangerous for verification integrity.
That last point is why citation transparency matters more than raw sharing power. A platform that shows you which 1900 U.S. Census enumeration district supports Margaret’s birth year gives remote relatives something concrete to audit. It beats asking them to trust a family legend scribbled in a Bible margin.
Start today by exporting your current tree to GEDCOM format from whatever platform holds it now. That portable file gives you freedom to test each permission structure against Sarah-style discoveries before committing years of research to one system.
The Platform Scorecard Nobody Publishes
That counting exercise works on paper. The harder question is where you build the tree that makes it stick. Ancestry owns the cultural mindshare. Most people start there because family members already have accounts. But subscription renewals run higher than introductory teasers. Citation workflows push users toward external spreadsheets when attaching sources inside the tree grows tedious.
FamilySearch solves the cost problem entirely at $0. Its interface shows its church-funded age, and collaboration features lag behind paid rivals. Here is the five-point comparison we assembled from user forums and current 2026 pricing:
| Criteria | Ancestry | MyHeritage | FamilySearch | GenWed |
| Price transparency (renewal rates) | Weak. Intro deals obscure true cost | Moderate. Clear tiered plans | Excellent. Free always | Moderate |
| Record depth (US vital records) | Strong | Strong for European collections | Excellent for US civil records | Growing |
| DNA integration | AncestryDNA native | MyHeritage DNA included in top tiers | No DNA testing offered | Third-party tools only |
| Tree-building ease of use | High polish, but source citation is manual inside profiles | Good, with automated record hints | Functional but dated interface | Simple, citation-first design |
Where Records Live—And Where They Don’t
That 1940 census trick works beautifully for American families. But your great-grandparents’ paper trail thins dramatically once you cross a border. Country-level record strength varies wildly, and this shapes which platform deserves your subscription.
FamilySearch’s digitized collection leans heavily on U.S. vital records and census schedules. Its International Genealogical Index covers 400 million names globally, but depth varies by region. Scandinavia sets the gold standard. Sweden’s ArkivDigital offers nearly complete parish registers from the 1600s onward, searchable with original images. Denmark and Norway follow suit through Rigsarkivet and Digitalarkivet, both free government portals that make American researchers envious of the preservation culture.
Germany is a patchwork problem. Civil registration began nationally in 1876, but earlier records live in church books scattered across dozens of regional archives. Ancestry and MyHeritage each hold roughly 300 million German records, but coverage clusters around specific provinces like Hesse or Pomerania.
| Region | Strongest Platform | Record Strength |
| United States | FamilySearch | Excellent (vital + census) |
| Scandinavia | ArkivDigital / Digitalarkivet | Near-complete parish registers |
| Germany (pre-1876) | Archion (paid) | Spotty. Archive-by-archive |
| UK & Ireland | Findmypast / GRO indexes | Very strong civil registration |
The United Kingdom fares better than Germany because centralization happened early. England’s General Register Office holds civil birth records from 1837 forward, with Findmypast’s British collection rivaling Ancestry’s for parish transcripts and probate files.
Asia-Pacific remains the frontier territory for Western researchers. Australia’s National Library Trove portal offers free access to newspapers spanning 1803—invaluable for tracking family announcements across colonies—but Chinese or Indian genealogical records rarely appear on mainstream platforms at all.
Practical move: before choosing a paid subscription, check which country collections dominate your tree’s bottleneck generation. Open FamilySearch’s free catalog page for your ancestor’s village name and see what microfilm exists. That thirty-second lookup tells you whether you need a global archive or a targeted regional service like Archion or ArkivDigital.
Why This Matters for Your Tree
That GEDCOM export is your escape hatch from every walled garden in genealogy. Ancestry’s subscription model buries its real costs behind tiered pricing, and its source citations often link to other users’ trees rather than original records—a chain of hearsay that erodes confidence with each generation it passes.
Sarah’s confirmation didn’t come from Ancestry’s shaky hints. It came from a read-only GenWed link shared with Margaret’s grandchildren, who recognized the 1940 census enumeration district and a handwriting match on Elias Whitfield’s 1892 will. The two-number system gave them the vocabulary; the transparent source-linking gave them the proof.
Transparency isn’t a luxury feature. It’s the difference between a family tree and a family story. When every matched record carries its citation visibly, collaboration becomes verification instead of blind trust. FamilySearch offers free record access, but its tree is a shared public space where edits by distant strangers can silently alter your ancestors’ details.
The generation-counting method is the same whether you count on paper or in a spreadsheet. But Sarah’s real breakthrough was not the arithmetic. It was trusting the process enough to ask living relatives for confirmation.
That two-number system will serve you on every branch of your tree. The next question is simpler than it seems: which record will you verify this week? Open FamilySearch and pull one census page for your great-grandparents’ siblings. A single name listed there might hand you your own Margaret from Ohio.
