Your family tree as clean CSV tables.

Built for machine-readability

The files follow RFC 4180: comma-separated, CRLF line endings, quotes only where needed, and a UTF-8 byte-order mark so Excel opens accented names correctly too. Every value is exactly what the GEDCOM contains — dates stay in forms like 2 JUN 1985 or ABT 1900 rather than being coerced into a locale format your pipeline would then have to guess at.

Two tables that join on IDs

individuals.csv: ID, given name, surname, sex, birth and death dates and places, occupation, father ID, mother ID, spouse IDs, and notes. families.csv: family ID, both partners (ID and name), marriage and divorce details, and the children as a list of IDs. The IDs are the GEDCOM cross-references with the @-signs stripped, so the two tables join directly — and match the IDs in the JSON export if you use both.

Want an Excel workbook instead?

For a nicer human-facing file — named worksheets, bold headers, column widths — the GEDCOM to Excel converter builds a real .xlsx from the same tables. And a CSV can come back: the CSV to GEDCOM converter turns edited rows into a valid .ged again.