GEDCOM 7 Family Link Auditor
Inspect selected INDI/FAM pointers in an actual local GEDCOM 7 source file, preserving line evidence and separating missing targets from review observations.
Loading tool…
How to use GEDCOM 7 Family Link Auditor
Check the local relationship links in a small genealogy exchange file before reviewing it in your genealogy application. The report lists selected spouse/child family pointers, unresolved or wrong-type targets, explicit void pointers and reciprocal-link observations while retaining the original records for manual inspection.
- Choose a small local UTF-8 GEDCOM 7 file or load the generated fictional family example.
- Run the selected-link audit and inspect missing targets, target types and reciprocal-link observations by source line.
- Use the retained records for manual review without treating the report as full schema, privacy or genealogical validation.
Good to know
- One well-formed UTF-8 file of at most 200,000 bytes, 5,000 lines, 500 top-level records and 20 levels. An initial UTF-8 BOM is recorded and removed. CRLF, CR and LF are accepted; final line termination is required. Banned controls, malformed spacing, level jumps, repeated cross-reference IDs and non-record cross-references are refused.
- Requires first HEAD, childless final TRLR and exactly one HEAD.GEDC.VERS value of 7.0. Selected INDI/FAM records must have document-local IDs. This is not an older GEDCOM/ANSEL parser or a full version 7 schema validator.
- Only direct INDI FAMS/FAMC and FAM HUSB/WIFE/CHIL are resolved. Missing/wrong-type targets are evidence findings; absence of a reciprocal link is a review observation. A direct FAMC without CHIL membership can be permitted and is never automatically labeled invalid.
- Dates, names, biological/adoptive meaning, extension semantics, other relationships, resources and media are not interpreted or fetched. Raw source records and private notes remain in the downloaded evidence; this tool does not anonymize living people or establish genealogical truth.
- Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.
Common questions
Does a missing return pointer prove that a family relationship is invalid?
No. The report distinguishes unresolved IDs from missing selected reciprocal pointers. In particular, the GEDCOM specification permits some FAMC pointers without direct CHIL membership. Review the original record context in a trusted genealogy application.
Is this input sent to a server?
No. The application processes this input inside your browser tab and does not save it to persistent storage.
Keep going with related tools
All files →Text File Encoding Converter
Decode a local text file with an explicit charset and export UTF-8 with chosen BOM and newline handling.
TextText Diff
Compare two texts line by line and download an easy-to-read difference report, entirely in your browser.
DataStructured Data Redaction Preview
Replace or remove explicitly selected JSON Pointer fields and show a transparent local change report.
EducationFamily Relationship Path Workbench
Trace two people through your supplied parent links and export closest-common-ancestor paths, generation counts and limited cousin-pattern evidence.