How to uninstall Resilio Sync on Mac
Before removing Resilio Sync, save and copy every wanted file in each shared folder to a separate backup, then open the copy. This guide covers the official Mac download; Homebrew-specific removal is separate below.
Resilio Sync synchronizes between peers, so there may be no cloud website copy. Confirm a complete copy on another peer and COPY wanted local files outside every shared folder before quitting. Keep the shared folders; do not move or delete their contents while sync is active.
Quit and remove the app
Finish current work and quit Resilio Sync. Check Activity Monitor for its process before removing the app in Finder. In Applications, move Resilio Sync.app to the Trash; if you keep it elsewhere, use its actual location. Keep the Trash until your backup has been checked.
Check the result
This read-only check searches full process command lines, not disk contents.
pgrep -ifl 'Resilio Sync'
No output with exit status 1 means no matching command line was found. A printed entry needs inspection in Activity Monitor because names can match unrelated processes. An error is not proof of removal. Also check that the app is absent from its original Finder location; a retained data folder or independent component does not mean the app is still installed.
If you installed it with Homebrew
Use the installed cask receipt and uninstall without zap.
brew uninstall --cask resilio-sync
Ordinary uninstall requests the app to quit and removes its managed application without running zap. The live cask additionally names these zap targets, which can erase settings, local data or integration files; this is Homebrew’s list, not a vendor data-location claim.
~/Library/Application Scripts/com.resilio.Sync.FinderExtension~/Library/Application Support/Resilio Sync~/Library/Caches/com.resilio.Sync~/Library/Containers/com.resilio.Sync.FinderExtension~/Library/Group Containers/group.com.resilio.Sync~/Library/Preferences/com.resilio.Sync.plist
A direct brew uninstall --cask --zap resilio-sync runs its own zap scope without consulting Mole’s checkboxes. Mole uses zap only when the complete scope passes its gate; unchecked or shared paths, paths outside the review boundary, unknown stanzas and unsupported directives suppress it. Selected remnants still use Mole’s deletion path.
What Mole lists
~/Library/Application Support/Resilio Sync is local app state listed for review, not selected by default; retain it when you need its configuration. Exact-identity preferences and caches are normally selected. Finder extension containers still require permission and ownership checks, and App Group folders remain when Mole cannot exclude another installed owner. Keep your shared folders and their verified backups separately.
These defaults assume “Remove data and settings with apps” is off. Opting in also selects eligible reviewed app data; shared stores and protected data retain individual review or stay locked.
What this test covered
The October 3, 2026 record covers the following test. The official app was launched and removed using a source-built Mole app, without running a sync. Two App Groups remained because ownership inventory could not be read; a Finder extension container remained after a permission failure. First-launch coverage was partial. No peer sync or data preservation test was performed.