GEDCOM 5.5.1 vs. 7.0: What Actually Changed

GEDCOM 7.0, released in 2021, was the first major revision to the format since 5.5.1 — a gap of over two decades. If you're moving a file between programs or platforms, the version mismatch is often the quiet reason things don't come across cleanly.

Unicode handling

5.5.1 allowed several character encodings, including UTF-8, UTF-16, and the older ANSEL encoding built specifically for genealogical characters. This flexibility is exactly what causes garbled names — if a program that reads a 5.5.1 file guesses the wrong encoding, accented and non-Latin characters render as gibberish. GEDCOM 7.0 requires UTF-8 only, closing off that ambiguity for any file created fresh in a 7.0-compliant program.

Structured citations

5.5.1's source citation model was loosely defined enough that different software implemented it in incompatible ways — a citation built in one program often didn't survive a round trip through another. GEDCOM 7.0 introduced a more rigorously structured citation model specifically to fix this cross-program portability problem.

Media and GEDZIP bundling

In 5.5.1, media files (photos, documents) were referenced by file path or external link, which broke constantly when a file moved between computers — the classic "photos went missing" complaint. GEDCOM 7.0 introduces GEDZIP, a container format that bundles the GEDCOM data and its referenced media into a single zip file, so photos travel with the tree instead of being left behind.

NAME structure and RELA/ROLE mapping

5.5.1 stored names largely as a single formatted string with optional sub-parts. GEDCOM 7.0 expands this with more granular sub-structures and a clearer RELA (relationship) and ROLE mapping for how individuals relate to events and each other — useful for software that wants to reason about relationships programmatically, but it means a 7.0 file's NAME records won't necessarily parse the same way in software only built for 5.5.1.

Date qualifiers got clearer rules

Both versions support qualifiers like ABT (about), BEF (before), and AFT (after) for uncertain dates, but 5.5.1 left some edge cases — date ranges, dual dates spanning the old Julian/Gregorian calendar switch — loosely specified enough that different programs handled them inconsistently. GEDCOM 7.0 tightens the date grammar so a range or a calendar-spanning date parses the same way regardless of which program wrote it.

What this means practically

None of this is backward-incompatible in a way that breaks basic file reading — a 5.5.1 file will generally open in software with 7.0 support, and vice versa in simple cases. But full-fidelity round-tripping (keeping every citation, every media link, every structured detail intact) between a 7.0-native program and a 5.5.1-only one is not guaranteed, and this is a real source of the "some records were not uploaded correctly" pattern described in Why Does My GEDCOM Upload to FamilySearch Keep Failing?.

As of 2026, GEDCOM 7.0 support across genealogy software is still uneven — some major platforms have added it, others remain 5.5.1-only. If you're not certain your destination platform supports 7.0, exporting as 5.5.1 remains the safer default. Run your file through the Upload Readiness Checker to confirm which version you're working with before you upload.