System Data Is Huge After a macOS Update: Clear the Leftover Bloat (2026)

If your Mac's System Data jumped by several gigabytes after installing a macOS update, you're not imagining things. The update process deliberately keeps installer caches, old kernel extensions, firmware bundles, and local snapshots on disk long after the installation completes — and macOS won't clean them up on its own schedule. This guide explains exactly what those leftovers are, which ones are safe to remove, and how to reclaim the space without destabilizing your system.

Why System Data Gets Huge After a macOS Update

When macOS installs a major or minor update, several categories of files accumulate under the hood:

• Installer caches and receipts. The softwareupdate daemon downloads a full installer package and unpacks it into a staging area. On major updates (e.g., macOS 15 → 26) this can reach 10–15 GB. After a successful install the staged payload is supposed to be removed, but it often isn't — especially if the update was interrupted or retried.
• APFS local snapshots. Before applying any OS update, macOS automatically takes a local Time Machine snapshot so you can roll back. These snapshots are counted toward "System Data" in System Settings → General → Storage and can hold several gigabytes of your pre-update volume state.
• Old kernel extensions and firmware blobs. The update may leave previous versions of kernelcache, firmware support files, and Boot ROM bundles inside /System/Library/ under the sealed system volume. These are generally inaccessible without disabling SIP and are reclaimed on the next reboot cycle automatically — no manual action needed.
• CoreData and CloudKit sync caches. Apps that sync with iCloud (Photos, Notes, Mail) rebuild their local caches after an OS upgrade, temporarily doubling their footprint in ~/Library/Caches/ and ~/Library/Application Support/.
• Crash reports and diagnostics. The update process generates a burst of diagnostic reports stored in /Library/Logs/DiagnosticReports/ and ~/Library/Logs/.

Understanding the System Data Figure in Storage Settings

The "System Data" category in System Settings → General → Storage is a catch-all. It includes everything macOS cannot neatly categorise: caches, local snapshots, VM swap files, and protected system files. Because local snapshots are counted here, System Data can look two to three times larger than the actual recoverable waste — some of that number is disk space that APFS has already reserved but can reclaim automatically when free space runs low.

To see your actual local snapshots, open Terminal and run:

tmutil listlocalsnapshots /

Each line shows a snapshot date stamp. The total size is reported by:

tmutil listlocalsnapshotdates / | tail -n +2 | while read d; do
  tmutil deletelocalsnapshots "$d" --dry-run 2>/dev/null || echo "$d"
done

Note: --dry-run is not a real tmutil flag; to inspect snapshot sizes use diskutil apfs listSnapshots disk3s5 (replace the volume identifier with your own from diskutil list).

What Is Safe to Delete — and What Isn't

Important: all cache and snapshot cleaning is permanent. Before removing anything significant, confirm you have a full backup on an external drive or Time Machine volume that is not the local snapshot.

How to Clear Post-Update Bloat: Step by Step

1. Delete Stale Local Snapshots

1. Open Terminal.
2. List snapshots:

   tmutil listlocalsnapshots /

3. Delete a specific snapshot by its date stamp (example):

   sudo tmutil deletelocalsnapshots 2026-05-28-020312

4. To delete all local snapshots at once — only do this if you have an external backup:

   for snap in $(tmutil listlocalsnapshotdates / | tail -n +2); do
     sudo tmutil deletelocalsnapshots "$snap"
   done

2. Remove the macOS Installer Package

1. Open Finder and go to /Applications.
2. Look for an app named Install macOS [version].
3. If the update succeeded and your system is stable, drag it to Trash and empty Trash. It can be re-downloaded from the App Store at any time.

3. Clear User Caches

1. In Finder, press Shift-Command-G and enter ~/Library/Caches.
2. Sort by size. The largest folders are typically browser caches (Safari, Chrome) and app-specific caches.
3. You can delete the contents of individual app cache folders (not the folder itself) without harm. Leave the com.apple.* folders alone unless you know what they contain.

4. Flush System-Level Caches (optional, requires admin)

sudo rm -rf /Library/Caches/*

This is safe on a standard macOS install but will cause a brief slowdown the next time affected services start. Skip this step if you are not comfortable with Terminal.

5. Clear Diagnostic Reports

rm -rf ~/Library/Logs/DiagnosticReports/*
sudo rm -rf /Library/Logs/DiagnosticReports/*

Using Crumb to Identify Update Installer Caches and Snapshots

If you'd rather not navigate the filesystem manually, Crumb surfaces update installer caches, oversized log folders, and stale snapshot footprints in its Visualize treemap — so you can see at a glance which post-update leftovers are worth targeting. The one-click Clean action handles user caches, logs, and purgeable System Data in a single pass, and the "Is this safe to delete?" AI can explain any unfamiliar folder before you commit to removing it. You can download Crumb and run one free cleanup to see how much space is recoverable after your next update.

After Cleaning: What to Expect

• System Data will shrink, but not to zero. The OS legitimately uses several gigabytes for swap, dynamic linker caches, and protected system content.
• First app launches may be slower while caches rebuild — this is normal and resolves within a day of regular use.
• The storage bar may not update immediately. macOS refreshes its storage calculations lazily. Quit and reopen System Settings if the numbers look stale.
• Local snapshot space will be reused gradually even without manual deletion — APFS reclaims snapshots automatically when free space falls below a threshold. Manual deletion just accelerates this.

Preventing the Bloat Next Time

• Install updates when you have at least 20 GB free so the installer doesn't have to work in a cramped environment (a common cause of failed downloads that leave orphaned caches).
• After a major upgrade, wait a week before running aggressive cleanups — give macOS time to rebuild its own internal caches and for Spotlight to re-index.
• Keep a genuine external Time Machine backup. It lets you delete local snapshots confidently without losing rollback protection.

Post-update System Data bloat is real, but most of it is recoverable with a handful of Terminal commands or a single cleanup pass. The key is knowing which files are ephemeral caches versus which ones macOS genuinely needs — and giving the system a day or two to settle before drawing conclusions from the storage bar.