CleanMyMac: how to uninstall it cleanly
Thinning out the menu bar usually starts with the largest icon, and this one is often it. Then the search for "CleanMyMac uninstall" turns up two answers that contradict each other: drag it to the Trash like anything else, or use a specific procedure inside the app first.
Both are correct, and they remove different amounts. More importantly, neither of them touches billing, and neither of them frees the device slot the machine is holding. This is three separate jobs, not one, and doing them in the wrong order costs either money or an extra hour of cleanup.
Cancel before removing, not after
Deleting the app does nothing to a subscription. It renews on schedule and the card is charged, with the app gone. This is the single most expensive mistake in the whole process, and it is the first step for that reason.
A MacPaw Store purchase is cancelled by signing in to the MacPaw account, selecting the app, and using the cancel option. The status turns inactive within two to three minutes, and the page may need reloading if it still shows as active. An App Store purchase is cancelled from within the App Store app: the name at the lower left, Account Settings, then Manage next to Subscriptions. A Setapp membership is a different decision entirely, since it covers a catalogue rather than this one title.
Cancelling does not shorten access. Everything keeps working until the end of the period already paid for, and only then do the modules lock. That makes a useful sequence available: cancel now, keep using it until the paid period runs out, remove it at the end. There is no reason to do both on the same afternoon.
If the purchase was recent, check the refund window before anything else
Cancelling stops the next charge. It does not return the last one. When removal is happening days rather than months after buying, there is a separate window that closes on its own schedule.
The MacPaw Store checkout page lists a 30 day money back guarantee on the annual and one-time plans, and 14 days on the monthly plan, checked on 10 September 2026. The shorter window on monthly tracks its smaller amount. Refunds are requested through the developer's support channel rather than from a button in the app, and the knowledge base carries a dedicated article on eligibility, so the criteria can be read before writing in rather than after.
App Store purchases follow Apple's process instead, which runs through Apple's own reporting flow and applies Apple's rules rather than the developer's. Setapp is separate again, since the charge covers a catalogue membership.
The reason this belongs before removal rather than after is evidence. A refund conversation goes faster when the plan status, the purchase date, and the account are all still in front of the person asking. Wiping the app, signing out, and then trying to reconstruct which email address the licence sits under turns a five minute request into an afternoon.
The order that avoids all of it: check whether the purchase falls inside the window, request the refund if it does, cancel the subscription either way, then move on to the app itself. Nothing in that sequence is undone by the later steps.
Free the device slot while the account still knows about the Mac
MacPaw Store plans cover one, two, or five Macs, and the machine being wiped holds one of those slots until something releases it. Removing the app does not release it.
In the MacPaw account, choosing the app and then Manage Devices lists the slots. Removing the entry for this Mac frees it for another machine. If a slot was shared with someone else by invitation, that slot does not come back on its own either, and it has to be revoked from the same screen. Revoking sends the other person an email notification.
There is a second route that behaves differently and is worth knowing about. Activating the app on a new Mac when all slots are occupied offers to replace an existing device, which takes the slot immediately. Whoever was using that slot loses access and sees a deactivation message in the app, but receives no email or other warning. Revoking from the account page is the visible version of the same action, and generally the better one when another person is involved.
Two removal methods, and what each leaves behind
The developer documents both and is explicit that they are not equivalent.
The easiest way to uninstall CleanMyMac is to drag and drop it into the Trash, like any other app. However, the most effective way is to use the Applications module in CleanMyMac, which ensures that all traces and supporting files are completely removed. Source: macpaw.com, checked 10 September 2026
The self removal path runs like this: open the app, click Applications in the sidebar, click Scan and wait for results, click Manage My Applications, open the Uninstaller category, find the app in the list, select it, and click Uninstall.
The ordering constraint is obvious once stated and easy to get wrong. The app has to be running to remove itself. Dragging it to the Trash first destroys the tool that would have done the thorough job. Anyone who wants the supporting files gone has to do it before the icon leaves the Applications folder.
That same list is organised into groups, which makes it worth a pass while it is open: all applications, anything unopened for six months, grouped by store, grouped by vendor, and by plugin type. Sorting by size or last opened date turns a removal session into a general audit. System apps required by macOS are excluded from the list entirely, since macOS does not permit removing them.
What the Trash method leaves
Dragging works, with a delay that surprises people. Apple's documentation is direct about when removal actually happens.
The app is permanently removed from your Mac the next time you or the Finder empties the Trash. If you have files that you created with the app, you may not be able to open them again. Source: support.apple.com, checked 10 September 2026
Until the Trash is emptied, nothing is gone, and the app can be restored by selecting it in the Trash and choosing Put Back from the File menu.
What stays behind are the support files that live outside the Applications folder. This is not a criticism specific to one app: it is the general behaviour of Mac software, and it is the reason the uninstaller module exists in the first place. The developer describes leftover components as capable of running small service processes, and the Applications module separates them into two categories, installer remnants and leftover files from removed apps.
Practically, there are two honest routes. Use the app's own uninstaller while it still runs, or drag it out and accept that some support files persist. Hunting through library folders by hand for files whose purpose is unclear is the option least likely to end well, and the space at stake is typically tens of megabytes rather than gigabytes.
The App Store edition cannot finish the job
Removal completeness also depends on where the copy came from. The App Store edition cannot remove the core binaries of App Store apps, because Apple's restrictions do not allow it. Related files can go, and the binary itself has to be deleted manually afterwards.
That applies to removing itself as well. Running the uninstaller from an App Store copy clears the supporting files and stops at the app bundle, which then goes to the Trash the ordinary way.
A Setapp installation is different again. Removal starts from the Setapp app rather than from the Applications folder, and whether the Setapp membership continues is an unrelated decision. A single title can be removed while the membership stays active.
Three permission entries macOS keeps
After the app is gone, System Settings can still carry records of what it was allowed to do. Three places are worth checking:
- Login Items and Extensions, under General in System Settings, which lists what was permitted to run in the background
- Full Disk Access, under Privacy and Security, where depending on the macOS generation there may be three entries: the app, Health Monitor, and Menu
- Notifications, where a removed app's entry can persist in the list
There is also a privileged helper to consider. The component that prompts for an administrator password can be switched off from the app menu under Action, then Deauthenticate. Doing that before removal is cleaner, because it deals with the elevated privileges while the interface for doing so still exists.
None of these leftovers cause harm. They cause confusion three months later, when a list contains the name of an app that was supposedly deleted and nobody remembers whether it matters. Clearing them immediately after removal is the only time the answer is obvious.
Reinstalling later does not restore the trial
Sometimes the removal turns out to be premature. The relevant detail is that the seven day trial does not come back. The activation dialog simply does not offer it once it has been used, so a fresh install lands straight on the purchase choice.
With an active plan, reinstalling means signing in with MacPaw account credentials again, or using Restore Purchase on an App Store copy if the purchase is not detected. Reinstalling consumes a device slot again, so a slot freed earlier gets taken back at that point.
Settings are worth capturing before removal for the same reason. Whatever was excluded in the Scanning tab, and whatever was switched off in the Menu and Protection tabs, may not survive a round trip. A screenshot takes ten seconds and saves reconstructing a configuration from memory.
What removal does to the menu bar
Removing one icon frees exactly one slot, and the neighbouring icons close the gap. On a Mac carrying ten resident apps, dropping to nine changes almost nothing about the time spent hunting for the right one. The strip is still full, and the target is still somewhere in it.
There is also a loss on the other side. Anyone in the habit of glancing at free space, memory pressure, or battery health from that menu has to replace it with Activity Monitor or the storage settings pane, neither of which is one click away.
So removal is a weak tool for menu bar tidiness and a strong tool for cutting a subscription. Those are different goals, and it helps to be clear about which one is actually driving the decision.
What to change first
Cancel the subscription today, then decide about the app separately. If the modules earn their keep and only the icon is unwanted, a menu bar organizer folds it away while leaving the monitors reachable, which costs less than losing the tool entirely. The trade offs against other approaches are laid out on how it compares, and Koffret can be tried on the current arrangement before anything gets deleted.
Frequently asked questions
Is dragging it to the Trash enough?
It removes the app itself once the Trash is emptied, but support files outside the Applications folder remain. The developer points to the Applications module inside the app as the thorough route, since it clears the associated files too. That has to be done while the app is still installed and running.
Does uninstalling stop the subscription?
No. Removal and cancellation are separate. Cancel from the MacPaw account page for a MacPaw Store purchase, or from Account Settings in the App Store app for an App Store purchase. Access continues until the paid period ends, so cancelling first and removing later loses nothing.
Why does the name still appear in System Settings?
Permission records can outlive the app in three places: Login Items and Extensions, Full Disk Access, and Notifications. They are harmless but confusing later. Clearing them right after removal is easiest, and switching off the privileged helper through Action, then Deauthenticate before removing avoids one of them entirely.
Will reinstalling give another free trial?
No. Once the seven day trial has been used, the activation dialog stops offering it, and a reinstall goes straight to the purchase options. With an active plan, signing in again restores full functionality and takes up a device slot on that Mac.