How to uninstall Hyper on Mac

Hyper's configuration file .hyper.js and its plugins folder .hyper_plugins are what you would miss after uninstalling, and on a Mac they can sit in two places: inside ~/Library/Application Support/Hyper, where Hyper's documentation puts them, or directly in your home folder, the older location Hyper still reads. Copy whichever copy you use before removing anything. This guide covers the official arm64 zip build and the Homebrew cask hyper.

Save your config and plugins

Hyper's website gives the macOS locations as ~/Library/Application Support/Hyper/.hyper.js and ~/Library/Application Support/Hyper/.hyper_plugins. It says the older ~/.hyper.js and ~/.hyper_plugins are still supported but ignored once a config exists in the application folder, and that Hyper migrates them there on first run. In the recorded test both older items were also present in the home folder, so check both places:

ls -la ~/Library/Application\ Support/Hyper
ls -ld ~/.hyper.js ~/.hyper_plugins

• A listing that includes .hyper.js means your current config is in the Application Support folder; copy that folder if you want to keep it.
• "No such file or directory" for an item means it does not exist in that place.
• If both places have a .hyper.js, Hyper uses the one in Application Support.

Quit Hyper and remove the app

1. Close open terminal sessions and quit Hyper from its application menu.
2. Check Activity Monitor for a lingering Hyper process.
3. In Finder's Applications folder, move Hyper to the Trash. Hyper's site and its GitHub repository do not publish an uninstall page, so the other locations below come from the local test recorded for this guide and the Homebrew cask's zap list.

Where its data lives

If you installed it with Homebrew

The hyper cask's zap list includes ~/.hyper.js and ~/.hyper_plugins, which sit outside ~/Library, along with Application Support/Hyper and the caches, cookies, logs, preferences and saved state above. Mole leaves out --zap whenever a zap list reaches outside ~/Library, so it removes a Homebrew install of Hyper without --zap whatever you tick, and still moves the rows you selected to the Trash itself.

The cask also links a hyper command; Homebrew removes it together with the app.

Running the zap step yourself removes your config and plugins in both places:

brew uninstall --cask --zap hyper

To keep your config and plugins, copy them first, or remove only the app:

brew uninstall --cask hyper

Check the result

pgrep -il hyper
command -v hyper
ls -d ~/Library/Application\ Support/Hyper ~/.hyper.js ~/.hyper_plugins

• No output from pgrep means no Hyper process is running. The match is case-insensitive, so check the process name if something is listed.
• No output from command -v means the hyper command was not found in this shell's PATH. Output means it still resolves somewhere; check that location separately.
• ls -d prints each item that still exists and reports "No such file or directory" for the rest. Items you chose to keep are expected to remain.

What Mole lists

For Hyper installed from the official download:

• ~/Library/Application Support/Hyper, ~/.hyper.js and ~/.hyper_plugins are listed but not selected, so you choose whether to keep your configuration and plugins.
• The caches, cookies, logs, preferences and saved window state filed under co.zeit.hyper or the Hyper name are selected by default.

For a Homebrew install, the zap list reaches ~/.hyper.js and ~/.hyper_plugins, so Mole leaves --zap out whatever you tick.

What this test covered

On September 20, 2026, Hyper 3.4.1 was copied from the official arm64 zip into Applications, opened, and removed with a Preview build of Mole 1.15 (build 282) with every listed row ticked; there was no Homebrew receipt. Application Support/Hyper went to the Trash with the app. ~/.hyper.js and ~/.hyper_plugins in the home folder were not listed and stayed on disk after the app was removed; those review rows were added to Mole after this test. Plugins and the Homebrew cask were not tested.