If you've decided to uninstall Avast on Mac, dragging the app to the Trash is not enough. Avast installs background services, kernel extensions (on older macOS versions), and several hidden support files that survive a standard drag-to-trash removal. On macOS Sequoia and the upcoming Tahoe release — whether you're on Apple Silicon or an Intel Mac — this guide walks you through every step required to remove Avast Free Antivirus completely, with no leftover daemon running in the background.
Why Avast Leaves So Much Behind
Avast is a full security suite, not a simple utility. During installation it registers a LaunchDaemon (a system-level background service that starts before you log in), places helper tools outside the main app bundle, and writes configuration and quarantine databases to several locations in ~/Library and /Library. Even after you delete the main Avast.app, the LaunchDaemon keeps the core protection process running until the next reboot — or indefinitely if you never know to look for it.
Before You Start: Back Up and Check Running Processes
Before removing any security software, make sure you have an alternative plan or are ready to rely on macOS's built-in protections (XProtect, Gatekeeper, and the Malware Removal Tool). Then confirm Avast is actively running:
- Open Activity Monitor (Applications → Utilities → Activity Monitor).
- Search for
avastin the search bar. Note any processes listed — common ones includecom.avast.helperandcom.avast.proxy. - If you see an
Avastmenu-bar icon, click it and choose Quit Avast before proceeding.
Step-by-Step: How to Uninstall Avast on Mac Completely
Avast ships its own uninstaller inside the app bundle. Using it is the correct starting point because it stops the LaunchDaemon cleanly before deleting files.
- Open Avast Security. Find it in
/Applications/Avast.appand double-click to launch it. - Run the built-in uninstaller. In the menu bar click Avast Security → Uninstall Avast Security. A wizard will appear. Follow the prompts and enter your administrator password when asked.
- Restart your Mac. The uninstaller requires a reboot to finish removing kernel components on macOS Ventura and earlier. On Sequoia, a reboot is still recommended to clear any lingering network extension state.
- Verify the daemon is gone. After reboot, open Terminal and run:
launchctl list | grep avast
If the command returns nothing, the daemon was removed successfully. If you still see output, proceed to the manual cleanup section below.
Manual Cleanup: Every File Location to Check
Even after the official uninstaller runs, residual files often remain in user and system Library folders. Work through each location below. Use Terminal or Finder's Go → Go to Folder menu to navigate to hidden paths.
Application Support and Preferences
~/Library/Application Support/com.avast.AAFM~/Library/Preferences/com.avast.AAFM.plist~/Library/Preferences/com.avast.helper.plist~/Library/Saved Application State/com.avast.AAFM.savedState
Caches
~/Library/Caches/com.avast.AAFM/Library/Caches/com.avast.antivirus
System-Level Files (require administrator password)
/Library/Application Support/Avast— quarantine database and scan engine/Library/LaunchDaemons/com.avast.proxy.plist— the background service definition/Library/LaunchDaemons/com.avast.helper.plist/Library/LaunchAgents/com.avast.useralert.plist/Library/PrivilegedHelperTools/com.avast.helper/private/var/log/avast— log files
To remove a LaunchDaemon safely in Terminal before deleting its plist, unload it first:
sudo launchctl bootout system /Library/LaunchDaemons/com.avast.proxy.plistsudo rm /Library/LaunchDaemons/com.avast.proxy.plist
Repeat for each daemon plist you find. Then delete the remaining folders with sudo rm -rf for system paths and rm -rf for user paths.
Folder Size Reference: What Avast Leaves Behind
The exact sizes vary depending on how long Avast has been installed and how much it has quarantined, but this table gives realistic ballpark ranges based on typical installations:
| Location | Contents | Typical Size |
|---|---|---|
/Applications/Avast.app |
Main app bundle (removed by uninstaller) | 300–600 MB |
/Library/Application Support/Avast |
Virus definitions, scan engine, quarantine database | 100–400 MB |
~/Library/Caches/com.avast.AAFM |
UI and update caches | 10–80 MB |
/Library/Caches/com.avast.antivirus |
Antivirus engine cache | 20–150 MB |
| LaunchDaemons / LaunchAgents plists | Service definition files | <1 MB |
| Preference plists & saved state | Settings, window state | <5 MB |
In total, a fully cleaned-up Avast removal can recover anywhere from 400 MB to over 1 GB of disk space, depending on how large the virus definition database grew. If you want a complete picture of what other apps are leaving behind in similar locations, see our guide on how to completely uninstall apps on Mac.
Checking for Network Extensions (macOS Sequoia)
Modern versions of Avast use a Network Extension instead of a legacy kernel extension to filter web traffic and implement its Web Shield feature. On macOS Sequoia, Network Extensions are managed through System Settings rather than the kernel extension approval flow used on older macOS releases.
After the uninstaller runs, verify the extension is gone:
- Open System Settings → General → Login Items & Extensions.
- Scroll to the Network Extensions section. No Avast entry should appear.
- Also check VPN under Network in System Settings — Avast's proxy sometimes registers a VPN configuration. Remove it if present.
Confirming a Clean Removal
Once you believe everything is gone, run a quick Terminal sweep to catch any remaining files:
find /Library ~/Library -iname "*avast*" 2>/dev/nullfind /private/var -iname "*avast*" 2>/dev/null
If either command returns results, those are files the uninstaller missed. Review each path, confirm it is Avast-related, and delete it with the appropriate rm command (using sudo for paths under /Library or /private).
If you remove several apps regularly and want to avoid hunting through a dozen Library folders each time, a tool like Crumb can audit all of these locations at once and show what is safe to delete before anything is removed.
What to Do If Avast Won't Quit or the Uninstaller Fails
Occasionally the Avast process will not respond to a normal quit, especially if the System Extension is locked by macOS. Try these steps in order:
- Force-quit the app from Activity Monitor by selecting the Avast process and clicking the stop button.
- Restart in Safe Mode. On Apple Silicon, shut down, then hold the power button until startup options appear, select your disk, then hold Shift and click Continue in Safe Mode. On Intel, hold Shift during startup. Safe Mode disables third-party kernel extensions and launch agents, so the Avast daemon will not load — run the uninstaller from here.
- Manually unload the daemon. In Terminal (in Safe Mode or normal mode if the process has been force-killed):
sudo launchctl bootout system /Library/LaunchDaemons/com.avast.proxy.plist, then run the uninstaller again.
After a full removal, reboot once more and run the find sweep above to confirm a clean slate. You can also check what is taking up space on your Mac to see the overall impact after clearing Avast and any other accumulated software leftovers.