How to Open a GEDCOM File (and Why It Sometimes Fails)
A GEDCOM file lands in your inbox or your downloads folder. You double-click it. Your computer shrugs. No app claims it, or a text editor opens and shows a wall of codes, or a family history program opens it and half the people are gone.
All three results are common, and none of them means the file is lost. A GEDCOM file is plain text in a set form. You just need the right way to open it for the job you want to do. This guide walks through each way, from a quick look to a full import. If you are not sure what the file is at all, read what is a GEDCOM file first. When you want the file checked and turned into clean tables, the GedConvert tool on the home page reads it in your browser session and reports what it finds.
First, Know What "Open" Means for You
People say "open" and mean three different jobs. The best method depends on which job is yours.
| Your goal | Best way to open the file | What you get |
|---|---|---|
| Take a quick look inside | A text editor | The raw lines, names, and dates |
| See the tree as a tree | A genealogy program or viewer | Charts, person pages, family groups |
| Work with the data in tables | A converter to CSV or Excel | One row per person, family, or event |
| Check the file for faults | A validator | A list of errors with line numbers |
| Move the tree to a new service | Import on the new service | Your tree rebuilt inside that service |
A text editor will always "work," but it only shows you raw data. A genealogy program shows you a tree, but it may hide faults or drop parts it does not understand. Pick the method that fits the goal, and do not judge the file by the wrong tool.
Way 1: Open It in a Text Editor
Every computer has a text editor. On Windows that is Notepad. On a Mac it is TextEdit. Right-click the file, choose "Open with," and pick the editor. Do not let a word processor open it as a formatted document; word processors can change the text when they save.
You will see lines like these:
| Line part | Example | What it tells you |
|---|---|---|
| Level | 0, 1, 2 | How deep the line sits in the record |
| ID | @I14@ | The code other lines point to |
| Tag | NAME, BIRT, DATE | What kind of data the line holds |
| Value | Mary /Smith/ | The data itself |
Scroll and search. Use Find to search for a surname. Look at the top lines for the CHAR tag, which states the encoding, and at the last line for TRLR, which marks a complete file. A text editor is the best first check. It proves the file has real content and shows you its rough size and shape in under a minute.
What a text editor cannot do is show the tree. Ten thousand lines of text do not draw a chart. For that, you need a program that reads the form.
Way 2: Open It in a Genealogy Program
Desktop programs read GEDCOM files by import, not by double-click. That one fact causes most of the confusion. The steps are near the same in most programs:
- Open the program and make a new, empty tree or file.
- Find the import command. It is often under File, then Import, then GEDCOM.
- Pick your file and start the import.
- Read the import log if the program shows one. It lists what was skipped or changed.
- Check three things at once: the person count, one person you know well, and one photo or note you expect to see.
Free and paid programs both do this. Gramps is free and runs on Windows, Mac, and Linux. RootsMagic and Family Tree Maker are paid desktop tools. Free web viewers also exist if you only want to look and not edit.
Always import into a new, empty file. Never import a new tree on top of an old one unless you mean to merge them. A merge is hard to undo. A fresh import costs you nothing and can be deleted in one click if it goes wrong.
Way 3: Open It on a Family History Website
The big sites accept GEDCOM uploads. Ancestry, MyHeritage, and FamilySearch each have an upload path. You make a new tree, choose the upload or import option, and give it the file. The site builds a tree from it.
Two points matter here. First, an upload makes a new tree. It does not add people to a tree you already have. If you upload twice, you get two trees. Second, hints and record matches do not travel with the file. The site will offer you fresh hints for the new tree, and you will need to review them again.
If your goal is to leave a site, not join one, the flow runs the other way. You export from the old site, then import the file to the new home. The guide on why genealogy data gets locked in explains how to keep control of that move.
Way 4: Turn It Into a Spreadsheet
Sometimes you do not want a tree at all. You want a list. A list of all births in one town. A list of everyone with no source. A list you can sort, filter, and share with a cousin who uses Excel.
That is a conversion job, not an import job. The file is read once and written out as tables: one row per person, one row per family, and on paid plans one row per event, source, and note. The guide on how to convert a GEDCOM file to Excel walks through the steps and the checks to run on the result. The free plan on GedConvert covers the validation report plus the individual and family tables, which is enough for most quick lists.
Why a GEDCOM File Sometimes Fails to Open
Now for the hard part. A file can be a real GEDCOM file and still fail. Here are the faults that cause most failures, in the order you are most likely to meet them.
The File Is Not a GEDCOM File at All
A file can carry a .ged name and hold something else. It may be a zip file that was renamed. It may be a backup file from one program, which only that program can read. It may be an HTML page saved with the wrong name after a failed download.
How to tell: open it in a text editor. A real GEDCOM file starts with the line "0 HEAD" and ends with "0 TRLR." If the first lines say PK, or show HTML tags, or look like random symbols, the file is not GEDCOM text. Fix the download or ask the sender for a true export.
The File Was Cut Short
Email, downloads, and old disks can cut a file. If the last line is not "0 TRLR," the file is not complete. A program may refuse it, or worse, import it and drop the people near the end in silence. Get a fresh export. A cut file cannot be made whole by any tool, because the missing lines are simply not there.
The Encoding Is Wrong
The HEAD block states the encoding in the CHAR line. Old files often say ANSEL. New files say UTF-8. If the file states one encoding but was saved in another, names with accents or special letters turn into garbled text, and some programs refuse the file outright. This fault is so common that it has its own guide: GEDCOM encoding errors explained.
The File Uses a Form the Program Does Not Know
A GEDCOM 7.0 file opened in an old program can fail or lose data, because 7.0 changed some rules and tags. The reverse is safer: new programs read 5.5.1 files well. If an old program rejects a new file, convert the file down to 5.5.1 first. Version conversion is a paid feature on GedConvert, listed on the pricing page.
The File Has Broken Links or Bad Lines
One wrong level number can break a whole record. A link that points to an ID that is not in the file breaks the tree at that point. Some programs stop at the first bad line. Others skip it and keep going, so the tree opens but is quietly missing people. A validation report finds these faults before you import, which is why the next section matters.
Check the File Before You Import It
Import is the worst time to learn that a file is faulty. The program makes choices you cannot see, and the log, if there is one, is easy to miss. Check first, import second. A two-minute check saves hours of repair later.
Run the file through a validator. A good report lists each problem with its line number and tells you how bad it is. Errors block a clean import. Warnings mark data that may change shape. Notes mark things worth a look. The article on why GEDCOM exports fail validation goes through the common errors one by one and shows how each one is fixed.
On GedConvert, the free plan gives you that full report plus the individual and family CSV tables. Paid plans add the repaired file. The repair fixes format faults only — encoding, line ends, header fields — and never changes your facts. What it will not do is invent missing people or guess at a cut file. No honest tool can.
A Short Checklist for a Safe First Open
- Make a copy of the file. Work on the copy, keep the first file untouched.
- Open the copy in a text editor. Check for 0 HEAD at the top and 0 TRLR at the end.
- Note the CHAR line and the version line. You will need them if anything looks garbled.
- Run a validation check and read the error list.
- Import into a new, empty tree. Read the import log.
- Compare counts: people and families in the report versus people and families in the new tree.
- Spot-check one person you know well, with dates, places, and a source.
If the counts match and the spot check passes, the file opened in full. If they do not, the report and the log together tell you where the loss happened.
Frequently Asked Questions
Why does my computer say it has no app for this file? Most computers ship with no genealogy program installed, so no app claims the .ged type. That says nothing about the file. Use a text editor, a viewer, or an online tool.
Can I open a GEDCOM file in Excel? Not directly. Excel does not read the GEDCOM form. Convert the file to CSV first, then open the CSV in Excel. Each table becomes one sheet with one row per record.
Is it safe to upload my file to an online tool? Read the tool's terms before you upload. A family file holds data about living people. Choose a tool that states how files are handled and deleted, and avoid any tool that keeps or shares your file without a clear reason.
The tree opened but some people are missing. What happened? The most common causes are a cut file, broken links, or records the program dropped on import. Compare the counts in a validation report with the counts in the program to find where the loss is.
Can I open a GEDCOM file on a phone or tablet? Yes. Some apps import GEDCOM files, and web tools run in the browser. For a quick look, a web viewer or a CSV table is often easier on a small screen than a desktop program.
The names show strange symbols. Is the file ruined? Almost never. Garbled names are an encoding fault. The data is still there; it was read with the wrong character map. A repair that reads the file with the right map and saves it as UTF-8 fixes most cases.
References
- https://gedcom.io/ — The home of the GEDCOM standard, with the 7.0 and 5.5.1 specs that define the file form.
- 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.