How to uninstall GitUp on Mac
Keep your Git repositories when removing GitUp. Finish any active Git operation and save uncommitted work before quitting; deleting the client is separate from deleting a repository and its .git data. This guide covers the official Mac app and the Homebrew cask gitup-app.
Quit GitUp and remove the app
Quit GitUp with Command + Q, then move GitUp.app from Applications to Trash. If macOS says it is in use, check it in Activity Monitor before trying again. The official project documentation describes GitUp as a client that works directly with repositories on disk, so leave those working folders in place.
Review preferences rather than repositories
The following locations are named in the Homebrew cask, and the recorded uninstall also removed GitUp's preferences and HTTP storage. They are not the folders holding your source code.
| Location | What to do |
|---|---|
| ~/Library/Caches/co.gitup.mac | GitUp's own cache. Inspect after quitting. |
| ~/Library/HTTPStorages/co.gitup.mac | App-specific HTTP state. Keep if needed for a reinstall, or remove after quitting. |
| ~/Library/Preferences/co.gitup.mac.plist | Preferences. Keep to reuse your setup, or remove to reset it. |
Use Finder's Shift + Command + G to inspect each exact path and skip missing ones. Do not delete your project folders, .git directories, SSH keys or the system Git installation as part of removing GitUp.
The cask also names a GitUp recent-documents entry inside Apple's sharedfilelist store. Do not delete that shared parent or unrelated applications' entries manually.
Check the app and command-line entry
pgrep -il GitUp
ls -d /Applications/GitUp.app "$HOME/Library/Preferences/co.gitup.mac.plist"
command -v gitup
No output from pgrep means no matching process name is running; a match needs a check in Activity Monitor. A path printed by ls still exists, a missing-path error means it is absent, and a permission error leaves the state unknown. command -v gitup prints the command resolved by your shell; no output only means it is not on that shell's PATH. If a command remains, inspect which installation owns it before removing anything.
If you installed it with Homebrew
brew uninstall --cask gitup-app
This uninstalls without zap. The cask manages both GitUp.app and its gitup command link, so ordinary removal is not limited to the app icon.
A direct brew uninstall --cask --zap gitup-app additionally applies the cache, HTTP storage, preferences and recent-documents list from the cask, regardless of Mole's checkboxes. Leave zap out when keeping that state.
Mole checks Homebrew's full removal list and skips --zap when it reaches unchecked data, shared files or anything it cannot verify. It still removes the leftovers you selected.
What Mole lists
GitUp's bundle-identified cache, HTTP storage and preferences are selected by default when present. Mole can also list GitUp's own exact recent-documents file, selected by default, while the sharedfilelist parent and other apps' lists remain protected. Uncheck the preferences if you want to keep them.
Your repositories and independently installed Git tools are outside this app's uninstall list.
What this test covered
GitUp 1.5.0 from the official package was copied to Applications, opened and uninstalled on September 21, 2026, without a Homebrew receipt. The app, preferences, HTTP storage and identified temporary caches went to Trash, and no survivor was recorded from that removal list. The run did not verify a Homebrew-managed gitup link or restoration of repositories and GitUp-specific history.