How to uninstall Stremio on Mac

Stremio runs an embedded local streaming server alongside its window, so quitting the app closes both together. Anything you play through Stremio's cloud catalog or a signed-in Stremio account lives on Stremio's servers, not on your Mac, so removing the app never touches your account or its watch history. These steps cover the official DMG from Stremio's download page; the Homebrew cask stremio is a separate path with its own risk, described below.

Quit Stremio and remove the app

1. Stop anything playing, then quit Stremio from its menu or Dock icon. This also stops its embedded local server.
2. Search for Stremio in Activity Monitor to confirm it has exited; look for the main Stremio process together with the local node helper it starts.
3. Find Stremio in Finder's Applications folder and move it to the Trash. If macOS says it is in use, return to the previous step.
4. Open System Settings › General › Login Items & Extensions and check for a Stremio entry, though the recorded test found none registered.

Where Stremio keeps local data

If you have used Stremio since an older version, its Homebrew cask still names legacy identifiers such as com.smartcodeltd.stremio and com.stremio.stremio-shell-macos for preferences, caches and WebKit data; those come from earlier app releases and are separate from the current bundle ID above.

Check the result

pgrep -il stremio
launchctl list | grep -i westbridge
ls -d ~/Library/Application\ Support/stremio-server
ls ~/Library/Caches | grep -i node

• No output from pgrep means neither Stremio nor its embedded server process is running. A listed process means it is still active; quit it before touching its data.
• No output from launchctl list means no background job under Stremio's identifier is loaded; the recorded test never found one.
• ls -d printing the stremio-server path means that row is still there, expected if you kept it unticked. "No such file or directory" means it is gone.
• The node cache line printing a result is not evidence of a Stremio leftover on its own; several other apps that bundle Node.js can write the same folder name.

If you installed it with Homebrew

Mole checks the zap list first: unchecked or shared data, or anything it cannot fully verify, keeps --zap out, and it still removes whatever you selected.

The stremio cask's zap list reaches ~/Library/Application Support/stremio-server, plus the app's own and legacy preferences, caches and WebKit data, and Stremio's crash reports under ~/Library/Logs/DiagnosticReports. Running brew uninstall --cask --zap stremio yourself moves all of that to the Trash without looking at Mole's checkboxes. Homebrew Stremio cask

Since the zap list reaches the unticked Application Support/stremio-server row, Mole leaves out --zap for a Homebrew install of Stremio unless you tick it.

To remove only the app and keep its server settings:

brew uninstall --cask stremio

What Mole lists

• ~/Library/Application Support/stremio-server is listed but not selected, since it is named after the embedded server component rather than the app's bundle ID.
• Preferences, caches and WebKit data filed under com.westbridge.stremio5-mac are selected by default, along with their short-lived temporary caches.
• Data written under the shared executable name node, such as ~/Library/Caches/node, is never claimed; Mole does not attribute a generic shared runtime name to one app.
• Your Stremio account, its cloud library and watch history are never listed; they live on Stremio's own servers.

What this test covered

On September 25, 2026, Stremio 5.1.26 was downloaded from the official DMG, installed into Applications, opened once with nothing played and no sign-in, then removed with a development build of Mole with every listed row ticked, without ever running Homebrew. The 271.9 MB app and all nine listed rows, under 2 MB together, went to the Trash with no failures. A rescan by name afterwards found data written under the shared node executable name (~/Library/Caches/node, ~/Library/HTTPStorages/node, ~/Library/Preferences/node.plist, a Node compile cache in the temporary folder), which is not attributed to Stremio by design, the same way a generic Electron name is never claimed. It also found three empty WebKit helper folders and a socket file named after Stremio in the per-user temporary folder under /var/folders, which Mole had not listed. No sign-in, streaming or cloud library sync was tested.