What is a GEDCOM file
A plain text format for exchanging family trees. Learn how its records and pointers work, and what to check before another program imports it.
Beginner · 10 minutes · checked 6 Sep 2026
Choose the task that matches your file. Keep your original GEDCOM, review the proposed changes, and save each output under a new name. The tools read files in your browser. Optional AI actions send the text described beside their buttons after you choose to send it.
Open an unfamiliar file, understand its contents, or check it before an import.
A plain text format for exchanging family trees. Learn how its records and pointers work, and what to check before another program imports it.
Beginner · 10 minutes · checked 6 Sep 2026
Someone emailed you a .ged file. Open it as people, families and a pedigree in a browser tab, with nothing uploaded and nothing installed.
Beginner · 10 minutes · checked 6 Sep 2026
Start with a local preflight report, review structure, links, media and privacy, then check the exact file you plan to import.
Beginner · 30 minutes · checked 6 Sep 2026
Someone sent you a .ged and you have no program to open it. Read the version, the producer, the charset, the counts, the custom tags and the people, in order.
Beginner · 20 minutes · checked 6 Sep 2026
Recover a file, interpret an error, or repair names that display with the wrong characters.
Inspect an import failure, review structural recovery and its loss report, then validate the output before a test import. Keep the original export.
Beginner · 15 minutes · checked 6 Sep 2026
Müller reads as Müller, or as M?ller. Compare charset detection and proposed corrections, preserve the original, and check the UTF-8 output.
Beginner · 15 minutes · checked 6 Sep 2026
Use an import error as a starting point. Check the file's structure, encoding and pointers before choosing a repair, and review what recovery changes.
Beginner · 15 minutes · checked 6 Sep 2026
Your file says 1 CHAR ANSEL and the accents came out as separate marks. ANSEL puts the accent before the letter, and Unicode puts it after.
Intermediate · 15 minutes · checked 6 Sep 2026
Two records, one person, or two people who share a name.
Review duplicate candidates and their evidence, merge confirmed pairs, and export the decisions and undo data. Keep a pre-merge backup.
Intermediate · 30 minutes · checked 6 Sep 2026
Review same-named siblings without merging them on shared parents alone. Check the dates, sources and limits of the necronym heuristic.
Advanced · 25 minutes · checked 6 Sep 2026
Restore a merge from its exported inverse when the data survives and still matches. Check recovery limits, preserve backups, and validate the restored records.
Intermediate · 15 minutes · checked 6 Sep 2026
Trace a broken relationship or an ambiguous date to its record before changing it.
Find missing and wrong-type pointer targets, review delete, repoint and placeholder options, then check reciprocal family links in the repaired output.
Intermediate · 20 minutes · checked 6 Sep 2026
Check numeric date order, calendar conversion and chronology findings. Review ambiguous readings against records before changing dates in your export.
Intermediate · 20 minutes · checked 6 Sep 2026
Organize the evidence you have and plan searches for what your file does not yet document.
Recognize supported archive identifiers, review source-record proposals, and preserve the original citation wording without treating a parsed reference as proof.
Advanced · 30 minutes · checked 6 Sep 2026
Find gaps in your GEDCOM, review archive suggestions, and save a research plan. Use optional AI ordering without treating suggestions as evidence.
Intermediate · 20 minutes · checked 6 Sep 2026
Check the destination's accepted version and inspect conversion warnings before importing.
Compare version mappings and unrepresentable structures before converting. Review extension or drop choices, validate the output and keep the original.
Intermediate · 20 minutes · checked 6 Sep 2026
The checked date records our review against the GEDCOM Tools implementation. Screenshots use public test files, so your counts and names will differ. Destination services change their import behavior; test a copy before replacing a tree you use.
A clean file check cannot prove a family relationship. Compare identity changes with source records, inspect privacy findings before sharing, and keep reports with the exact file you checked.