How to uninstall CloudMounter on Mac

CloudMounter shows your cloud storage in Finder without syncing it to your Mac, so your files stay in Dropbox, Google Drive, OneDrive, S3 or wherever they live, and removing the app does not delete them. Two things need care first. Deleting a file inside a mounted drive deletes it in the cloud, so do not "clean up" through a mount. And if you used CloudMounter's encryption, copy out readable versions of anything you need while CloudMounter is still installed and you still have the password. This guide covers CloudMounter downloaded from Electronic Team's site (formerly Eltima) and the Homebrew cask cloudmounter; both install CloudMounter.app with the bundle ID com.eltima.cloudmounter.

Unmount your drives first

1. Let any copy to or from a mounted drive finish.
2. Unmount every connected drive in CloudMounter, or eject it in Finder's sidebar.
3. If you encrypted folders, make sure you have what you need. CloudMounter keeps the encryption password in your Keychain when you let it, and removes it while the folder is locked (CloudMounter: using encryption); the documentation does not describe reading encrypted files without CloudMounter.
4. Quit CloudMounter from its menu bar icon and check Activity Monitor that no CloudMounter process is left.

Remove the app

Electronic Team's steps are to drag CloudMounter from Applications to the Trash. If macOS says the app cannot be moved, disable the CloudMounter extension first, then try again (Uninstall CloudMounter). Their page names the older System Preferences › Extensions pane; on current macOS the extensions are in System Settings › General › Login Items & Extensions. In the test, the app went to the Trash without that step.

CloudMounter ships two extensions inside the app, a Finder extension and a File Provider extension that presents the mounts, plus a small launcher used for opening it at login. All three leave with the app.

Where CloudMounter keeps its data

These locations come from the Homebrew zap list and the test; Electronic Team's page lists none of them.

Check the result

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

pgrep -il cloudmounter
pluginkit -m | grep -i eltima.cloudmounter
ls -d "$HOME/Library/Group Containers/XS85JU6YZ3.com.eltima.cloudmounter"

• No output from pgrep means CloudMounter is not running. A listed process means the app or one of its extensions is still active.
• No output from pluginkit means the extensions are no longer registered. A listed line means macOS still has a CloudMounter extension registered, usually from another copy of the app somewhere on the Mac.
• ls -d printing the path means the group container is still there, which is what happened in the test. Once you are sure no copy of CloudMounter is left on the Mac, you can move it and the ~/Library/Application Scripts folder of the same name to the Trash in Finder. "No such file or directory" means it is 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 cloudmounter cask's zap list covers every ~/Library/Application Scripts/*.com.eltima.cloudmounter* folder, ~/Library/Application Support/com.eltima.cloudmounter, ~/Library/Application Support/FileProvider/com.eltima.cloudmounter.mountprovider, the cache, every ~/Library/Containers/com.eltima.cloudmounter.* folder, every ~/Library/Group Containers/*.com.eltima.cloudmounter folder, the HTTP storage, ~/Library/Logs/CloudMounter.log, the recent-documents list, the preferences file and ~/Library/Preferences/com.eltima.activator.xml. Running brew uninstall --cask --zap cloudmounter yourself moves all of them to the Trash, including the Eltima file another app may use, whatever you ticked in Mole. Because the group container and the Eltima file are unticked by default, Mole leaves --zap out while they stay unticked. To remove only the app:

brew uninstall --cask cloudmounter

Homebrew's cloudmounter cask

What Mole lists

For CloudMounter downloaded from Electronic Team:

• The preferences file, Application Support/com.eltima.cloudmounter, the cache, HTTP storage, WebKit data, CloudMounter.log and the temporary caches are selected by default.
• The Containers and Application Scripts folders of the two extensions inside the app, CMFinderSync and mountprovider, are selected by default, because both ship in CloudMounter.app and their IDs continue the app's own.
• Application Support/FileProvider/com.eltima.cloudmounter.mountprovider is listed but not selected. Tick it after your drives are unmounted.
• The group container XS85JU6YZ3.com.eltima.cloudmounter and its Application Scripts folder are listed but not selected. Before removing a group, Mole checks that no other installed app claims it; when that check cannot clear the group, Mole keeps it and the row says it could not confirm that no other app uses the group.
• com.eltima.activator.xml is listed but not selected.

What this test covered

On September 26, 2026, CloudMounter 4.18 was downloaded from Electronic Team's download server, installed, launched once without adding a cloud account, and uninstalled with a development build of Mole with every listed row ticked. While it ran, Mole's Status page showed CloudMounter as one row of three processes, about 50 MB. The app and 14 listed rows went to the Trash, including both extensions' folders and the File Provider folder. Mole kept the group container and its Application Scripts folder: during the uninstall another app's files on the Mac changed, so Mole could not confirm that no other app used the group. No login item or background task appeared. An earlier test on September 23, 2026 with the same version also removed everything else and also left the group container and its Application Scripts folder, for a different reason on that run; the File Provider extension did not stop the app from going to the Trash. No drive was mounted and no encryption was used, so the unmount and encryption steps come from Electronic Team's documentation.