What Apple puts in System Data

Apple describes System Data as files that do not fit a more specific category. It can include logs, caches, virtual-memory files, temporary files, fonts, plug-ins, and app support data. Its size changes with the current state of the Mac.

That explains why generic advice to clear one cache folder rarely solves the whole number—and why the category may change after indexing, a restart, or macOS cleanup.

Investigate the largest contributors in this order

  • User and system Library folders, especially Application Support
  • Local iPhone and iPad backups
  • Developer data from Xcode, simulators, package managers, and containers
  • Virtual machines and Docker disk images
  • Mail, Messages, browser profiles, and media caches
  • Local snapshots and purgeable capacity, which are not ordinary folders

What is usually safe—and what requires care

Delete abandoned installers, old device backups through their owning interface, obsolete developer builds, and replaceable downloads after verifying them. Application-specific cache cleanup is safer when the application documents it.

Do not recursively erase Library, /private, /System, virtual-memory files, or unfamiliar container data. Close the owning application and make a backup before removing data whose purpose is not obvious.

Why System Data may not shrink immediately

The Storage chart can take time to recategorize files. Trash still consumes disk space until emptied. APFS snapshots and purgeable space follow their own lifecycle. Compare actual available capacity as well as the category chart before concluding that cleanup failed.

Primary sources

Product and platform facts were checked against these first-party references: