# GEDCOM

> Mediated Wiki article. Canonical URL: https://mediated.wiki/source/GEDCOM
> Markdown URL: https://mediated.wiki/source/GEDCOM.md
> Source: https://en.wikipedia.org/wiki/GEDCOM
> Source revision: 1354714792
> License: Creative Commons Attribution-ShareAlike 4.0 International (https://creativecommons.org/licenses/by-sa/4.0/)

Specification for genealogical data

GEDCOM Filename extension .ged Internet media type application/vnd.familysearch.gedcom [1] application/vnd.familysearch.gedcom+zip [1] Developed by LDS FHD Initial release 1984; 42 years ago (1984) Latest release 7.0.18 17 February 2026; 4 months ago (2026-02-17)[2] Type of format Genealogy data exchange Standard De facto[3] Open format? yes Website gedcom.io github.com/familysearch/GEDCOM

**FamilySearch GEDCOM**, or simply **GEDCOM** ([/ˈdʒɛdkɒm/](https://en.wikipedia.org/wiki/Help:IPA/English) [*JED-kom*](https://en.wikipedia.org/wiki/Help:Pronunciation_respelling_key), [acronym](/source/Acronym) of *Genealogical Data Communication*), is an [open file format](/source/Open_format) and the [de facto standard](/source/De_facto_standard) specification for storing [genealogical](/source/Genealogy) data.[3] It was developed by [the Church of Jesus Christ of Latter-day Saints](/source/The_Church_of_Jesus_Christ_of_Latter-day_Saints) (LDS Church), the operators of [FamilySearch](/source/FamilySearch), to aid in the research and sharing of genealogical information.[4] A common usage is as a standard format for the backup and transfer of [family tree](/source/Family_tree) data between different [genealogy software](/source/Genealogy_software) and [websites](/source/Genealogy_websites), most of which support importing from and exporting to GEDCOM format.[5]

GEDCOM is defined as a [plain text](/source/Text_encoding) file, using [UTF-8](/source/UTF-8) encoding as of version 7.0. This file contains genealogical information about individuals such as names, events, and relationships; [metadata](/source/Metadata) links these records together.

GEDCOM 7.0, released in 2021, is the most recent version of the GEDCOM specification as of July 2024[\[update\]](https://en.wikipedia.org/w/index.php?title=GEDCOM&action=edit).[6] However, its predecessor, GEDCOM 5.5.1, remains the industry's format standard for the exchange of genealogical data.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] First released as a draft standard in 1999, GEDCOM 5.5.1 received only minor updates in the subsequent 20 years leading up to the release of 5.5.1 final in 2019. To address its shortcomings, some genealogy programs introduced [proprietary](/source/Proprietary_file_format) extensions to GEDCOM which are not always recognized by other programs, such as GEDCOM 5.5 EL (Extended Locations).[7][8][9] Efforts have been made to have 7.0 more widely adopted since its release. [FamilySearch](/source/FamilySearch) intends to be GEDCOM 7.0 compatible in the third quarter 2022 and [Ancestry.com](/source/Ancestry.com) is planning for 7.0 compatibility, but has not yet specified an implementation date.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

## Data model

GEDCOM uses a lineage-linked [data model](/source/Data_model) based on the [conceptual model](/source/Conceptual_schema) of the [nuclear family](/source/Nuclear_family). The family (FAM) record type is therefore the only source of links between the individuals (INDI) in the file, assigning parents (as HUSB and WIFE) and children (as CHIL) by referring to individuals' [unique ID](/source/Unique_identifier) numbers.[10] These historical origins are described in the 7.0 specification document: "The FAM record was originally structured to represent families where a male HUSB (husband or father) and female WIFE (wife or mother) produce CHIL (children)."[11]

Although the links in a GEDCOM family record still use the original naming indicating a husband and a wife, the specification now states that "sex, gender, titles, and roles of partners should not be inferred based on the partner that the HUSB or WIFE structure points to" and that these individuals within a family structure are collectively referred to as 'partners', 'parents' or 'spouses'. A FAM record can also be used for "cohabitation, fostering, adoption, and so on, regardless of the gender of the partners."[11]

## File structure

A GEDCOM file consists of a [header](/source/Header_(computing)) section, records, and a [trailer](/source/Trailer_(information_technology)) section. Within these sections, [records](/source/Record_(computer_science)) represent people (INDI record), families (FAM records), sources of information (SOUR records), and other miscellaneous records, including notes. Every line of a GEDCOM file begins with a level number where all top-level records (HEAD, TRLR, SUBN, and each INDI, FAM, OBJE, NOTE, REPO, SOUR, and SUBM) begin with a line with level 0, while other level numbers are positive [integers](/source/Integer).

Although it is possible to write a GEDCOM file by hand, the format was designed to be used with software and thus is not especially human-friendly. A GEDCOM validator[12] that can be used to validate the structure of a GEDCOM file is included as part of [PhpGedView](/source/PhpGedView) project, though it is not meant to be a standalone validator. For standalone validation "The Windows GEDCOM Validator" can be used.[13] or the older unmaintained Gedcheck[14] from the LDS Church.

During 2001, *The GEDCOM TestBook Project* evaluated how well four popular genealogy programs conformed to the GEDCOM 5.5 standard using the Gedcheck program.[15] Findings showed that a number of problems existed and that "The most commonly found fault leading to data loss was the failure to read the NOTE tag at all the possible levels at which it may appear."[16] In 2005, the *Genealogical Software Report Card* was evaluated (by Bill Mumford who participated in the original *GEDCOM Testbook Project*)[17] and included testing the GEDCOM 5.5 standard using the Gedcheck program.[18]

To assist with adoption of GEDCOM 7.0, validation tools now exist for that standard as well.[19]

### Example

The following is a sample GEDCOM file.

sample.ged 0 HEAD 1 SOUR PAF 2 NAME Personal Ancestral File 2 VERS 5.0 1 DATE 30 NOV 2000 1 GEDC 2 VERS 5.5 2 FORM LINEAGE-LINKED 1 CHAR ANSEL 1 SUBM @U1@ 0 @I1@ INDI 1 NAME John /Smith/ 1 SEX M 1 FAMS @F1@ 0 @I2@ INDI 1 NAME Elizabeth /Stansfield/ 1 SEX F 1 FAMS @F1@ 0 @I3@ INDI 1 NAME James /Smith/ 1 SEX M 1 FAMC @F1@ 0 @F1@ FAM 1 HUSB @I1@ 1 WIFE @I2@ 1 MARR 1 CHIL @I3@ 0 @U1@ SUBM 1 NAME Submitter 0 TRLR

The header (HEAD) includes the source program and version (Personal Ancestral File, 5.0), the GEDCOM version (5.5), the [character encoding](/source/Character_encoding) ([ANSEL](/source/ANSEL)), and a link to information about the submitter of the file.

The individual records (INDI) define John Smith (ID I1), Elizabeth Stansfield (ID I2), and James Smith (ID I3).

The family record (FAM) links the husband (HUSB), wife (WIFE), and child (CHIL) by their ID numbers.

## Versions

The current version of the specification in wide use is GEDCOM *5.5.1 final*, which was released on 15 November 2019. Its predecessor, GEDCOM *5.5.1 draft*[20] was issued in 1999, introducing nine new attribute, tags and adding [UTF-8](/source/UTF-8) as an approved [character encoding](/source/Character_encoding). The draft was not formally approved, but its provisions were adopted in some part by a number of genealogy programs[21][22][23] including FamilySearch.org.[20]

Lineage-linked GEDCOM is the deliberate de facto common denominator.[3] Despite version 5.5 of the GEDCOM standard first being published in 1996, many genealogical software suppliers have never fully supported the feature of multilingual Unicode text (instead of the ANSEL character set) introduced with that version of the specification. Uniform use of Unicode would allow for the usage of international character sets. An example is the storage of East Asian names in their original [Chinese, Japanese and Korean (CJK)](/source/CJK) characters, without which they could be ambiguous and of little use for genealogical or historical research.[24] [PAF 5.2](/source/Personal_Ancestral_File) is an example of software that uses [UTF-8](/source/UTF-8) as its internal character set, and can output a UTF-8 GEDCOM.[24][25]

GEDCOM 7.0 *requires* UTF-8 encoding throughout,[26] and resolves other long-standing issues with GEDCOM 5.5.1. Multimedia support in the form of an associated .zip file, called a GEDZip, is another inclusion. Efforts are underway to see 7.0 embraced as the new exchange standard.[27] GEDCOM 7.0 allows explicitly identifying what standards other than GEDCOM may apply to a particular file. GEDCOM has always been [extensible](/source/Extensibility), but prior to 7.0 there was no standard way to identify such extensions. Also, GEDCOM 7.0 allows explicitly marking an event as nonexistent. This allows, for example, documenting that a particular individual never married.[28] GEDCOM 7.0 was the first version to use [semantic versioning](/source/Semantic_versioning), and is the most recent [minor version](/source/Minor_version) of the specification.

As of July 2024[\[update\]](https://en.wikipedia.org/w/index.php?title=GEDCOM&action=edit), the next planned minor release is v7.1, which is under development.[29]

### Release history

GEDCOM version Release date Notes Unsupported: 1.0[30] 1984[31] – Unsupported: 2.0[30] Dec 1985[32] PAF 2.0 Unsupported: 2.1 Feb 1987[32] GEDCOM for PAF 2.1 Unsupported: 2.3 Draft 7 August 1985[33] with PAF2.0 GEDCOM implementation conventions Unsupported: 2.4 Draft 13 December 1985[33] with PAF2.0 GEDCOM implementation conventions Unsupported: 3.0 Standard[30] 9 October 1987[34] PAF 2.0 and 2.1 implementation of 3.0 Unsupported: 4.0 Standard August 1989 PAF 2.1 – 2.31 Unsupported: 4.1 Draft[35] – – Unsupported: 4.2 Draft[36] 25 January 1990[37] – Unsupported: 5.0 Draft[30] 31 December 1991[33] lineage-linked structures were introduced.[38] Unsupported: 5.1 Draft 18 September 1992[32] – Unsupported: 5.2 Draft 22 January 1992[39] – Unsupported: 5.3 Draft 4 November 1993[40] Unicode standard (ISO/IEC 10646) was introduced as an additional character set. Unsupported: 5.4 Draft 21 August 1995[41] – Unsupported: 5.5 Standard 11 December 1995[42] PAF 3, 4 and 5 Supported: 5.5 Standard January 2, 1996[43][44] PAF 3, 4 and 5 / 5.5 Standard[45] Unsupported: GEDCOM (Future Direction) Draft[38][46] May 1, 1998[47][48] "it used an entirely new data model"[49] Unsupported: 5.5.1 Draft[50][51] October 2, 1999[20] Used by FamilySearch.org[20] UTF-8 added as an approved character encoding. Supported: 5.5.1 Release[52] November 15, 2019 current standard, minor text modifications to 5.5.1 Draft. Unsupported: 5.6 Private Draft -[53] "Jed Allen sent those two files to a few people only for sort of "private comments"[54] Unsupported: 6.0 XML Draft December 28, 2001[55] Was not a complete specification, and not recommended to begin to software implementations. Unsupported: 7.0.0-rc1 Draft February 2021[56] Release candidate revealed for RootsTech 2021, but then all talks, specifications and the web site were removed on 25 February 2021[57] Unsupported: 7.0[58] 27 May 2021 Modernize character encoding, clarify ambiguities in 5.5.1 specification, introduce semantic versioning, improve multimedia handling Latest version: 7.0.18[59] 17 Feb 2026 Legend: Unsupported Supported Latest version Preview version Future version

## Limitations

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This section does not cite any sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (February 2009) (Learn how and when to remove this message) This section needs to be updated. The reason given is: This section needs to be checked against GEDCOM 7.0 for accuracy, and sourced if still true. Please help update this article to reflect recent events or newly available information. (July 2022) (Learn how and when to remove this message)

### Support for multi-person events and sources

A GEDCOM file can contain information on events such as births, deaths, census records, ship's records, marriages, etc.; a rule of thumb is that an event is something that took place at a specific time, at a specific place (even if time and place are not known). GEDCOM files can also contain attributes such as physical description, occupation, and total number of children; unlike events, attributes generally cannot be associated with a specific time or place.

The GEDCOM specification requires that each event or attribute is associated with exactly one individual or family.[60] This causes redundancy for events such as census records where the actual census entry often contains information on multiple individuals. In the GEDCOM file, for census records a separate census "CENS" event must be added for each individual referenced. Some genealogy programs, such as [Gramps](/source/Gramps_(software)) and [The Master Genealogist](/source/The_Master_Genealogist), have elaborate database structures for sources that are used, among other things, to represent multi-person events. When databases are exported from one of these programs to GEDCOM, these database structures cannot be represented in GEDCOM due to this limitation, with the result that the event or source information including all of the relevant citation reference information must be duplicated each place that it is used. This duplication makes it difficult for the user to maintain the information related to sources.

In the GEDCOM specification, events that are associated with a family such as marriage information is only stored in a GEDCOM once, as part of the family (FAM) record, and then both spouses are linked to that single family record.[60]

### Ambiguity in the specification

The GEDCOM specification was made purposefully flexible to support many ways of encoding data, particularly in the area of sources. This flexibility has led to a great deal of ambiguity, and has produced the side effect that some genealogy programs which import GEDCOM do not import all of the data from a file.[61]

### Ordering of events that do not have dates

The GEDCOM specification does not offer explicit support for keeping a known order of events. In particular, the order of relationships (FAMS) for a person and the order of the children within a relationship (FAM) can be lost. In many cases the sequence of events can be derived from the associated dates. But dates are not always known, in particular when dealing with data from centuries ago. For example, in the case that a person has had two relationships, both with unknown dates, but from descriptions it is known that the second one is indeed the second one. The order in which these FAMS are recorded in GEDCOM's INDI record will depend on the exporting program. In Aldfaer[62] for instance, the sequence depends on the ordering of the data by the user (alphabetical, chronological, reference, etc.). The proposed XML GEDCOM standard[55] does not address this issue either.

## Lesser-known features

GEDCOM has many features that are not commonly used. Some software packages do not support all the features that the GEDCOM standard allows.

### Multimedia

The GEDCOM standard supports the inclusion of multimedia objects (for example, photos of individuals).[63] Such multimedia objects can be either included in the GEDCOM file itself (called the "embedded form") or in an external file where the name of the external file is specified in the GEDCOM file (called the "linked form"). Embedding multimedia directly in the GEDCOM file makes transmission of data easier, in that all of the information (including the multimedia data) is in one file, but the resulting file can be enormous. Linking multimedia keeps the size of the GEDCOM file under control, but then when transmitting the file, the multimedia objects must either be transmitted separately or archived together with the GEDCOM into one larger file. Support for embedding media directly was dropped in the draft 5.5.1 standard.[64]

### Conflicting information

The GEDCOM standard allows for the specification of multiple opinions or conflicting data, simply by specifying multiple records of the same type. For example, if an individual's birth date was recorded as 10 January 1800 on the birth certificate, but 11 January 1800 on the death certificate, two BIRT records for that individual would be included, the first with the 10 January 1800 date and giving the birth certificate as the source, and the second with the 11 January 1800 date and giving the death certificate as the source. The preferred record is usually listed first.

This example encoded in GEDCOM might look like this:

0 @I1@ INDI
1 NAME John /Doe/
1 BIRT
2 DATE 10 JAN 1800
2 SOUR @S1@
3 DATA
4 TEXT Transcription from birth certificate would go here
3 NOTE This birth record is preferred because it comes from the birth certificate
3 QUAY 2
1 BIRT
2 DATE 11 JAN 1800
2 SOUR @S2@
3 DATA
4 TEXT Transcription from death certificate would go here
3 QUAY 2

Conflicting data may also be the result of user errors. The standard does not specify in any way that the *contents* must be consistent. A birth date like "10 APR 1819" might mistakenly have been recorded as "10 APR 1918" long after the person's death. The only way to reveal such inconsistencies is by rigorous validation of the *content data*.

### Internationalization

The GEDCOM standard supports internationalization in several ways. First, newer versions of the standard allow data to be stored in Unicode (or, more recently, UTF-8), so text in any language can be stored.[65] Secondly, in the same way that one can have multiple events on a person, GEDCOM allows one to have multiple names for a person,[66] so names can be stored in multiple languages, although there is no standardized way to indicate which instance is in which language. Finally, in version 5.5.1, the NAME field also supports a phonetic variation (FONE) and a romanized variation (ROMN) of the name.[67]

## GEDCOM X

In February 2012 at the RootsTech 2012 conference, [FamilySearch](/source/FamilySearch) outlined a major new project around genealogical standards called GEDCOM X, and invited collaboration.[68] It includes software developed under the [Apache](/source/Apache_License) [open source license](/source/Open_source_license). It includes data formats that facilitate basing family trees on sources and records (both physical artifacts and digital artifacts), support for sharing and linking data online, and an API.[68][69][70]

In August 2012 [FamilySearch](/source/FamilySearch) employee and GEDCOM X project leader Ryan Heaton dropped the claim that GEDCOM X is the new industry standard, and repositioned GEDCOM X as another FamilySearch [open source](/source/Open_source) project.[71]

After the release of GEDCOM 7, FamilySearch positioned GEDCOM X as useful for interoperation with its FamilySearch Family Tree software.[72]

## Alternatives

Commsoft, the authors of the [Roots](/source/Ancestry.com#Past_products)[73] series of genealogy software and Ultimate Family Tree, defined a version called Event-Oriented GEDCOM (also known as "Event GEDCOM" and originally called InterGED[74]),[75] which included events as first class (zero-level) items. Although it is event based, it is still a model built on assumed reality rather than evidence. Event GEDCOM was more flexible, as it allowed some separation between believed events and the participants. However, Event GEDCOM was not widely adopted by other developers due to its semantic differences.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*] With Roots and Ultimate Family Tree no longer available, very few people today are using Event GEDCOM.[76]

[Gramps XML](/source/Gramps_(software)#File_format) is an [XML](/source/XML)-based [open format](/source/Open_format) created by the [open source](/source/Open_source) genealogy project [Gramps](/source/Gramps_(software)) and used also by [PhpGedView](/source/PhpGedView).

The Family History Information Standards Organisation was established in 2012 with the aim of developing international standards for family history and genealogical information.[77] One of the standards the organization proposed was Extended Legacy Format (ELF), compatible with GEDCOM 5.5(.1), but including an extensibility mechanism. The organization requested public comment on the proposed standard in 2017.[78] It withdrew the proposal because release 7.0 of GEDCOM addressed many of the organization's concerns.[28]

## See also

- [FamilySearch](/source/FamilySearch) - [Ancestral File Number](/source/Ancestral_File_Number) - [International Genealogical Index](/source/International_Genealogical_Index)

- [GENDEX](/source/GENDEX) – Genealogical index

- [Genealogical numbering systems](/source/Genealogical_numbering_systems)

- [GNTP](/source/GNTP) – Genealogy Network Transfer Protocol

- [Tiny Tafel Format](/source/Tiny_Tafel) – encoded "ancestor table"

- [List of genealogy databases](/source/List_of_genealogy_databases)

## Notes

## References

1. ^ [***a***](#cite_ref-GordonClarke_1-0) [***b***](#cite_ref-GordonClarke_1-1) Clarke, Gordon (2021-12-07). ["Media subtype name: vnd.familysearch.gedcom+zip"](https://www.iana.org/assignments/media-types/application/vnd.familysearch.gedcom+zip). *[Internet Assigned Numbers Authority](/source/Internet_Assigned_Numbers_Authority)*. Retrieved 2022-10-01.

1. **[^](#cite_ref-2)** ["Releases · FamilySearch/GEDCOM"](https://github.com/FamilySearch/GEDCOM/releases). *GitHub*. Retrieved 17 May 2026.

1. ^ [***a***](#cite_ref-defacto_3-0) [***b***](#cite_ref-defacto_3-1) [***c***](#cite_ref-defacto_3-2) [Subject: GEDCOM and Formal Standards Organizations](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind9601D&L=GEDCOM-L&P=R1252&D=0&H=0&I=-3&O=T&T=0&m=904) Date: Wed, 24 Jan 1996 11:53:52 -0700 From: Bill Harten – Organization: Brigham Young University "why wasn't GEDCOM developed through a formal standards organization?..."Thus GEDCOM was born as a deliberate, de facto standard, to be followed only by those who felt it was in their best interest to do so.

1. **[^](#cite_ref-4)** [Subject: rep: T Jenkins – open letter to GEDCOM-L](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind9509e&L=gedcom-l&T=0&I=-3&P=655) – "The goal was to try and provide a standard to allow developers to provide a vehicle for their users to share genealogical conclusions and supporting evidence with others." From: "Jed R. Allen" Brigham Young University – Date: 29 Sep 1995 17:40:04 -0600 – GEDCOM-L Archives – September 1995, week 5 (#7)

1. **[^](#cite_ref-5)** ["Genealogical Software Report Card"](https://web.archive.org/web/20090211172052/http://mumford.ca/reportcard/index.htm). March 2005. Archived from [the original](http://www.mumford.ca/reportcard/index.htm) on 2009-02-11.

1. **[^](#cite_ref-specV7_6-0)** ["The FamilySearch GEDCOM Specification"](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html). *gedcom.io*. 8 February 2024. Retrieved 10 July 2024.

1. **[^](#cite_ref-7)** [GEDCOM 5.5 EL](http://wiki-en.genealogy.net/Gedcom_5.5EL) [Archived](https://web.archive.org/web/20200111114712/http://wiki-en.genealogy.net/Gedcom_5.5EL) 2020-01-11 at the [Wayback Machine](/source/Wayback_Machine) (Extended Locations) specification

1. **[^](#cite_ref-8)** [Ability to save information against places](http://www.fhug.org.uk/wishlist/wldisplay.php?currentpage=2&wlwlref=249) [Archived](https://web.archive.org/web/20200124125538/https://www.fhug.org.uk/wishlist/wldisplay.php?currentpage=2&wlwlref=249) 2020-01-24 at the [Wayback Machine](/source/Wayback_Machine) – "Support for parts of the GEDCOM 5.5EL proposal" – FHUG Wish List

1. **[^](#cite_ref-9)** [0000688: Support for Gedcom 5.5EL](http://bugs.gramps-project.org/view.php?id=688) [Archived](https://web.archive.org/web/20110726125916/http://bugs.gramps-project.org/view.php?id=688) 2011-07-26 at the [Wayback Machine](/source/Wayback_Machine) – Gramps Bugtracker

1. **[^](#cite_ref-10)** ["The GEDCOM Standard Release 5.5: Data Model Chart"](https://homepages.rootsweb.com/~pmcbride/gedcom/55gcmod.htm). *homepages.rootsweb.com*. Retrieved 2022-07-21.

1. ^ [***a***](#cite_ref-:0_11-0) [***b***](#cite_ref-:0_11-1) ["The FamilySearch GEDCOM Specification"](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#records). *gedcom.io*. 2022-06-07. Retrieved 2022-07-21.

1. **[^](#cite_ref-12)** ["View of phpgedview's GEDCOM validator source code"](http://phpgedview.svn.sourceforge.net/viewvc/*checkout*/phpgedview/trunk/phpGedView/gedcheck.php).[*[permanent dead link](https://en.wikipedia.org/wiki/Wikipedia:Link_rot)*]

1. **[^](#cite_ref-13)** ["VGed 3.02"](https://web.archive.org/web/20110106162327/http://www.rumblefische.com/vged/vged.html). *Rumble Fische*. Archived from [the original](https://rumblefische.com/vged/vged.html) on January 6, 2011.

1. **[^](#cite_ref-14)** [Gedcheck](http://www.familysearch.org/eng/home/faq/faq_gedcom.asp) [Archived](https://web.archive.org/web/20090207121907/http://www.familysearch.org/eng/home/faq/faq_gedcom.asp) 2009-02-07 at the [Wayback Machine](/source/Wayback_Machine) – "uses a grammar file for the specific version of GEDCOM to be checked against." The Church of Jesus Christ of Latter-day Saints

1. **[^](#cite_ref-15)** ["GEDCOM TestBook Project"](https://web.archive.org/web/20060615015106/https://www.ngsgenealogy.org/ngsgentech/projects/TestBook2001/index.cfm). 2001. Archived from [the original](https://www.ngsgenealogy.org/ngsgentech/projects/TestBook2001/index.cfm) on 2006-06-15.

1. **[^](#cite_ref-16)** [GEDCOM and the GenTech Testbook Project] Genealogical Computing 7/1/2001 – Archive Summer 2001 Vol. 21.1 – Ancestry.com

1. **[^](#cite_ref-17)** [The Genealogical Software Report Card](https://archive.today/20120708201214/http://groups.yahoo.com/group/NEOCAG/message/571) 2000 S W Mumford Last updated March 2005 [*[unreliable source?](https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources)*]

1. **[^](#cite_ref-18)** [Reviews from the NGS Newsmagazine and its Predecessors.](http://www.mumford.ca/reportcard/review.htm) [Archived](https://web.archive.org/web/20090212181201/http://mumford.ca/reportcard/review.htm) 2009-02-12 at the [Wayback Machine](/source/Wayback_Machine) – Test Result are in the PDF's

1. **[^](#cite_ref-19)** ["Tools for FamilySearch GEDCOM"](https://gedcom.io/tools/). *FamilySearch GEDCOM*. Retrieved 2022-07-21.

1. ^ [***a***](#cite_ref-GEDCOM_5.5.1_draft_20-0) [***b***](#cite_ref-GEDCOM_5.5.1_draft_20-1) [***c***](#cite_ref-GEDCOM_5.5.1_draft_20-2) [***d***](#cite_ref-GEDCOM_5.5.1_draft_20-3) Family History Department GEDCOM Coordinator (2 October 1999). ["The GEDCOM Standard: Draft Release 5.5.1"](http://www.phpgedview.net/ged551-5.pdf) (PDF). [The Church of Jesus Christ of Latter-day Saints](/source/The_Church_of_Jesus_Christ_of_Latter-day_Saints). Retrieved 2022-10-01.

1. **[^](#cite_ref-21)** [GED-GEN is based on GEDCOM version 5.5.1 (draft)](http://www.ged-gen.com/help/hlpintro.html) [Archived](https://web.archive.org/web/20090203215917/http://ged-gen.com/help/hlpintro.html) 2009-02-03 at the [Wayback Machine](/source/Wayback_Machine), dated 2 October 1999. The following record types are parsed: header, individual, family, notes, source, and repository. However not all elements within these records are processed. – Specifications – GED-GEN Introduction

1. **[^](#cite_ref-22)** [0000688: Support for Gedcom 5.5EL](http://bugs.gramps-project.org/view.php?id=688) [Archived](https://web.archive.org/web/20110726125916/http://bugs.gramps-project.org/view.php?id=688) 2011-07-26 at the [Wayback Machine](/source/Wayback_Machine)(0008068) romjerome (developer) 2009-01-25 06:13 – "Note : GRAMPS 3.0.x supports a part of GEDCOM 5.5.1 on export, which is not supported by most programs" – Gramps Bugtracker

1. **[^](#cite_ref-23)** ["MyBlood supports the GEDCOM 5.5 and 5.5.1 file format."](http://www.myblood-line.com/Support.html) [Archived](https://web.archive.org/web/20090605143052/http://www.myblood-line.com/Support.html) 2009-06-05 at the [Wayback Machine](/source/Wayback_Machine) – MyBlood Support – Forum, FAQ, Know Problems

1. ^ [***a***](#cite_ref-ldscatalog.com_24-0) [***b***](#cite_ref-ldscatalog.com_24-1) [Personal Ancestral File 5.2 and PAF Companion 5.4 – Software Version Changes](http://www.ldscatalog.com/webapp/wcs/stores/servlet/ProductDisplay?partNumber=77065000&catalogIdentifier=LDS_SalesCatalog&action=Changes) [Archived](https://web.archive.org/web/20090306010346/http://www.ldscatalog.com/webapp/wcs/stores/servlet/ProductDisplay?partNumber=77065000&catalogIdentifier=LDS_SalesCatalog&action=Changes) 2009-03-06 at the [Wayback Machine](/source/Wayback_Machine) Release 5.0.1.4, 22 December 2000 – "10.GEDCOM improvements: Table:Destination:PAF 5 GEDCOM Version:5.5 Character Set:UTF-8

1. **[^](#cite_ref-25)** [Personal Ancestral File 5.1](http://www.mumford.ca/reportcard/PAF5.pdf) [Archived](https://web.archive.org/web/20070721110633/http://www.mumford.ca/reportcard/PAF5.pdf) 2007-07-21 at the [Wayback Machine](/source/Wayback_Machine) – "Also noted in a second test was the use of four tags from a later draft version of the Gedcom specification, FONE (phonetic name), ROMN (romanized name), EMAIL (e-mail), and _UID" Jan/Feb 2002 NGS Newsmagazine

1. **[^](#cite_ref-26)** ["The FamilySearch GEDCOM Specification"](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#characters). *gedcom.io*. 2022-06-07. Retrieved 2022-07-21.

1. **[^](#cite_ref-27)** ["Implementation Progress • Genealogy"](http://familysearch.org/en/GEDCOM/implementation-progress). *Genealogy*. Retrieved 2022-07-21.

1. ^ [***a***](#cite_ref-:1_28-0) [***b***](#cite_ref-:1_28-1) Smith, Richard (2021-07-21). ["FamilySearch GEDCOM 7"](https://fhiso.org/2021/07/familysearch-gedcom-7/). *Family History Information Standards Organisation*. [Archived](https://web.archive.org/web/20210804002707/https://fhiso.org/2021/07/familysearch-gedcom-7/) from the original on 2021-08-04. Retrieved 2023-01-30.

1. **[^](#cite_ref-29)** ["GitHub - FamilySearch/GEDCOM at v7.1"](https://github.com/FamilySearch/GEDCOM/tree/v7.1). *GitHub*. Retrieved 10 July 2024.

1. ^ [***a***](#cite_ref-beitrag103_30-0) [***b***](#cite_ref-beitrag103_30-1) [***c***](#cite_ref-beitrag103_30-2) [***d***](#cite_ref-beitrag103_30-3) [pafuser : Beitrag: Re: \[pafuser\] PAF 5.01 und GEDCOM](https://archive.today/20130105083459/http://de.groups.yahoo.com/group/pafuser/message/103) By Eckhard Henkel – Beitrag #103 von 1494 – Yahoo Groups

1. **[^](#cite_ref-31)** [Subject:description of InterGED theory](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind9407D&L=GEDCOM-L&P=R519&I=-3) From:Gary Steiner – "The first GEDCOM standard, version 1.0, was released to the genealogical software development community in 1984." – GEDCOM-L Archives – July 1994, week 4 (#14)

1. ^ [***a***](#cite_ref-timeline2000_32-0) [***b***](#cite_ref-timeline2000_32-1) [***c***](#cite_ref-timeline2000_32-2) [Subject:Timeline of GEDCOM versions and PAF](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0011C&L=GEDCOM-L&P=R645&I=-3&m=5582) By George Archer – GEDCOM-L Archives – November 2000, week 3 (#12)

1. ^ [***a***](#cite_ref-starkey59_33-0) [***b***](#cite_ref-starkey59_33-1) [***c***](#cite_ref-starkey59_33-2) [Subject:Re: GEDCOM standards help please](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0006D&L=GEDCOM-L&T=0&F=&I=-3&S=&P=59) From:Graham Starkey – "DRAFT VERSION 2.3–7 August 1985 with PAF2.0 GEDCOM implementation conventions" – GEDCOM-L Archives – June 2000, week 4 (#1)

1. **[^](#cite_ref-34)** [RootsWeb: ROOTS-L Re: Large Charts (fairly long)](https://archiver.rootsweb.ancestry.com/th/read/ROOTS/1990-02/0634862536-01):Date:Tue, 11 Jul 89 15:14:31 CDT From: Marty Hoag <NU021172@N...> Subject:Re: Printing trees with PAF? From soc.roots ... * GEDCOM release 3.0, 9 Oct 1987, 131 pages (!)

1. **[^](#cite_ref-35)** ["LISTSERV - GEDCOM-L Archives - LISTSERV.NODAK.EDU"](https://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind9410A&L=GEDCOM-L&P=R880&I=-3&T=0). *listserv.nodak.edu*.

1. **[^](#cite_ref-36)** [File Structures for PAF and GEDCOM](https://groups.google.com/group/soc.genealogy.computing/browse_thread/thread/bddc9724596065ed/fc70b4faae5128a4?lnk=gst&q=gedcom+released#fc70b4faae5128a4) – Date: 1996/01/04 – soc.genealogy.computing | Google Groups:

1. **[^](#cite_ref-37)** [Subject:4.x specs](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind9405A&L=GEDCOM-L&T=0&F=&I=-3&S=&P=1781) From:Rafal Prinke -"while this document has the date January 25, 1990. So maybe it is GEDCOM 4.2 ?" – GEDCOM-L Archives – May 1994, week 1 (#19)

1. ^ [***a***](#cite_ref-jedfuture_38-0) [***b***](#cite_ref-jedfuture_38-1) [Subject: GEDCOM (Future Direction) Announced by Family History](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind9805A&L=GEDCOM-L&P=R2&I=-3&T=0) From: "Jed R. Allen" Date: Fri, 1 May 1998 18:08:24 -0600

1. **[^](#cite_ref-39)** [Subject:Re: GEDCOM standards help please](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0006D&L=GEDCOM-L&T=0&F=&I=-3&S=&P=59) From:Graham Starkey – "DRAFT Release 5.2–22 January 1992 120kb" – GEDCOM-L Archives – June 2000, week 4 (#1)

1. **[^](#cite_ref-40)** [GEDCOM 5.3 draft](http://ftp.aset.psu.edu/genealogy/gedcom55/gedstand.t82) [Archived](https://web.archive.org/web/20100722012217/http://ftp.aset.psu.edu/genealogy/gedcom55/gedstand.t82) 2010-07-22 at the [Wayback Machine](/source/Wayback_Machine) – 4 November 1993

1. **[^](#cite_ref-41)** [THE GEDCOM STANDARD](http://www.lege.com/gedcom54.html) – DRAFT Release 5.4–21 August 1995

1. **[^](#cite_ref-42)** [Subject:Timeline of GEDCOM versions and PAF](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0011C&L=GEDCOM-L&P=R645&I=-3&T=0) By George Archer – "5.5 11 Dec 1995 (Title Page for 5.5)"- GEDCOM-L Archives – November 2000, week 3 (#12)

1. **[^](#cite_ref-43)** [GEDCOM 5.5 Standard](http://www.familysearch.org/GEDCOM/GEDCOM55.EXE) [Archived](https://web.archive.org/web/20061120085819/http://www.familysearch.org/gedcom/gedcom55.exe) 2006-11-20 at the [Wayback Machine](/source/Wayback_Machine) (Executable file in Envoy format)

1. **[^](#cite_ref-44)** [Re: Looking for GEDCOM versions 4 & 5.xx](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind9608B&L=GEDCOM-L&P=R89&I=-3&T=0) "Brian C. Madsen" – "A GEDCOM 5.5 Errata Sheet dated 10 January 1996 supposedly contains corrections to pages 23, 24, 25, 26, 29, 29, 29, 33, 34, 39, 57, 79, and 85."

1. **[^](#cite_ref-45)** [Gedcom Documentation Library](https://chronoplexsoftware.com/gedcomvalidator/gedcom/index.htm) [Archived](https://web.archive.org/web/20160601054626/https://chronoplexsoftware.com/gedcomvalidator/gedcom/index.htm) June 1, 2016, at the [Wayback Machine](/source/Wayback_Machine), Chronoplex Software

1. **[^](#cite_ref-46)** [GEDCOM Specification Future Direction](https://web.archive.org/web/20200312132308/ftp://ftp.ldschurch.org/genealogy/GEDCOM/Future/Gedfmstr.pdf) (1999-07-07)

1. **[^](#cite_ref-47)** ["LISTSERV - GEDCOM-L Archives - LISTSERV.NODAK.EDU"](https://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0002C&L=GEDCOM-L&P=R351&I=-3). *listserv.nodak.edu*.

1. **[^](#cite_ref-48)** [Comments on the GEDCOM Future Directions document](http://xml.coverpages.org/gedcomments9808.html) [Archived](https://web.archive.org/web/20160612041604/http://xml.coverpages.org/gedcomments9808.html) 2016-06-12 at the [Wayback Machine](/source/Wayback_Machine) Michael H. Kay, 17 May 1998

1. **[^](#cite_ref-49)** [Subject:GEDCOM Future Directions](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind9805B&L=GEDCOM-L&P=R154&I=-3) – From:John Nairn – Date:Mon, 11 May 1998 13:38:45 -0600 – GEDCOM-L Archives – May 1998, week 2 (#3)

1. **[^](#cite_ref-50)** [GEDCOM 5.51 data model in UML format](http://www.softwarerenovation.com/igenie/GEDCOM.aspx) – Software Renovation Corporation

1. **[^](#cite_ref-51)** ["Gedcom 5.5.1 – GenWiki"](https://web.archive.org/web/20190604095318/http://wiki-en.genealogy.net/Gedcom_5.5.1). *wiki-en.genealogy.net*. Archived from [the original](http://wiki-en.genealogy.net/Gedcom_5.5.1) on 2019-06-04. Retrieved 2009-02-11.

1. **[^](#cite_ref-52)** ["THE GEDCOM STANDARD Release 5.5.1"](https://edge.fscdn.org/assets/img/documents/ged551-5bac5e57fe88dd37df0e153d9c515335.pdf) (PDF).

1. **[^](#cite_ref-53)** [Subject:Re: GEDCOM History](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0102c&L=gedcom-l&T=0&I=-3&P=63) From:STEFANO BOSCOLO – Date:Tue, 20 Feb 2001 19:54:06 +0100 – GEDCOM-L Archives – February 2001, week 3 (#1)

1. **[^](#cite_ref-54)** [Subject: Re: GEDCOM History](http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0102c&L=gedcom-l&T=0&I=-3&P=331) From:"Rafal T. Prinke" – Date:Tue, 20 Feb 2001 22:14:55 +0100 – GEDCOM-L Archives – February 2001, week 3 (#4)

1. ^ [***a***](#cite_ref-xml_gedcom_55-0) [***b***](#cite_ref-xml_gedcom_55-1) ["Draft Specification for GEDCOM XML 6.0"](https://web.archive.org/web/20061116032407/http://www.familysearch.org/GEDCOM/GedXML60.pdf) (PDF). *[FamilySearch](/source/FamilySearch)*. Archived from [the original](http://www.familysearch.org/GEDCOM/GedXML60.pdf) (PDF) on 2006-11-16. Retrieved 2006-11-19.

1. **[^](#cite_ref-GEDCOM_7.0_draft_56-0)** ["Web site for GEDCOM 7.0"](https://web.archive.org/web/20210225095749/http://gedcom.io/). Archived from [the original](http://gedcom.io/) on 2021-02-25. Retrieved 2021-02-22.

1. **[^](#cite_ref-57)** ["GEDCOM 7.0 at Louis Kessler's Behold Blog"](https://beholdgenealogy.com/blog/?p=3724). [Archived](https://web.archive.org/web/20210511122903/https://beholdgenealogy.com/blog/?p=3724) from the original on 2021-05-11.

1. **[^](#cite_ref-58)** ["The FamilySearch GEDCOM Specification Release 7.0.9"](https://github.com/FamilySearch/GEDCOM/releases/download/v7.0.9/gedcom.pdf) (PDF). *[GitHub](/source/GitHub)*.

1. **[^](#cite_ref-59)** ["The FamilySearch GEDCOM Specification Release 7.0.18"](https://github.com/FamilySearch/GEDCOM/releases/download/v7.0.18/gedcom.pdf) (PDF). *[GitHub](/source/GitHub)*.

1. ^ [***a***](#cite_ref-gedcom2627_60-0) [***b***](#cite_ref-gedcom2627_60-1) GEDCOM Standard 5.5, pp. 26–27.

1. **[^](#cite_ref-61)** ["Why GEDCOM Files are Not in Sync with All Genealogy Programs"](https://web.archive.org/web/20160303223418/http://www.family-genealogy.com/downloads/GEDCOM_Sync_Issues.pdf) (PDF). *family-genealogy.com*. 2011-04-24. Archived from [the original](http://www.family-genealogy.com/downloads/GEDCOM_Sync_Issues.pdf) (PDF) on 2016-03-03. Retrieved 2015-03-17.

1. **[^](#cite_ref-62)** ["Aldfaer, Hét gratis stamboomprogramma"](http://www.aldfaer.nl) [Aldfaer, the free family tree program]. *www.aldfaer.nl* (in Dutch). [Netherlands](/source/Netherlands). Retrieved 2022-10-01.

1. **[^](#cite_ref-63)** GEDCOM Standard 5.5, p. 28.

1. **[^](#cite_ref-64)** Draft GEDCOM Standard 5.5.1, p. 6.

1. **[^](#cite_ref-65)** GEDCOM Standard 5.5, p. 45.

1. **[^](#cite_ref-66)** GEDCOM Standard 5.5, p. 27.

1. **[^](#cite_ref-67)** GEDCOM Draft 5.5.1, p. 38

1. ^ [***a***](#cite_ref-gedcomx_68-0) [***b***](#cite_ref-gedcomx_68-1) ["GEDCOM X"](http://www.gedcomx.org/). FamilySearch. Retrieved February 4, 2012.

1. **[^](#cite_ref-69)** ["Ryan Heaton: A New GEDCOM"](https://ancestryinsider.blogspot.com/2012/02/ryan-heaton-new-gedcom.html). *The Ancestry Insider*. 2012-02-04. Retrieved 2012-02-16.

1. **[^](#cite_ref-70)** ["RootsTech Learning #3 – GEDCOM X and/or BetterGEDCOM and/or FHISO"](https://geneapoppop.blogspot.com/2012/02/rootstech-learning-3-gedcom-x-andor.html). *Stardust 'n' Roots*. 2012-02-13. Retrieved 2012-02-16.

1. **[^](#cite_ref-71)** [2012-08-31 GEDCOM X: no industry standard](http://www.tamurajones.net/GEDCOMXNoIndustryStandard.xhtml), FamilySearch abandons GEDCOM X push, By Tamura Jones, Modern Software Experience.

1. **[^](#cite_ref-72)** ["General FAQs"](https://gedcom.io/generalfaqs/). *FamilySearch GEDCOM*. Retrieved 2022-07-25.

1. **[^](#cite_ref-73)** [CommSoft to Return?](https://www.ancestry.com/learn/library/article.aspx?article=3549) Dick Eastman Online 3/14/2001 – Archive – Ancestry.com

1. **[^](#cite_ref-74)** [RootsWeb: TMG-L \[TMG\] InterGED/Event GEDCOM](https://archiver.rootsweb.ancestry.com/th/read/TMG/2002-02/1013805198) Date: Fri, 15 Feb 2002 13:33:18 -0700

1. **[^](#cite_ref-75)** ["Commsoft: The Roots Story"](http://sonic.net/~commsoft/rstory.html). Retrieved 2008-11-20.

1. **[^](#cite_ref-76)** ["TMGL Archives: Event-oriented"](https://web.archive.org/web/20071101122737/http://archiver.rootsweb.com/th/read/TMG/2000-06/0962255126). 2000-06-29. Archived from [the original](https://archiver.rootsweb.com/th/read/TMG/2000-06/0962255126) on 2007-11-01. Retrieved 2008-11-20.

1. **[^](#cite_ref-77)** ["Family History Information Standards Organisation"](http://fhiso.org/). FHISO. [Archived](https://web.archive.org/web/20160430173206/https://fhiso.org/) from the original on 2016-04-30. Retrieved 25 April 2016.

1. **[^](#cite_ref-78)** ["Annual Report to Members for 2018"](https://fhiso.org/report-2018/). *Family History Information Standards Organisation*. [Archived](https://web.archive.org/web/20190225053312/https://fhiso.org/report-2018/) from the original on 2019-02-25. Retrieved 2023-02-04.

## External links

**General**

- [GEDCOM Standard](http://gedcom.io/)

- [FamilySearch GEDCOM Guide](http://www.familysearch.org/developers/docs/guides/gedcom)

- [GEDCOM X Project](http://www.gedcomx.org/)

- ["More on LDS Church's Adoption of the XML Standard"](https://web.archive.org/web/20110927061127/http://www.ancestry.com/learn/library/article.aspx?article=3438). *ancestry.com*. Archived from [the original](https://www.ancestry.com/learn/library/article.aspx?article=3438) on 2011-09-27. Retrieved 20 April 2024.

- [THE GEDCOM STANDARD Release 5.5.1](https://edge.fscdn.org/assets/img/documents/ged551-5bac5e57fe88dd37df0e153d9c515335.pdf), released 15. November 2019

v t e Genealogy software Open source Desktop Family.Show GenealogyJ Gramps LifeLines Web-based GeneWeb Gramps Web PhpGedView webtrees Freeware Desktop My Family Tree (Windows) Ancestral Quest (Windows) Genealogica Grafica (Windows) Legacy Family Tree (Windows) Personal Ancestral File (discontinued) RootsMagic Essentials (Windows & Mac OS) Retail software Desktop Ancestral Quest (Windows) Brother's Keeper (Windows) Family Historian (Windows) Family Tree Maker (Windows & Mac OS) Genbox Family History (Windows) GenoPro (Windows) Kith and Kin Pro (Windows) GEDitCOM (Mac OS) MacFamilyTree (Mac OS & iOS) Personal Ancestral File (Mac OS) Reunion (Mac OS & iOS) RootsMagic (Windows & Mac OS) The Master Genealogist (Windows) TreeDraw (Windows) Web-based TNG Software as a service (SaaS) Free/web-based FamilySearch GEDmatch Rodovid WeRelate WikiTree Retail/web-based Ancestry.com Familio Findmypast GenealogyBank Geneanet Genes Reunited Geni.com MyHeritage DNA services 23andMe AncestryDNA FamilyTreeDNA Living DNA MyHeritage DNA Nebula Genomics TellmeGen General Comparison of web-based genealogy software Family tree mapping GEDCOM Genealogy websites Category

---
Adapted from the Wikipedia article [GEDCOM](https://en.wikipedia.org/wiki/GEDCOM) by Wikipedia contributors ([contributor history](https://en.wikipedia.org/wiki/GEDCOM?action=history)). Available under [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/). Changes may have been made.