How to uninstall Folx on Mac
Before removing Folx, save and copy your finished downloads, incomplete downloads and torrent data to a separate backup, then open the copy. This guide covers the official Mac download; Homebrew-specific removal is separate below.
Quit and remove the app
Finish current work and quit Folx. Check Activity Monitor for its process before removing the app in Finder. In Applications, move Folx.app to the Trash; if you keep it elsewhere, use its actual location. Keep the Trash until your backup has been checked.
Review local data
These exact locations were observed in the removal record. 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/Folx~/Library/HTTPStorages/com.eltima.Folx3
Check the result
This read-only check searches full process command lines, not disk contents.
pgrep -ifl 'Folx'
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 folx
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.eltima.Folx3.FolxSafariExtension~/Library/Application Support/Eltima Software/Folx3~/Library/Application Support/Folx~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.eltima.folx.host.json~/Library/Application Support/Mozilla/NativeMessagingHosts/com.eltima.folx.host.json~/Library/Caches/com.eltima.Folx3~/Library/Containers/com.eltima.Folx3.FolxSafariExtension~/Library/HTTPStorages/com.eltima.Folx3~/Library/Internet Plug-Ins/Folx3Plugin.plugin~/Library/Logs/Folx.log~/Library/Logs/Folx3.log~/Library/Preferences/com.eltima.Folx3.plist~/Library/Preferences/com.eltima.FolxAgent.plist~/Library/Saved Application State/com.eltima.Folx3.savedState
A direct brew uninstall --cask --zap folx 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/Folx is listed for review and is not selected by default. ~/Library/HTTPStorages/com.eltima.Folx3 is selected by default when it is attributable and not protected.
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 official app was launched and removed. The support and HTTP storage rows were left unchecked and survived. Downloads and a pre-existing vendor activation file were not removed.