How to Clear System Data on Mac in 2025 (6 Real Fixes)

If you have ever opened your Mac's storage breakdown and wondered what is System Data on Mac — and why it takes up 50, 80, or even 100+ GB — you are not alone. System Data on Mac is one of the most confusing storage categories because Apple provides almost no detail about what it contains, and the number seemingly grows on its own. This guide explains exactly what fills that category, why it gets so large on a MacBook, and how to clear System Data on Mac safely without breaking anything.

Table of Contents

• What Is System Data on Mac?
• Why Is Mac System Data Too Large?
• Quick Fix Summary
• 1. Delete Time Machine Local Snapshots
• 2. Clear App Caches and Log Files
• 3. Remove Old macOS Installers
• 4. Clear Virtual Memory Swap Files
• 5. Delete Unused Language Packs
• 6. Trim Xcode Caches and Simulator Data
• FAQ
• Conclusion

What Is System Data on Mac?

System Data is a catch-all category in macOS's Storage panel that groups together files macOS does not assign to any other category. It is sometimes called "Other" on older versions of macOS. When you open Apple menu > System Settings > General > Storage, you see categories like Apps, Documents, and iCloud Drive — everything that does not fit neatly into those categories lands in System Data.

The main types of files that count as System Data include:

• Time Machine local snapshots — macOS keeps recent Time Machine backups on your local drive even if you do not have an external backup disk connected
• Application caches — temporary files stored in ~/Library/Caches and /Library/Caches
• System logs — diagnostic and crash logs in /Library/Logs and ~/Library/Logs
• Virtual memory swap files — files macOS writes to disk when RAM is full
• Fonts — third-party fonts installed for design applications
• Browser data — cached websites, cookies, and session data
• Plugin and extension files — audio plug-ins, screen savers, kernel extensions
• macOS installer packages — leftover .pkg and installer caches from OS updates
• Xcode derived data and simulator images — for developers, these can be enormous

The reason System Data can be massive while your actual document count stays low is that caches, logs, and snapshots grow in the background silently.

Why Is Mac System Data Too Large?

Understanding what causes the growth helps you target the right fix.

• Time Machine is enabled but no external drive is always connected — macOS stores "local snapshots" on your main drive as a fallback, and these can consume 20–50 GB over time
• Xcode is installed — derived data, simulator runtimes, and device support files can easily add up to 30–60 GB of System Data
• Heavy browser use — Chrome and Firefox in particular can cache several gigabytes of website data
• Apps with large caches — video editing apps like Final Cut Pro and DaVinci Resolve create substantial render caches; music apps like Logic Pro store sound library previews
• Frequent macOS updates — update installers download to your drive and sometimes leave residual package files even after a successful upgrade
• Log files from crashes or errors — if an app has been crashing repeatedly, its log files can balloon into hundreds of megabytes
• Virtual memory activity — Macs with 8 GB of RAM running many tabs and apps generate large swap files on the SSD
• Old iOS backups counted in System Data on some macOS versions
• Accumulated font libraries from creative software installers

Quick Fix Summary

1. Delete Time Machine Local Snapshots

Why Local Snapshots Grow So Large

This is the most common and most impactful fix for oversized System Data. When Time Machine is turned on, macOS creates hourly "local snapshots" — essentially mini backups stored on your main drive — even when your external backup drive is not connected. These snapshots let you restore recent versions of files without needing the backup disk. The downside is they can accumulate to 20–60 GB without any warning.

Steps to list and delete local snapshots via Terminal:

1. Open Terminal from Applications > Utilities (or press Command + Space, type Terminal, hit Return)
2. List all current local snapshots:

tmutil listlocalsnapshots /

You will see output like com.apple.TimeMachine.2025-03-10-143022. Each line is one snapshot with a date stamp.

3. To delete a specific snapshot, copy its date string from the output and run:

sudo tmutil deletelocalsnapshots 2025-03-10-143022

Replace 2025-03-10-143022 with the actual date from your output. Enter your admin password when prompted.

4. To delete all local snapshots at once:

for snap in $(tmutil listlocalsnapshots / | awk -F. '{print $NF}'); do sudo tmutil deletelocalsnapshots $snap; done

Tip: After running this, go back to System Settings > General > Storage and refresh the view. System Data should drop noticeably — sometimes by 20–50 GB. macOS will start creating new local snapshots again automatically, but they will stay small as long as your backup drive is connected regularly.

Alternatively, disable local snapshots entirely:

sudo tmutil disablelocal

Note: this option was removed in newer versions of macOS. On macOS Ventura and later, the approach above (deleting individual snapshots) is the correct path.

2. Clear App Caches and Log Files

Caches and Logs — Silent Space Hogs

App caches and log files sit in your ~/Library folder and grow constantly. Caches are rebuilt automatically when you use an app; logs are just diagnostic records. Both are safe to delete.

Steps to clear user caches:

1. Open Finder
2. From the menu bar, select Go > Go to Folder (or press Command + Shift + G)
3. Type ~/Library/Caches and press Return
4. You will see a list of folders named after each application
5. Select the folders for apps you regularly use (look for large ones like com.google.Chrome, com.apple.Safari, Slack, Spotify)
6. Right-click and select Move to Trash
7. Empty the Trash

Tip: Do not delete the entire Caches folder as a parent directory — just the subfolders inside it. Deleting the parent can confuse some processes that expect the folder to exist. Selecting and deleting the contents is safe.

Steps to clear log files:

1. Press Command + Shift + G in Finder
2. Type ~/Library/Logs and press Return
3. Select all folders inside (press Command + A)
4. Move to Trash and empty it

Then repeat for system-level logs:

1. Press Command + Shift + G
2. Type /Library/Logs and press Return
3. Review folders — any folder associated with a known app is safe to clear
4. Move to Trash and empty it

For a fast Terminal alternative that shows which cache folders are largest before you delete:

du -sh ~/Library/Caches/* | sort -rh | head -15

3. Remove Old macOS Installers

Leftover Installers Consume Gigabytes

When macOS downloads a system update, it stores the full installer in your Applications folder. These files range from 3 GB to 14 GB each and serve no purpose once the update is complete. If you have upgraded macOS multiple times, you may have several old installers.

Steps:

1. Open Finder and navigate to Applications (click it in the Finder sidebar)
2. Look for files named like:
   • Install macOS Sequoia
   • Install macOS Sonoma
   • Install macOS Ventura
3. If you find any, right-click and select Move to Trash
4. Empty the Trash

Tip: Before deleting, verify you no longer need the installer. If you use it to reinstall macOS on other Macs or create bootable USB drives, move it to an external drive first rather than deleting it outright.

Also check for leftover package cache files that macOS update installers leave behind:

sudo rm -rf /Library/Caches/com.apple.pkg.*

Enter your admin password when prompted. This clears macOS package installer caches.

4. Clear Virtual Memory Swap Files

What Swap Files Are and Why They Exist

When your Mac runs low on RAM, macOS writes memory contents to the SSD in a process called "swapping." The files it creates are swap files, stored at /private/var/vm/. They can grow to several gigabytes if you run a lot of apps simultaneously.

You cannot safely delete swap files while macOS is running — the operating system holds locks on them. The correct way to clear swap files is to restart your Mac.

Steps:

1. Save all open work
2. Click Apple menu > Restart
3. Wait for the Mac to fully reboot
4. After restart, check System Data size in System Settings > General > Storage

macOS creates fresh swap files on restart, but they start small and only grow again if RAM runs out.

Tip: If your Mac is regularly creating very large swap files, the underlying issue is insufficient RAM for your workload. Consider which apps you run simultaneously — closing browser tabs, quitting unused apps, and limiting background processes reduces swap usage more sustainably than clearing the files.

You can check current swap usage without restarting using Terminal:

sysctl vm.swapusage

This shows total swap allocated and how much is currently in use.

5. Delete Unused Language Packs

How Language Packs Waste Space

Most Mac applications ship with support for dozens of languages — French, German, Japanese, Chinese, and many more. Unless you actually use those languages, those resource files just sit there. On a typical Mac with 50–100 apps installed, stripping unused language packs can recover 1–3 GB.

You can do this manually for individual apps, or use Terminal for a more thorough approach.

Manual method for a single app:

1. Open Finder and go to Applications
2. Right-click the app you want to clean (e.g., Pages.app)
3. Select Show Package Contents
4. Navigate to Contents > Resources
5. You will see folders ending in .lproj — each one is a language pack (e.g., fr.lproj for French, de.lproj for German)
6. Keep en.lproj (English) and delete any others you do not need
7. Empty the Trash

Tip: Do not do this for system apps like Finder, Safari, or System Settings — only for third-party applications where you are confident about the change. Also note this change will be overwritten if the app updates itself.

Terminal method to identify total language pack size:

find /Applications -name "*.lproj" -not -name "en.lproj" -not -name "Base.lproj" | xargs du -sh 2>/dev/null | sort -rh | head -20

This lists the largest non-English language packs across all your applications, so you can see how much space is actually recoverable before committing to deletions.

6. Trim Xcode Caches and Simulator Data

Xcode: The Biggest Offender for Developers

If Xcode is installed on your Mac, it is very likely the single largest contributor to your System Data. Xcode stores derived build data, simulator runtime images, device support files, and documentation caches that collectively can hit 30–80 GB without you ever noticing.

Steps to clear Xcode derived data:

1. Open Terminal
2. Delete the derived data folder where Xcode stores build artifacts:

rm -rf ~/Library/Developer/Xcode/DerivedData

3. Delete simulator data (these are disk images for iOS/iPadOS simulators):

rm -rf ~/Library/Developer/CoreSimulator/Caches

4. List and remove unused simulator runtimes. First, list what is installed:

xcrun simctl runtime list

5. Delete a specific unused runtime by its identifier shown in that list:

xcrun simctl runtime delete <runtime-identifier>

Tip: Only delete simulator runtimes for iOS/iPadOS versions you no longer test against. If you have iOS 16, iOS 17, and iOS 18 simulators and only test on iOS 18, you can safely delete the iOS 16 and 17 runtimes.

Clear Xcode's own caches:

rm -rf ~/Library/Caches/com.apple.dt.Xcode

Remove old device support files (created when you connect older iPhones for debugging):

ls ~/Library/Developer/Xcode/iOS\ DeviceSupport/

Delete folders for iOS versions you no longer develop against:

rm -rf ~/Library/Developer/Xcode/iOS\ DeviceSupport/15.*

Together, these Xcode-related cleanups routinely recover 20–50 GB in System Data for active developers.

FAQ

What counts as System Data on Mac?

System Data on Mac is a catch-all category for files that do not belong to the standard storage categories (Apps, Documents, iCloud Drive, Photos, Mail). It primarily includes Time Machine local snapshots, app caches, system and application log files, virtual memory swap files, plugin data, browser caches, macOS installer remnants, and — for developers — Xcode build data and simulator images.

Why is my MacBook System Data so large even though I haven't stored much?

The most common reason is Time Machine local snapshots. If Time Machine is enabled but your external backup drive is not always plugged in, macOS stores backup snapshots directly on your internal SSD. These build up silently and can reach 20–60 GB. The second most common reason is app caches — especially from browsers, video editors, and developer tools like Xcode — which grow in the background regardless of how many personal files you store.

Is it safe to delete System Data on Mac?

You cannot delete "System Data" as a category directly — it is not a single folder. What you can safely delete are the individual items inside it: Time Machine snapshots (via tmutil), app caches in ~/Library/Caches, log files in ~/Library/Logs, and Xcode derived data. None of these deletions will harm your personal files or system stability. Apps rebuild their caches as needed, and macOS creates new snapshots going forward.

How do I delete System Data on Mac using only built-in tools?

Use Terminal for Time Machine snapshots (tmutil listlocalsnapshots / and tmutil deletelocalsnapshots), use Finder's Go to Folder to navigate to ~/Library/Caches and delete app cache folders, and restart your Mac to clear swap files. For Xcode, use rm -rf ~/Library/Developer/Xcode/DerivedData in Terminal. All of these are built-in approaches that require no third-party software.

Will System Data shrink immediately after I delete files?

The System Settings > General > Storage panel does not update in real time. After clearing files, wait 30–60 seconds and then quit and reopen System Settings, or navigate away and back to the Storage panel. The recalculation happens in the background. In some cases macOS takes a few minutes to reflect large changes like snapshot deletion.

Conclusion

System Data on Mac grows quietly and consistently — driven by Time Machine snapshots, app caches, Xcode artifacts, and log files that accumulate in the background. Clearing it requires targeted action rather than a single button, but none of the steps above require paid tools or technical expertise beyond running a few Terminal commands. Start with Time Machine snapshot deletion since that is almost always the biggest single gain, then work through caches, logs, and Xcode data if applicable. Revisiting these steps every few months keeps System Data from creeping back to problematic sizes and keeps your Mac running smoothly on whatever storage capacity it came with.