How to Fix Broken Family Links in a GEDCOM File
A broken family link means a GEDCOM pointer only goes one way. Here's how that happens, how to spot it, and how to fix it in your file without losing data.
A family link in GEDCOM is supposed to work in both directions: a person's record points to a family they belong to, and that family's record points back to them. When only one side of that pointer exists, the link is "broken" — not missing entirely, just incomplete. This is one of the most common structural problems in real-world GEDCOM files, and it's usually invisible until something tries to read the file and gets confused.
How the two-way link is supposed to work
Every person who's a child in a family has a FAMC (family-as-child) pointer to that family's record, like 1 FAMC @F12@. The family record at @F12@ is supposed to list that same person under a CHIL line. The same pattern applies to spouses: a person's FAMS (family-as-spouse) pointer should be matched by a HUSB or WIFE line in the family record pointing back to them. When both sides agree, the relationship is unambiguous no matter which record a piece of software reads first.
How it ends up one-way
Broken links almost never happen on purpose. The most common cause is manual editing in a text editor or an older desktop program: someone adds a FAMC line to a person's record to fix a parent relationship, but doesn't also add the corresponding CHIL line to the family record — or does the reverse. Partial exports are another frequent cause — if a piece of software exports a family record but skips one of the individuals it references (or exports individuals but truncates a family), the surviving side of the pointer has nothing to match against. Merges between two trees can also produce this: a person gets merged into an existing family, but the merge logic updates one side of the relationship and not the other.
Why it matters more than it looks
A one-way link doesn't corrupt the file the way a dangling reference does — every record involved still technically exists. But it means the relationship is only visible if you happen to read the file starting from the side that has the pointer. A pedigree viewer that builds a tree by walking FAMC/FAMS pointers from a specific person, for example, can end up showing that person's siblings but not their parents, or the reverse, depending on which side of the family the break is on. That inconsistency is exactly what makes these bugs hard to notice through normal use — the file looks fine until you look at the specific person affected.
Finding broken links in your file
Scanning for these by eye in a large file isn't realistic — you'd need to manually cross-reference every FAMC/FAMS line against every CHIL/HUSB/WIFE line. The Validator does exactly this check automatically: it flags every one-way link as a warning, names the two records involved, and gives you the line number in your file where the incomplete pointer sits.
Fixing a broken link
Once you know which side is missing, the fix is a single line. If a person has 1 FAMC @F12@ but family @F12@ has no matching CHIL line for them, add 1 CHIL @I7@ (using that person's actual ID) to the family record. If a spouse's FAMS pointer isn't matched by a HUSB or WIFE line in the family, add the missing line the same way. Always add the missing side rather than deleting the existing one — removing a pointer erases a relationship the file otherwise correctly recorded, which is a worse outcome than the inconsistency you started with.
If you're working from a file you didn't create yourself — inherited from a relative, or exported from software you no longer have access to — see Cleaning Up a GEDCOM Inherited From a Relative for a broader workflow that covers this alongside the other issues that tend to show up in older files.
Do it now
Keep reading
Common questions
- Is a broken family link the same as a dangling reference?
- No, though they're related. A dangling reference points to a record ID that doesn't exist at all. A broken (one-way) link points to a record that does exist, but that record doesn't point back — the relationship is only recorded from one side.
- Will a broken link definitely cause a problem when I import the file?
- It depends on the software. Some import tools silently ignore the incomplete side of the relationship, some flag it, and a few reject the file outright. Since behavior isn't consistent across platforms, it's safer to fix broken links before importing rather than hope the destination handles them gracefully.
- Can I fix this without editing raw GEDCOM text?
- For a handful of issues, yes — most desktop genealogy software lets you re-link a child to a family or a spouse to a marriage through its normal UI, which regenerates the pointers correctly on export. For dozens of issues across a large file, editing the raw text with a validator report open next to it is usually faster.