Skip to main content
Mole
Features Tested apps Testimonials Pricing FAQ Blog
EnglishEN 简体中文中 繁體中文繁 日本語日 한국어한 FrançaisFR DeutschDE ItalianoIT EspañolES PortuguêsPT
Buy nowBuy Download

    Help, documentation, releases, and articles.

    Home/Apps tested with Mole

    How to uninstall OmniDiskSweeper on Mac

    Quit OmniDiskSweeper before removing it, and keep the files it showed in its disk scan. The vendor describes it as a viewer that can Trash files you choose; scanned documents do not become app data. This guide covers the official DMG app and Homebrew cask omnidisksweeper.

    Remove the viewer, keep scanned files

    Stop using its Trash action and close any scan windows, then quit OmniDiskSweeper. Do not select other files in OmniDiskSweeper as a way to uninstall the viewer.

    If retaining settings for a reinstall, copy ~/Library/Preferences/com.omnigroup.OmniDiskSweeper.plist and verify the copy first. Then move OmniDiskSweeper.app from Applications to the Trash in Finder. The current cask also lists ~/Library/Caches/com.omnigroup.OmniDiskSweeper and generated help entries named OmniDiskSweeper Help* inside ~/Library/Caches/com.apple.helpd/Generated. Inspect that parent in Finder and remove only confirmed OmniDiskSweeper help entries, keeping the parent and other apps' help.

    The same cask lists updater data shared under Omni's name:

    • ~/Library/Application Scripts/com.omnigroup.OmniSoftwareUpdate.OSUCheckService
    • ~/Library/Containers/com.omnigroup.OmniSoftwareUpdate.OSUCheckService
    • ~/Library/Preferences/com.omnigroup.OmniSoftwareUpdate.plist

    Keep these if you still use another Omni application or cannot confirm exclusive ownership. They are not the files displayed in your scan.

    If you installed it with Homebrew

    The cask declares no separate ordinary uninstall step beyond its managed application.

    brew uninstall --cask omnidisksweeper
    

    Zap additionally processes all the settings, caches, help and updater locations above. A direct brew uninstall --cask --zap omnidisksweeper ignores Mole's checkboxes and can affect updater data needed by another Omni app. Mole uses zap only when its complete scope passes selection, ownership and safety checks; selected remnants otherwise use its own Trash flow.

    Check the result

    pgrep -ifl OmniDiskSweeper
    ls -ld "$HOME/Library/Preferences/com.omnigroup.OmniDiskSweeper.plist"
    

    No pgrep output means no arguments matched that name; identify a surviving match before quitting it. A printed preferences path still exists, which is expected if saved. A missing-path error means that exact file is absent; permission and command errors are inconclusive. Your documents staying on disk is the intended result.

    What Mole lists

    The app's exact cache and preferences rows are selected by default, so uncheck preferences you want to keep. Other cask-derived updater and help entries need separate ownership review. Reviewed app data starts unchecked with Remove data and settings with apps off; turning it on can preselect eligible unshared data, but shared Omni stores still need individual review and safety checks.

    What this test covered

    On September 21, 2026, OmniDiskSweeper 1.16 from its official DMG was copied into Applications, opened and removed using the default selection. The record confirms app removal, not deletion of the files it can scan or recovery of saved settings. The Homebrew route and shared updater removal were not tested.

    If Mac apps leave files behind after uninstalling, try Mole. I've personally tested and inspected 799 Mac apps.

    Try Mole

    Mole · 鼴

    Cleanup, software, and status for your Mac.

    v1.16.0 (301) · Release notes

    Product

    Mac Cleaner App Uninstaller Mac Optimizer Disk Analyzer System Monitor

    Support

    Help Documentation Releases Blog

    Legal

    Terms of Service Privacy Policy Refund Policy

    Resources

    CLI Tool Affiliate Program

    Connect

    Twitter hi@mole.fit

    Mole’s only official website mole.fit · Avoid installers from unknown sources

    The CLI stays free for terminal workflows.