How to uninstall Dropzone 5 on Mac
Copy wanted custom actions and note transfer destinations before removing Dropzone 5. This guide covers the downloaded Mac app, with Homebrew handled separately below.
Quit and remove the app
Keep files already transferred to other destinations. Review the action database before deleting the support folders.
Following the official Dropzone 5 uninstall instructions, click its menu-bar icon, open the Settings gear at the top right, and choose Quit. In System Settings › General › Login Items & Extensions, turn off any Dropzone 5 login entry if present. After backing up, move /Applications/Dropzone 5.app to Trash in Finder and leave Trash intact until the wanted data is confirmed saved.
Review local data
The data review below covers Dropzone 5. Keep Dropzone 4 data if that older app is still used; the Homebrew section separately describes its version 4 cask.
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/Dropzone |
Local data or settings; back up before deciding to remove |
~/Library/Application Support/Dropzone 5 |
Local data or settings; back up before deciding to remove |
If you installed it with Homebrew
The live dropzone cask installs Dropzone 4, while the test here used the official Dropzone 5 download. These commands handle the Homebrew installation and do not replace the Dropzone 5 removal steps.
To uninstall without running zap:
brew uninstall --cask dropzone
This removes the cask-managed app, 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 dropzone
The live zap targets are ~/Library/Application Scripts/com.aptonic.Dropzone4, ~/Library/Application Scripts/com.aptonic.LaunchAtLogin, ~/Library/Application Support/Dropzone 4, ~/Library/Caches/com.aptonic.Dropzone4, ~/Library/Containers/com.aptonic.Dropzone4, ~/Library/Containers/com.aptonic.LaunchAtLogin, ~/Library/Preferences/com.aptonic.Dropzone4.plist, ~/Library/Saved Application State/com.aptonic.Dropzone4.savedState.
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/Dropzone 5.app'
pgrep -ifl '/Applications/Dropzone 5[.]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/Dropzoneis listed for review and not selected by default.~/Library/Application Support/Dropzone 5is listed for review and not 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 official Dropzone 5 download was launched and removed; a later retest confirmed both action folders were removed. A system-rejected sharing container remained. No configured cloud actions were tested.