Loading route foundation…
getting started
A family tree shows relationships across generations. A family history archive preserves the sources, photographs, stories, timelines and context that explain those relationships and individual lives. The two are complementary: the tree is a map; the archive is the organized evidence and human history behind it.
A family tree is a structured representation of people and their relationships, usually showing descent, parentage and partnerships. A family history archive is a broader organized collection that can include the tree as well as person profiles, images, documents, oral histories, research logs, citations, conflicts, places and historical context.
A tree helps answer “How are these people connected?” An archive can also answer “What do we know about them, how do we know it, what did family members remember, and what remains uncertain?” Neither replaces the other.
A tree compresses complex relationships into a form people can scan. It can show ancestors, descendants, siblings, partners and family branches. Dates and places attached to profiles help distinguish people with similar names and support navigation between generations.
This structure is invaluable, but compression has a cost. A box joined by a line cannot fully explain an informal adoption, a disputed father, a name change, a second household, estrangement or the difference between biological, legal and caregiving relationships. Good tree software may support notes and sources, yet the visual tree remains primarily a relationship model.
A tree should therefore state the relationship it actually represents. DNA evidence, a birth registration, a step-parent relationship and a person raised as family may all matter, but they are not interchangeable. Respectful family history can preserve several kinds of truth without forcing them into one unlabeled line.
The Society of American Archivists explains that archives can hold unique materials in many formats, including letters, photographs, diaries, sound and digital equivalents. A family history archive applies organization and description to this broader body of material.
A tree may state that Samuel Lee was Ana Lee's father. The archive can preserve the baptism entry, census households, land record and oral account used to assess that relationship. It can record a conflict and explain why the current conclusion is provisional.
A profile and timeline can connect Samuel to his work, neighborhood, migration, church, schooling and community. Photographs and stories reveal relationships that a pedigree view does not express.
An archive records who created or supplied an item, where the original is held, who identified a photograph and whether use is restricted. This information helps future family members evaluate and responsibly reuse it.
Logs, negative searches, hypotheses and open questions show what has been attempted. FamilySearch's research-log guidance describes a log as a list of sources searched or planned, with the purpose of each search. This prevents repeated effort and makes unfinished work visible.
| Question | Family tree | Family history archive |
|---|---|---|
| Primary purpose | Show people and relationships | Preserve and explain family material and research |
| Typical unit | Person, couple or relationship | Item, person, event, story, source, place or question |
| Best at | Generational overview | Evidence, context, narrative and provenance |
| Sources | May attach to facts or profiles | Can be catalogued, transcribed and linked to claims |
| Conflicts | Often shown in notes | Can be tracked as competing evidence and analysis |
| Photographs | Usually attached to profiles | Described as archival items with creator, source and rights |
| Stories | Often short notes | Attributed narratives, recordings and transcripts |
| Research management | Varies by tool | Can include plans, logs, hypotheses and reports |
| Preservation | Not guaranteed | Requires an explicit preservation and backup process |
The table describes functions, not universal software limits. Some tree programs support rich media; some so-called archives are merely folders. The distinction is the design emphasis and the quality of organization.
Suppose a tree profile reads “Rosa Navarro, born about 1910, Iloilo.” Without a source, the next researcher cannot tell whether the information came from a civil record, a grave marker, an aunt's estimate or an online tree. If an image is attached without a caption, people may soon forget which woman is Rosa.
Records themselves are not infallible. The US National Archives cautions that historical records may retain original mistakes. Ages, names and relationships can vary because of informant knowledge, language, enumeration or transcription. A tree that silently chooses one value hides the evidence problem. An archive can keep each report, its source and an explanation of the conclusion.
An archive without navigational structure can become a digital attic. Users need routes through the material: by person, family, date, place, topic or collection. A tree is one of the clearest routes because it shows where a person sits in the family and opens related profiles and records.
The tree also reveals gaps. A missing parent, a child with no supporting record or two people accidentally merged becomes easier to notice. Used responsibly, it is both a discovery interface and a research map.
_Fictional example:_ Ben creates a tree showing his great-grandmother Lucia and her three children. His cousin contributes a photograph labelled only “Mama Cia at the shop.” An aunt remembers that Lucia sold cloth, while a city directory lists her husband as a tailor.
The tree connects Lucia to the descendants. The archive assigns an item number to the photograph, records who supplied and identified it, links it to Lucia's profile, transcribes the label and marks the shop ownership as unresolved. A research note asks whether the directory, licenses or newspapers can identify the business. The memory is preserved without being promoted to documented fact.
Use a tree-first approach when the immediate task is to establish basic relationships, identify missing generations or share a simple overview. Add archival structure when photographs are losing their identities, evidence needs evaluation, stories need attribution, several people are contributing, or the project must survive beyond one researcher's private files.
Most serious family projects eventually need both. Begin with a small, sourced tree and connect a manageable set of high-value records and stories. Expand only after the naming, description and backup routine is sustainable.
Consider what would count as success in the next three months. If relatives mainly need to see how two branches connect, a carefully sourced tree may be enough for the first phase. If the urgent problem is a box of unnamed photographs, begin with an item inventory and identification sessions, then connect confirmed people to the tree. If a disputed relationship is driving the project, prioritize a research question, evidence table and citations before designing a polished narrative.
Also ask who will use the material. Researchers may need image-level citations and conflict analysis; relatives may need approachable profiles and readable stories; a future custodian will need exports, filenames and a maintenance note. One archive can serve all three groups, but the navigation and access rules should be intentional.
Finally, test portability. Can the tree be exported? Can media and descriptions be recovered outside the application? Can another person understand the folder and identifier system? These questions matter more than the number of decorative features.
Do not assume a “private tree” or archive is private without checking actual access settings and export behavior. Limit details about living people, especially dates of birth, addresses, health, adoption, parentage, allegations and DNA. Ask for consent before publishing sensitive stories or identifiable photographs.
DNA relationships are probabilistic evidence that may reveal information about people who did not test. Keep raw DNA data outside ordinary public archive content and do not upload it to unverified AI systems. Copyright, data protection and access rules vary by location; this article is practical guidance, not legal advice.
The Roots Adventure Full Archive is suited to deeper work that may combine a tree with profiles, sources, research evidence, timelines, reports and open questions. The Roots Adventure Lite Archive emphasizes a basic tree, clear profiles, photographs, stories and easy contribution prompts. The right choice depends on whether the immediate need is intensive research organization, approachable family participation, or a staged combination.
Compare Full and Lite, view the Full Archive, or explore the Lite Archive.
A family tree and a family history archive solve different parts of the same problem. The tree makes kinship visible. The archive protects the records, stories, context and reasoning that give those lines meaning. Together they let a family see both the structure of descent and the evidence-rich lives inside it.
Editorial basis: International Council on Archives and Society of American Archivists definitions; US National Archives genealogy and record-integrity guidance; FamilySearch research-log and citation guidance; Smithsonian archival description examples; FTC genetic-privacy guidance.
A digital family history archive is an organized home for the records, research and stories that explain a family across generations. It connects a family tree to photographs, documents, memories, places and evidence so that people can understand not only who belongs in the family, but how those lives were lived and how each conclusion was reached.
Genealogy research needs enough structure to show what was searched, what each source reports and why a conclusion is reasonable. Family history needs room for voice, relationships, place and uncertainty. The answer is not to choose between a database and a narrative, but to connect them through people, events, sources and research questions.
Relatives do not need genealogy training to make valuable contributions. They can identify people, explain relationships, share memories, locate originals, describe places and traditions, correct mistakes and say what should remain private. A clear, low-pressure contribution process turns family knowledge into material that can be checked, attributed and preserved.
