How to uninstall Reqable on Mac

Reqable installs its own CA certificate so it can inspect HTTPS traffic. Moving the app to the Trash does not remove that certificate, and your Mac keeps trusting it until you delete it. Reqable also keeps its configuration and logs in one Application Support folder, so back that up first if you want your settings later. This guide covers the official Mac download from reqable.com and the Homebrew cask reqable.

Quit Reqable

Finish any capture session, then quit Reqable from its menu. Check Activity Monitor for a lingering Reqable process before deleting its data.

Remove the proxy certificate

The certificate is a Keychain item, not a file, and Reqable's Mac FAQ handles it in Keychain Access: when fixing browser trust problems it tells you to delete the installed Reqable CA certificate there and reinstall it from Reqable. For an uninstall you only need the first half.

  1. Open Keychain Access.
  2. Search for "Reqable Proxy", the certificate name the Homebrew cask also removes.
  3. Delete the certificate, confirming with your administrator password if asked.

Move Reqable to Trash

Open the Applications folder in Finder and move Reqable to Trash.

Review app data

Press Shift + Command + G in Finder and check the paths below. Skip any that are missing.

Location What it holds What to do
~/Library/Application Support/com.reqable.macosx Reqable's cache and configuration folder, with logs in its log subfolder, per Reqable's FAQ Back up anything you want to keep before removing
~/Library/Caches/Reqable Cache Safe to remove
~/Library/Preferences/com.reqable.macosx.plist App preferences Safe to remove
Reqable Proxy certificate (login keychain) Lets Reqable decrypt HTTPS traffic that your Mac routes through it Not a file; delete it in Keychain Access as above

If you installed it with Homebrew

The reqable cask deletes the "Reqable Proxy" certificate as part of its normal uninstall, not as part of --zap, so any brew uninstall --cask reqable removes it. Its zap list is ~/Library/Application Support/com.reqable.macosx, ~/Library/Caches/Reqable and ~/Library/Preferences/com.reqable.macosx.plist. Running --zap yourself removes all three, configuration included, whatever you ticked in Mole. To keep them, leave --zap out:

brew uninstall --cask reqable

When Mole removes a Homebrew-installed Reqable, all three zap entries sit inside ~/Library and match rows Mole selects by default, so Mole runs --zap unless you untick one of them. Untick the Application Support row to keep your configuration and Mole leaves --zap out.

Check the result

pgrep -il reqable
ls -d "$HOME/Library/Application Support/com.reqable.macosx"
security find-certificate -c "Reqable Proxy" -a
  • No output from pgrep means no Reqable process is running.
  • ls -d printing the path means the Application Support folder is still there; "No such file or directory" means it is gone.
  • security find-certificate only searches your keychains and changes nothing. No output, or "The specified item could not be found in the keychain", means the certificate is gone; a printed certificate block means it is still installed, so delete it in Keychain Access.

What Mole lists

For Reqable installed from reqable.com's own download:

  • ~/Library/Application Support/com.reqable.macosx, ~/Library/Caches/Reqable and ~/Library/Preferences/com.reqable.macosx.plist are listed and selected by default when they exist. The Application Support row holds your configuration, so untick it if you want to keep it.
  • Mole does not list Keychain items, so the Reqable Proxy certificate never appears; remove it yourself as described above.

What this test covered

Reqable 3.2.23 was downloaded from reqable.com, copied into Applications, and removed on September 21, 2026 with Mole 1.15 Preview (build 282) and Full Disk Access, in a batch with several other Mac apps. Reqable was not signed in. The uninstall used the default selection, without selecting the review rows, and only the .app (96.8 MB) went to the Trash; no Reqable data folders were left behind. Installing and removing the certificate, a paid license, and the Homebrew cask were not tested.