How to uninstall Dropzone 4 on Mac
Before removing Dropzone 4, save and copy your files queued in Drop Bar, custom actions and upload settings to a separate backup, then open the copy. This guide covers the Dropzone 4 Mac app; Homebrew-specific removal is separate below.
Finish file transfers and move wanted Drop Bar material into a separate copied backup before removing data. The vendor’s current uninstall page describes Dropzone 5, so its version-specific gear menu is not evidence for Dropzone 4. Quit your installed Dropzone 4 through its own menu, then remove that version’s app. Keep other Dropzone versions and their files.
Quit and remove the app
Finish current work and quit Dropzone 4. Check Activity Monitor for its process before removing the app in Finder. In Applications, move Dropzone 4.app to the Trash; if you keep it elsewhere, use its actual location. Keep the Trash until your backup has been checked. Official documentation
Review local data
The locations below come from the test record or the live cask; their individual treatment is explained below. Open them through Finder’s Go › Go to Folder. Copy wanted contents first; leave them if you want to keep settings or cannot establish ownership. They are optional data removal, not a prerequisite for removing the app.
~/Library/Application Support/Dropzone~/Library/Application Support/Dropzone 4~/Library/Application Support/com.aptonic.Dropzone4
Check the result
This read-only check searches full process command lines, not disk contents.
pgrep -ifl 'Dropzone 4'
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 dropzone
The command removes the cask’s managed application artifacts 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.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
A direct brew uninstall --cask --zap dropzone 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.
com.aptonic.LaunchAtLogin is a companion identifier, not proof of exclusive ownership by Dropzone 4. Keep its script directory and container if another Dropzone installation still uses them; do not use direct zap in that case.
What Mole lists
~/Library/Application Support/Dropzone and ~/Library/Application Support/Dropzone 4 are listed for review and are not selected by default. ~/Library/Application Support/com.aptonic.Dropzone4 is a bundle-identity row selected by default when present and not protected. Back up all wanted content before selecting these rows. The shared extension container may be retained when permission checks fail.
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 September 21, 2026 record covers the following test. The record covers Dropzone 4 and its observed user files, not Dropzone 5. Accessibility permission was not granted. The selected Dropzone 4 and bundle-identity support folders were removed; the unsuffixed Dropzone folder survived and was later added for review. A Share container remained after a permission failure. The installation channel was not separately established in that record.