How to uninstall Jitsi Meet on Mac

The Jitsi Meet desktop app is a window onto meetings that run on a Jitsi server, so removing it does not delete any meeting, room or account. Only the app's own settings and web data live on this Mac. If you pointed the app at your own Jitsi server instead of the default one, note that address before you remove it. This guide covers the Jitsi Meet app downloaded from the jitsi-meet-electron GitHub releases and the Homebrew cask jitsi-meet; both install Jitsi Meet.app with the bundle ID org.jitsi.jitsi-meet.

Quit Jitsi Meet and remove the app

  1. Leave any meeting and quit Jitsi Meet from its menu.
  2. Check Activity Monitor that no Jitsi Meet process is left.
  3. Move Jitsi Meet.app from Applications to the Trash.

The project's README documents installation, including brew install --cask jitsi-meet, but gives no uninstall steps, so the locations below come from the Homebrew zap list and the recorded test.

Where Jitsi Meet keeps its data

Location What it holds What to do
~/Library/Application Support/Jitsi Meet The app's local data: settings and web storage, 1.9 MB after one launch in the test Remove it once you no longer use the app; nothing in it is needed to join meetings elsewhere
~/Library/Logs/Jitsi Meet App logs Remove with the app
~/Library/Preferences/org.jitsi.jitsi-meet.plist App preferences Remove with the app

Check the result

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

pgrep -lf "Jitsi Meet.app"
ls -d "$HOME/Library/Application Support/Jitsi Meet" "$HOME/Library/Logs/Jitsi Meet"
  • No output from pgrep means the app is not running. A listed process means it is still open or still in a meeting.
  • ls -d prints each folder that still exists and reports "No such file or directory" for the rest. Application Support/Jitsi Meet still being there is what a Mole uninstall with the default selection leaves; the logs folder should be gone.

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 jitsi-meet cask's zap list names two paths, ~/Library/Application Support/Jitsi Meet and ~/Library/Logs/Jitsi Meet. Running brew uninstall --cask --zap jitsi-meet yourself moves both to the Trash, whatever you ticked in Mole. To remove only the app:

brew uninstall --cask jitsi-meet

Homebrew's jitsi-meet cask

What Mole lists

For Jitsi Meet downloaded from GitHub:

  • ~/Library/Application Support/Jitsi Meet is listed but not selected, because it is named after the app rather than its bundle ID.
  • The rebuildable caches inside it (Cache, Code Cache, GPUCache, DawnGraphiteCache, DawnWebGPUCache, blob_storage) are listed as their own rows and selected by default.
  • ~/Library/Logs/Jitsi Meet, the org.jitsi.jitsi-meet preferences file, its recent-documents list and its temporary caches are selected by default.

What this test covered

On September 26, 2026, Jitsi Meet 2026.8.0 was downloaded from the jitsi-meet-electron GitHub releases, installed, launched once without joining a meeting, and uninstalled with a development build of Mole with every listed row ticked. While it ran, Mole's Status page showed Jitsi Meet as one row of six processes, about 374 MB. The app and all 12 listed rows went to the Trash, including the 1.9 MB data 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 same source gave the same result. No meeting was joined in either run, so camera, microphone and screen sharing were not exercised.