How to uninstall MacZip on Mac

MacZip is a free archive utility for Mac, formerly called eZip, from ezip.awehunt.com. It opens and creates archives, can encrypt them with a password, and adds a Finder extension. The archives you made are ordinary files wherever you saved them, so removing the app does not touch them; keep them, and keep the passwords you set. The vendor's page also says MacZip runs inside the macOS sandbox, which is why almost everything it keeps sits in sandbox containers. This guide covers the disk image from the vendor and the Homebrew cask maczip; the Mac App Store version of MacZip is a separate install that was not tested.

Quit and remove the app

1. Move any archive you still need out of folders you plan to clear. Nothing MacZip made sits inside the app.
2. Quit MacZip with Command + Q.
3. Open Finder, go to Applications, select MacZip and press Option + Command + Delete, which the vendor's uninstall instructions describe, or drag it to the Trash.

The test recorded no login item or launch agent for MacZip.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

If macOS says it is not allowed to remove a container, quit MacZip first and try again in Finder; macOS can still refuse while it protects sandboxed app data. Then either grant Mole Full Disk Access in System Settings › Privacy & Security › Full Disk Access and let it retry the failed rows, or remove the folder yourself once nothing is using it.

Check the result

pgrep -il maczip
ls -d "$HOME/Library/Containers/com.jinghaoshe.ezip"* "$HOME/Library/Group Containers/group.com.jinghaoshe.ezip.shared" "$HOME/Library/Application Scripts/com.jinghaoshe.ezip"*
pluginkit -mA | grep -i jinghaoshe

• No output from pgrep means MacZip is not running. A printed line is a process still alive; quit it or restart the Mac once.
• A path printed by ls still exists. No such file or directory means that path is gone. A surviving container after Mole ran without Full Disk Access is the expected case described above.
• No output from pluginkit means macOS lists no MacZip extension. A printed line means an extension for the app is still registered; log out and back in, then run it again.

If you installed it with Homebrew

brew uninstall --cask maczip

The cask has no uninstall step, so this removes the app and leaves its containers. Its zap list covers ~/Library/Containers/com.jinghaoshe.ezip, ~/Library/Application Scripts/com.jinghaoshe.ezip, ~/Library/WebKit/com.jinghaoshe.ezip and ~/Library/Preferences/com.jinghaoshe.eZipAssistant.plist, the preferences file of an older helper called eZip Assistant. Running brew uninstall --cask --zap maczip deletes those whether or not you reviewed them, does not read Mole's checkboxes, and needs Full Disk Access to touch the container. Mole adds --zap only when its whole removal scope passes its zap gate; unchecked or shared paths, paths outside the reviewed boundary and any matching path it did not list suppress it, and it then removes the selected rows itself.

What Mole lists

Mole selects the app, both containers, both Application Scripts folders and the temporary cache folder. It lists the App Group container and its Application Scripts folder for review and selects them by default, since the group is named after the app's own bundle ID. Before removing, Mole asks MacZip to quit and then force quits it if it does not, and it also clears the app's preference domain with defaults delete, which cannot be recovered from the Trash. With Full Disk Access Mole can move the containers; without it, Mole's report names Full Disk Access and offers a retry.

What this test covered

On November 9, 2026, the test downloaded the Universal disk image 2.4 from the vendor's CDN, whose sha256 matched the Homebrew cask, copied the app to Applications without running brew install, opened it once and quit it. It was removed with a source-built, re-signed Debug build of Mole with every review row ticked; Mole's notarized release build was not used. Mole moved the app, both Application Scripts folders and the temporary cache to the Trash, and macOS refused to move the two containers with error 513 because the test build ran without Full Disk Access, so they stayed. On the first run Mole also skipped the group's Application Scripts folder as protected and left the group container; a repeat run on the same package after that was fixed moved both, the group container after macOS asked to allow access to data from other apps. Status showed one MacZip row with 1 process, and Mole found no update channel, so no update was run. Creating or opening archives, encryption, the Finder extension in use, the Mac App Store version and a Homebrew-managed uninstall were not tested.