System Data is the group that makes people nervous, and the feeling is fair: it has a vagueness to it, as though the Mac is hiding something. It is not. System Data is simply a label for a handful of ordinary things the system keeps on your behalf, and once you know the list, most of the mystery leaves the room.
What the label covers
Under the System Data heading macOS collects several kinds of files: caches that speed up repeated work, logs that record what happened, indexes that make searching quick, temporary files that should clear themselves, device backups taken from a phone or tablet, and local snapshots taken by Time Machine. Different Macs show very different sizes here because the mix depends on how you use the machine.
Caches
A cache is a stored copy of something the system expects to need again, kept so it does not have to work it out twice. Browsers, image previews and the system itself all keep caches. They are usually disposable: clearing one costs a little speed the next time it is used, then it rebuilds. You rarely need to reach for caches by hand, because macOS manages them, but they explain why the group can be large.
Logs
Logs are the machine's diary: a record of events, useful for finding the cause of a problem and of little use afterwards. They are small next to caches and snapshots, and macOS rotates and trims them on its own. There is no routine reason to touch them.
Indexes
An index is a catalogue that makes searching fast. Spotlight keeps one, and Mail and Photos keep smaller ones. If an index grows bloated or becomes confused, rebuilding it can both fix odd search results and settle its size. The rebuild is done through the ordinary panels, and it runs in the background while you carry on.
Device backups
When you back up an iPhone or iPad to this Mac rather than to iCloud, the copy is stored here. These backups can be very large — many gigabytes each — and they are genuinely important. They belong on the drive only if this is where you intend to keep them. Moving device backups to an external drive is often the single largest change a MacBook owner can make in this group.
What is safe, and what is precious
The useful distinction is not size but replaceability. Caches and temporary files can be recreated by the system whenever it needs them, so they are the safe end of the group. Logs are harmless. Indexes are rebuildable. Device backups and local snapshots are different: they are copies of things you may not be able to recreate, so they are the precious end, and they deserve a second copy before any removal.
| Inside System Data | Replaceable? | Routine approach |
|---|---|---|
| Caches | Yes, rebuilt on demand | Leave to macOS; clear a specific one only if it misbehaves |
| Logs | Yes | Leave alone |
| Indexes | Yes, rebuilt | Rebuild through the panel if search is odd |
| Temporary files | Yes | Cleared after a restart |
| Device backups | No | Keep a copy elsewhere, then move or remove |
| Local snapshots | No | Covered in the snapshots chapter |
Do not reach into the hidden Library folders and remove files by hand. That is where the real damage happens: a missing index is a nuisance, but a missing support file can break a panel entirely. Everything in this chapter is done through the ordinary screens, or not at all.
A careful routine
- Measure firstRead the size of the System Data group before you change anything, and note it down.
- Deal with device backupsIf you keep phone backups here, decide whether they belong on this drive, and move them to an external one if not.
- Check snapshotsOpen Time Machine settings and see how much space local snapshots hold. The next chapter covers them in detail.
- Let the system tidy itselfRestart the Mac. Temporary files clear, caches settle, and the figure often falls on its own.
- Rebuild only if neededIf search misbehaves, rebuild the index through the panel rather than deleting anything.
- Recheck and compareReturn to Storage and compare with your first note. Real progress shows up as a real change.
Readers are often surprised how much of this group simply settles itself once the two large, precious items — device backups and snapshots — have been understood and, where sensible, moved. That is the whole lesson of this chapter: name the contents, respect the precious parts, and leave the rest to the system that made it.