How to Convert a GEDCOM File to Excel or CSV

A family tree is easy to browse and hard to scan. In a tree view you see one family at a time. In a table you see everyone at once. You can sort by birth year, filter by town, find every person with no source, and share the list with someone who has no genealogy software at all.

That is why people convert GEDCOM files to Excel or CSV. This guide explains what the conversion makes, how to do it step by step, and how to check the result so the table you trust is the table your file really supports. For background on the file itself, see what is a GEDCOM file. To convert now, the GedConvert tool on the home page reads your file and writes the tables for you.

Why CSV Comes First, Then Excel

Tools talk about CSV and Excel as if they were two different jobs. They are one job done in two steps. CSV is a plain text table: one row per record, one column per field, fields split by commas. Excel opens CSV files at once, and from there you can save as a true Excel file (.xlsx) with as many sheets as you need.

CSV is the right middle step for three reasons. First, every spreadsheet program reads it: Excel, Google Sheets, LibreOffice Calc, and Apple Numbers. Second, it is plain text, so nothing hides inside it — no macros, no formatting tricks. Third, one CSV per table keeps the shape clean. People in one file, families in another, events in a third. An Excel workbook can then hold each table as its own sheet.

Watch one detail on export: text encoding. Names with accents need UTF-8, and Excel on Windows reads UTF-8 CSV files best when the file starts with a byte order mark, often called a BOM. GedConvert writes its CSV files in UTF-8 so names arrive intact in Excel and in other tools.

What Tables a GEDCOM File Makes

A GEDCOM file is not one table. It is a set of linked records, and each record type makes its own table. Here is the full set:

The free plan on GedConvert covers the first two tables — individuals and families — plus the full validation report. Paid plans add events, sources, and notes. That split is practical, not arbitrary. The first two tables answer the common questions: who is in the tree, and how do they group? The event and source tables serve deeper work: timelines, source audits, and research planning. Plans are compared on the pricing page.

Notice what the ID columns do. The same ID, like @I14@, appears in the individuals table and in every event row for that person, and inside the family rows that list that person as a partner or child. IDs are how you join tables back together in a spreadsheet. Keep them. The urge to delete an "ugly code column" is strong, and it is the one column you must not drop.

Step by Step: From .ged to a Working Spreadsheet

1. Validate the file first. A broken link or a bad encoding becomes a wrong row. Run the file through validation and fix errors before you convert. The guide on why GEDCOM exports fail validation explains the common faults.
2. Convert the file. Upload it to the converter and download the CSV tables. Check the row counts against the report: the individuals table should hold one row per person record in the file.
3. Open the CSV in your spreadsheet program. If names with accents look wrong, do not fix them cell by cell — the file was opened with the wrong encoding. Import it again and choose UTF-8, or use a converter that writes UTF-8 with a BOM.
4. Save as a workbook. In Excel, use Save As and pick the .xlsx format. Put each table on its own sheet and name the sheets Individuals, Families, Events, Sources, Notes.
5. Freeze the header row and turn on filters. With filters on, every column becomes a question you can ask: show me births in Ohio, deaths before 1900, marriages with no source.
6. Work on a copy. Sort, filter, and mark up the copy. Keep one clean copy of the workbook as converted, so you can always go back to the true output.

What You Can Do With the Tables

The value of the tables shows up in the work they make easy. Here are the jobs researchers do most once a tree is in rows:

Find gaps. Filter the individuals table for blank death places, or the events table for events with no source link. A tree view hides gaps. A table lists them, one row each, ready to work through.

Clean duplicates. Sort individuals by name, then by birth date. People entered twice sit side by side in the sorted list, where the tree view kept them far apart. Mark the pairs in the sheet, then merge them in your genealogy program — not in the sheet, for reasons the next section gives.

Build a timeline. Sort the events table by date and filter by place. You get a plain chronology of one town, one surname, or one family line. Timelines expose errors a tree hides, like a child born two years after a parent died.

Share with family. Many relatives have no genealogy program and no wish to learn one. A spreadsheet of names and dates is something they can open, read, and correct. Send the individuals table, ask for fixes in a new column, and fold the fixes back into your main tree yourself.

Audit your sources. Join the events table to the sources table by ID, or simply scan the source column for blanks. You get a true picture of how much of your tree rests on records and how much rests on memory or on other trees.

The Limits: A Spreadsheet Is Not a Tree

Read this part before you fall in love with the tables. A spreadsheet is a view of your data, not a home for it.

Edits in the sheet do not flow back into your GEDCOM file. If you fix a date in Excel, your tree still holds the old date. The sheet is a snapshot from the moment of conversion. When the tree changes, convert again to refresh the tables.

Relationships flatten. A tree knows that a person has two parents, three partners, and nine children, all as links. A row in a table shows IDs in columns. You can read the links, but the sheet does not enforce them. Delete a row and nothing warns you that three other rows pointed to it.

Order is lost. GEDCOM files carry an order for children in a family and for some events. A sorted table destroys that order on screen. The data is safe in the file, but do not treat the sheet's row order as a fact.

So the rule is simple. Do analysis in the spreadsheet. Do edits in your genealogy program, then re-export and convert again. That loop keeps one source of truth — the tree — and makes the tables a tool you can trust because you can rebuild them at will.

Common Problems and Fixes

Commas inside names or places split a field. A place like "Smithfield, Ohio" holds a comma. In a CSV file, fields with commas must be wrapped in quotes, and a good converter does this for you. If your columns shift out of line, the file was written without quoting. Use a converter that quotes fields per the CSV rules, or choose a semicolon separator if your spreadsheet locale expects one.

Dates sort in the wrong order. Spreadsheet programs guess at date formats. GEDCOM writes dates like 12 MAR 1904, which some programs read as text. Text sorts by letters, not by time. If sorting matters, add a helper column with the year alone, taken from the date text, and sort by that. Or filter by year text contains. Do not retype dates by hand; you will add errors faster than you fix them.

Leading zeros and long IDs change shape. Excel likes to turn codes into numbers and dates. The @I14@ form is safe because of the @ signs, but plain numeric IDs and some place codes can be reshaped. If a column looks wrong, set its format to Text before you paste or import more data.

The file is too big to open comfortably. A tree with tens of thousands of people makes a fine CSV — text is small — but the events table can reach hundreds of thousands of rows. Excel handles that, though filters get slow. Split the work: convert, then filter and save smaller working sheets per family line or per town.

A Note on Privacy

A spreadsheet of your tree is easy to copy, email, and post. That ease is a risk. Your file likely holds birth dates of living people, and a CSV strips away the privacy guards your genealogy program applies. Before you share a table, filter out living people or remove their dates. GedConvert converts what your file holds; the choice of what to share stays with you. The backup guide covers the wider habit of keeping copies safe: how to back up your family tree.

Frequently Asked Questions

Can Excel open a .ged file directly? No. Excel does not read the GEDCOM form. Convert to CSV first, then open the CSV in Excel and save it as a workbook if you want sheets and formatting.

Will I lose data in the conversion? A table holds the fields that fit in columns. Long notes become a notes table. Media links appear as paths or links, not as images in cells. Nothing is deleted from your GEDCOM file; the tables are a new output, and you keep the original.

How many people can the tables hold? As many as your file holds. The practical limit is your spreadsheet program. Excel allows just over a million rows per sheet, far more than most trees need.

Can I convert the spreadsheet back into a GEDCOM file? Not cleanly with a plain save. The links and structure of a GEDCOM file do not survive as spreadsheet columns alone. Keep your GEDCOM file as the master copy. Treat the tables as output only.

Why do I need the events table? Can't I get dates from the individuals table? The individuals table holds the headline dates: birth and death. The events table holds the rest — census, residence, occupation, military service, and every dated fact for families too. Research questions live in the full event list.

What separator should I choose, comma or semicolon? Comma is the standard and works in most cases. If your computer uses a locale where commas are decimal marks, Excel may expect semicolons. Pick the one your spreadsheet opens cleanly, and state your choice when you share the file.

References

• https://gedcom.io/ — The home of the GEDCOM standard, with the 7.0 and 5.5.1 specs that define the records these tables come from.
• https://www.archives.gov/research/genealogy — The U.S. National Archives guide to genealogy research and records.
• https://www.loc.gov/ — The Library of Congress, a major source of census, local history, and family history material.