How to uninstall Sourcetree on Mac

Removing Sourcetree does not touch your repositories: they are ordinary folders wherever you cloned them. Push anything you have not pushed yet, since the app is going away, not your work. Sourcetree keeps its own user data in ~/Library/Application Support/SourceTree; copy that folder first if you want Sourcetree to come back with the same setup after a reinstall. These steps cover the official download from sourcetreeapp.com and the Homebrew cask sourcetree, which install the same app.

Quit Sourcetree and remove the app

Quit Sourcetree from its app menu, then move Sourcetree from Applications to the Trash. Sourcetree can also install a privileged helper, which the Homebrew cask unloads under the name com.atlassian.SourceTreePrivilegedHelper2; it exists only if Sourcetree installed it, and the check below shows whether it did. Git credentials you saved may also sit in your login keychain; Mole never reads or removes keychain items.

If you installed Sourcetree's stree command-line tool, the check below shows whether the command is still on your PATH.

Where Sourcetree keeps its data

These paths come from the Homebrew cask's zap list and Mole's test. The app's bundle identifier is com.torusknot.SourceTreeNotMAS, which is why the files carry that name rather than "Sourcetree".

Check the result

Run these read-only commands in Terminal:

pgrep -il sourcetree
ls /Library/LaunchDaemons /Library/PrivilegedHelperTools | grep -i sourcetree
ls -d ~/Library/Application\ Support/SourceTree
command -v stree

• No output from pgrep means Sourcetree has quit.
• No output from the second line means no Sourcetree helper is installed. A listed com.atlassian.SourceTreePrivilegedHelper2 entry means the helper is still there; move it to the Trash in Finder with an administrator password, then restart.
• The ls -d line printing the path means Sourcetree's user data is still there, which is expected if you kept it; "No such file or directory" means it is gone.
• No output from command -v stree means the command is not on your PATH. A printed path means a link is left; inspect it with ls -l and remove it only if it points into the Sourcetree app you removed.

If you installed it with Homebrew

The sourcetree cask quits Sourcetree, unloads com.atlassian.SourceTreePrivilegedHelper2 and removes the stree command it links. Its zap list includes ~/Library/Application Support/SourceTree, the cache, ~/Library/Logs/Sourcetree, both preferences files, the saved window state and its entry in the recent-documents list. brew uninstall --cask --zap sourcetree moves them to the Trash whatever you selected in Mole. To keep Sourcetree's user data, remove only the app:

brew uninstall --cask sourcetree

Mole adds --zap only when everything in the zap list sits in your own ~/Library, is a row you left selected, and is not claimed by another installed app. Application Support/SourceTree is listed but not selected, so unless you tick it Mole removes Sourcetree without --zap and moves only the rows you selected.

What Mole lists

When you remove it with Mole:

• Both preferences files, the cache, ~/Library/Logs/Sourcetree and the saved window state are selected by default.
• ~/Library/Application Support/SourceTree is listed but not selected, because it is named after the app rather than its bundle identifier.
• Mole does not search custom project folders for repositories, and Keychain items are outside its uninstall scope.

What this test covered

Sourcetree was installed from the official download and uninstalled on September 19, 2026, with a Mole Preview build, with the review list shown. Only the app was copied into Applications and the privileged helper was never installed, so the helper was not tested. The preferences, logs and temporary caches were removed; the empty Application Support/SourceTree folder was listed, left unselected and stayed on disk. No repositories or accounts are recorded, and the Homebrew cask was not part of this test.