Stable Gramps tags on gramps-project/gramps releases publish Windows AIO, macOS Arm and Intel dmgs, and often a Linux snap. Prefer non-prerelease tags such as the current release. Ignore beta tags when a stable family tree build already exists.
Windows AIO naming
The Windows asset looks like GrampsAIO-*-win64.exe with a double-dash before the build number. Notice the double-dash before the build number. Match GrampsAIO-*-win64.exe and refuse renamed “family tree setup” downloads from review portals.
macOS dmgs
The same tag ships Gramps-Arm-*.dmg and Gramps-Intel-*.dmg. Apple Silicon users take Arm; Intel Macs take Intel. Homebrew users can run brew install --cask gramps instead of opening a dmg.
Linux snap
When present, gramps_*-amd64.snap sits on the release. Everyday Linux users can also run sudo snap install gramps from the Snap Store or sudo apt install gramps on Debian-family systems.
How release assets are matched
Build-time fetch reads the latest non-prerelease tag and matches asset regexes in site config. The install panel shows the live file names. Home: family tree install. Safe path: download safe.
Cadence
Recent maintenance tags ship AIO, dmgs, and often a snap together. Beta tags exist but are not the default for this family tree guide. Prefer the newest stable asset set unless you are testing.
Checksums and mirrors
If a mirror republishes the AIO under a new name, treat it as untrusted. Prefer the GitHub Releases URL you typed. When in doubt, compare the filename and size against the release page before you run anything.
After you pick a file
Windows users run the AIO once. macOS users open the matching dmg or finish the brew cask. Linux users finish snap or apt. Then create one Family Tree and prove a Home Person before large GEDCOM imports. Guide: first hour.
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.