Your family tree, checked, repaired and set free
Drop in a GEDCOM file from Ancestry, MyHeritage, FamilySearch, Gramps or any other program. GedConvert validates it line by line, turns it into clean spreadsheets, and hands back a repaired file — so your research is never trapped in one app again.
Drop GEDCOM files here, or click to choose
.ged / .gedcom · loading your plan…
What the checker looks for
Broken links
Pointers to people, families and sources that do not exist in the file
One-way family links
A family lists a child whose own record never points back (and the reverse)
Duplicate IDs
The same cross-reference ID used by two records, so links become ambiguous
Impossible dates
31 February, a day with no month, misspelled months, broken date ranges
Encoding trouble
ANSEL, Windows-1252 and UTF-16 files decoded properly — plus a warning when the declared encoding does not match the bytes
Missing frame
No HEAD header, no TRLR trailer — the usual signs of a truncated export
Five spreadsheets, not two
Most converters stop at people and families. Researchers work with events, sources and notes — so GedConvert exports all five tables: individuals, families, events, sources (with citation counts) and notes, as UTF-8 CSV files that open cleanly in Excel, LibreOffice and Google Sheets.
Questions
What does GedConvert do with my GEDCOM file?
It reads the file on our server, checks it against the GEDCOM rules, and shows you a report: how many individuals, families, events, sources and notes it found, and every problem it spotted, graded as error, warning or note, with the line number in your file. You can then download your data as spreadsheets (CSV files that open in Excel) and, on paid plans, a repaired GEDCOM and a version-converted GEDCOM.
What does "repaired" mean? Do you change my data?
No. The repaired file only fixes format: it is rewritten as UTF-8 with clean line endings, a complete header and normalized continuation lines, and it comes with a list of every change made. Broken links, wrong dates and other content problems are reported, never silently rewritten — that is your research, and only you should change it.
Is the 5.5.1 to 7.0 conversion complete?
It is a subset conversion, and we say so on the result page: the header version, the encoding and the continuation-line rules are converted properly, and all of your records, dates and notes are carried over. A few structures that GEDCOM 7.0 renamed or dropped may need a review in a strict 7.0 program afterwards.
My file is not UTF-8. Is that a problem?
No. GedConvert reads UTF-8, UTF-16, ANSEL (the old FamilySearch encoding, including its accented characters) and Windows-1252 files. The report tells you which encoding your file actually uses, and warns you when the encoding declared in the file header does not match the bytes — a common cause of garbled names after an export.
Why do I need an account? The file works in my program.
You do not need one to try: guests convert one file and get the report plus the individuals spreadsheet. An account adds batches, history and the rest of the exports. The real reason this tool exists is lock-in: sites and programs hold your tree in their format. A clean GEDCOM, checked and exported to plain spreadsheets, is how you keep your research yours.
How long do you keep my files?
Uploads and results are deleted automatically after 72 hours. Files are processed on our own server and are never shared. See the privacy policy for the details.