How to uninstall Proxifier on Mac

Save Proxifier profiles and rules before removing the Mac app. This procedure covers the app copy without an activated system extension, matching the recorded test. The vendor's v3 introduction says its network engine uses Apple's Network Extension framework, so removing an active installation needs its extension state checked separately.

Preserve local settings

Quit Proxifier after finishing work using it. Copy wanted existing ~/Library/Containers/com.initex.proxifier.v3.macos and ~/Library/Application Support/Proxifier outside sync/removal roots and verify the copies before deleting local state. The first container was recorded locally and the latter comes from the cask. Keep the extension-associated group ~/Library/Group Containers/NXELXU5YLW.com.initex.proxifier.v3.macos rather than treating it as ordinary cache.

For the inactive-extension app copy, follow Apple's Finder removal instructions and move Proxifier.app from Applications to the Trash after backup. If your extension is activated, keep the app available while resolving its supported removal with the vendor; the recorded test does not establish that flow. Do not delete shared network configuration or another proxy app's settings.

If you installed it with Homebrew

The cask declares no separate system-extension uninstall step and removes its managed bundle without zap:

brew uninstall --cask proxifier

Zap names ~/Library/Application Scripts/com.initex.proxifier.*.macos, ~/Library/Containers/com.initex.proxifier.*.macos, ~/Library/Group Containers/*.com.initex.proxifier.*.macos, ~/Library/Application Support/Proxifier, ~/Library/Logs/Proxifier, ~/Library/Caches/com.initex.proxifier.macosx, ~/Library/Preferences/com.initex.proxifier.macosx.plist, ~/Library/Saved Application State/com.initex.proxifier.macosx.savedState and matching Proxifier Help* files in ~/Library/Caches/com.apple.helpd/SDMHelpData/Other/English/HelpSDMIndexFile. These wildcards cover more than one spelling/version; inspect exact matches and keep extension-owned/shared data.

Direct brew uninstall --cask --zap proxifier ignores Mole's checkboxes. Mole uses zap only when the entire scope passes selection, ownership and safety checks; selected remnants otherwise use its own Trash flow. Zap is not a documented activated-extension removal procedure.

Check the result

pgrep -ifl proxifier
systemextensionsctl list
ls -ld "$HOME/Library/Containers/com.initex.proxifier.v3.macos" "$HOME/Library/Group Containers/NXELXU5YLW.com.initex.proxifier.v3.macos"

No process match means no arguments matched that pattern. A printed container/group remains, expected when kept. The extension list describes registered state: inspect the actual Proxifier publisher/identifier, without removing another product's entry. A successful list without its matching entry is narrower than proof every network configuration was removed. Missing-path errors concern those paths only; other errors are inconclusive.

What Mole lists

The exact main container and Application Scripts rows follow default selection rules and can be selected by default, so back up and uncheck wanted profiles. The group declared by the system extension remains outside ordinary app-data selection. Reviewed unshared support/log data starts unchecked with Remove data and settings with apps off; eligible rows may be preselected when enabled, without bypassing extension ownership or permissions.

What this test covered

On September 23, 2026, the official-download Proxifier 3.15.0 app copy was removed with selected main container and Application Scripts data. Its system extension was not approved; the extension-declared group was not listed and remained. Activated-extension removal, profile restoration and Homebrew were not tested.