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 Audio Hijack on Mac

    Export or copy recordings to a folder you control and open a sample file. Review sessions, schedules and custom presets in Audio Hijack before clearing support data. Recordings saved to a user-selected folder are not disposable app caches.

    The recorded test used the official Mac package; the Homebrew route below is separate.

    Remove the app

    If you installed the optional Audio Hijack Scheduler, open Audio Hijack Settings and use its Uninstall button first. The current vendor manual then says to quit Audio Hijack and move the app to Trash. Do not manually remove audio components used by SoundSource or another Rogue Amoeba app.

    Review local data

    The path below is documented in the current Homebrew cask. In Finder, use Go › Go to Folder to inspect it. Do not remove its parent directory or another product’s data.

    Location Decision
    ~/Library/Application Support/Audio Hijack 4 Support folder in the cask zap list; inspect sessions and presets before removal.

    The tested package uses bundle ID com.rogueamoeba.audiohijack. Review only files that actually appear on this Mac. A missing path needs no cleanup.

    Vendor documentation · Additional vendor instructions

    Check what remains

    Run these read-only commands after quitting the app:

    pgrep -il 'Audio Hijack'
    ls -d "$HOME/Library/Application Support/Audio Hijack 4"
    

    No process output means there is no matching process running now; it does not prove every helper is gone. A listed process needs its owner checked. If ls prints the path, that item remains and needs review. “No such file or directory” means this path is absent; a permission error means its state was not established.

    If you installed it with Homebrew

    The current audio-hijack cask has a zap list covering Audio Hijack 4 support data, cache, HTTP storage, preferences and WebKit data. A direct brew command with --zap applies the cask list without consulting Mole’s checkboxes. After backing up, use this command without --zap:

    brew uninstall --cask audio-hijack
    

    Mole checks each zap path against your selections, other installed apps, and protected locations. An unchecked, shared, or unverifiable path suppresses --zap; selected remnants can still use Mole’s own removal flow. This cask was not the recorded installation channel.

    What Mole lists

    Mole selects exact bundle-ID cache, HTTP storage and preference rows by default. The display-name support folder is a review row. Mole does not replace the vendor flow for optional Scheduler or shared audio components.

    What this test covered

    The official ZIP build 4.6.0 was installed and removed on September 20, 2026. The first run did not write an Audio Hijack 4 support folder. The test did not establish whether a shared audio backend was installed or safely removed.

    Mac running low on space or slowing down? Mole can clean out the junk, remove apps completely and keep macOS in shape.

    Try Mole

    Mole · 鼴

    Cleanup, software, and status for your Mac.

    v1.16.0 (296) · 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.