telecuro.com → best good → format ddr4 mla → what is gedcom format
Posted on by Jacob Alvarez

What Is GEDCOM Format

Text file showing sample gedcom code with family tree data on a computer screen

The gedcom format is a standardized text-based file format used to store and exchange genealogical data, including individuals, families, events, sources, and media references. It was developed by the Church of Jesus Christ of Latter-day Saints in the 1980s and remains the most widely supported format for transferring family history records between different genealogy software applications.

Gedcom files use plain ASCII text with a hierarchical structure based on levels of indentation. Each line begins with a level number, followed by a tag (like NAME, BIRT, or FAM), and then the associated data. For example, a birth event might appear as:

2 DATE 1 JAN 1950
2 PLAC New York, NY, USA

This structure allows programs to parse the data consistently, regardless of the software used to create or read it.

While newer formats exist, gedcom remains the de facto standard for interoperability. Major genealogy tools such as Ancestry, MyHeritage, Legacy Family Tree, and Gramps all support importing and exporting gedcom files. The format aims to be human-readable and machine-parsable, making it ideal for long-term data preservation and cross-platform compatibility.

How GEDCOM Works

Gedcom uses a simple hierarchy where each line starts with a level number indicating its position in the data tree. Level 0 represents the root element-typically an individual or a family-and higher levels indicate nested relationships. For example:

0 @I1@ INDI
1 NAME John /Smith/
1 SEX M
1 BIRT
2 DATE 15 APR 1940
2 PLAC Boston, MA, USA
1 FAMC @F1@
1 FAMS @F2@

Each record begins with a unique identifier (like @I1@) and contains fields separated by tags. The system relies on consistent spacing and capitalization to ensure accurate parsing. Lines with the same level are siblings; lines with increasing levels are children.

Software interprets this structure by building a database or tree model from the text. When a program imports a gedcom file, it reads each line, checks the level and tag, and assigns the data to the correct entity. This process allows users to move their family trees between applications without losing core information.

Despite its simplicity, the format supports complex data. It includes fields for multiple names (including nicknames and alternate spellings), various life events (birth, marriage, death), sources, citations, media links, and even custom tags. These features make it suitable for detailed family research.

Types and Versions of GEDCOM

Several versions of the gedcom standard have been released since its inception. The most widely adopted version is GEDCOM 5.5.1, published in 2006. It introduced improvements such as better handling of multilingual characters, support for multimedia objects, and enhanced source citation structures.

A table below outlines key differences between major versions:

Version Release Year Key Features Adoption Status
GEDCOM 1.0 1985 Basic individual and family records Obsolete
GEDCOM 2.0 1988 Added support for sources and notes Obsolete
GEDCOM 5.5 2001 Improved multilingual support, better date formatting Widely used
GEDCOM 5.5.1 2006 Final official version; added media handling, improved source citations Standard

Although GEDCOM 5.5.1 is the current standard, some software still exports older versions due to backward compatibility requirements. The format's flexibility allows extensions through custom tags, though these may not be recognized by other programs.

GEDCOM does not enforce strict validation rules. As a result, malformed files can cause import errors. A single missing newline or incorrect level number can disrupt parsing. This limitation means users must verify exported files before sharing them.

Common Misconceptions and Pitfalls

Many users assume that a gedcom file contains everything about a person-photos, documents, and detailed narratives. This is incorrect. The format stores metadata and references, not the actual files. Media such as images or scanned documents are stored separately; the gedcom file only includes paths or URLs pointing to them.

Another misconception is that gedcom preserves privacy settings. It does not. Any sensitive data-such as living relatives' names, addresses, or private notes-will be included in the exported file unless manually removed. Users must review the contents before sharing.

A lesser-known issue is the lack of standardized encoding. While UTF-8 is recommended, many older files use ASCII or Windows-1252. This causes problems when transferring data across systems with different default encodings. A file created on a Mac using UTF-8 may display garbled text on a Windows system that expects ANSI.

I once encountered a case where a client exported a gedcom from a popular genealogy app. Upon importing it into another tool, several ancestors appeared with incorrect birth dates. After debugging, I discovered that the original software had used a non-standard date format (e.g., "1/15/1940" without specifying month-first or day-first convention). The receiving program misinterpreted the format, shifting dates by months. This highlights the importance of consistent data entry and verification.

Where and Why GEDCOM Is Used

Gedcom is used primarily in genealogy software to transfer family trees between platforms. It enables researchers to switch tools without rebuilding their work from scratch. For example, someone using RootsMagic can export a gedcom file and import it into Ancestry.com, preserving most of the data.

It's also used for backup and archival purposes. Because it's a plain-text format, gedcom files can be opened and edited in any text editor. This makes them durable over time-unlike proprietary binary formats that may become unreadable as software evolves.

Organizations like the FamilySearch International Genealogical Society and the National Archives of the United States recommend using gedcom for public data submissions. The format ensures consistency across large-scale digitization projects. For instance, FamilySearch's online database accepts gedcom uploads from volunteers who contribute their own research.

However, gedcom is not ideal for collaborative editing. Its flat structure doesn't support version control well. Multiple users editing the same file simultaneously can lead to conflicts. For shared projects, cloud-based platforms like Ancestry or MyHeritage offer better synchronization and conflict resolution.

What GEDCOM Is Not

Gedcom is not a database. It is not a real-time collaboration tool. It does not track changes or maintain audit trails. It is not designed for high-speed queries or large datasets. Unlike SQL databases or JSON-based APIs, gedcom lacks indexing, search optimization, or schema enforcement.

It is also not a replacement for structured data models. While it supports rich metadata, it lacks formal validation rules. This leads to inconsistencies across files. Two programs may interpret the same tag differently-one treating "FAMC" as a child's family of origin, another as a reference to a marriage contract.

Finally, gedcom is not secure. It contains no encryption, access controls, or authentication mechanisms. Sharing a gedcom file publicly exposes all personal data. Always remove sensitive information before uploading or distributing.

Understanding what is gedcom format means recognizing both its strengths and limitations. It is a foundational tool in genealogy, enabling data portability and long-term preservation. But it requires careful handling to avoid data loss, misinterpretation, or privacy breaches.


Related Posts