How it works
The workflow, examples and limits behind every tool.
Members ↗
Each person has a stable ID independent of their name.
Example: Two people can have the same display name.
Parent-child relationships only; no spouse graph or GEDCOM import. Nothing is uploaded. Shared-device users can see locally saved family records.
Parent links ↗
Self-links, duplicate parents and ancestry cycles are rejected.
Example: Link Alex as a parent of Sam.
Parent-child relationships only; no spouse graph or GEDCOM import. Nothing is uploaded. Shared-device users can see locally saved family records.
Generation chart ↗
Generation is one beyond the highest parent generation; roots are generation zero.
Example: A parent and child occupy neighbouring generations.
Parent-child relationships only; no spouse graph or GEDCOM import. Nothing is uploaded. Shared-device users can see locally saved family records.
Print & export ↗
Long names are abbreviated in boxes; the full record remains editable.
Example: Move a JSON backup to another browser to continue editing.
Parent-child relationships only; no spouse graph or GEDCOM import. Nothing is uploaded. Shared-device users can see locally saved family records.
Local work, explicit limits
Each workspace reports its input and file limits. Imports validate the supported format before asking to replace saved work. Plain text is displayed as text, never executed as markup. Both languages use the same tools; the root address always opens in English, with Chinese under /zh/.