What is System Data on Mac? System Data is the storage category macOS uses for files that do not belong to Applications, Documents, Photos or another named category: caches, logs, temporary files, app support data, virtual memory, Time Machine local snapshots and developer files such as simulators. It gets big when a few hidden folders grow quietly, most often leftover browser update copies, large app data folders, Xcode device support files and simulators.
To clear it safely: find which of those folders is large, clear each one with the method that fits it, and leave swap, update files and local snapshots to macOS. There is no single “clear all” button, and the goal is usable free space, not a System Data figure of zero.
What is System Data on Mac?
On macOS 13 Ventura and later, open System Settings → General → Storage. System Data includes Apple and third-party files that do not fit a more specific category. The number alone does not tell you which files are disposable. Categories can change as macOS recalculates storage.
Apple includes items such as logs, caches, temporary files, app support files, plug-ins and virtual memory in this general category. A large virtual disk or a development workload can also be worth investigating when the total grows. Device backups, applications or other files may appear under their own named categories instead. Do not assume every file below is counted as System Data on every Mac.
Why is my System Data so high?
System Data is high when something on your Mac keeps data that has no category of its own. On most Macs a few sources explain the bulk of it:
- Leftover browser copies. Chrome and other Chromium browsers keep a full copy of the app in a hidden temporary folder for updates, and old copies are not always removed. They can reach 20 GB or more.
- Large app data folders. Browsers, code editors and AI apps keep caches, checkpoints and downloaded runtimes in Application Support, which Storage counts as System Data.
- Developer tools. Xcode device support files, simulator runtimes, DerivedData and Docker’s disk image each run to tens of gigabytes.
- macOS working space. Virtual memory, update files and Time Machine local snapshots grow and shrink on their own.
Start by asking what changed recently: did you install Xcode, download an AI model, run Docker, update macOS or keep a browser open for weeks? A large System Data total does not by itself mean something is wrong with macOS. The table of hidden contributors below gives typical sizes and the safe way to clear each one.
How to clear System Data on Mac, step by step
1. Establish whether you actually need more space
Open Storage settings and let the calculation finish. Record available space and the task that needs it, such as an installer or a project export. Save your work and keep a backup of important data. The goal is usable space for that task; the System Data label does not need to reach zero.
2. Review app-owned caches and downloads
Start with the storage or download controls in the application that created the files. Remove an offline download only if you can obtain it again when needed. If an app is closed and you recognize a replaceable cache, review that specific item. Avoid deleting all of ~/Library/Caches or treating Application Support as a disposable folder. The cache safety guide explains the distinction.
3. Separate development storage by its owner
For Xcode, review DerivedData and archives separately: regenerated build output and a retained distribution archive have different value. Shut down a simulator before reviewing its test data. Simulator device data and runtime installations are separate; erasing one does not uninstall the other.
For Docker, inspect its disk usage and the images, containers, volumes and build cache behind it. Preserve databases and writable container data you need before pruning. A large Docker.raw file is not a cache to drag to Trash; follow the Docker storage guide. Manage other virtual machines through their own software.
4. Review old device backups deliberately
If you recognize a local iPhone or iPad backup you no longer need, connect the device, select it in Finder, open General → Manage Backups and inspect the device and date. Keep a recovery copy you still rely on. Apple's backup deletion cannot be undone; do not edit individual files inside a backup. These backups may be listed as iOS Files rather than System Data.
5. Let macOS complete updates and manage recovery data
Finish an in-progress macOS update and restart if prompted. Leave protected update downloads, installation state and swap files alone. Old installer files you knowingly kept in Downloads are different from the update system's working files. Time Machine local snapshots are recovery points managed by macOS; connecting the backup disk and allowing a backup to complete is a better starting point than deleting snapshots to change a chart.
6. Check the result after one reviewed change
Reopen the application or project affected by the cleanup, then compare available space in the same storage view. Files moved to Trash still occupy storage; inspect them before emptying it permanently. Storage categories can take time to recalculate, and shared APFS blocks may prevent a candidate's displayed size from translating into the same amount of available space.
The hidden contributors that grow fastest
When System Data is far larger than expected, a handful of locations usually explain most of it. None of them appear in Finder's normal view, and each needs a different decision.
| Contributor | Typical size | Safe to clear? | Guide |
|---|---|---|---|
Browser update copies (*.code_sign_clone) | 5–30 GB | Yes, with the browser quit | Chrome code_sign_clone |
| App data in Application Support | 1–30 GB per app | Only the cache parts | Application Support is huge |
| Xcode device support files | 5–50 GB | Old versions, yes | iOS DeviceSupport |
| Simulator devices and runtimes | 10–40 GB | Depends on what you test | Delete iOS simulators |
| Docker disk image | 10–60 GB | Through Docker only | Docker.raw is huge |
| Time Machine local snapshots | Varies | Usually leave to macOS | Local snapshots |
| Local AI models | 2–100 GB | Yes, if you can download them again | Where AI models live |
The sizes are typical ranges we see, not limits. Measure your own Mac before deciding; on one developer Mac, browser copies alone were 30 GB and a single code editor's history was 21 GB.
Check storage before deleting
- Open Storage settings and allow the categories to finish calculating. Note available space as well as System Data.
- Review Documents and Applications first. For an unfamiliar file, reveal it in Finder and identify the owning app.
- Use Finder's Go → Go to Folder to inspect a known location, such as
~/Library/Developer/Xcode/DerivedData. Do not treat the whole Library as a cache. - For a read-only view of the largest top-level Library folders, use the command below. Permission errors mean the result is incomplete; they are not a reason to disable macOS protections.
du -sh ~/Library/* 2>/dev/null | sort -h | tail -15This read-only command lists sizes, not cleanup recommendations. A large Application Support folder can contain documents and databases. Inaccessible folders make the results incomplete; do not disable macOS protections or feed the output into a deletion command.
What can you remove safely?
| Category | Safe to remove? | Important consideration |
|---|---|---|
| Temporary app caches | Sometimes | Prefer the app's controls. Offline downloads and app data may be mixed in; caches can regrow. |
| Xcode DerivedData | Generally, with care | Quit builds first; indexes and build products are regenerated. The next build can take longer. |
| Old simulator data | Depends | May contain test apps and data you still need. Device data and runtimes are separate. |
| Time Machine snapshots | Depends | Backup recovery points managed by macOS; usually leave them alone. |
| VM and container disks | Only through the owning app | Can hold entire working systems and databases. |
| Unknown system folders | No blanket recommendation | May be required by macOS or an installed application. |
What MacMonitor actually handles
MacMonitor 1.2 adds a System Data view in Storage Lens. It measures the contributors above that it can read on your Mac and sorts them into three groups, so you can see what is behind the number before you remove anything. It does not reproduce Apple's private System Data total, and its measured figure should not be subtracted from that label as if the two were the same measurement.
| Group | What it includes | How removal works |
|---|---|---|
| Safe to clean | Browser update copies in your own temporary area, Xcode device support files, SwiftUI preview data, simulator caches and known re-downloadable developer tool caches | Ticked by default and cleaned in one click; skipped while the owning app is open; moved to the Trash with Put Back |
| Worth a look | Cursor checkpoints, AI app virtual machines, simulator runtimes and devices, unavailable simulators, Docker, other ~/.cache tools, and large app data folders | One item at a time after a confirmation; simulator removal goes through Xcode's own tool and is permanent; app data folders open into their safe, review and your-data parts |
| Managed by macOS | Virtual memory, Time Machine local snapshots and system logs | Shown so the total makes sense; never offered for removal |
Inside a large app data folder, such as Chrome's or a code editor's, MacMonitor separates caches it can rebuild from data with meaning and from your own profiles and history, which it never offers. The Application Support guide explains the same rules for doing it by hand. Junk, Build Caches and Model Vault in the Cleaner continue to cover user caches and logs, DerivedData and archives, Docker pruning and local AI models.
MacMonitor's System & other figure is the remainder outside its measured folder categories. It can include macOS, other users, inaccessible locations and APFS accounting differences. It is not a renamed or independently verified Apple System Data total. Permissions can limit coverage in either build.
Leave system-managed files alone. Do not remove
/System, /Library/Apple, swap files in /private/var/vm, or unknown Application Support and Group Containers folders. Shared containers may contain data for several apps.Example: 67 GB found on one developer’s Mac
On a MacBook Pro used for app development and AI tools, Storage settings showed a large System Data figure with no detail. Measuring the contributors above found, in November 2026:
| Contributor | Measured size | How to handle it |
|---|---|---|
Chrome update copy (code_sign_clone) | 23 GB | Safe to remove with Chrome quit |
Cursor checkpoints (snapshots) | 20 GB | Review: older edits can no longer be restored |
| Claude app virtual machine bundle | 10 GB | Review: downloaded again when the feature is next used |
| An iOS simulator runtime no longer tested | 8.5 GB | Remove through Xcode if you no longer test that version |
| Xcode iOS DeviceSupport | 5.95 GB | Safe to remove for versions your devices no longer run |
Those five items came to about 67 GB, and none of them appears in Finder’s normal view. Each needs a different decision, which is why a single “clear System Data” button does not exist. Only two of them are safe to remove without thinking about what you lose; the other three cost a re-download, older checkpoints or a test setup. After you remove something and empty the Trash, compare available space rather than the System Data figure, which can take a few minutes to recalculate.
Questions about clearing System Data
Can I delete all System Data?
No. It includes files your Mac and apps need. Identify the owner and purpose of an item before deciding what to remove.
Why does the number grow again?
Apps regenerate caches, builds create new products, and backups retain recovery points. Investigate a recurring large folder rather than repeating a broad cleanup.
Did an update cause it?
Check whether installation has completed and compare available space after Storage finishes recalculating. A change in the System Data label alone does not identify the cause. Inspect files you recognize and let macOS manage update files and backup snapshots.
Choosing a cleanup tool? See the CleanMyMac and MacMonitor comparison, including their limits.
Is an app’s reported cleanup total the same as System Data?
No. A cleanup application usually measures supported files it can read. Apple’s Storage categories use their own accounting. A tool can help identify candidates without reproducing the System Data label or guaranteeing that the label will shrink by the same amount.
Should I reinstall macOS to reduce System Data?
A large category alone does not establish that reinstallation is appropriate. First identify the actual storage constraint and inspect known contributors. Reinstallation is a much larger intervention and should follow a separate backup and troubleshooting decision.
Can a cleaner remove everything in the table safely?
The table is a set of decisions, not a selection preset. Developer data may be replaceable but expensive to rebuild; simulator data may contain a test state you need; app caches may include useful offline material. Review the specific item and the consequence of removing it.
See what is inside your System Data
Open Storage Lens → System Data in MacMonitor to see the contributors on your Mac sorted into safe to clean, worth a look and managed by macOS, with sizes and plain explanations. Safe items clean in one click and go to the Trash with Put Back; nothing is removed while its app is open. Potential cleanup size is not measured reclaimed storage: compare available space after you empty the Trash.