Open any family tree software and you'll see the same thing: a branching chart of names and dates, connected by lines representing marriages and children. It's a diagram of who existed and how they were related. It's organized, searchable, and extensible.
It's also flat.
The people in it — the great-grandparents who built lives in difficult circumstances, the relatives who made improbable journeys, the family members who shaped everything that came after — exist in those trees as data points. A name. A birth year. A place. A death date. A photograph if you're lucky.
A living family tree is something different. It includes the voices of the people in it. It contains first-hand accounts of what their lives were like. It has the kind of texture and personality that makes you feel like you actually know someone rather than just know about them.
Building one isn't complicated. But it requires a different way of thinking about what a family tree is for.
What Makes a Family Tree "Living"
The term is straightforward: a living family tree is one that contains living content — recordings, stories, memories, and perspectives — rather than just static records.
The key difference is presence. When someone opens a standard family tree profile, they see facts. When they open a living family tree profile, they can hear the person talk. They can read a first-hand account of what that person's childhood was like, what they valued, what they wanted their grandchildren to know.
That presence changes everything. It's the difference between knowing that your great-grandmother came to America in 1923 and hearing her voice tell you what she felt when she saw the coast for the first time. The second kind of knowledge is not just more interesting — it's more generative. It creates connection across generations in a way that bare facts cannot.
A living family tree is also designed to grow. It's structured so that future family members can add recordings and stories of their own, creating a resource that becomes richer over time rather than static after a certain point.
The Core Components
A living family tree has three layers.
The documentary layer is what you already have: names, dates, locations, relationships, official records. This is the skeleton that everything else hangs on. It provides verifiable facts and creates the structure that makes the tree navigable.
The oral history layer is recordings and transcripts from interviews with living family members. This is the layer that most family trees are missing. It's what turns names into people — what gives the skeleton a voice, a personality, a set of experiences.
The media layer is photographs, letters, documents, and other artifacts that provide visual and material texture. This layer is well-understood — most genealogists already work with photos and documents. Voice recordings slot into this layer as a specific type of media.
Building a living family tree means intentionally constructing all three layers and connecting them so that anyone navigating the tree can move fluidly between them.
How to Connect Voice Recordings to Tree Profiles
The mechanics depend on which platform you're using, but the principle is consistent: every person in your tree who has a recorded oral history should have that recording (or its transcript) accessible directly from their profile.
On FamilySearch:
FamilySearch has native support for audio in its Memories feature. Navigate to any person's profile, click the Memories tab, and you can upload audio files directly. They play in-browser and are associated with the person permanently. Add transcripts as Stories and source citations to complete the connection.
The collaborative nature of FamilySearch makes it particularly good for a living family tree — anyone in your family who accesses the profile can add their own memories, corrections, and photos, and you can all see each other's contributions.
On Ancestry.com:
Ancestry.com doesn't support direct audio playback from profiles, but you can attach transcripts as Stories and create source citations that link to audio stored externally. The practical approach is to store audio in a cloud service and maintain links from the Ancestry tree to the external files.
In a standalone archive:
If you maintain your living family tree as a self-managed archive rather than (or in addition to) a commercial platform, cross-reference recordings to tree profiles in your master index. Every recording should be linked to the specific individuals it discusses in a way that makes them findable when someone is researching a particular person.
Starting with the People Who Are Here Now
The most natural starting point for a living family tree is the oldest generation of living relatives.
These are the people who most urgently need to be recorded — not just because they're getting older, but because they have direct memories of people two generations further back. Your 85-year-old grandmother doesn't just have her own story. She has stories about your great-grandparents that exist nowhere else.
Start with a single interview. Choose one willing relative. Prepare a set of questions focused on their own life story and on what they know about the generations before them. Record the conversation. Get it transcribed. Attach it to the relevant profiles in your tree.
That's the first node of your living family tree. The structure is established. Now you can build outward.
Work systematically through the oldest generation first, then move to the next generation. Aim for at least one recorded session per person. Multiple sessions are better — people often remember different things in different conversations, and a second session usually produces material the first one didn't.
Structuring for the Future
A living family tree is worth building only if future generations can use it and add to it. This requires thinking about structure from the beginning.
Use platforms and formats that will last. Commercial genealogy platforms will change over time — some will merge, some will sunset features, some will be acquired. Don't rely entirely on any single platform. Maintain a local archive with copies of all recordings and transcripts, in formats (MP3, PDF, plain text) that will be readable on future devices.
Document your structure clearly. Write a one-page guide to how the archive is organized, where files are stored, how recordings are named, and how new recordings should be added. Store this guide in the archive itself. This is what allows the project to continue after you.
Share access intentionally. Choose two or three other family members who understand the project and give them full access to the archive. At least one should be in a different generation — a child or niece or nephew who will be around to maintain it in fifty years.
Make contribution as easy as possible. The harder it is to add something to the living family tree, the less it will grow. If your structure requires technical knowledge to add a recording, most family members won't do it. Consider using a service like LifeEcho for the recording layer specifically because it requires nothing from the contributor except a phone call.
Making It Navigable
A living family tree with hundreds of recordings is only useful if someone can find what they're looking for. Navigation is the design problem most people don't think about until their archive is already large and hard to search.
Build a person index. A simple document that lists every person in the tree who has associated recordings, with links to those recordings, is often the most useful navigation tool. Organize it alphabetically by surname, and include brief notes about what each recording contains.
Use consistent naming. Recording file names should always include the person's name, so searching a file system or archive for a name surfaces all the relevant recordings.
Tag by topic and generation. In your master index, tag recordings with the generations they discuss (e.g., a recording where your grandmother talks about her grandmother is tagged with both women's names and generations). This allows someone researching a specific time period or family branch to find all relevant recordings quickly.
Create entry points for different audiences. A grandchild doing a school project needs different access than a genealogist doing deep research. Consider creating a simple "family stories" folder with the most engaging recordings, separately from the full archive. This brings more people into the project and generates more contributions over time.
What Happens When You Have It
The families who have built living family trees describe a consistent experience: the recordings become what everyone wants to hear at family gatherings. They become what people share with children and grandchildren as a way of introducing them to relatives they never met. They become the artifact that holds the family together across distance and time.
A name and a date connects you to someone abstractly. A voice — telling a story, explaining a decision, describing what something felt like — connects you to someone actually.
The living family tree is the version of family history that people return to. Not to update the database, but because they want to spend time with the people in it.
Building It Is Not That Hard
The concept of a living family tree sounds ambitious. In practice, building one is a series of small, manageable steps: one interview, one recording, one attachment to one profile. Then another.
You don't need to capture everyone at once. You don't need to build the perfect archive before you start. You need to make one recording with one willing relative, and then make the next one.
The urgency is real — the people who can give you the oldest memories are the most time-limited. But the method is simple. A phone call. A question. A recording. A transcript. Attached to a profile in a tree that will outlast everyone in it.
LifeEcho is built to be the recording layer of your living family tree. Relatives call in on any phone, conversations are recorded and transcribed automatically, and you get clean files ready to attach to your tree profiles. Start building your living family tree with LifeEcho.