How to uninstall Dropshare 6 on Mac
Save upload history and copy any wanted local files before removing Dropshare. Confirm remote uploads in the storage service itself. This guide covers the downloaded Mac app, with Homebrew handled separately below.
Quit and remove the app
Keep remote uploads, storage accounts and local originals. Removing this Mac app does not cancel storage billing or erase hosted files.
Quit Dropshare 6 using its own quit action. In System Settings › General › Login Items & Extensions, turn off any Dropshare 6 login entry if present. After backing up, move /Applications/Dropshare 6.app to Trash in Finder and leave Trash intact until the wanted data is confirmed saved.
Review local data
Use Shift + Command + G in Finder to inspect each complete path. Copy wanted contents elsewhere before deciding to move that item to Trash. These locations come from the recorded test and the live Homebrew cask. Do not create a missing path. A * marks a matching range, not a literal filename; inspect the actual matches individually.
| Location | Contents and decision |
|---|---|
~/Library/Application Support/Dropshare 5 |
Local data or settings; back up before deciding to remove |
~/Library/Application Support/Dropshare 6 |
Local data or settings; back up before deciding to remove |
~/Library/Application Support/net.mkswap.Dropshare5 |
Local data or settings; back up before deciding to remove |
~/Library/Caches/net.mkswap.Dropshare6 |
Cache, logs or web state; optionally remove after quitting |
~/Library/Cookies/net.mkswap.Dropshare6.binarycookies |
Cache, logs or web state; optionally remove after quitting |
~/Library/Logs/Dropshare 6 |
Cache, logs or web state; optionally remove after quitting |
~/Library/Preferences/net.mkswap.Dropshare6.plist |
Preferences; keep if you want to restore settings |
If you installed it with Homebrew
To uninstall without running zap:
brew uninstall --cask dropshare
This removes the cask-managed app and its managed ds command link, without running its zap data list.
The following direct command applies the cask’s entire zap list independently of Mole’s checkboxes. Use it only after backing up and approving every target.
brew uninstall --cask --zap dropshare
The live zap targets are ~/Library/Application Support/Dropshare 6, ~/Library/Caches/net.mkswap.Dropshare6, ~/Library/Cookies/net.mkswap.Dropshare6.binarycookies, ~/Library/Logs/Dropshare 6, ~/Library/Preferences/net.mkswap.Dropshare6.plist.
Group folders, containers and support folders may contain wanted data. Use the command without zap when retaining any of them. Live cask.
Check the result
ls -ld '/Applications/Dropshare 6.app'
pgrep -ifl '/Applications/Dropshare 6[.]app/'
A listed app path means that bundle remains. “No such file or directory” means that exact path is absent; “Permission denied” leaves the check unconfirmed. This checks one location, not other copies, background services or user data.
A pgrep result means a running command line matches this app path. No output means no such match, not that independent helpers or other app copies are absent; an error leaves this step unconfirmed.
What Mole lists
~/Library/Application Support/Dropshare 5is listed for review and not selected by default.~/Library/Application Support/Dropshare 6is listed for review and not selected by default.~/Library/Application Support/net.mkswap.Dropshare5is selected by default.
These defaults assume “Remove data and settings with apps” is off, which is the default. Enabling it also selects eligible reviewed app data; shared and protected items retain their individual boundaries. Mole invokes Homebrew zap only when the whole zap scope passes its check. Unchecked, shared or out-of-boundary paths and unsupported directives suppress zap; selected remnants still use Mole’s own deletion flow.
What this test covered
The downloaded app was launched and uninstalled, then a separate removal retest confirmed the two history folders were removed. A system-rejected sharing container remained. No upload account or populated upload history was tested.