macOS users of this family tree guide have two verified doors: Homebrew cask gramps, and Arm/Intel dmgs on the same GitHub release tag as the Windows AIO.
Homebrew cask
Run brew install --cask gramps in Terminal. The cask tracks the project release assets. When an update lands, brew upgrade --cask gramps is the refresh path. Confirm the cask still resolves on formulae.brew.sh if your brew is very old.
Dmg path
Open Releases, download Gramps-Arm-*.dmg or Gramps-Intel-*.dmg, open the disk image, and drag Gramps into Applications. That path matches users who refuse Homebrew.
First Family Tree
Launch Gramps, create a Family Tree, add a Home Person, and save. Import GEDCOM only after that proof. Guide: first hour.
Common macOS mistakes
Downloading an Intel dmg on Apple Silicon is the top failure. Mixing beta tags with production trees is second. Expecting online research hints inside the dmg is third; Gramps is the local family tree database.
Verify against research notes
Facts on this page come from the gramps-project/gramps README, GitHub Releases tag assets, Homebrew cask JSON for gramps, Snap Store metadata, and the Gramps wiki checked on 2026-09-15. If a newer stable tag appears, prefer the live Releases list and exact filenames over any hard-coded memory of one version alone. The home install panel reads gh.json at build time so the current release link stays fresh.
Keep one update door
One install style per machine. Write it down.
Pick one install style per machine and write it down. Windows AIO users return to GitHub Releases. Homebrew users run brew upgrade. Snap users refresh the snap. apt users use distro tools. Mixing three doors on one PATH creates confusing dual launches and stale Family Trees.
Privacy and offline use
- Local Family Trees keep pedigree data on disk after install.
- Online research in a browser is optional and separate.
Living-person details deserve care. Export GEDCOM only when you mean to share, and review privacy options before you upload a file to any third party. A desktop family tree is useful precisely because the database can stay offline after the first download.
Classroom and shared PCs
Shared labs often block unknown publishers. Document the asset name in your image build notes. Societies that need offline pedigrees should prefer a machine they administer. Keep GEDCOM licences and contributor agreements with the archive so redistribution stays clear.
Network and offline
You need network once to download the AIO, dmg, brew bottle, or snap. After the Family Tree lives on disk, editing people and printing charts works offline unless you choose online research later. That split is why a desktop family tree beats a fragile tab for travel and archive work that forbids cloud uploads.
After install checklist
Confirm the window opens, create one Family Tree, add a Home Person, save, and bookmark Releases or note the brew/snap door. Then read first-run and safety guides. If policy blocks unknown executables, ask an admin instead of smuggling a random mirror binary.
Extra install discipline
Write the asset name or package command in a short text file next to your backups. When someone else inherits the research PC, that note prevents a second random download for the same family tree job. Prefer stable tags, refuse renamed wrappers, and keep living-person exports intentional.
Why this matters for searchers
People who type family tree into a search box often land on adware portals. A clear install door, an exact filename, and a local Family Tree proof keep the job honest. Repeat the same door on the next machine instead of improvising a new mirror each time you travel.
Source checklist
- GitHub Releases stable tag assets
- Homebrew cask metadata when used
- Snap or apt package ids when used
- Gramps wiki for workflow menus after install
If any of those sources disagree with this page, prefer the upstream page and file a correction through the contact path so research notes can be updated.
Frequently asked questions
Should I use Homebrew or a dmg?
If Homebrew is already on the Mac, brew install --cask gramps is the simplest verified door for this family tree path. Otherwise download Gramps-Arm-*.dmg or Gramps-Intel-*.dmg from GitHub Releases and drag the app into Applications.
How do I pick Arm vs Intel?
Apple Silicon Macs use the Arm dmg for this family tree app. Intel Macs use the Intel dmg. Choosing the wrong architecture usually fails to open cleanly, so match the CPU before you download from Releases.
Does Gatekeeper block Gramps?
macOS may ask to open an app downloaded from the internet when you use a dmg for this family tree install. Prefer the Releases URL you typed. Homebrew cask installs follow Homebrew quarantine handling on supported versions.