Guide11 min
How to Find What's Taking Up Space on Your C: Drive with PowerShell
You finish with each large C: folder matched to its owner, whether an AI model folder, a package cache or the hibernation file, and to the cleanup it needs.
These guides find what fills a developer's disk on a Mac or a Windows PC, measure what each cleanup gave back, and free it one tool at a time.
On a Mac, df, du and the cleanup tools don’t agree on how much space a
cleanup freed. The number that says what the Mac got back is the APFS
container’s free space, read before and after every cleanup:
$ diskutil info / | grep "Container Free Space"Each of the others misses something. The Used column of df -h / counts the
sealed system volume, not your files. ls reports a sparse file such as
Docker.raw at its full limit. A cleanup tool’s own total can far exceed what
the disk gained, as one uv cache prune run showed. A Docker prune can return
its space minutes after it reports, so re-read the free space before the next
cleanup.
Finding what’s taking up the space narrows
a full disk to one tool with du. The rest of the
Free Up Space on a Developer Mac
series takes one cause each: the uv cache,
Docker.raw, Xcode’s simulators and
DeviceSupport, build folders in
idle projects and what Claude Code
leaves on disk, where a folder that looks
abandoned can hold the only copy of a commit.
On Windows the job starts from PowerShell. Finding what’s taking up the C: drive sizes it one folder at a time until each large folder belongs to one tool, and opens the Free Up Space on a Windows PC series.
7 articles
Guide11 min
You finish with each large C: folder matched to its owner, whether an AI model folder, a package cache or the hibernation file, and to the cleanup it needs.
Guide9 min
Get the space in Docker.raw back on a Mac by pruning images no container uses, keeping the volumes that hold app data and the images stopped containers need.
Guide9 min
A read-only prompt makes Claude Code sort its scratch folders, worktrees and session history into in use, recoverable or unknown, with evidence for each.
Guide9 min
The build folders in projects you've stopped working on held about 27 of the 63 GiB on the test Mac, and those are the ones safe to clear.
Guide9 min
Pruning cut a 133 GiB uv cache to 4 GiB, and free-space readings before and after show the real gain: about 28 GB on a 1 TB Mac.
Guide11 min
You measure Xcode's simulators, runtimes and DeviceSupport and delete what nothing uses, including the runtime images a du of your home folder misses.
Guide8 min
Find which developer tool is filling your Mac's disk, such as uv, Xcode or Docker, and which cleanup applies.