How to Delete an App on a MacBook: Every Method Explained

Removing apps from a MacBook sounds straightforward — and often it is — but there are actually several different ways to do it, and the right approach depends on how the app was installed in the first place. Use the wrong method and you might leave behind gigabytes of leftover files, or find the app still appears in your library even after you thought you removed it.

Here's a clear breakdown of every deletion method, what each one actually removes, and the factors that determine which approach fits your situation.

Why Deleting Mac Apps Isn't Always One-Step Simple

Unlike iOS, macOS doesn't enforce a single installation system for all apps. Some come from the Mac App Store, others from a developer's website as a .dmg or .pkg installer, and some arrive bundled inside other software. Each pathway leaves files in different locations — which means each requires a slightly different removal process.

Simply dragging an app to the Trash removes the main application bundle, but many apps also write preference files, caches, support files, and launch agents to other folders like ~/Library/Application Support/ or ~/Library/Preferences/. Whether those leftovers matter depends on how much storage you care about recovering and whether the app was storing sensitive data.

Method 1: Drag to Trash (Basic Removal)

This works for most standard applications and is the fastest approach.

  1. Open Finder and navigate to your Applications folder (Shift + Command + A)
  2. Locate the app you want to remove
  3. Drag it to the Trash, or right-click and select Move to Trash
  4. Empty the Trash to complete the deletion

🗑️ This removes the app's core executable and bundled resources, but does not automatically remove associated preference files or cached data stored in your Library folder. For most apps, those leftover files are small and harmless. For apps you used heavily or apps that stored local data, it's worth checking.

Method 2: Using Launchpad (App Store Apps)

If an app was downloaded from the Mac App Store, you can delete it directly from Launchpad — the same way you'd delete an app on an iPhone.

  1. Open Launchpad (F4 key, or pinch with thumb and three fingers on trackpad)
  2. Click and hold the app icon until icons begin to wiggle
  3. Click the X button that appears on the app
  4. Confirm deletion when prompted

This method only works for App Store apps. If you don't see an X appear, the app wasn't installed through the App Store and needs to be removed another way.

Method 3: Using the App's Built-In Uninstaller

Some applications — particularly larger software suites — come with a dedicated uninstaller. This is common with productivity suites, antivirus software, creative tools, and apps that install system-level components or drivers.

Check your Applications folder for a subfolder with the app's name. If there's an Uninstall tool inside, use it rather than dragging the app to the Trash. These uninstallers are designed to remove everything the app installed, including components that live outside the Applications folder.

If you installed the app from a .pkg file and no uninstaller is present, the removal process is more manual — the app may have placed files in /Library/ (system-level) directories that the Trash method won't touch.

Method 4: Manual Deep Removal via Library Folders

For a thorough removal — especially for apps that stored user data or ran background processes — you can manually hunt down and delete associated files. 💻

The key locations to check:

Folder PathWhat's Stored There
~/Library/Application Support/App data, databases, saved states
~/Library/Preferences/Settings and preference files (.plist)
~/Library/Caches/Temporary cached files
~/Library/Logs/App log files
/Library/LaunchAgents/Background processes started at login
/Library/LaunchDaemons/System-level background services

To access your Library folder (it's hidden by default): open Finder, hold Option, click the Go menu, and select Library.

Search each folder for files or subfolders named after the app or its developer. Delete what you find, then empty the Trash.

This approach requires comfort navigating hidden system directories. Deleting the wrong files can affect other apps or system behavior, so be specific about what you're removing.

Method 5: Third-Party Uninstaller Apps

Several third-party utilities automate the deep-removal process by scanning for all files associated with a given app before deletion. These tools display everything linked to the app across all Library folders and let you remove it in one step.

This approach is particularly useful if you regularly install and remove software, or if storage space is a priority. The tradeoff is adding another piece of software to your system to manage the removal of others — and not all utilities are equally thorough or trustworthy.

What Affects Which Method Is Right for You

Several variables determine the best removal path for any given app:

  • How the app was installed — App Store, direct download, .pkg installer, or bundled installer
  • Whether the app installed system-level components — drivers, browser extensions, kernel extensions, or login items
  • How much storage you want to recover — if you just want the icon gone vs. wanting every byte back
  • Your comfort level with navigating Library folders — manual cleanup requires some file system familiarity
  • Whether the app had an active subscription or account — deleting the app doesn't cancel subscriptions; that's managed separately through the App Store or the developer's website

🔍 Apps tied to subscriptions deserve extra attention: removing the app from your MacBook doesn't automatically end billing. If the subscription was purchased through the Mac App Store, you manage it under your Apple ID settings. If purchased directly from a developer, you'll need to cancel through their platform separately.

The Part That Varies by Setup

A casual user removing a rarely-used free app has a very different situation than someone uninstalling a creative suite they used professionally for years, or removing a security tool that installed kernel-level components. The files left behind, the risk of incomplete removal, and the importance of a thorough cleanup all shift depending on what that specific app was doing on your system.

Knowing which installation method the app used is the first question worth answering — because that single factor determines everything else about how the removal should go.