How to uninstall Ferdium on Mac

Ferdium keeps the sign-in sessions of every service you added only on this Mac. Its documentation says that session information stays on your local machine, so after a reinstall or on another Mac each service has to be signed in again. Export your Ferdium configuration first if you want your services and workspaces back later. Removing the app does not sign you out of the services themselves or delete a Ferdium account. This guide covers Ferdium downloaded from ferdium.org or its GitHub releases and the Homebrew cask ferdium; both install Ferdium.app with the bundle ID org.ferdium.ferdium-app.

Export your configuration

With Ferdium open, choose Help › Import/Export Configuration Data. It opens a local page in your browser where you can export a .ferdium-data file (Ferdium: internal server). Keep the file somewhere off this Mac. The export restores the service list and settings, not the sessions: Ferdium's migration notes say every service must be signed in by hand again.

If you use a Ferdium account or your own Ferdium Server, services and workspaces sync through that server instead (Ferdium FAQ); the export is still a useful copy.

Quit Ferdium and remove the app

  1. Quit Ferdium from its menu and check Activity Monitor that no Ferdium process is left.
  2. Move Ferdium.app from Applications to the Trash.
  3. If Ferdium was set to open at login, open System Settings › General › Login Items & Extensions afterwards. In an earlier test a Ferdium login entry was still registered with macOS after the app was gone; an entry pointing at a removed app starts nothing, and you can turn it off there.

Where Ferdium keeps its data

After completing the export and quitting, press Shift + Command + G in Finder to open each exact location below and move only the Ferdium item you chose to discard to the Trash. Removing local session data requires signing in to each service again; keep files downloaded from those services separately.

Location What it holds What to do
~/Library/Application Support/Ferdium Ferdium's configuration folder: services, workspaces, settings and every service's local session Keep it until you have exported what you need; remove it once you no longer use Ferdium on this Mac
~/Library/Preferences/org.ferdium.ferdium-app.plist App preferences Remove with the app
~/Library/Application Support/Caches/ferdium-updater, ~/Library/Logs/Ferdium The updater's download cache and logs named in the Homebrew zap list Remove with the app if present
~/Library/Caches/com.ferdium.ferdium-app and ~/Library/Caches/com.ferdium.ferdium-app.ShipIt Older-ID app and updater caches in the current cask Remove only if attributable to this retired Ferdium installation
~/Library/Preferences/com.ferdium.ferdium-app.plist, ~/Library/Preferences/com.electron.ferdium.plist and ~/Library/Preferences/com.electron.ferdium.helper.plist Older-ID app and helper preferences in the current cask Copy wanted settings first; keep while another Ferdium installation uses them
~/Library/Saved Application State/com.ferdium.ferdium-app.savedState and ~/Library/Saved Application State/org.ferdium.ferdium-app.savedState Saved window state in the current cask Remove only the confirmed unwanted Ferdium entries

For the cask's ByHost preferences, open ~/Library/Preferences/ByHost and inspect only filenames beginning com.ferdium.ferdium-app.ShipIt. and ending .plist. For recent-document records, open ~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments and inspect files matching org.ferdium.ferdium-app.sfl*. These are filename patterns, not literal paths to paste. Remove only a confirmed current or previously used Ferdium file that no retained installation needs; leave the parent and other apps' files alone.

The configuration folder location comes from the Ferdium FAQ. Files you downloaded from inside a service went wherever you saved them, usually your Downloads folder, and are yours to keep.

Check the result

After the app is in the Trash, run these read-only commands:

pgrep -lf Ferdium.app
ls -d "$HOME/Library/Application Support/Ferdium"
  • No output from pgrep means this full-command pattern found no match, not that every Ferdium helper has exited. Check any remaining processes in Activity Monitor against their executable paths.
  • ls -d printing the path means the configuration folder is still there, which is expected when you leave that row unchecked. "No such file or directory" means it is gone.

For how chat apps split cache from history, see Discord, Slack, and Teams on Mac: Cache vs History vs Downloads.

If you installed it with Homebrew

Mole skips --zap when the zap list reaches data you left unchecked, a path another installed app uses, or anything Mole cannot check, and it still cleans the leftovers you selected.

The ferdium cask's zap list includes ~/Library/Application Support/Ferdium, which holds your services and their sessions, and ~/Library/Application Support/Caches/ferdium-updater, along with caches, ~/Library/Logs/Ferdium, the recent-documents list, and preferences and saved state under both org.ferdium.ferdium-app and the older com.ferdium.ferdium-app and com.electron.ferdium names. Running brew uninstall --cask --zap ferdium yourself moves all of them to the Trash, whatever you ticked in Mole. Ordinary uninstall requests Ferdium to quit and removes the managed app plus the cask-defined Ferdium Helper diagnostic reports under /Library/Logs/DiagnosticReports. It leaves zap-only profile and settings data:

brew uninstall --cask ferdium

Homebrew's ferdium cask

What Mole lists

For Ferdium downloaded from ferdium.org:

  • ~/Library/Application Support/Ferdium holds services and sessions. It is listed unchecked when Remove data and settings with apps in General > Cleaning is off; turning it on can preselect this eligible folder. Complete the configuration export before deleting it, or uncheck it to retain the profile.
  • The rebuildable caches inside it (Cache, Code Cache, GPUCache, DawnGraphiteCache, DawnWebGPUCache, blob_storage) are listed as their own rows and selected by default.
  • The org.ferdium.ferdium-app preferences file, its recent-documents list and its temporary caches are selected by default.
  • Files you saved to Downloads are not listed.

What this test covered

On September 26, 2026, Ferdium 7.2.3 was downloaded from Ferdium's GitHub releases, installed, launched once without an account or any service, and uninstalled with a development build of Mole with every listed row ticked. While it ran, Mole's Status page showed Ferdium as one row of seven processes, about 495 MB. The app and all 11 listed rows went to the Trash, including the 2.2 MB configuration folder, and a rescan found none of them left; no login item or background task appeared. An earlier test on September 21, 2026 with the same version from the official download removed the same folders; that time a Ferdium login entry stayed registered with macOS after the app was gone. No service was added, so the export and session behaviour above comes from Ferdium's documentation, not from this test.