System Data is huge on my Mac
What Apple says System Data holds, and three places on a developer's Mac you can measure yourself: folders inside your Library, Docker's disk image, and space that deleting did not give back. From Apple's and each tool's own documentation.
What Apple says it is
Apple's System Information guide says this category primarily includes "log files, caches, VM files and other runtime system resources." (About System Data, macOS 12 version of the guide)
That still does not say which folders on your Mac make up the number. So instead of guessing, measure. Here are three places on a developer's Mac you can measure yourself. They are places to look, not a list of what System Data is.
- Developer folders inside your Library folder.
- Docker's disk image.
- Space that deleting files did not give back.
1. Developer folders inside ~/Library
Several tools keep their folders inside ~/Library. Each tool's own documentation names its folder:
- pip: "MacOS:
~/Library/Caches/pip".pip cache purge"will clear all files from pip's wheel and HTTP caches." (pip: Caching) - Homebrew:
brew --cachewill "Display Homebrew's download cache."brew cleanupremoves "outdated downloads for all formulae and casks". (brew manpage) - Xcode: build output in
~/Library/Developer/Xcode/DerivedData, which Xcode makes again when you build. How to remove it safely.
To see the largest folders in your Library, from Terminal:
du -sh ~/Library/* 2>/dev/null | sort -h | tail -152. Docker's disk image
Docker's documentation: "Docker Desktop stores Linux containers and images in a single, large "disk image" file in the Mac filesystem." Its own example location is inside ~/Library/Containers/com.docker.docker. (Docker Desktop for Mac FAQ) How to read its real size and shrink it.
3. Space that deleting did not give back
Apple's documentation on APFS, the Mac's file system: "A clone is a copy of a file or directory that occupies no additional space on disk." Copies "continue to share the unmodified blocks." Deleting one copy of a cloned file frees only what it did not share. (About Apple File System)
Time Machine local snapshots can hold deleted files' space too. Measured on the developer's MacBook Air M1: with no backup disk connected, 22 hourly local snapshots each lived 20 s to 43 min 38 s before macOS removed them. After a real backup on 11 Oct 2026, one snapshot held 24.46 GB for 2 h 4 min. The full measurements.
Some used space belongs to no folder you can see
When Spaceific added up every folder it could read on the developer's Mac on 8 Oct 2026, 14.31 GB of the 239.01 GB macOS reported as used could not be tied to any folder. That is not free space. It is used space that no folder you can read accounts for.
What not to do
- Do not delete folders in the system's own locations by hand.
- If a tool gives you one total for System Data, ask which folders make it up, and whether each one comes back on its own.
Sources
- System Information User Guide, System Data, Apple, macOS 12 version.
- About Apple File System, Apple Developer Documentation, read 3 Nov 2026.
- pip: Caching, read 3 Nov 2026 (from github.com/pypa/pip, docs).
- Homebrew manpage, read 3 Nov 2026 (from github.com/Homebrew/brew, docs).
- FAQs for Docker Desktop for Mac, read 3 Nov 2026 (from github.com/docker/docs).