Uninstall Keka on Mac

Your archives are your own files wherever you created or extracted them; uninstalling Keka never touches anything outside its own sandboxed data. This guide covers the official DMG from Keka's GitHub releases and the Homebrew cask keka; both install the same sandboxed app under the same bundle identifier, com.aone.keka, so the paths below apply either way.

Quit Keka and remove the app

Quit Keka from its menu, then move Keka.app from Applications to the Trash. Keka's context-menu shortcuts (Send to Keka, Extract using Keka, Compress using Keka) and its Finder extension stop working once the app is gone; you don't need to disable them separately first.

Where Keka keeps its data

Keka has been sandboxed since version 1.1.0, both the direct-download and Mac App Store builds, so its data sits inside App Group and container paths rather than loose files in your home folder.

Keka's own uninstall instructions describe removing the same container, group container, and Finder-extension container by hand with rm -r and defaults remove. Mole's rows cover the same paths through its ordinary review-and-Trash flow instead of raw shell commands.

About the Finder extension on macOS 15 and later

Since macOS 15 Sequoia, Apple removed the System Settings toggle for enabling or disabling Finder extensions, including Keka's context-menu integration; Keka's own fix is a small companion app, Keka Helper, that works around it. If you installed Keka Helper to keep the context menu working, it is a separate app with its own entry in Applications: quit and remove it the same way you would any other app; this guide's test did not cover it specifically.

Check the result

Run these read-only commands in Terminal:

pgrep -il keka
ls -d ~/Library/Containers/com.aone.keka
pluginkit -m | grep -i keka

No output from pgrep means no Keka process is running. ls -d prints the container's path if it's still on this Mac, or "No such file or directory" once it's gone. pluginkit -m lists registered Finder/system extensions; no Keka line means the Finder extension is no longer registered.

If you installed it with Homebrew

The next Mole update will skip --zap when its list reaches unchecked or shared data, or cannot be fully checked. Mole will still clean the leftovers you selected. Preview 290 does not include this protection.

Mole Preview 290 removes a Homebrew-installed Keka the same way as brew uninstall --cask --zap keka. The cask's zap list trashes the same container, group container, Finder-extension container, and Application Scripts paths in the table above, along with the preferences and saved state, whatever you left checked in Mole. It also names a legacy ~/Library/Application Support/Keka folder from before Keka was sandboxed (pre-1.1.0); a current install normally has nothing there, but zap trashes it too if it exists:

brew uninstall --cask keka

Homebrew Keka cask

What Mole lists

This describes Mole 1.15, currently in Preview. The main app's sandbox container, its App Group container, and the Application Scripts entry for the main app are selected by default, the same generic rule Mole applies to any sandboxed app's own container and group container. The Finder extension's own container and Application Scripts entry are listed but not selected: Mole treats a separately identified embedded helper's container as a review row rather than selecting it alongside the main app.

What this test covered

Keka was installed from the Homebrew cask keka and uninstalled with a development build of Mole on September 17, 2026. The App Group container and main sandbox container were removed cleanly; the Finder extension's container appeared as a review row, as expected. No new leftover was found. Keka Helper, the macOS 15+ companion app for re-enabling the Finder extension, and the Mac App Store build specifically were not part of this test.