Uninstall Raycast on Mac

Before removing Raycast, save the shortcuts, extension settings, and clipboard items you want to keep. Raycast’s clipboard history database lives in ~/Library/Application Support/com.raycast.macos, and clipboard images sit under ~/Library/Caches/com.raycast.macos; both may exist only on this Mac, and being stored under Caches does not make the images replaceable downloads. Removing the app does not cancel a Raycast Pro subscription; manage that in your Raycast account. This guide covers Raycast downloaded from its website and the Homebrew cask raycast.

Save configuration and quit

Use the configuration export in Raycast's settings, and save important clipboard images as separate files. A configuration export is not proof that every clipboard item was backed up. Raycast manual

Quit Raycast from the menu bar, then move it from Applications to the Trash. Raycast registers a login item; if it is still listed in System Settings › General › Login Items & Extensions after removal, turn it off there. If its hotkey still opens Raycast, check Activity Monitor for another running copy.

If you installed it with Homebrew

Mole skips --zap when its list reaches unchecked or shared data, or cannot be fully checked, and still cleans the leftovers you selected.

The raycast cask’s zap list includes ~/Library/Application Support/com.raycast.macos (clipboard history and app data), ~/Library/Caches/com.raycast.macos (clipboard images) and ~/.config/raycast (configuration), plus cookies, web data and preferences. Running brew uninstall --cask --zap raycast yourself moves them all to the Trash, whatever you selected in Mole. Export first, or remove only the app:

brew uninstall --cask raycast

Review data and caches

Press Shift + Command + G in Finder and open the following locations one at a time. Skip any that do not exist.

Check the result

Run these read-only commands after the app is in the Trash:

pgrep -il raycast
ls -d "$HOME/Library/Application Support/com.raycast.macos" ~/Library/Caches/com.raycast.macos ~/.config/raycast

• No output from pgrep means Raycast has quit. A listed process means a copy is still running; quit it before deleting data.
• ls -d prints each folder that still exists and reports “No such file or directory” for the rest. Surviving folders are expected for anything you chose to keep.

If clipboard images are missing after reinstalling

Verify that the exported configuration includes the shortcuts and extension settings you need, then separately open the clipboard images you saved. These are different kinds of data. Touch ~/Library/Caches/com.raycast.macos only when you have decided those images are no longer needed; the word Caches does not guarantee that everything can be downloaded again.

If a hotkey still opens a search window after removal, identify the running Raycast app in Activity Monitor and login items instead of trying to force a process to quit by clearing its configuration.

What Mole lists

For Raycast downloaded from its website:

• ~/Library/Application Support/com.raycast.macos is selected by default, because it is filed under Raycast’s own bundle ID. It holds your clipboard history, so export and save first, or uncheck it.
• ~/Library/Caches/com.raycast.macos, ~/Library/Application Support/.com.raycast.macos.backups and ~/.config/raycast are listed but not selected. Mole’s Clean tab never offers the clipboard-image cache; only its plain URL cache counts as cache there.
• Preferences, cookies and web data filed under com.raycast.macos are selected by default.

What this test covered

Raycast is installed on the test Mac and was not uninstalled. On September 22 and 23, 2026, a development build of Mole previewed its uninstall list for that installation without removing anything. On the 22nd the clipboard-image cache was missing from the list because it was protected everywhere. On the 23rd, after that was changed, it listed 19 items, 12 of them selected by default, with the clipboard-image cache among the unselected rows and nothing missing. It did not verify that configuration exports include all data from every extension, and the Homebrew cask was not tested.