How to uninstall Fork on Mac

Removing Fork 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. Fork keeps its settings in ~/Library/Application Support/com.DanPristupov.Fork, and Mole selects that folder by default, so copy it first if you customized Fork and want the same setup after a reinstall. These steps cover the official download from git-fork.com and the Homebrew cask fork, which install the same app.

Quit Fork and remove the app

Quit Fork from its app menu, then move Fork from Applications to the Trash. Removing the app does not affect a purchased Fork license. If you set up the fork command-line tool, the check below shows whether the command is still on your PATH.

Where Fork keeps its data

These paths come from the Homebrew cask's zap list and Mole's test. Only remove the com.plausiblelabs.crashreporter.data/com.DanPristupov.Fork folder, never its shared parent, which other apps use too.

Check the result

Run these read-only commands in Terminal:

pgrep -il fork
ls -d ~/Library/Application\ Support/com.DanPristupov.Fork
ls -d ~/Library/Application\ Support/Fork
command -v fork

• No output from pgrep -il fork means Fork has quit. The word also matches unrelated processes whose names contain "fork", so check that a listed process is really Fork before acting on it.
• For the two ls -d lines, a printed path means the folder is still there, which is expected if you kept it; "No such file or directory" means it is gone.
• No output from command -v fork 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 Fork app you removed.

If you installed it with Homebrew

The fork cask links a fork command and removes it on uninstall. Its zap list covers every row in the table above, both Application Support folders included, plus Fork's entry in the recent-documents list. brew uninstall --cask --zap fork moves them to the Trash whatever you selected in Mole. To keep Fork's settings, remove only the app:

brew uninstall --cask fork

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/Fork is listed but not selected, so unless you tick it Mole removes Fork without --zap and moves only the rows you selected.

What Mole lists

When you remove it with Mole:

• ~/Library/Application Support/com.DanPristupov.Fork is selected by default, because it is named after the bundle identifier. Untick it if you want to keep Fork's settings.
• The preferences, both caches, HTTP storage, cookies, WebKit data and saved window state are selected by default.
• ~/Library/Application Support/Fork comes from a name Mole cannot tie to the bundle identifier, so it is listed but not selected. ~/Library/Logs/Fork.log is matched by the app's name in Logs, which Fork rebuilds, so it is selected by default.
• Mole does not search custom project folders for repositories.

What this test covered

Fork was installed from the official download on September 19, 2026, updated inside Mole from 2.66.7 to 2.70.0, and then uninstalled with a Mole Preview build. The Application Support/com.DanPristupov.Fork folder was selected by default and removed. The removal was confirmed while Fork's leftover scan was still running, so its unselected rows were not part of that run. No repositories are recorded, the fork command was not tested, and the Homebrew cask was not part of this test.