← All articles
10 July 2026 · Kinfoly · Updated 5 November 2026

What Is a GEDCOM File? Inside the .ged Format, Line by Line

Someone emails you a file called family.ged, or a genealogy site offers to "export your tree as GEDCOM" and you wonder what exactly you would be taking away with you.

A .ged file is not exotic and it is not locked. It is a plain text file with a forty-year-old structure, and a few minutes with its first lines tell you most of what there is to know: what it holds, what it quietly leaves behind, and why the same file can look perfect in one program and broken in another.

A .ged file turning into a family tree inside a browser window

What is a GEDCOM file?

GEDCOM — GEnealogical Data COMmunication — is the format family trees travel in. It was created by the Family History Department of the Church of Jesus Christ of Latter-day Saints in 1984, and it is still the one thing every genealogy program agrees on. Ancestry, MyHeritage, FamilySearch, Gramps, Family Tree Maker and RootsMagic all export to it, and all of them read it back.

That makes a .ged file the one copy of your research that does not belong to a company. A subscription can lapse and a website can close; the file keeps working.

What is inside a .ged file

Every line is a level number, sometimes a record id, a tag, and a value. Level 0 starts a record; a higher number means "this describes the line above me".

0 @I12@ INDI
1 NAME James /Carter/
1 SEX M
1 BIRT
2 DATE 14 MAR 1921
2 PLAC Leeds, England
1 FAMS @F4@

Four of those seven lines are worth knowing by sight:

Seven lines of a GEDCOM file with the record id, the tag, the nested date and the family pointer called out

That is one person, and the rest of a typical file is more of the same: thousands of short lines, each one hanging off the line above it.

The records in a GEDCOM file

A file is a run of records, each starting at level 0. Most files use only a handful of kinds:

Record What it holds
HEAD The header: the program that wrote the file, the GEDCOM version, the character set
INDI One person: names, sex, events, and pointers to their families
FAM One couple or single parent, and their children
SOUR A source — a census, a parish register, a book — that facts can cite
REPO The archive or library that holds a source
NOTE A note that several records share (SNOTE in GEDCOM 7.0)
OBJE A photo or document — as a path to a file, not the file itself
SUBM Who submitted the file
TRLR The last line of the file

A person never names their parents directly. They point at the family they were a child in (FAMC) and the families they made (FAMS), and each FAM record lists its HUSB, WIFE and CHIL. That double bookkeeping is how a family tree survives being written down as a flat list of lines — and why a file edited by hand so easily ends up with a child whose family does not list them back.

The tags you will meet most

Tags are short English abbreviations, always in capitals. A dozen of them carry most trees:

Tag Meaning
NAME A name, with the surname between slashes: Mary /Smith/
SEX M, F, or U for unknown
BIRT, CHR, BAPM Birth, christening, baptism
DEAT, BURI Death, burial
MARR, DIV Marriage, divorce — inside a FAM record
RESI, OCCU, CENS Residence, occupation, a census entry
IMMI, EMIG, NATU Immigration, emigration, naturalization
DATE, PLAC When and where, under any of the events above
SOUR, NOTE The source a fact rests on, and a note about it

Programs may add tags of their own, which start with an underscore — _MARNM for a married name, _UID for an id. Another program is free to ignore them, and most do.

How dates are written in GEDCOM

A full date is day, three-letter month and year: 14 MAR 1921. A month and year, or a year alone, is fine too. The useful part is the words in front:

  • ABT 1850, EST 1850, CAL 1850 — about, estimated, calculated from something else
  • BEF 1850, AFT 1850 — before, after
  • BET 1840 AND 1845 — some time in that range
  • FROM 1840 TO 1845 — a period that lasted that long, such as a residence
  • INT 1850 (the year of the flood) — a date read from a phrase, with the phrase kept

Older files may also carry a double year such as 1750/51, from before England changed its calendar. Keep these words when you type dates: they are what lets a program, or the GEDCOM checker, tell an approximate year from a mistake.

What a GEDCOM file does not contain

Your photos. This is the one that catches people out. A .ged records the path to a picture on the computer that exported it, not the picture itself. Move the file to another machine and every image is a dead reference. If you are leaving a site you have been paying for, download the media gallery separately — the GEDCOM will not bring it with it.

It also loses whatever the program it came from kept outside the standard: coloured labels, custom fact types, hints and matches. Those are features of that site, not of your family.

GEDCOM 5.5.1 or 7.0 — which should I export?

Two versions matter in 2026. 5.5.1 is the one almost everything writes, and the safest choice when you do not know what will read it. 7.0, published by FamilySearch on 19 May 2021, tidies up the dark corners of the old specification, requires UTF-8 so accented names survive the trip, and can carry photos in a .gdz package — a zip with the GEDCOM inside it.

If a program offers you both and you are moving between modern tools, take 7.0. If you are handing the file to a relative who may open it in something from 2009, take 5.5.1.

Why a file sometimes opens as gibberish

If Müller arrives as Müller, or accented names come through as question marks, the file was written in an older character set — GEDCOM 5.5 defaulted to ANSEL, and Windows programs often wrote ANSI — and whatever opened it assumed UTF-8. The fix is not to retype anything: open it in something that reads the declaration in the header and falls back, or re-export from the original program as GEDCOM 7.0, which is UTF-8 only.

What to open it with

To see the family rather than the lines, drop the file on the free GEDCOM viewer: it runs in the browser and nothing is uploaded. Any text editor shows the raw lines, which is enough to read the header. A genealogy program imports it when you mean to keep researching. And to sort the people in a spreadsheet, the GEDCOM to CSV and Excel converter writes one row per person.

Where to get your file in the first place

Every major site exports one, usually from the tree's settings: Ancestry has Tree Settings → Export tree, MyHeritage Manage trees → Export to GEDCOM, and desktop programs keep it under File → Export. Only the owner of a tree can export it, so if the tree is a relative's, the download is theirs to make.

Common questions

Is it safe to share a GEDCOM file?

It holds everything you have recorded, living relatives included: names, birthdays, places. Most genealogy programs can leave out or privatize living people when they export — use that before sending a file outside the family or posting it online.

What is the difference between .ged and .gdz?

A .ged is the text file itself. A .gdz is a GEDZIP package from GEDCOM 7.0: a zip holding the .ged together with the photos and documents it refers to. Unzip it to get at the .ged.

Can I edit a GEDCOM file by hand?

You can — it is plain text — but people and families point at each other by id, so a deleted line easily leaves a pointer to nobody. Make the change in a genealogy program and export the file again.


A viewer is read-only on purpose. When you find the wrong date, the missing sibling or the branch that stops too early, import the same file into a free Kinfoly account and carry on from where the file left off — edit people and relationships, add events and sources, and keep the tree private by default.

Next: how to read a big family tree once the file turns out to hold four hundred people, and how to print one as a poster when you want it on a wall rather than a screen.

Open your .ged file now
Drop it on the free viewer — it is read on your own device, nothing is uploaded, and there is no account to create.