Interpreting Cousin Match Centimorgans
A DNA match shows 214 cM and labels the person a possible third to fourth cousin. That sounds precise until you try to build an actual family tree from it. This is where interpreting cousin match centimorgans stops being a technical exercise and becomes a research decision. The number matters, but what you do next matters more.
For many family historians, especially those working through missing records, name changes, migration, or the 1870 brick wall, centimorgans are one of the few clues that can still move the case forward. They can point you toward the right generation, the right branch, and sometimes the right county. But they do not name the ancestor for you. They never work alone.
What centimorgans really tell you
A centimorgan, usually written as cM, is a unit used to measure shared DNA. In practical genealogy terms, it estimates how much DNA you and another person inherited from a common ancestor. Higher numbers usually mean a closer relationship. Lower numbers usually mean a more distant one.
Usually is the key word.
DNA inheritance is uneven. One second cousin may share much more DNA with you than another second cousin from the same family line. Two people with the same total cM can fit very different relationship categories. That is why experienced researchers do not treat one cM total as one fixed answer. They treat it as a range of possibilities that has to be tested against age, geography, paper records, and shared matches.
If you remember one thing, remember this: centimorgans narrow the field. They do not finish the job.
Interpreting cousin match centimorgans by range
Most cousin-match questions start with total shared cM. The broad pattern is simple enough to use right away.
If a match shares under 90 cM, you are usually looking at a more distant cousin relationship, often in the fourth cousin range or farther, though some third cousins can fall there. These matches can still be useful, especially when several of them cluster around the same ancestral line.
From roughly 90 to 230 cM, you are often in the third cousin territory, with overlap into second cousin once removed, half relationships, and more distant fourth cousin scenarios. This is a productive range because the common ancestors are often recent enough to document, but not so close that the answer is obvious.
From roughly 230 to 620 cM, the possibilities usually include second cousins, first cousins twice removed, half first cousins once removed, and similar relationships. This range often gives you enough signal to build real hypotheses quickly, especially if the person has a tree or strong shared-match clustering.
Above that, the relationship is generally closer, though endogamy, pedigree collapse, and half relationships can complicate the picture fast.
Those ranges are useful, but they are still just ranges. What matters is how you reduce ambiguity.
The total cM is only the first filter
When two people share 176 cM, that number does not say, "You are definitely third cousins." It says, "Here are the relationship categories worth testing first." Your job is to decide which category actually fits the family evidence.
That means looking at three things right away: the match's age relative to yours, the pattern of shared matches, and where each family was living in the generations where the common ancestor likely lived. If one possible relationship would require a person to have a child at age nine, you can discard it. If shared matches all point to your maternal side in central Alabama, that matters more than the platform's generic cousin label.
Why cousin labels are often misleading
Consumer DNA platforms use relationship labels because people expect them. The problem is that labels like "3rd-4th cousin" can sound firmer than they are. They are estimates, not proof.
Half relationships can distort the picture. So can double relationships, where cousins are related through more than one line. Endogamy can raise shared cM totals because the same community intermarried over generations. This is especially relevant in some Acadian, Ashkenazi Jewish, Appalachian, Indigenous, island, and small rural populations, but it can appear anywhere a community stayed closely connected over time.
For African American family history, another complication is record disruption. A DNA match may fit neatly on paper in theory, but the records needed to confirm the line may sit scattered across plantation papers, county probate files, Freedmen's Bureau labor contracts, bank records, cohabitation registers, or federal pension files. In that context, centimorgans are not the answer. They are the pressure point that tells you where to search next.
How to use centimorgans to find the right ancestor
Start by asking a better question. Not "What exact cousin is this?" but "What generation likely holds the shared ancestor?"
That shift matters because research happens by generation. If your match likely descends from a shared set of great-great-grandparents, you can focus on that level of the tree. If the cM range suggests the ancestor is probably one generation closer, your search target changes.
Once you have the likely generation, build sideways before you build backward. Look at siblings, not just direct ancestors. Many DNA breakthroughs come from collateral lines because one descendant kept better records, stayed in the same county, or appears in an obituary that names relatives others left unnamed.
Then use shared matches to identify the branch. If you and the match both share DNA with several descendants of your maternal grandmother's line, that tells you where not to waste time. The branch is probably there. If the cluster is mixed or unclear, you may be dealing with endogamy, multiple shared lines, or simply not enough tested relatives yet.
A practical example
Say you share 142 cM with a match. The platform suggests a third cousin type relationship. The match is about your age, and your shared matches connect to descendants of a family from Wilkinson County, Mississippi, then later appear in Louisiana after the Civil War.
That does not prove the relationship. But it gives you a working hypothesis: your common ancestors may sit around the great-great-grandparent level, and the research corridor likely runs through that county migration pattern. Now the next step is not guessing harder. The next step is checking censuses, probate, labor contracts, marriage records, and military pension records tied to that place and generation.
This is where a stronger workflow changes everything. Instead of staring at a cM chart, you move from DNA to archive strategy.
Interpreting cousin match centimorgans when the records are thin
Some families have neat paper trails. Many do not. If your ancestors were formerly enslaved, poor, displaced, or moving across state lines after the war, the records may appear late, fragmented, or under somebody else's surname.
In those cases, DNA has more weight, but it also needs more discipline. One match rarely breaks the wall. A cluster of matches can.
Look for repeated surnames, repeated counties, and repeated migration routes among matches in the same cM neighborhood. A single 58 cM match with no tree may not help much on its own. Five matches from 40 to 110 cM, all tracing to the same county or associated white enslaver family, can point to a real lead. Patterns beat isolated numbers.
This is one place where tools that translate DNA into archive direction are worth more than tools that simply rank your matches. The real value is not another chart. It is knowing which county deeds, Freedmen's Bureau field office, or NARA microfilm series you should pull next. That is the difference between information and momentum.
Common mistakes that slow people down
The biggest mistake is taking the platform's cousin label literally. The second is ignoring half relationships. The third is trying to solve the match without building out the match's tree.
Another common problem is treating low-cM matches as useless. Some are noise, yes. Some are gold, especially when they triangulate a hard-to-document line. The trade-off is time. Chasing every 23 cM match is rarely efficient, but ignoring a cluster of low-cM matches from the same county can cost you the breakthrough.
People also overfocus on direct ancestors. Your answer may live in a sister's death certificate, a brother's pension file, or a niece's marriage record. DNA often points to a family network before it points to one named individual.
What to do next with a cousin match
When you are interpreting cousin match centimorgans, the smartest next step is usually simple. Estimate the likely generation of the shared ancestor, identify whether the match sits on your maternal or paternal side, study shared-match clusters, and map the likely counties involved. Then go to the records for that place and generation.
If the number is moderate and the match has a usable tree, build that tree out. If the tree is missing, research the match through public records and family connections. If the records are weak, focus on clusters rather than single matches. And if the evidence points to a specific county after the war, prioritize the federal and local collections most likely to name Black families in transition.
At The 1870 Project, that is the standard we care about - not just telling you that 142 cM could mean several things, but helping you turn that number into the next search, the right archive, and the record set most likely to name your people.
Your DNA match is not a verdict. It is a lead. Treat the cM total as the start of the trail, then follow the families, the counties, and the records until the story stops being possible and starts being proven.



