Build a Family Tree With Photos of Every Relative
A name is a starting point, a face is a memory. Add photos to every member of your tree and bring your heritage to life.
Family Tree Simple makes it effortless to add and manage photos. Upload from any device, crop with a tap, and watch your tree transform from data to legacy.
One-Tap Photo Uploads
Upload directly from phone, tablet or computer. Photos are automatically optimised and cropped to a square avatar, no editing software required.
Photos in Every View
Faces appear in the tree diagram, card view, list and table, and on every shared link and exported PDF. Your family's gallery, beautifully presented.
Privacy You Control
Photos are private by default. Choose exactly which relatives can see and edit your tree, or generate a public read-only link to share more widely.
Give each photograph a reliable identity
A photograph makes a family tree easier to recognise, but a mistaken identification can spread just as easily as an incorrect name. Before attaching an image to a person, record who identified the subject and what supports that identification. A note on an album page, a relative's memory and a dated document are different kinds of evidence.
Do not assume the person nearest a handwritten name is necessarily the named subject. The writing may refer to the photographer, the recipient or someone outside the frame. Preserve the context and ask a focused question before making the association permanent in a shared tree.
If the identification is uncertain, keep the photograph in an organised research folder with a descriptive label. “Possibly Maria at the family home” is more honest than presenting an unconfirmed portrait as certain. You can still use the image as a research lead without allowing a guess to become part of the family's accepted record.
Preserve an original before making a display copy
Keep an untouched digital original of every important scan or photograph. Make a separate copy for cropping, rotation or display in the tree. This preserves the full frame, borders and any visual details that may become useful later, even if a small portrait crop looks better on screen.
Use descriptive filenames that remain understandable outside the application. A name, approximate date and short context are often more useful than a camera-generated number. If the date is uncertain, make that clear in the filename or accompanying note instead of creating false precision.
Store the original and its context together. A scan of the reverse side, an album-page reference or a note from the owner may explain the image better than the picture alone. Keep a simple inventory so you can find both the display copy and the source material when another relative asks about it.
Choose a portrait crop that helps recognition
For a person card, a clear face usually matters more than a large surrounding scene. Crop a display copy with enough space around the head that the interface does not cut off important features. Check the result at the small size the tree actually uses, not only in a full-screen image viewer.
Do not enlarge a tiny face so aggressively that the image becomes misleading or unreadable. A modest crop with visible context may be better than a heavily processed portrait. If an image is restored or altered, preserve the original and identify the edited version in your records.
A group photograph may be better kept as a family document rather than forced into one person's portrait. If you create individual crops, connect each crop back to the complete group image. That relationship helps later researchers understand where the portrait came from and who else appeared in the scene.
Add useful captions instead of repeating the name
A good caption adds context: the approximate date, place, event and source of the identification. If the person card already displays the name, repeating it alone contributes little. Explain what a viewer could not infer from the image.
Keep observations separate from interpretation. “Three people standing outside a house” describes the picture. “At the family home after the wedding” may depend on a relative's account. Both can be recorded, but the origin of the second statement should remain clear.
Where the tool's current interface does not provide every field you need, maintain the extra context in a separate photo log. Use a consistent image identifier to connect the log to the tree. Do not lose the evidence simply because the visible portrait area is designed to stay compact.
Handle uncertain dates and locations
Photographs often lack exact dates. Clothing, vehicles, buildings and the apparent ages of known people can provide clues, but a clue is not the same as a documented date. Record an estimated range and explain the basis if that estimate matters to the research.
Avoid copying a date from a digital file's creation time and treating it as the date of the original photograph. A scan made recently can depict an event from decades earlier. Keep the digitisation date separate from the date of the scene.
A place name may also need qualification. A relative may remember the region but not the exact house or town. Record the level of certainty you have and preserve the original wording. A future comparison with another image or document may allow a more precise identification.
Ask before sharing photographs of living people
A family tree can move from a private working record to a shared link or printed chart. Before that happens, consider who appears in the images and what they expect. A relative may agree to a private family copy but not to a publicly accessible page.
Be especially thoughtful with photographs of children, private homes or sensitive family situations. You can choose a different image, omit the portrait from a shared version or restrict the audience through the controls available to you. The fact that a photo exists in an old album does not automatically settle whether it should be published online.
Keep track of the intended audience for a shared export. A PDF or downloaded image may be forwarded beyond the original recipients. Review the visible details before sending it and explain any sharing preference directly to the people receiving the file.
Organise a collection before uploading everything
A small, well-labelled set is easier to manage than hundreds of unidentified images. Sort the collection into useful groups, such as person, household, event or source album. Keep duplicates together so you can choose the best display copy without losing the original versions.
- Give each important image a stable identifier.
- Record the people shown and any uncertainty about their identities.
- Separate the scene date from the scan or download date.
- Retain the full image and reverse-side information.
- Create display copies without overwriting originals.
- Review the intended audience before sharing.
Start with a few portraits that have strong identifications. Add more as the research supports them. A tree does not need a photograph for every person to be useful, and an empty portrait is preferable to the wrong face.
Example: a group photograph with two similar names
Imagine an album contains a wedding group with a note naming “Aunt Rose.” The family includes two people known by that name, and neither is labelled directly in the picture. One relative believes the person on the left is the older Rose, while another remembers the younger Rose attending the event.
Keep the complete image and record both accounts with their sources. Compare the event date, known ages and other identified people. If another photograph provides a reliable comparison, you may be able to resolve the identification. Until then, avoid using an uncertain crop as a definitive portrait in the public tree.
This approach preserves the image's value while preventing a guess from hardening into fact. The research note also gives another family member a clear question to help answer rather than presenting a conclusion they may assume has already been verified.
Review photographs in the finished chart
After adding portraits, view the tree at its normal zoom and on a smaller screen. Check that faces remain recognisable, crops are not awkward and the images do not make names harder to read. The portrait should support the relationship chart rather than dominate it.
Review a print or PDF separately. A photo that looks clear on screen may become too small in a chart containing many generations. Consider using fewer portraits or splitting the chart into branches if the output becomes crowded. Keep an overview for relationships and a separate photo document when that better serves the audience.
Check that every displayed image is attached to the intended person. Similar names and repeated family names make a final identity review worthwhile. A quick scan of the chart by someone familiar with the family can catch a misplaced portrait before it is widely shared.
Keep the photo collection portable
Maintain your own organised copies alongside the tree. Do not assume that a genealogy data export will contain every image file in a form another application can immediately display. Transfer formats and media handling differ, so test a small export and import before relying on it as your only photo backup.
A useful backup includes the original images, display copies, captions and the log connecting them to people. Store it somewhere you can access independently of a single application. Check that the files open and that the labels remain meaningful rather than only confirming that a folder exists.
As the family contributes new material, keep the same naming and evidence habits. A consistent collection becomes easier for the next person to inherit, and the tree remains a clear guide to the people behind the photographs rather than an unexplained set of pictures.
Tools for your family history
- Drag-and-drop photo uploads
- Automatic crop and optimisation
- Photos appear in every view and export
- Private by default, share when ready
- Free with no storage paywall
Frequently asked questions
What photo formats are supported?
JPG, PNG and most common image formats. Photos are optimised automatically to keep your tree fast.
Is there a storage limit?
There is no artificial cap on storage. Upload a photo for every relative.
Can I update photos later?
Of course. Edit any member to swap or remove their photo at any time.