Safe downloads for this family tree path start at GitHub Releases for gramps-project/gramps, or at Homebrew and Snap channels that publish the same project. Avoid Softonic-style pages that wrap the AIO in a second installer.
Exact Windows name
Match GrampsAIO-*-win64.exe. Real tags use a double-dash before the build, for example GrampsAIO-*-win64.exe (double-dash before build). If the filename lost the AIO token or gained “SetupOnline”, stop.
macOS and Linux
Prefer brew install --cask gramps or the Arm/Intel dmgs from Releases. On Linux prefer sudo snap install gramps or distro apt install gramps. Those doors were verified as package ids for this guide.
No winget invent
This guide did not verify a winget package id. Inventing one would be dishonest. Stay on the AIO from Releases until a verified package appears and research is updated.
SmartScreen and Gatekeeper
Windows may show SmartScreen for an unfamiliar publisher. Prefer the Releases URL you typed. macOS Gatekeeper may ask to open an app from the internet when you use a dmg. Brew cask installs follow Homebrew’s quarantine handling.
Living-person privacy
A family tree database often includes living relatives. Keep backups local, review GEDCOM exports before you upload them anywhere, and prefer offline charts when privacy matters.
Update door
One door forever: GitHub Releases for AIO and dmgs, or brew upgrade / snap refresh when that is how you installed. Do not stack three mirrors “just in case.”
Related
Windows install, is it safe, releases.
Why exact filenames matter
Search results for a family tree install are crowded with renamed wrappers. Matching the upstream asset on GitHub Releases, or a verified brew or snap package, is the difference between a clean Family Tree and a second cleanup afternoon. Prefer stable tags over betas when your research PC needs predictability.
Write down which door this computer used. The next volunteer who opens the archive should not have to guess whether the machine used an AIO, a dmg, Homebrew, or snap. That note belongs beside your GEDCOM backups.
Local database habits
A family tree only helps when the database path is intentional. Create trees on disks you back up. Export GEDCOM or Gramps XML before risky imports. Keep media folders in the same backup set. Living-person details deserve the same care you would give any other personal archive.
Charts and reports can wait until a handful of people exist. Graphviz helps some graph outputs on Linux and other systems; install it when a report asks. Geography views and maps are optional power features, not first-hour requirements.
Parallel research without cloud lock-in
Many researchers keep a local family tree as the system of record while browsing online genealogy sites for clues. That hybrid approach works when you export carefully and avoid deleting the only copy of either side too early. GEDCOM remains the bridge when you need to move.
If a society already standardized on a commercial suite, evaluate migration cost before you switch for branding alone. Gramps wins when GPL-2.0 and offline disks matter. Online SaaS wins when you cannot install software or you need hosted hints every day.
Update discipline
Return to the same door forever. Windows users take the next AIO from Releases. Homebrew users upgrade the cask. Snap users refresh. apt users follow distro tools. Do not stack three mirrors “just in case.” One honest door prevents dual launches and confusion after a reimage.
When a newer stable tag appears, read the release notes, back up Family Trees, then upgrade. Beta tags are for testers. This family tree guide defaults to stable assets so classrooms and societies can reproduce installs.
Where to go next
Home install panel: family tree install. Windows deep dive: Windows. Safety: is it safe. First hour: installed. Guides hub: guides.
Corrections to filenames or package ids belong on the contact page with a source URL. Software bugs belong on the upstream GitHub issues list for gramps-project/gramps in a new tab.