How to uninstall MEGAsync on Mac

Verify wanted local files and cloud copies before removing MEGAsync. Save an independent copy of important files outside any active sync root. The official removal instructions then log out of the desktop app, choose Quit from its menu-bar icon and move the app from Applications to the Bin. Uninstalling the client does not itself delete the cloud account.

Remove the sync client

Complete wanted transfers and check copies before logging out and quitting. Keep local sync folders and downloaded files; client state under ~/Library/Application Support/Mega Limited/MEGAsync is not a substitute for the files themselves.

For Homebrew, the current cask supports:

brew uninstall --cask megasync

Ordinary removal unloads its updater, quits MEGAsync and removes its login item and app. Zap adds the listed Finder extension scripts/container, cache, updater plist and preference. Direct --zap ignores Mole selections; review its data targets independently from your actual sync roots.

ls -ld "/Applications/MEGAsync.app"
ls -ld "$HOME/Library/Application Support/Mega Limited/MEGAsync"

Printed paths remain. Missing-path errors apply only to those locations; permission errors leave them unknown. These checks do not verify sync completion, custom sync roots or file recovery.

What Mole lists

The selected app and exact unprotected leaves can be checked. Review the product support and cache children separately from the shared Mega Limited parent. Confirmed own Finder extension containers/scripts can be checked by default; the team-prefixed mega.mac group needs review, is unchecked by default and is not automatically selected by the data setting. Deletion still checks group ownership. Remove data and settings with apps is off by default.

What this test covered

The official client and selected data were removed with source-built Mole on October 3, 2026. First launch reached sign-in without login or a sync root. A later run removed the previously missed product support/cache leaves and logs; group container and scripts remained after ownership refusal. Populated file recovery, live sync behavior and Homebrew-managed uninstall were not tested.