A GEDCOM file is the common language that lets your family tree move between programs, and understanding what it does, and does not, carry is what makes it a reliable exit plan.
The useful test is not how quickly a page appears. It is whether you can identify a person correctly, record uncertainty, attach evidence, protect living relatives, and keep a usable copy. A careful approach can do all of that, but only if you set up the first steps deliberately.
GEDCOM file explained: what a useful result looks like
GEDCOM is a text-based standard for exchanging genealogical data between different software. The reliable result of using it is portability: your people, relationships, and many facts move from one tool to another. A common surprise is that some custom fields and media may not transfer perfectly, which is why testing a GEDCOM before trusting it matters.
This suits a beginner with a handful of known relatives as well as a researcher moving notes out of paper files. Start with a small, documented piece. A short, checked result is more useful than a large one copied without evidence.
Whether your notes call the task the GEDCOM format or a GEDCOM export, keep one verified master and treat any display, download, or shared page as a purpose-built version.
Before you begin
Brief preparation prevents crowded results, incorrect relationships, lost context, and privacy repairs. Write down the rules used across each branch.
1. Define the scope
Decide why you need GEDCOM: to switch tools, back up, or share, since each affects what to check.
2. Prepare the information
Note which data matters most, notes, sources, media, so you can verify it survives.
3. Protect the working copy
Keep the original tree intact until you confirm the GEDCOM imported correctly.
A practical step-by-step method
Work from the focal person or a small test group. Review each stage before adding more, because a sample is easier to repair.
1. Understand what GEDCOM is
Learn that GEDCOM is a standard text format for exchanging family tree data.
Knowing it is a transfer format, not a program, sets the right expectations. Before moving on, compare the result with the original notes and correct any field that gained more certainty than the source supports.
2. Know what it carries well
Recognise that people, relationships, dates, and many facts transfer reliably.
Understanding the core content tells you what you can count on moving. Pause here for a visual check: someone who has not seen the project should be able to explain what the box, line, or file represents.
3. Know its limits
Learn that media, custom fields, and formatting may not transfer perfectly.
Anticipating limits prevents alarm when a photo link or custom note shifts. Record the decision in a brief note so a later editor knows why this arrangement, label, or storage choice was made.
4. Export a GEDCOM from your tool
Produce a GEDCOM file from your current program’s export function.
A clean export is the starting point for any transfer, backup, or share. Use a small sample first. If the sample survives editing, exporting, and reopening, repeat the same method for the remaining work.
5. Import and inspect it
Bring the GEDCOM into another tool and check people, sources, and notes.
Inspection confirms the transfer worked before you rely on it. Keep the working version separate from the final display copy, because research corrections are normal and should not damage an earlier reviewed edition.
6. Keep media and a backup separately
Save photos and documents alongside the GEDCOM and keep a dated copy.
Media often travels as links, so a separate copy protects your images. Ask whether this step protects identity, evidence, readability, and future access; if one is missing, revise before adding more.
Choices that change the result
The following decisions change what the final result can communicate and how easily it can be corrected. Make each choice according to the project, not because a default happened to be selected.
GEDCOM for transfer or for backup
It serves both, but a backup also needs the media stored separately, since GEDCOM may link rather than embed images. Use this option only when it supports the intended audience and final size; a feature that looks useful on screen may not survive later use.
Trust the export or test it
An export button is only useful if the file imports correctly. Test with an inspection before relying on it. Treat this as a documented choice rather than a default. Write down the trade-off so relatives can understand and revise it later.
Structured data or a picture
GEDCOM carries structured relationships; a PDF carries appearance. Keep both when you need portability and readability. Test the choice with one small case that includes a long name, an uncertain date, and a relationship that needs an explicit label.
Latest standard or compatibility
Newer GEDCOM versions carry more, but the receiving tool must support them. Match the version to what both programs handle. The right setting keeps the project clear without pretending that every family, record, or tool behaves in the same way.
Common mistakes and how to repair them
Treating “Understand what GEDCOM is” as optional
Rushing this point can leave the result attractive but hard to verify or revise. Return to the practical instruction: Learn that GEDCOM is a standard text format for exchanging family tree data. Then compare the change with the original notes, save it under the correct version, and ask whether a reader could understand the decision without being present.
Treating “Know what it carries well” as optional
Rushing this point can leave the result attractive but hard to verify or revise. Return to the practical instruction: Recognise that people, relationships, dates, and many facts transfer reliably. Then compare the change with the original notes, save it under the correct version, and ask whether a reader could understand the decision without being present.
Treating “Know its limits” as optional
Rushing this point can leave the result attractive but hard to verify or revise. Return to the practical instruction: Learn that media, custom fields, and formatting may not transfer perfectly. Then compare the change with the original notes, save it under the correct version, and ask whether a reader could understand the decision without being present.
Treating “Export a GEDCOM from your tool” as optional
Rushing this point can leave the result attractive but hard to verify or revise. Return to the practical instruction: Produce a GEDCOM file from your current program’s export function. Then compare the change with the original notes, save it under the correct version, and ask whether a reader could understand the decision without being present.
Evidence, privacy, and responsible sharing
Use an outside reference for methods and definitions, then evaluate each record in the context of your own family. FamilySearch GEDCOM specification provides a useful starting point at FamilySearch GEDCOM specification. A search result or another person’s tree is a lead until identity and relationships are supported.
For each important fact, preserve enough citation detail to locate the source again: repository or website, collection, item or image number, event, date, and access information. Attach a source to the fact it actually supports rather than assuming one document proves every statement on a profile.
Privacy review is a separate task from factual review. Remove exact living-person dates, contact information, sensitive stories, and unapproved photographs from public or classroom copies. Preview the final file or link as a recipient, because an editor screen can hide what a shared view reveals.
Run a final quality-control pass
Read the work in both directions. Start with the focal person and trace outward, then choose an outer point and trace back. This catches a connection that points to the wrong place even when every individual name is spelled correctly.
- Confirm names, alternate spellings, and repeated people.
- Check that dates are possible and uncertainty is visible.
- Verify every relationship and connection in scope.
- Review source numbers, captions, and ownership notes.
- Inspect readability, layout, and how the result will be used.
- Open a backup on a second device and keep a dated copy.
Use the related term transfer a family tree only where it describes the project accurately. Natural language and precise labels help readers more than repeating a keyword in every heading or paragraph.
Turn the finished work into useful family history
For the central workflow and related tools, continue to the genealogy records guide. It keeps this topic connected to the main resource instead of leaving the article as an isolated tip.
Next, use the live supporting guide to move records with GEDCOM. That second step adds context without sending readers to a future article that has not yet been published.
Use this GEDCOM file explained as a reviewed version of family knowledge, not a substitute for the records and conversations behind it. Save the evidence, label uncertainty, protect living people, and update the result when a better source changes the story.
Frequently asked questions
What is a GEDCOM file?
It is a text-based standard for exchanging genealogical data between different programs. Think of it as a common language: it lets your people, relationships, and many facts move from one family tree tool to another, which makes it your main exit plan and backup format.
What does a GEDCOM file include?
It reliably carries people, relationships, dates, and many facts and notes. What may not transfer perfectly are media files, custom fields, and formatting, so it is best to know the limits in advance and check the important data after any transfer.
Will my photos transfer in a GEDCOM?
Often not directly. Media frequently travels as links rather than embedded images, so photos can be left behind when a tree moves. Keep your images and documents saved separately alongside the GEDCOM so they are not lost in a transfer.
How do I know a GEDCOM exported correctly?
Import it into another tool and inspect the people, relationships, sources, and notes before relying on it. An export button is only useful when the resulting file actually reopens with your data intact, so testing is the step that confirms your exit plan works.
