GEDCOM, short for Genealogical Data Communication, is a standard for exchanging genealogical information between computer programs. It defines a text-based representation of people, family relationships, life events, source citations, notes, and related records. Developed by the Church of Jesus Christ of Latter-day Saints and maintained through FamilySearch, GEDCOM enables family-history information to move between applications with different internal databases. It is principally an interchange format, not a complete research methodology, a database system, or a guarantee that every feature will transfer unchanged.
Purpose and scope
Genealogy programs organize information in different ways. One application may store birth details in a dedicated table, while another represents them as general events. GEDCOM provides a shared vocabulary and structure through which these applications can export and import information.
Common uses include:
- Moving a family tree between desktop applications or online services.
- Sharing selected research with other genealogists.
- Providing a software-independent copy of core family-history data.
- Transferring relationships, documentary references, notes, and links to media.
Its central benefit is interoperability, but support varies by application and version. A program may recognize the basic people and relationships in a file while ignoring specialized fields or interpreting them differently.
GEDCOM can contribute to data portability, but an exported file is not necessarily a complete backup of the originating application. Interface settings, research tasks, proprietary annotations, and externally stored images may not be included.
Origins and versions
GEDCOM emerged in the 1980s as part of efforts to exchange computerized family-history information. Successive versions expanded and clarified its record structures and genealogical vocabulary.
Several versions are especially significant:
| Version | Significance |
|---|---|
| 5.5 | Published in 1996; became a widely implemented basis for genealogical data exchange. |
| 5.5.1 | Dated 1999; added and revised features, including support for UTF-8, and became widely used by genealogy software. |
| 7.0 | Released in 2021 as FamilySearch GEDCOM 7; modernized the specification, standardized UTF-8 encoding, clarified structures, and introduced standardized packaging for accompanying files. |
Version numbers matter because the same-looking file may contain structures or values that an older reader does not support. A file identifies its GEDCOM version in its header; that declaration is separate from the name and version of the application that created it.
GEDCOM should also be distinguished from GEDCOM X, a separate genealogical data model and family of specifications. GEDCOM X is not simply another name for a GEDCOM 7 text file.
File structure and syntax
An ordinary GEDCOM file is a line-oriented text document, commonly using the .ged extension. Unlike XML or JSON, it represents nesting through numerical levels at the beginning of lines.
A line generally contains:
- A level number.
- An optional cross-reference identifier.
- A tag identifying the kind of information.
- An optional value or reference.
The exact permitted syntax depends on the version. A typical line is:
1 NAME Ada /Morgan/
Here, 1 is the nesting level, NAME identifies a personal name, and the remainder is its value. In this conventional GEDCOM name representation, slashes delimit the surname.
Level-zero lines begin top-level records. Higher-numbered lines belong to the preceding enclosing structure. Thus, level-two date and place lines can qualify a level-one birth event.
The nesting resembles a tree, but cross-references connect separate records. Taken together, these references describe a network of people, families, sources, and other entities rather than a single simple family tree.
Example
The following fragment illustrates structures used in GEDCOM 5.5.1-style files. It is not a complete exchange file:
0 @I1@ INDI
1 NAME Ada /Morgan/
1 BIRT
2 DATE 12 MAR 1900
2 PLAC York, England
1 FAMS @F1@
0 @I2@ INDI
1 NAME Ellis /Taylor/
1 FAMS @F1@
0 @I3@ INDI
1 NAME Robin /Morgan/
1 FAMC @F1@
0 @F1@ FAM
1 HUSB @I1@
1 WIFE @I2@
1 CHIL @I3@
INDI introduces an individual record, and FAM introduces a family record. Identifiers such as @I1@ and @F1@ allow records to refer to one another. FAMS links an individual to a family in which that individual occupies a spouse or parent position; FAMC links an individual to a family as a child.
These identifiers normally function within the file. They are not inherently permanent, globally unique identifiers for real people.
Complete files also contain a header and a terminating TRLR record. The header supplies metadata such as the format version and information about the producing application.
Genealogical information model
Individuals and families
Individual records can contain names, events, attributes, notes, citations, and relationships. Multiple names or multiple instances of an event can be represented where the specification permits them.
Family records connect partners or parents with children. Historically named tags such as HUSB and WIFE reflect the format’s origins. Their interpretation and the representation of diverse family arrangements depend on the specification version and application behavior.
A family link does not by itself establish the biological nature of a relationship. Additional structures may describe adoption, fostering, or other pedigree relationships. Nor does a family record alone prove that a legal marriage occurred: a marriage event is separately recorded.
Events, dates, and places
GEDCOM supports common events such as birth, death, marriage, and burial, together with other events and attributes.
Dates need not always be exact. The format provides representations for approximate dates, ranges, and periods. Some calendar information can also be expressed. These distinctions matter because “about 1850,” “before 1850,” and an exact date in 1850 make different claims.
Place information is commonly exchanged as text. A place name does not necessarily identify a unique geographic entity or preserve historical boundaries. Applications may use differing conventions for jurisdictional order, spelling, or geographic coordinates.
Sources, citations, and media
GEDCOM distinguishes source descriptions from citations that connect particular assertions to supporting material. A citation can include details such as a page reference or a transcription, depending on the version and structure used.
This supports the transfer of evidence-related information, but does not determine whether a claim is historically correct. The presence of a source citation is not equivalent to verification of the associated assertion.
Multimedia structures can reference photographs, document scans, recordings, and other files. A plain .ged file usually stores references rather than embedding the media bytes. Consequently, sending the text file alone may leave its recipient without the referenced images.
Character encoding and GEDCOM 7 packaging
Character encoding is important because genealogical data frequently contains names and places in multiple writing systems.
Older GEDCOM versions allowed several encodings, including ANSEL and, in GEDCOM 5.5.1, UTF-8. Incorrect handling of an encoding declaration can corrupt accented letters or other characters during import.
GEDCOM 7 standardizes UTF-8, providing a consistent encoding for Unicode text. This reduces encoding ambiguity but does not resolve differences in spelling, transliteration, name order, or cultural naming conventions.
GEDCOM 7 also defines GEDZIP, a ZIP-based package convention, commonly using the .gdz extension, for carrying a GEDCOM dataset together with accompanying files. Packaging addresses the practical problem of transferring a text file whose media references would otherwise depend on files left on another computer.
Interoperability and limitations
Application-specific extensions
Genealogy applications often support information beyond the standard vocabulary. GEDCOM permits extension mechanisms; in older versions, custom tags commonly begin with an underscore.
Extensions can preserve specialized information when both applications understand them. Otherwise, an importer may ignore them, convert them to notes, or discard them. A syntactically valid export therefore need not be a lossless representation of the original database.
Round-trip fidelity
A round trip—exporting data, importing it elsewhere, and exporting it again—can alter information even when all resulting files are readable.
Typical difficulties include:
- Different mappings for events and attributes.
- Flattening structured citations into plain text.
- Changes to name components or place hierarchies.
- Loss of unsupported relationships or custom fields.
- Missing media caused by external file paths.
- Changed record identifiers.
These problems illustrate the difference between syntactic compatibility and semantic compatibility. Two applications may parse the same lines successfully while assigning them different meanings.
Validation and historical accuracy
Structural validation can check matters such as permitted tags, required elements, valid references, and acceptable date syntax. It cannot establish that two similarly named records describe the same person or that a proposed parent-child relationship is correct.
GEDCOM also does not itself perform duplicate detection, evidence analysis, or conflict resolution. Those functions belong to genealogy software and research practice. File validity and genealogical data quality are separate properties.
Privacy and security
GEDCOM files can contain birth dates, addresses, contact information, private notes, and details about living people. They may also expose sensitive relationships or information about relatives who did not create the file.
The text format does not inherently enforce access control or encryption. Restriction or privacy markings, where supported, depend on receiving software for their interpretation and enforcement. Excluding living people or private fields from an export is likewise an application function, not an automatic property of GEDCOM.
A file can remain available after the permissions on the originating website or database have changed. Its privacy characteristics therefore depend on both its contents and the systems through which it is stored and distributed.