Uninstall Logi Options+ on Mac

Logi Options+ installs across both your user folder and system-level /Library, runs a device-management daemon, and its installer sets up a second, separate program alongside it, so plan for an admin password prompt and a possible restart. These steps cover Logitech's official installer (from logitech.com) and the Homebrew cask logi-options+, which runs that same official installer under the hood.

Quit Logi Options+ and its background processes

Quit Logi Options+ from its menu bar icon. Logitech's installer also sets up several background jobs: com.logi.optionsplus (the main app), com.logi.optionsplus.driverhost and com.logi.optionsplus.updater, and com.logi.cp-dev-mgr, a device-manager daemon that runs even when Logi Options+ itself is closed. The installer may also set up com.logitech.LogiRightSight and its agent, which handle AI framing for Logitech webcams. Move Logi Options+ from Applications to the Trash once these have quit; if macOS says it is still running, check Activity Monitor first.

The separate LogiPluginService app

Logitech's installer also places a second, independent program at /Applications/Utilities/LogiPluginService.app (com.logi.pluginservice). It is not part of the Logi Options+ bundle and is not removed when you uninstall Logi Options+ through either channel below; it shows up as its own entry in Mole's Software list. Remove it separately, the same way, if you no longer want it.

If your Mac shows a Logitech.localized/LogiRightSightForWebcams entry, that is also a separate product the installer sets up for webcam framing, with its own installer receipt and login item; moving Logi Options+ to the Trash or removing it with Mole does not remove it either, while the Homebrew cask's uninstall step does (see below).

Where Logi Options+ keeps its data

A small ~/Library/Application Support/LogiOptionsPlus folder can end up owned by root rather than by you, because Logitech's installer runs the driver setup step with administrator privileges. The September 23 to 24 tests could not move that folder; a later October 3 run did remove it, so a prior permission failure does not mean it is always protected. Check ownership and permissions (ls -la ~/Library/Application\ Support/) before deciding whether to remove it yourself with Finder or an administrator's help.

Check the result

Run these read-only commands in Terminal:

pgrep -il logi
launchctl list | grep -i logi
launchctl print system/com.logi.cp-dev-mgr
pkgutil --pkgs | grep -i logi

No output from pgrep means no matching Logitech process was found. The launchctl list filter only checks this user session. The separate launchctl print checks the system device-manager daemon: a record means registered, state = running means running, and a service-not-found message means absent. Permission errors leave that check unresolved. pkgutil lists any Logitech installer receipts still recorded on this Mac; a receipt without a matching app or folder is a record, not a running program, and does not affect anything.

For other apps whose installer leaves a background job running after the app itself is gone, see App Still Running After Uninstall on Mac? Find Login Items and Launch Tasks.

If you installed it with Homebrew

Mole skips --zap when its list reaches unchecked or shared data, or cannot be fully checked, and still cleans the leftovers you selected.

The logi-options+ cask runs Logitech's own installer with sudo, so installing it also prompts for an administrator password, and Logitech's installer recommends a restart afterward. Even without --zap, Homebrew's ordinary removal already quits the background jobs above, deletes the app, the Driver Installer bundle and the system-level /Library/Application Support/Logi and /Library/Application Support/Logitech.localized/LogiOptionsPlus folders, so ordinary removal can affect another Logitech app using that shared Logi folder even if you omit zap. It also stops the LogiRightSight jobs and removes the LogiRightSightForWebcams package. Running brew uninstall --cask --zap logi-options+ yourself additionally removes your device profiles (~/Library/Application Support/LogiOptionsPlus), a shared ~/Library/Application Support/Logi folder, several preferences files including com.logi.cp-dev-mgr.plist, saved window state, and two folders, logi and LogiOptionsPlus, in the Shared folder under Users that every account on this Mac can see, not just yours, whatever you selected in Mole. It does not remove LogiPluginService.app, which stays installed either way. Back up your device profiles first, or skip zap to keep them:

brew uninstall --cask logi-options+

Account and subscription

Logi Options+ is free; there is no subscription. If you sign in with a Logi ID, the app can back up your device settings to Logitech's cloud automatically. Check the sync/backup toggle in the app's account settings before removing anything if you want those settings available on another Mac later. Uninstalling does not delete your Logi ID account; it only removes what is stored on this Mac, and Windows and Mac device settings are not compatible with each other even in the same account.

What Mole lists

When you remove it with Mole:

• For the official installer, Mole can list system-level Logi folders and their log folder for administrator-approved removal. Keep the shared /Library/Application Support/Logi row if another Logitech product still uses it; review the Options+-specific leaf separately.
• /Applications/Utilities/LogiPluginService.app is never treated as part of Logi Options+; it appears as its own row in Mole's Software list.
• The September 23 to 24 official-installer tests left the root-owned ~/Library/Application Support/LogiOptionsPlus folder and the com.logi.cp-dev-mgr preferences behind; the October 3 run removed both reviewed paths. That does not establish removal of every possible device-manager cache. Mole can also list the home-folder data from Homebrew's zap list. With Remove data and settings with apps off, those review rows are unselected; enabling it can preselect eligible app-owned data. Keep device profiles you still need and shared device-manager data used by another Logitech app. A selected row can still fail to move if its permissions prevent removal.
• For a Homebrew install, Homebrew's own uninstall step clears the system-level /Library folders. The cask's zap list also reaches the Shared folder under Users, outside your ~/Library, so Mole leaves --zap out and moves only the rows you selected.

What this test covered

On October 3, 2026, a Mole Preview build removed Logi Options+ from an official installer installation with all 21 review rows selected. Twenty checked paths were moved to the Trash, including the user support directory, both Options+-specific system support leaves, the log leaf, the com.logi.cp-dev-mgr preferences and three launch jobs. A diagnostic report was kept by the test Mac’s whitelist. Logi Options+ Driver Installer and LogiPluginService were then selected and removed separately; their four checked app/data paths and the Driver Installer’s empty outer bundle were absent afterwards. RightSight was retained as a separate product. The first-launch file scan was partial, receipts were left in place and no full device-profile restoration was tested.

Logi Options+ was tested through Homebrew and the official installer. On September 19, 2026, a Preview build of Mole removed it through the Homebrew cask: only the main app was selected by default, while the Driver Installer and LogiPluginService rows were shown but not ticked; 567.3 MB was removed, 29 KB was kept (a system crash report and a launch item), and LogiPluginService.app (346 MB) was left behind by design. On September 23 and 24, 2026, the official Logitech installer was used instead: the first Mole run removed the main /Library/Application Support/Logi folder and three background jobs but missed a 753 MB Logitech.localized/LogiOptionsPlus folder because of how its vendor folder was named; that gap was fixed, and a second run on September 24 removed it along with the log folder. A folder inside the Driver Installer bundle, the root-owned home-directory folder above, and the com.logi.cp-dev-mgr preferences were left behind in both September official-installer runs.