Uninstalling an app on a Mac, and the gigabytes that stay behind
Apple's own steps, the gigabytes that stay on the disk after the app is gone, and how to find the leftovers for one app with a couple of commands.
By Chethan Kumar S N · Updated
Two different searches end up on this page. One is from someone who wants an app off their Mac and expects it to take ten seconds. The other is from someone who has been told to open Launchpad, hold an icon until it wobbles and click the little cross, and who cannot find Launchpad anywhere on their machine.
The second person is not confused. On macOS 27 the program they are looking for does not exist. The gesture does, under a different name and behind a different button, and the folder that used to hold it has one letter of overlap with the app that replaced it.
The first person is in for the more expensive surprise. Dragging an app to the Bin removes the app. It does not remove what the app wrote, and on a machine that has been in use for a while the difference is measured in gigabytes rather than megabytes.
Everything below comes from reading two Apple documents for macOS 27, from the files on an M1 Pro running macOS 27.0.1, and from the machine’s own record of what each app has left in your Library. Nothing was uninstalled while writing it, every app it measures is still installed, and every command shown only reads.
What you are actually deleting
An app on a Mac is a folder with a name that ends in .app. That is not a metaphor, it is the file system’s answer, and you can look at it:
$ ls /Applications/Slack.app/Contents
CodeResources Frameworks Info.plist MacOS PkgInfo Resources _CodeSignature
$ du -sh /Applications/Slack.app
273M /Applications/Slack.app
Everything that makes the app work is inside that one folder: the executable in MacOS, the libraries in Frameworks, the images and strings in Resources, and the signature that proves who built it in _CodeSignature. The Finder shows it as a single icon because the extension tells it to, which is a convenience that has one side effect worth knowing before you delete anything: the folder you drop in the Bin is a container, not the whole app, and the parts of the app that matter to a cleanup are the parts it put outside.
The file that ties an app to everything else it owns is Info.plist, and one key in it does most of the work:
$ plutil -p /Applications/Mos.app/Contents/Info.plist | grep -E "CFBundleIdentifier|CFBundleExecutable|CFBundlePackageType|LSMinimumSystemVersion"
"CFBundleExecutable" => "Mos"
"CFBundleIdentifier" => "com.caldis.Mos"
"CFBundlePackageType" => "APPL"
"LSMinimumSystemVersion" => "10.13"
That identifier is the app’s real name as far as macOS is concerned, and it is the string you will search for in the next section if you want to find what an app left behind. Note that it has nothing to do with the name you see. The app is called Mos, the bundle is Mos.app, and the identifier is com.caldis.Mos, which is a domain the developer owns read backwards. Three names for one thing, and the folders on disk use whichever of the three the developer felt like.
Apple’s own instructions, in the order it gives them
Apple’s macOS 27 user guide has a short page on this, and it starts with a step most people skip: if the app arrived in a folder, open that folder and check whether a second app is sitting next to it with a name like Uninstall. If there is one, run it. The guide’s warning is about the Trash rather than the uninstaller, which is that the app is permanently removed the next time you empty the Bin, and that if you want it back before that you select it in the Bin and choose File > Put Back.
The support article behind that page is more specific, and it explains why the uninstaller matters rather than just recommending it. Its reason, in its own words, is that an uninstaller is the best way to delete the app and any login items, extensions or other data the app might have stored in other locations. That is the same leftover problem this page is about, named by Apple as a reason to prefer the developer’s own tool over yours.
The full order, from both documents:
- Quit the app if it is open.
- Find the app in the Finder. Apple’s own trick, if you do not know where it lives, is to search for it with Spotlight and then hold the Command key while double-clicking the result, which opens a Finder window with the app selected instead of launching it.
- Check for an uninstaller in the same folder as the app, and run it if there is one. Some apps put an uninstall, remove or reset option inside the app’s own menus or settings instead.
- Otherwise drag the app to the Bin, or select it and choose File > Move to Bin.
- If you are asked for a username and password, use an administrator account, which is usually the account you log in with.
- Choose Finder > Empty Bin, because Apple’s line is that the space does not become available until you do.
Two more things from the same articles are worth keeping. You cannot use the Finder to delete what Apple calls apps that are required by the Mac, and its list is Mail, Music, Books, Notes, Podcasts, Maps, News and Stocks, plus anything in the System folder. And if the Finder tells you an app is in use, the fix is to make sure it is not open, and then, if that does not help, to restart or start up in Safe Mode and try again.
Where apps live, and the one that is not really there
There are three places an app can live on a Mac, and they behave differently when you try to remove something from them:
| Location | On this Mac | What it means for deleting |
|---|---|---|
/Applications | 32 app bundles, owned by root with group admin and mode drwxrwxr-x | The default, and the one Apple names. An admin account can move things out of it without being asked for a password, and many third party apps are owned by your own user account |
~/Applications | exists, mode drwx------, holding a single item | The per user Applications folder Apple mentions. Only your account can see inside it, so only your account can tidy it |
/System/Applications | 48 app bundles, owned by root with group wheel, carrying the restricted flag | Apple’s own apps. Restricted means the system protects them, and this Mac has System Integrity Protection enabled |
That third row is where the surprising case lives. Safari is one of the apps people try to delete first, and here is what is actually in /Applications:
$ ls -lO /Applications/Safari.app
lrwxr-xr-x@ 1 root wheel restricted,hidden 54 Sep 24 12:40 /Applications/Safari.app -> ../System/Cryptexes/App/System/Applications/Safari.app
It is not an app. It is a symbolic link, 54 bytes long, pointing into a sealed system folder, and it carries the restricted and hidden flags. Dragging it to the Bin cannot work in any meaningful sense, and the Finder will refuse, which is a much better explanation than the one people usually get. Mail and the rest of Apple’s own apps sit in /System/Applications with the same restricted flag on their contents.
Launchpad is gone, and the pages that send you there are out of date
This is the part that sends people to a search engine in the first place. On this Mac:
$ ls -d /System/Applications/Launchpad.app
ls: /System/Applications/Launchpad.app: No such file or directory
$ mdfind -name Launchpad
$
Nothing. Not a hidden app, not a renamed app, and nothing in the Spotlight index. What is there instead is a folder with a name that looks like the result of a typo:
$ plutil -p /System/Applications/Apps.app/Contents/Info.plist | grep -E "CFBundleIdentifier|CFBundleDisplayName|LSMinimumSystemVersion|LSUIElement"
"CFBundleDisplayName" => "Apps"
"CFBundleIdentifier" => "com.apple.apps.launcher"
"LSMinimumSystemVersion" => "27.0"
"LSUIElement" => true
$ du -sh /System/Applications/Apps.app
260K /System/Applications/Apps.app
A 260 KB bundle that only runs on macOS 27, marked as an agent rather than an ordinary app, whose whole declared purpose is in the identifier: com.apple.apps.launcher. The old program held a grid of every app on the machine in its own window. This one does not, and that is why the folder is so small.
Apple’s own documentation moved at the same time, and this is the evidence worth keeping, because it settles what the button in your Dock is called. The App Store user guide for macOS 27, on the page about installing and uninstalling purchases, now says to click the Apps icon in the Dock, then to click and hold the icon of the app you want to delete until it begins to jiggle, and then to click the close button. The wording of the gesture has not changed at all. The name of the door has.
So for an App Store app the wobble and cross still work, and you will find them through the Apps icon in your Dock rather than through a program called Launchpad. For everything else, the Finder route from the previous section does the same job and does not care which name the launcher has this year. And if you have read a page telling you to open Launchpad from Spotlight, or to look in a folder that no longer exists, the page is simply older than your Mac.
What a deleted app leaves behind, measured
This is where the ten second job turns into a different job. Below is what is currently sitting on this machine for seven installed apps: the size of the app bundle itself, the size of everything found in your Library under the app’s name or its bundle identifier, and how many separate paths that turned out to be.
| App | The bundle | Left in your Library | Paths found |
|---|---|---|---|
| Slack | 273 MB | about 1.8 GB | 6 |
| Claude | 626 MB | about 4 GB | 6 |
| Comet | 1 GB | about 3 GB | 3 |
| ChatGPT | 2 GB | about 3 GB | 6 |
| Blender | 953 MB | 4 KB | 1 |
| OpenUsage | 64 MB | 9 MB | 8 |
| Mos | 26 MB | 60 KB | 2 |
Read the top and bottom of that table together, because they are the honest shape of the problem. Slack’s own code is 273 MB and its cached conversations are 1.5 GB, with another 274 MB of a saved installer sitting in Caches under a name that includes the word ShipIt, which is the updater that downloaded it. Claude is a 626 MB app with roughly 4 GB behind it. Blender, a 953 MB application, leaves 4 KB, because it keeps everything that matters inside its own bundle and writes almost nothing to your Library.
Two details in that table explain why finding this by hand is harder than it should be. The first is the folder name. Slack’s data folder is called Slack, so a search for the app’s name finds it. ChatGPT’s data folder is called com.openai.codex, which contains neither the word ChatGPT nor the word OpenAI in a form that a file search for the app’s name will match. The second is that one app can use several names at once. OpenUsage has a folder called OpenUsage and a folder called com.robinebers.openusage, so searching for either one alone gives you a partial answer and a false sense of having finished.
Here is what those leftovers actually are, in the folders they live in:
~/Library/Application Support/Slack 1.5 GB
~/Library/Caches/com.tinyspeck.slackmacgap.ShipIt 274 MB
~/Library/Caches/com.tinyspeck.slackmacgap 468 KB
~/Library/Preferences/com.tinyspeck.slackmacgap.plist 4 KB
~/Library/HTTPStorages/com.tinyspeck.slackmacgap 232 KB
~/Library/HTTPStorages/com.tinyspeck.slackmacgap.binarycookies
Application Support is where apps keep the things they want to survive a reboot, in Slack’s case your message cache. Caches is where they keep downloads and working files, which is why the biggest single item in Slack’s list is an updater’s copy of the app itself. Preferences holds the settings, usually as one small plist, and every read and write of it goes through a single system daemon rather than the app opening the file itself, which is what the cfprefsd page is about. HTTPStorages holds the cookies and website data from any part of the app that is a browser underneath, which for modern chat and mail apps is most of it. To those five, a sandboxed app can add a folder in ~/Library/Containers with all of its own data nested inside, and a few apps add a Login Item or a background agent, which is the subject of the background items guide.
Finding one app’s leftovers yourself
Two commands, and the second one is a loop because there is no single folder to look in:
$ defaults read /Applications/Mos.app/Contents/Info.plist CFBundleIdentifier
com.caldis.Mos
$ for d in "Application Support" Caches Preferences HTTPStorages Containers "Group Containers" Logs; do
ls -d "$HOME/Library/$d"/*com.caldis.Mos* 2>/dev/null
done
/Users/chethankumar/Library/Preferences/com.caldis.Mos.plist
/Users/chethankumar/Library/HTTPStorages/com.caldis.Mos
Mos is the clean case: two paths and no cache worth mentioning. Swap the identifier for com.robinebers.openusage and the same loop returns eight, including the two folders that do not use the identifier in their names at all. If you would rather do it from the Finder, ~/Library is hidden by default, and Apple’s own way in is to hold the Option key while choosing Library from the Go menu.
Search for the app’s name as well as its identifier, and remember what you are doing here. This is a name match across a handful of folders, not a manifest of every file an app has ever created. macOS does not keep such a manifest for an ordinary drag installed app, which is why the next section exists.
The apps that do leave a manifest
If an app arrived as an installer package, the installer wrote a receipt, and a receipt is a list:
$ pkgutil --pkgs | wc -l
52
$ pkgutil --pkg-info com.microsoft.teams2
package-id: com.microsoft.teams2
version: 26276.505.5234.9924
volume: /
location: Library/Caches/com.microsoft.autoupdate.helper/Clones.noindex
install-time: 1794645341
$ pkgutil --files com.microsoft.teams2 | wc -l
1588
Fifty two receipts on this Mac, and one of them accounts for 1,588 files that the installer knows the name of, starting with the app itself and then walking through its frameworks. That is the closest thing macOS has to a proper uninstall record, and it exists only for software that was installed by a package rather than dragged in from a disk image.
The tool can also discard the record, and its help text is careful about what that means:
--forget PKGID Discard receipt data for the specified package
Discard the receipt data. Not delete the files. If you are comfortable in Terminal, this is still the more honest way to see what a package installed, because pkgutil --files prints the paths and you can decide what to do with them yourself. Coming the other way, --learn PATH updates a receipt from what is actually on disk, which tells you what the tool is: a record keeper, not a cleaner.
What deleting an app does not do
Four things, and the first two are Apple’s own statements rather than deductions.
It does not delete your files. The support article says a deletion does not remove any documents or other files you created with the app, and adds the practical consequence, that you might need the app in order to open such files. Your projects stay where they are.
It does not cancel a subscription. The same article says deleting an app does not cancel any subscription you purchased with it. An App Store subscription is cancelled in your Apple Account, and one bought on a developer’s website is a message to that developer. Removing a 40 MB app and expecting the monthly charge to stop is the most expensive misunderstanding in this whole area.
It does not clean up the login items. If the app installed a background agent, that entry stays in your Login Items list and in the notification that started this whole search for a lot of people, which is covered in detail in the background items guide. Apple’s advice to use the app’s own uninstaller exists precisely because that is the only thing that usually removes them.
It does not free the space straight away. The Bin has to be emptied, which is Apple’s wording, and even then a snapshot can hold on to the blocks for a while. The arithmetic behind that is in the storage guide.
There is a fifth thing, softer but real. macOS keeps its own list of every app the machine has ever seen, so an app you deleted can linger in an Open With menu:
$ ls -l /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister
-rwxr-xr-x 1 root wheel 292048 Sep 24 12:40 .../lsregister
That 292 KB tool is the interface to the Launch Services database, and the rebuild people recommend is one of its options rather than something you have to type from memory. It is not a cleanup step and this page did not run it, because a rebuild is a system change with a cost rather than a fix for anything. Spotting a deleted app in an Open With list a few minutes after deleting it is normal, and it usually resolves on its own.
There is a third record, and it is the one that decides whether the app was allowed to run in the first place. Every app the Mac assesses gets an entry in the policy database behind Gatekeeper, which is what the syspolicyd page is about. Deleting an app does not touch it, and it is not yours to tidy.
The App Store case
Apps from the App Store get one extra wrinkle and lose one. They cannot be deleted with a licence key you lost, because there is no licence key: reinstalling is free and unlimited, and Apple’s steps are to open the App Store, click your name at the bottom left, find the app in your purchases and click the download button. That is a genuine advantage of the store over a direct download, where a lost installer means asking the developer for a new link.
The wrinkle is in where the app keeps its data. An App Store app is sandboxed, so its files live inside ~/Library/Containers/<identifier>/Data rather than in your own Application Support folder, and this Mac has 681 containers, almost all of them from Apple’s own apps and from work software. Because the container is a separate item in a separate folder, trashing the app leaves it behind just as reliably as any drag installed app leaves its cache, and it is one more place to look with the loop from earlier.
You can tell which apps came from the store by looking inside the bundle for a receipt of a different kind:
$ ls -l /Applications/Xcode-27.0-backup.app/Contents/_MASReceipt/
-rw-r--r-- 1 root wheel 4832 Oct 20 17:07 receipt
A 4,832 byte file that says this app was delivered by the Mac App Store. It is signed with the app, so it cannot be faked, and it is the reason a store app launches without the downloaded from the internet warning that a direct download triggers. When an app opens, it is this file the store’s background machinery checks, and the appstoreagent page measures the agent that does that checking at about five seconds of processor time a day.
The order that actually works
For a single app you no longer want:
- Quit it, then look in its folder for the developer’s own uninstaller and use that if it exists.
- If it does not, find the app in the Finder and drag it to the Bin.
- Empty the Bin.
- Ask whether it was the sort of app that caches. A chat client, a mail client, a browser, a media app or a development tool almost certainly was, and an app that is a single window over a few files almost certainly was not.
- If it was, get its bundle identifier and run the loop from this page, looking at the sizes before removing anything. A 4 KB preferences file is not worth the risk of guessing wrong, and a 1.5 GB cache clearly is.
- Check your Login Items for anything the app left running, and check
~/Library/Containersand~/Library/Group Containersif it came from the App Store. - If you paid for it in an app or on a website, cancel that separately.
For a machine that has filled up over a few years, the same list works in bulk, and the largest wins are predictable: browsers, chat clients, video editors and anything with the word Sync in its name. The System Data page covers the category macOS itself puts those folders in.
What this page cannot tell you
The first limit is a deliberate one. Nothing was uninstalled while writing this, so the sizes in the tables are what each app is holding right now, not the result of an experiment. The claim that a folder stays behind after you trash an app is not a guess either, since the Finder moves exactly the item you dragged and every path in those tables is outside that item.
The second is that this is one machine on one day. The numbers will differ on yours, and some apps leave nothing at all. Blender is in this page’s own table as proof that the dramatic version of this advice is not universal.
Third, the search by name is a search by name. An app that names its folder something unrelated to both its name and its identifier will hide from the loop above, and the only tools that know the whole list are the app’s own uninstaller and, for package installs, the receipt. Pages that offer to find everything for you are usually describing a tool they sell, and Apple’s own position is that the developer’s uninstaller is the most reliable option when one exists.
And one detail for anyone following an older guide: the folder called Saved Application State, which older advice tells you to empty for every app you remove, does not exist on this Mac at all. There is no ~/Library/Saved Application State directory to check. Apple stopped keeping that kind of per app state on this build, and the guides that still list it are describing a Mac that is a few years old.
Where window managers fit
Nothing here changes how your windows behave, and a tidy Library does not make a desktop easier to work on. The two meet at the same feeling, though, which is a Mac holding on to things you did not ask for: unsigned downloads, background agents, caches measured in gigabytes and a launcher whose name changed while you were not looking.
Ribbon takes the visible half of that. Instead of stacking windows on top of each other and leaving you to dig through them, every window gets its own full size column on a single strip that runs past the edges of the screen, so nothing is buried and nothing gets shrunk to make room. It is $15 once for up to 3 Macs, with a full refund within 10 days, on macOS 14 Sonoma and later, on Apple silicon and Intel Macs. You can drive the strip in your browser before you install anything, which is also the fastest way to decide whether it is worth the space.
The short version
An app is a folder, which is why deleting it is easy, and the folder is only part of what the app owns, which is why deleting it is not the same as removing it. Apple’s own order is to use the developer’s uninstaller if there is one, then the app’s own uninstall option, then a drag to the Bin followed by an empty Bin, and it says plainly that an uninstaller is the best way to catch the login items and the files stored elsewhere.
For App Store apps the wobble and cross gesture still exists and now lives behind the Apps icon in the Dock, because there is no Launchpad on macOS 27 to open. For everything else the Finder works and always did.
The leftovers are real and they are not always small. On this Mac, Slack would leave about 1.8 GB behind against a 273 MB app, Claude about 4 GB against 626 MB, and Blender 4 KB against 953 MB. They live in a handful of folders under ~/Library, some of them named after the app and some named after a bundle identifier you have to look up. Two commands find them for one app, and looking at the sizes before you remove anything is the only part of this that needs judgement.
Questions
How do I uninstall an app on a Mac?
Apple's order of preference is worth following exactly, because it is not the same as the popular advice. First, if the app came in a folder, open that folder and look for a second app inside it called Uninstall or something Uninstaller; if it exists, run it, because Apple says that is the best way to delete the app along with any login items, extensions or other data it stored elsewhere. Some apps instead put an uninstall, remove or reset option in their own menus or settings, and that is the next best thing. If neither exists, quit the app, find it in the Finder (most live in Applications), and drag it to the Bin or select it and choose File > Move to Bin. You may be asked for an administrator name and password. Then choose Finder > Empty Bin, because the space is not free until you do.
Where is Launchpad, and how do I delete apps without it?
On macOS 27 this Mac has no Launchpad at all. There is no /System/Applications/Launchpad.app, a Spotlight search for the name returns nothing, and the app that does the job is /System/Applications/Apps.app, whose bundle identifier is com.apple.apps.launcher and which requires macOS 27.0. Apple's own App Store guide for macOS 27 describes the delete gesture in the same way it always did, holding an icon until it jiggles and then clicking the close button, but the step before it now reads click the Apps icon in the Dock. That icon is in your Dock whether or not you ever used Launchpad, so the short answer is that the feature is still there and the name on the door has changed. The Finder route works for every app, Launchpad or not.
What gets left behind when you delete an app?
Everything the app wrote outside its own bundle, which the Finder does not touch because you only dragged one folder. On this Mac, deleting Slack.app would free 273 MB and leave about 1.8 GB behind, including 1.5 GB of chat cache in Application Support, a 274 MB saved installer in Caches, and its preferences and website data. Claude leaves about 4 GB against a 626 MB app, and ChatGPT about 3 GB against a 2 GB app. The leftovers sit in a handful of folders in your Library: Application Support, Caches, Preferences, HTTPStorages, Containers, Group Containers and Logs. Some apps do leave almost nothing, so this is not a rule about all apps, it is a rule about apps that cache.
Does deleting an app cancel a subscription or delete my files?
Neither, and Apple says both plainly. Deleting or uninstalling an app does not remove any documents or other files that you created with the app, and it does not cancel any subscription you purchased with the app. So a cancelled project still opens if you reinstall, and a subscription keeps billing whether the app is on your Mac or not. If you subscribed through the App Store, the place to cancel is your Apple Account subscriptions rather than the app or the Finder, and if you subscribed on the app's own website, that is a support request to them. Deleting the app is the wrong lever for the payment.
Why won't some apps delete, and why do they still show up after I delete them?
Apps inside the System folder cannot be removed with the Finder, and neither can the apps that are part of macOS, which Apple lists as Mail, Music, Books, Notes, Podcasts, Maps, News and Stocks. Dragging Safari to the Bin does nothing because the item in Applications is a restricted symbolic link into the system's cryptex, which is one honest explanation for a puzzle people hit on the first try. If the Finder says the app is in use, quit it, and if that does not help, restart or start up in Safe Mode. And an app you deleted can still appear in an Open With menu for a while, because macOS keeps a separate list of every app it has seen and rebuilds it on its own schedule.
Ready? Buy Ribbon for $15, or read all the guides.