Private GEDCOM subset, family map and relationship report
A local file desk for carefully sharing a family branch. Review the source relationships and privacy choices before producing a new, bounded subset.
Family Tree File Desk
The example has four people, two families, an adopted relationship, uncertain dates, a linked source and an external media path. Nothing is fetched.
Supported scope: UTF-8 GEDCOM 5.5.1/7.0.x up to 8 MiB, 100,000 lines, 5,000 records and 2,000 people; subset up to 200 people, diagram/print HTML up to 60. PDF uses a bundled Latin/Greek/Cyrillic font; use SVG/print HTML for unsupported glyphs. No GEDZIP/media embedding, ANSEL/UTF-16, record merging, online account import or full semantic certification.
Genealogy source
Required fields are marked with an asterisk.
Family subset desk
Review your output, then save it to your device.
Make the next step clear.
Your findings, assumptions and next steps will appear here after you run the check.
Family Tree File Desk · https://ancestryfiles.kitforma.com/ · KitForma
GEDCOM 5.5.1 and 7 UTF-8 parsing
Conservative privacy and explicit reference audit
GEDCOM, relationship SVG and printable PDF listing
Understand the evidence.
Focused guides explain the rules, the edge cases and the checks worth doing before you act.
Share a bounded GEDCOM family subset
Select the intended records and keep an audit of removed references.
Read the guide ↗Field guide / 02Review conservative living-person redaction
Use automatic rules as a starting point for a human privacy decision.
Read the guide ↗Field guide / 03Read GEDCOM links, dates and relationship diagrams
Keep source structure distinct from historical conclusions.
Read the guide ↗Before you start
How does automatic living-person privacy work?
Anyone without DEAT Y or a death-date structure is treated as potentially living. Their name becomes Private person and only supported family links remain. You can mark additional IDs private. This is conservative but not proof of anonymity: record IDs, relationships and retained text can still reveal identities.
Are notes and source documents preserved?
In privacy mode, notes, sources, media, custom fields and ancillary records are removed. If you deliberately turn privacy off, reachable ancillary records and source links are retained where they remain inside the subset. External media paths remain text; files are never fetched or embedded.
Does family-link distance mean generations?
No. One step follows membership in a family record and may reach a partner, parent or child. The diagram is a relationship map in source record order, not an inferred biological pedigree. Multiple families and adoption labels are retained when supported.
Can I recover broken or missing people?
No. Missing cross-reference targets are reported. The exported subset removes pointers whose targets are absent instead of inventing records. Keep the original and investigate missing people in the source genealogy application.
Will uncertain dates be converted to calendar dates?
No. Expressions such as ABT 1980, BEF 2000 and date ranges remain literal source text. The tool does not infer an exact birth date or assume that an old birth date proves a person is deceased.
What can I download?
A new GEDCOM subset, a privacy/reference audit, a relationship SVG, offline print HTML and a PDF relationship inventory. Diagrams support up to 60 people; GEDCOM and PDF listings support up to 200. PDF glyph coverage is explicit, and the original file is never overwritten.
Sources & assumptions
Formats, algorithms and supported features are documented below. Check the stated scope and inspect your output before using it.
- FamilySearch GEDCOM 7 ↗
The structured text, pointer and family relationship specification.
- GEDCOM specifications ↗
Official version documents for 5.5.1 and 7.
- GEDCOM 5.5.1 errata ↗
Published clarifications to earlier interchange semantics.
Reviewed 2026-10-19. Read our methodology or report an issue.