System Data is a category, not a location
macOS uses System Data for files that do not fit a more specific storage category. It can include logs, caches, virtual-memory files, app support data, local snapshots and other changing content.
Because the category is assembled from metadata, its total can change after indexing, a restart or cloud synchronisation. There is no single System Data folder to empty.
Why the number can be surprisingly large
Developer tools, virtual machines, containers, creative applications and local AI runtimes may store large support data under Library folders that macOS groups broadly.
Time Machine local snapshots and purgeable data can also appear confusing. macOS may count space used by snapshots as available because it can remove them when needed.
What to inspect safely
Start with the applications and workloads you recognise. Use their own storage views or cleanup tools, and confirm whether data is cache, downloaded content, a database or source material.
- Application Support belonging to a known app
- Xcode DerivedData and simulator runtimes
- Container images and build cache, not unknown data volumes
- Local AI models that can be downloaded again
- Old device backups you can identify
What not to do
Do not disable System Integrity Protection, edit the sealed system volume or erase Library folders wholesale. Administrator access does not turn an unknown file into junk.
If the number remains unexplained, measure which user-owned folder is growing over time. Change history is often more useful than a one-off total.