Search for Ancestris and Google's first page is almost all the project's own documentation, plus a Facebook thread asking whether anyone has used it. The plainest written verdict we could find is a genealogy blog post from 21 November 2014. It gave the program 1 out of 5 stars and put "Not intuitive or easy to use at all" at the top of its cons. The current stable release, Ancestris 13, came out at the end of November 2025, and version 14 is rebuilt every day. That verdict describes a program eleven years gone, so we downloaded version 13 and read its documentation to see what it is now.
Your tree is a GEDCOM file, and the whole design follows from that.
Most desktop genealogy programs keep your research in their own database and use GEDCOM only to move it in and out. Ancestris has no separate database. Its homepage says so in one line: "Your data is only in a Gedcom file, so never lost or unreadable by other software". When you edit a person, you are editing that file, and saving writes it. The code descends from GenJ, an older open-source Java genealogy program, and the core classes inside the version 13 download still carry the genj name.
It is free under the GPL version 3, with no limit on the number of people, and it is built by volunteers who spend donations on promoting it at genealogy and computing shows. There is no paid tier to hold anything back. That puts it in the same family as Gramps, but the two make opposite bets. Gramps stores more than GEDCOM can carry and warns you against archiving in GEDCOM, as our Gramps review explains. Ancestris never holds anything the format can't express, so nothing gets lost on the way out. The price is that your tree can only be as detailed as GEDCOM allows.
The promise that nothing is lost covers what Ancestris reads, and no more.
The project's pitch is that your data comes through intact. The migration guide is more careful than the summary. Ancestris recognises exports from more than a dozen programs, RootsMagic, Family Tree Maker, Legacy, Gramps and MyHeritage among them, and rewrites each one closer to standard GEDCOM, listing every change it made. It saves the result under a new name and leaves your original export alone. The guide says it "will recover all data read" and that "None of your original data is lost."
The word to notice is read. The guide names two ways data goes missing: your old program leaves it out of the export, or it arrives but lands somewhere you don't expect. On the first it is plain: "Ancestris cannot invent data that was not there." A badly broken export may not open at all, and then you fix the file by hand. For checking that everything made it across, it is blunt: "Only you can perform these two checks visually." That is honest advice, and it is the step a migration most needs. Before you switch, open the export in our GEDCOM viewer and look at what is really in it. Our guide to opening a GEDCOM file covers what the format carries and what it drops.
Two optional features send information outside the file.
Version 13 added an AI transcriber for register scans, listed in the release notes. It sends the image to an outside AI service on a free account that Ancestris users share. The quota is limited, and the registry records guide recommends setting your own key with the service, which it says can be free for occasional, non-commercial use. Its worked example, the birth record of Louis XIV, shows both sides fairly. The date, places and witnesses came back right. The service "assumed the last name was Bourbon", and it gave the father an age of 41 that the guide's own author couldn't explain: "Not sure where the 41 comes from." Transcribed records are saved to a separate CSV file, and you copy each one into the tree yourself. That copy step is where a person should be checking, and Ancestris puts it there.
Genealogy compare is the other one. To match your tree against other Ancestris users' trees, it shares your surnames, date ranges and places with them. The guide says "Your genealogy is never transferred to a server or to anybody", and that holds for the tree itself. Still, the homepage line about your data living only in a file doesn't mention it. Both are features you switch on yourself, so read what they send first.
Installing it means installing Java, except on Windows.
Version 13 runs on Java 17 to 25, according to the compatibility table. The Windows installer brings Java with it. On a Mac or Linux you install Java yourself first, and the guide points you to Adoptium. We checked: the version 13 Mac package contains no Java runtime. When Ancestris shows its splash screen and then stops, the guide says the cause is almost always the Java install. On a Chromebook, the guide's only route is switching on its Linux environment and trying from there.
Mac users get a better build than the Java label suggests. The package is signed by its developers and notarized by Apple (the copy we downloaded was signed on 16 October 2026), and the launcher inside runs natively on both Intel and Apple Silicon. The guide asks for 2 GB of RAM and recommends a 1920 by 1080 screen, and the screen size tells you how much it puts in front of you at once. Our look at genealogy software for Mac covers the other options on that platform.
It holds no records, and it publishes to sites that do.
No census pages, no parish registers, no hints arriving overnight. Like Gramps, Ancestris organises research you did somewhere else. What it does have is tools, more than 30 by the project's count: duplicate detection, Sosa and d'Aboville numbering, a GEDCOM compliance checker, and exports to Geneanet and Genealogieonline. The numbering systems and the Geneanet export show where it comes from, which is French genealogy, and its import list includes French programs such as Hérédis and Généatique.
The 2014 complaint about learning it still has a point.
We didn't repeat that reviewer's test, so we can't say which of the complaints survive in version 13. Some of them read as defaults rather than missing features, such as surnames shown in capitals, which is common practice in French genealogy and a setting you can change. The broader one, that the program takes learning, the project half concedes. Its migration guide promises you'll get used to the interface "After a few hours using it". For a program built around a file format rather than around a first evening, a few hours is an honest estimate.
Who should use it.
If you already hold a GEDCOM file and want that file, not a company's database, to stay the master copy, Ancestris is the most direct way to get there, and on Windows it installs in one step. If you cite carefully and need more structure than GEDCOM can hold, Gramps fits better. Our best genealogy software comparison and our roundup of free genealogy software cover the rest of the field.
We make AncestorIQ, where you build a tree by talking and Deep Research keeps the source for every fact it proposes. It imports and exports GEDCOM too, so a file you keep in Ancestris will open there. Whichever you pick, the file is the part worth protecting, and Ancestris is built around exactly that.


