From plain rows to a linked family tree.

Any reasonable CSV works

The delimiter is detected from the file — comma, semicolon (the “CSV” many European Excel locales produce), or tab — and quoted cells, embedded line breaks, and doubled quotes are handled per the standard. Encoding is sniffed too: UTF-8 first, with a Windows-1252 fallback so older exports keep their accented names. Exports from Google Sheets, Numbers, LibreOffice, Airtable, or a database query all drop straight in, as does text pasted directly from a spreadsheet.

How the family links work

GEDCOM connects people through family records, so the converter rebuilds them from your columns. Give each person an ID, then reference those IDs in Father ID, Mother ID, and Spouse ID columns. Children who share the same two parents are gathered into one family; a spouse pair with a marriage date becomes that family's marriage event. Headers like “First name”, “Born”, or “DOB” are matched automatically, and every guess can be corrected in the mapping table before you download.

Dates

ISO dates (1985-06-02) and unambiguous day-first or month-first dates are converted to GEDCOM's 2 JUN 1985 form; genealogy-style dates like ABT 1900 or BET 1900 AND 1905 pass through untouched, and ambiguous ones (03/06/1985) are kept as written and flagged so you can fix them at the source.

Starting from an Excel workbook?

Use the Excel to GEDCOM converter instead — it reads .xlsx files directly, including Excel's internal date cells, with no save-as-CSV step. And once you have your .ged, check it in the viewer or with the validator before importing it anywhere.