A chart with no crossing lines
What cannot be drawn cleanly waits behind a “Has more relatives” marker.
Upload your GEDCOM file — gedcom.me checks the tree: it finds duplicates by comparing families, tidies names and places and shows them in your language, and draws a chart where lines never cross. Living relatives are seen only by the people you invite.
gedcom.me fixes on its own only what cannot go wrong. Everything else — merges, patronymics, Sr. and Jr. — it suggests, and you decide.
1 NAME MARY /TAYLOR/ 1 NAME Gerhard G /Hamm/ 2 PLAC Korytnica akt 137, Węgrów 1 NAME Paweł /Raczkowicz/ h. Łabędź Everything the service does with a tree, by section. Each picture shows how it looks in the tree itself.
The tree chart is drawn without crossing lines, and families joined twice and the order of marriages are shown as they were.
What cannot be drawn cleanly waits behind a “Has more relatives” marker.
It happens when two families are joined twice: two brothers marry two sisters, or a widow marries her husband’s brother. A second card with a “×N” button jumps between them.
By marriage date; undated marriages can be moved, and the order is the same on the chart and in the card.
Birth and adoptive parents, disputed parentage, a child still on the way — everything is recorded as it is, not squeezed into a template.
A baptism record names one set of parents and another document a different one? Keep both versions with their documents and switch the branch on the chart. Once it is clear, confirm the main one; the other stays a hypothesis.
Adoptive and foster parents are added beside the birth parents, not instead of them. On the chart such a link is labelled separately.
A child can be added before birth; the name, sex and date can come later. The card shows the expected date, and once it has passed, the data checks remind you to update the record.
A role in the family — husband, wife or partner — does not depend on sex, a marriage need not be recorded, and a child can have two parents of the same sex. The family is shown as it is recorded.
Two records are compared not only by name and date but by parents, spouses and children. The service suggests, you merge — and a merge can be undone.
Records are compared by parents, spouses and children — in one table, differences first. You merge, and a merge can be undone.
Likely different people: the records name different fathers.
Both duplicates have a daughter Anna — two cards. That pair is offered for merging along with them; you decide whether to tick it and which fields to keep.
Mark them Daniel Smith Sr. and Daniel Smith Jr. with one button, and the pair is no longer a duplicate.
Search across all trees; linked only after you confirm, and only the facts you tick are copied.
The “Checks” page groups findings by kind. Safe fixes take one button; the rest let you choose row by row.
One button for the whole group; the history shows what was, what became and which rule did it.
For Russian, Ukrainian and Belarusian names the tree shows “Petrovich” at once; it is written to the card after you tick it.
A summary of changes record by record; cards keep their IDs, and people missing from the file are not deleted.
The spelling from the source is kept, while the display follows the language you read in.
A person can have several spellings — from GEDCOM, FamilySearch or added by you. The one chosen in settings is shown; by default, the interface language.
A name is entered once, in ordinary letters. The surname or the whole name in capitals is a display setting; the record stays as it is.
No need to remember how a name was entered — in its old form or today’s, in Cyrillic or Latin letters: “John” finds Іоаннъ, Jan and Johann alike.
Found by search both as Robert and as William.
In old Russian records Peter Andreev means Peter, son of Andrei. It stays that way: “Andreevich” is not added.
The spelling from the record is kept, and in Russian Heinrich reads as Генрих — from the dictionary, not letter by letter.
Ona Kazlauskas — the men's form for a woman. Your choice: Kazlauskaitė, Kazlauskienė or Kazlauskė.
Place names are matched with Wikidata and GeoNames. Every place has a card with a map and its names in different languages.
Every place is linked to Wikidata and GeoNames: a map, names in several languages and what the town was called in the year of the event.
Place: Lorain, Ohio, United States; “Age: 43” goes to the event's description.
Węgrów, Wegrow and Венгрув in different records. One group: for each spelling, “replace with” across all records.
A moderator picks the place seeing only the name — no people, no trees; the choice applies to every tree whose owner has not decided.
All the tree's photos and documents in one album, however many people a picture shows. Surname albums build themselves, copies and cut-out pieces are found on their own, and headstones and coats of arms are kept apart from family photos.
A portrait cut from a group photo is found on its own. The person gets a frame in their place on the whole photo, and the leftover piece is offered for removal from the tree.
The same photo uploaded again — in another size, rescanned or from another site. The best copy stays, and the people tagged on the others, with their faces, move to it.
Faces are found right in your browser, without a neural network, and offered to you rather than tagged by themselves.
Pick several people and only the photos where they are all together remain. A husband's and wife's surnames can be viewed as one album.
Search archives and work through documents right from a person's card. What you find is a lead to check, not a ready fact.
Search from the card: Geneteka, Metrikai.lt, Open Archives and more; the period comes from the life dates.
What a document says is compared with the tree; Claude reads the scan's text when you press the button, as an unreviewed transcription.
Relatives, links and events go into a separate tree in your account.
Claude or another client reads the tree itself; read-only by default.
Invite relatives by e-mail: each works in their own role, the history shows who changed what, and any edit can be undone. Invitations need the tree owner’s paid plan; the history and undo work on any plan.
Everyone in the tree with an e-mail is a participant. The invitation arrives as a letter with a link; you choose the role — from viewer to admin — and which person in the tree they are. You can also open a single branch for 1–365 days.
The settings show each participant’s last visit and number of changes, and “See the changes” opens the tree’s history with only their edits.
The history shows who, when, what it was and what it became — and by which rule. “Undo” is right there in the tree’s history and in the person panel; deleted items can be restored for 30 days.
gedcom.me hides everyone who may be alive from accounts without a role in your tree — on the server, before any data is sent.
The free plan covers your own trees: import and export, checks and photos. The paid plan lifts the limits and adds documents, archive search, collaboration, AI and the world tree.
For getting started and trees of up to 100 people
For large trees, documents, archives and working together
These are launch prices — the regular ones will be twice as high. Prices may change if archive search needs a costly integration.
A tree’s limits and features follow its owner’s plan, including for the members who work in it. The world tree follows your own plan.
It is built from the requests of people who keep a tree and fixes what gets in the way: duplicates are checked against the family, names and places are tidied without losing how they were written, and the chart never tangles its lines. The service fixes by itself only what cannot go wrong and suggests the rest. A tree from another program or site comes in as GEDCOM and goes back out with nothing lost.
From any program that saves a GEDCOM file (.ged): MyHeritage, Ancestry, Gramps, RootsMagic, Family Tree Maker and others. A tree on FamilySearch comes over directly once you sign in to FamilySearch. The original file is kept with the tree, and a repeat import updates the tree without deleting anyone.
Yes. The free plan covers your own trees: import and export, checks, up to 100 people per tree and 500 MB for photos. The paid plan removes the people limit, gives 20 GB and adds documents, archive search, collaboration, AI connections and the world tree.
You and the people you invite. Users on the paid plan may see deceased people from your tree in matches and the world tree, in limited form: names, dates and places, but no notes, photos or documents. People who may be alive are never shown to them.
Yes. Invite them by e-mail and choose a role — from viewer to admin — or open a single branch for 1–365 days. The history shows who changed what, and any edit can be undone. Invitations need the tree owner’s paid plan; the history and undo work on any plan.
A person who is not marked as deceased and has no date or place of death counts as possibly alive if they were born less than 110 years ago or their birth date is unknown. Record deaths, even approximate ones, so that deceased ancestors are not hidden.
Yes. Export any tree as a GEDCOM file at any time and download the original file you imported. For a full copy including photos and documents, write to [email protected].
Only when you ask. The “Read text from the scan” button sends the scan you chose to Anthropic, and the translate button sends the text you chose to Google Translate. Your own AI assistant sees a tree only if you connect it over MCP, and by default it can only read. Checks, duplicate search, names, places and faces on photos work without AI. We do not train models on your trees, and Anthropic does not use data received through its API for training.Every archive, database and site the app asks, with its terms and last check, is on the Sources page.
Write to [email protected] — you do not need an account. We will ask the tree’s owner to correct or remove the information and, for people who may be alive, act ourselves if they don’t. See the Living persons policy.
Export your trees first, then write to [email protected] from your account’s e-mail address. We delete the account and the trees you own within 30 days.
A GEDCOM from any program, a tree from FamilySearch or a new one from scratch.
By creating an account, you agree to the Terms of Service and confirm that you have read the Privacy Policy. You must be at least 16 years old.