How to Uninstall Apps That Won't Delete on Mac

Dragging an app to the Trash is usually all it takes to uninstall it on macOS — until it isn't. If you're trying to uninstall apps that won't delete on Mac, you've likely hit one of a handful of specific blockers: the app is still running, macOS reports the item is in use, you get a permission-denied error, or the app is managed by an organization's MDM profile. Each cause has a different fix, and using the wrong one can waste time or leave files behind.

This guide walks through every common scenario with the exact steps to resolve it.

Why macOS Blocks App Deletion

macOS prevents deletion in a few distinct situations:

• App is still running — the process holds a lock on the .app bundle.
• "Item is in use" error — a background process, Launch Agent, or daemon references the app.
• Permission denied — the app lives in a system-protected location or was installed by another user.
• Locked or immutable flag — the file has the macOS locked bit set.
• MDM/managed app — your employer or school enrolled the Mac and owns that application.
• SIP-protected bundle — System Integrity Protection prevents removing certain Apple or system apps.

Fix 1: The App Is Still Running

The simplest case. If the Dock icon is active or the app appears in the menu bar, quit it first.

1. Right-click the Dock icon and choose Quit.
2. If it doesn't quit, open Activity Monitor (Applications > Utilities > Activity Monitor), find the process by name, select it, and click the stop button (×) in the toolbar, then choose Force Quit.
3. Drag the .app to Trash and empty it.

For menu-bar apps that have no Dock icon, click the menu-bar icon, look for a Quit option, or find the process in Activity Monitor.

Fix 2: "Item Is in Use" — Killing Background Processes

This error usually means a Launch Agent or daemon is running and referencing the app bundle. The fix is to unload those background services first.

1. Open Terminal (Applications > Utilities > Terminal).
2. Find the app's process by name:

   lsof +D /Applications/AppName.app

   This lists every process with a file handle open inside that bundle.
3. Note the PID (second column) of any relevant processes and kill them:

   kill -9 <PID>

4. Check for Launch Agents and Daemons associated with the app. Look in these locations:

   ~/Library/LaunchAgents/
   /Library/LaunchAgents/
   /Library/LaunchDaemons/

   Find any .plist files with the app's name or developer identifier.
5. Unload the service before deleting:

   launchctl unload ~/Library/LaunchAgents/com.example.AppName.plist

6. Now try dragging the .app to Trash. If Trash still refuses, empty it with:

   sudo rm -rf ~/.Trash/AppName.app

   You'll be prompted for your admin password.

Fix 3: Permission Denied

If you see "You don't have permission to move AppName to the Trash," there are two likely causes: the app is in /Applications and was installed by a different admin account, or the bundle itself has restrictive permissions.

1. Try using Finder while authenticated: open Finder, navigate to /Applications, and attempt to move the app to Trash. macOS will prompt for your admin credentials.
2. If that fails, use Terminal with sudo:

   sudo rm -rf /Applications/AppName.app

3. If permissions on the app bundle itself are wrong, reset them first:

   sudo chmod -R 755 /Applications/AppName.app
   sudo chown -R $(whoami) /Applications/AppName.app

   Then move it to Trash normally.

Be careful with sudo rm -rf. Double-check the path before pressing Enter — this command is permanent and bypasses Trash.

Fix 4: The File Is Locked

macOS allows files and folders to have a "locked" flag set (visible in Get Info as a checkbox). To clear it:

1. Select the .app in Finder, press Command-I to open Get Info.
2. Expand the General section and uncheck Locked.
3. Try moving to Trash again.

Alternatively, from Terminal:

chflags -R nouchg /Applications/AppName.app

Then delete normally or via sudo rm -rf.

Fix 5: MDM-Managed or Organization-Controlled Apps

If your Mac is enrolled in Mobile Device Management (MDM) — common on work or school machines — some apps are deployed and protected by the MDM profile. You typically cannot remove these yourself.

• Open System Settings > Privacy & Security > Profiles (macOS Ventura and later) or System Preferences > Profiles (Monterey and earlier) to see if a profile exists.
• If it does, contact your IT department. They control what's installed.
• If the profile was installed without your knowledge on a personal Mac, you can remove it in System Settings — but only if you have admin rights to do so.

Fix 6: SIP-Protected System Apps

Apple's System Integrity Protection (SIP) prevents removal of certain built-in apps like Safari, Messages, and FaceTime. Even with sudo, deletion will be denied. You can disable SIP in macOS Recovery, but this is not recommended for most users — SIP is a core security layer that protects the system from malware. For most purposes, simply hiding an unwanted stock app from Launchpad is a better outcome than removing it.

Cleaning Up Leftovers After Uninstalling

Dragging an app to Trash removes the .app bundle, but not the support files, preferences, and caches it left behind — sometimes hundreds of megabytes spread across:

• ~/Library/Application Support/
• ~/Library/Caches/
• ~/Library/Preferences/
• ~/Library/Containers/
• /Library/Application Support/

Finding and removing all of these manually is tedious and easy to get wrong. Crumb's Uninstall tab handles this automatically: select an app, and it surfaces all associated leftover files so you can review and remove them together. Importantly, removal through Crumb is recoverable for 30 days — useful if you later realize you deleted something you needed. Download Crumb if you want a safer alternative to manual sudo rm commands.

Quick Reference: Which Fix for Which Error

Summary

Most "can't delete app" situations on Mac fall into one of the categories above, and each has a reliable fix. Start with the gentlest approach — quit the app, check Activity Monitor — before reaching for sudo. When using Terminal to force-delete files, always verify the path first; there is no undo for rm -rf. If you want a recoverable workflow that also catches support file leftovers, Crumb's Uninstall tab is worth trying before going the manual route.