Buying a new MacBook should feel like a fresh start — but if yours came through a corporate reseller, a carrier program, or even a well-meaning IT department, there is a good chance you are inheriting software you never asked for. Knowing how to remove bloatware from a MacBook properly means more than just dragging an icon to the Trash. The most persistent programs leave behind launch agents, helper daemons, login items, and deep-rooted support folders that continue to consume CPU cycles and storage long after the app itself appears gone. This guide covers every layer — from the obvious to the hidden — so you can reclaim a genuinely clean machine.
What Counts as Bloatware on a MacBook?
"Bloatware" is a loose term, but on a Mac it usually falls into a few recognizable categories:
- Reseller utilities — backup agents, remote-management tools, or custom help-desk apps the seller pre-installed to support the device during a lease or warranty program.
- Trial software — antivirus suites, Microsoft 365 trials, or creative-app demos with 30-day timers that add background processes even when idle.
- Corporate MDM payloads — Mobile Device Management profiles that survived a device wipe or were pushed before you received the machine. These appear in System Settings under Profiles.
- Browser extensions and toolbars — bundled as part of a "productivity suite" but rarely useful and occasionally privacy-invasive.
- Cloud-sync agents — multiple competing backup clients (Dropbox, OneDrive, Google Drive, and a reseller's own cloud) all fighting at startup.
Some of these register persistent startup entries; others modify system preferences or install kernel extensions. Removing them correctly requires addressing each layer in sequence.
Before You Delete Anything: Take a Baseline
Rushing straight to deletion is the fastest way to break something important. Spend five minutes auditing what is actually running:
- Open Activity Monitor (
/Applications/Utilities/Activity Monitor.app) and sort by CPU. Note anything with an unfamiliar publisher consuming persistent CPU at idle. - Open System Settings → General → Login Items & Extensions. This is the macOS Sequoia / Tahoe canonical location for both user-level login items and background extensions.
- Check System Settings → Privacy & Security → Profiles. If you see any configuration profiles you did not install yourself, those need to be removed before you tackle software — they can silently re-install apps.
- Run
sudo launchctl list | grep -v com.applein Terminal to see third-party system-level daemons.
Screenshot or paste the lists somewhere before touching anything. This becomes your rollback reference.
Where Bloatware Hides on macOS
The table below maps the most common locations where pre-installed software leaves persistent artifacts. Knowing these paths is essential when you want to be certain a removal is complete.
| Location | What lives there | Scope | Typical size |
|---|---|---|---|
/Library/LaunchDaemons/ |
System-wide background daemons (run as root) | All users | Small plists, but the processes they launch can be large |
/Library/LaunchAgents/ |
Per-login agents installed for all users | All users | Plist files + referenced binaries in /Library/Application Support/ |
~/Library/LaunchAgents/ |
Agents registered by the current user's apps | Current user | Varies; Dropbox, OneDrive each add 1-3 entries |
/Library/Application Support/ |
Shared support files, helpers, and update daemons | All users | 100 MB – several GB for suites like Microsoft 365 |
~/Library/Application Support/ |
Per-user app data, preferences, and caches | Current user | Often the largest contributor after browser data |
~/Library/Caches/ |
App caches — safe to clear after uninstalling | Current user | 1-20+ GB on older installs |
/Library/Extensions/ or /Library/StagedExtensions/ |
Kernel and system extensions (rare but high-impact) | All users | Usually small; requires reboot to unload |
/Library/Preferences/ and ~/Library/Preferences/ |
Plist preference files — typically tiny, safe to remove post-uninstall | Both scopes | Negligible |
How to Remove Pre-Installed Bloatware Step by Step
Work through these steps in order. Skipping ahead can leave orphaned daemons running even after the app bundle is gone.
Step 1 — Remove Any MDM Profiles First
Go to System Settings → Privacy & Security → Profiles. Select each profile you do not recognize and click the minus (–) button. You may need an admin password. If a profile is greyed out and cannot be removed, the machine may still be enrolled in a corporate MDM — contact the reseller to unenroll before proceeding.
Step 2 — Quit the App and Its Background Processes
Before uninstalling, right-click the app's menu-bar icon and choose Quit, or use killall AppName in Terminal. For stubborn daemons:
- Find the daemon label:
sudo launchctl list | grep vendorname - Stop it:
sudo launchctl bootout system/com.vendor.daemonname - Disable it:
sudo launchctl disable system/com.vendor.daemonname
Step 3 — Move the App Bundle to Trash
Drag the .app from /Applications/ to Trash, or select it in Finder and press Cmd+Delete. Some apps include their own uninstaller — check /Library/Application Support/VendorName/ for an Uninstall.app or uninstall.sh script; running the official uninstaller is always preferable when one exists.
Step 4 — Remove Launch Agents and Daemons
Search the four launch directories for any plist whose filename contains the vendor's name or bundle ID:
/Library/LaunchDaemons//Library/LaunchAgents/~/Library/LaunchAgents/~/Library/LaunchDaemons/(rare, but worth checking)
Move matching plists to Trash. Do not just delete them while the daemon is still loaded — unload first with launchctl bootout as shown in Step 2.
Step 5 — Clean Up Residual Files
After the app and its agents are gone, remove leftover data from:
~/Library/Application Support/VendorName//Library/Application Support/VendorName/~/Library/Caches/com.vendor.appname//Library/Caches/com.vendor.appname/~/Library/Preferences/com.vendor.appname.plist/Library/Preferences/com.vendor.appname.plist
For a deeper look at what these cache folders contain and why they grow so large, see our guide on what cache files are on a Mac.
Step 6 — Reboot and Verify
Restart the Mac. After login, re-open Activity Monitor and the Login Items list. Confirm that the vendor's processes are gone. If a process reappears after reboot, a plist file was missed or a profile is re-pushing it — repeat Steps 1–4 more carefully.
Handling Antivirus and Security Suites
Pre-installed antivirus tools (common on reseller machines) are the most stubborn category of bloatware. They often include kernel extensions, system extensions, and Network Extension entitlements that macOS protects aggressively. Most major vendors — Symantec/Norton, McAfee, Bitdefender, Sophos — publish a dedicated removal tool that is more reliable than manual deletion. Search for "[VendorName] Mac removal tool" on the vendor's official support site and use that first. After running it, follow Steps 4 and 5 above to catch any stragglers.
Checking Login Items the Right Way in macOS Sequoia and Tahoe
In macOS Ventura and later, Apple moved login item management to System Settings → General → Login Items & Extensions. The view is split into two sections: Open at Login (visible apps and agents the user added) and Allow in the Background (invisible background items registered by apps). Reseller bloatware almost always appears in the second section. Toggle the switch off for anything unfamiliar — this suppresses the agent without deleting it, which is a safe first step if you are uncertain.
For a comprehensive walkthrough of everything that can slow a Mac at startup, our article on how to completely uninstall apps on a Mac covers login items, preference panes, and app extensions together.
Doing It at Scale: When You Have Multiple Machines
IT administrators receiving a batch of reseller MacBooks often need to remove the same set of apps across dozens of devices. The manual steps above translate directly to shell scripts deployable via your MDM of choice (Jamf, Mosyle, Kandji). The core pattern is:
- Unload and disable the LaunchDaemon or LaunchAgent with
launchctl bootout. - Remove the plist from the appropriate
/Library/LaunchDaemons/or/Library/LaunchAgents/path. - Remove the app bundle from
/Applications/. - Purge support files from
/Library/Application Support/and~/Library/Application Support/.
Test the script on a single machine before deploying broadly, and scope removals by checking that the target path exists before calling rm -rf.
A Faster Way to Audit Everything at Once
Working through eight or more folder paths manually is tedious, and it is easy to miss a nested subfolder. A tool like Crumb can audit all of these locations at once and show what is safe to remove before you delete anything — including launch agents, application support folders, and cache directories grouped by their parent app. That kind of visibility makes it much easier to be thorough without second-guessing every folder you encounter.
Whether you go manual or use a utility, the goal is the same: a machine where only software you chose is running in the background, and the storage you paid for is yours to use.