I built this as a side project because I found existing family tree tools either too bloated or too manual—I spent more time dragging boxes and aligning lines than actually mapping my family history.
My goal was to make it instant: you just add the names, and the auto-layout engine handles the hierarchy and spacing automatically. It runs entirely in the browser and exports high-res PNG/JPGs.
Would love feedback on the layout logic (especially for complex families) and the overall UI flow. Happy to answer any questions!
I always wanted to make such a tool for myself but never sat to actually build it. User experience was a breeze.
I see that there is no import button. Adding Import will help many of us to keep editing the same tree instead of building it from scratch everytime. You can add a JSON export of the tree and then users can import this JSON to make edits. I can also share this JSON with other family members.
Thanks for the feedback! I’m glad the UX felt seamless—that was definitely the hardest part of the project.
Implementing JSON import/export is at the top of my roadmap for persistence: letting users "save" their progress locally without needing a cloud backend.
I’m working on the data schema for this right now. Stay tuned!
Great, keep us informed and let me know if any help is needed.
Love the simplicity. Most family tree tools are so bloated that it feels like a chore just to add a cousin. One quick question: Since it runs entirely in the browser, are the family names and data stored locally, or do you have a backend keeping track of the trees? Privacy is always a big concern for people when it's about family history.
Thanks! I’m glad the simplicity resonates with you—fighting against genealogy bloatware was exactly what I wanted to avoid.
As for privacy, everything stays in your browser. There’s no backend database tracking your family history.
The data is stored locally (via LocalStorage), so if you refresh the page or come back later, it’ll still be there—but I never see it.
Love how simple this is! It would be great if there you were able to add siblings without having a parent added first. And being able to add a child with only one parent present as well--there's an error that states the parent needs a spouse before adding a child.
Thanks! You’re right that adding siblings without a parent is tricky from a data-structure perspective—they need a common parent or family node to define the relationship.
To solve this without breaking the tree structure, I’m planning to support "single-parent" nodes. This will allow you to create an empty or placeholder parent to group siblings together without needing a spouse.
This should give you the flexibility you’re looking for while keeping the underlying hierarchy intact. Thanks for helping me refine these edge cases!
[dead]