GEDCOM Fix

GEDCOM Viewer

Open a GEDCOM file, search for a name, and browse that person's immediate family — parents, siblings, spouses, and children — without installing genealogy software.

Runs in your browser · nothing is uploaded

Drop your GEDCOM file here

Everything happens inside your browser — the file is never uploaded, and we never see it.

Choose a file

What this tool does

The viewer parses your file locally, builds a searchable index of every individual using their GEDCOM NAME record, and lets you jump to anyone by typing part of their name. Once you select a person, it resolves their FAMC pointer to show parents and siblings, and each FAMS pointer to show spouses and children — the same pointer structure documented in Understanding GEDCOM's Level/Tag/Value Structure.

Who this is for

Anyone who received or inherited a GEDCOM file and wants to quickly look someone up without installing desktop genealogy software, or anyone who wants to sanity-check a file's contents before importing it elsewhere.

If something looks wrong

A missing spouse or parent in the view usually points to a structural issue in the file itself, not a bug in the viewer — run the Validator to find dangling references and one-way family links with exact line numbers.

Common questions

Does this tool upload my GEDCOM file anywhere?
No. Your file is read and displayed entirely in your browser. It's never sent to our servers or stored anywhere.
What can I see for each person?
Their father and mother, siblings from the same parents, and each spouse with the children from that relationship — a one-generation-out view centered on whoever you search for. Click any name in the view to make them the new focus person and keep browsing outward.
Can I view a full tree diagram, not just one person at a time?
Not yet — this is a basic, search-first viewer, not a full pedigree chart renderer. For extracting or restructuring a large tree, see the Tree Splitter.
Why don't I see a spouse or parent I know is in the file?
This usually means the relationship is only recorded on one side of the pointer — for example, a family record lists someone as HUSB, but that person's own record has no matching FAMS pointer back. The Validator can find exactly this kind of one-way link.