Blog / Sep 21, 2026 · 4 min read

~/Library Is Where Your Mac Storage Hides (Safe Caches to Delete)

librarycacheshidden-filesmacoscleanup

Every Mac has a shame cabinet: ~/Library. It’s hidden by default, and it’s where apps bury caches, logs, and “attic” data. A 512 GB Mac with a mysteriously diminishing free bar usually finds its explanation in here — not in your Documents.

Let’s open the cabinet, identify what’s genuinely safe to trash, and reclaim the gigabytes.

Why it’s hidden and why that matters

~/Library is a per-user directory holding app support data, preferences, caches, and logs. The Finder hides it (⌘⇧. in a Finder window toggles hidden files) because messing with it can break apps — but the built-in fear overwhelms common sense: caches are safe to clear when the owning app is closed.

So the space Inside ~/Library is a mixture of precious (your app’s real data) and disposable (caches, logs, temp). The map matters more than the folder name.

The map of what’s inside

~/Library/Caches/            
~/Library/Application Support/
~/Library/Containers/        
~/Library/Logs/              
~/Library/Saved Application State/
~/Library/HTTPStorages/      
~/Library/WebKit/            
~/Library/Developer/         

Quick classification:

FolderWhat it isSafe to clear?
Caches/App cachesYes when app closed — it’s disposable
Containers/Sandboxed app dataPartially — app data, not all cache
Application Support/App’s real dataNo — that’s your files (mostly)
Logs/Log filesYes — logs are disposable
Saved Application State/Window stateYes — just restore windows
HTTPStorages/HTTP caches per appYes
WebKit/Web cacheYes
Developer/Xcode cachesYes — see DerivedData guide

Safe to delete — the honest one-liners

1. The whole caches folder (the whale)

sudo du -sh ~/Library/Caches
find ~/Library/Caches -mindepth 1 -maxdepth 1 -type d | head -30

You should see per-app cache dirs. Clear them (quit apps first!):

rm -rf ~/Library/Caches/* 2>/dev/null

⚠️ Don’t delete the ~/Library/Caches folder itself — apps expect it to exist. Clear within it.

Safe to delete? Yes — caches re-create on next launch. It’s the single fastest safe win after Logs.

2. Logs (the forgotten GB)

rm -rf ~/Library/Logs/*

Logs accumulate per app and system daemon. Safe to delete? Yes — new logs are written as needed.

3. Saved Application State

rm -rf ~/Library/'Saved Application State'/*

This is just “where was your window when you quit.” Deleting it means apps re-open in default positions — a non-event. Safe? Yes.

4. HTTPStorages and WebKit caches

rm -rf ~/Library/HTTPStorages/*
rm -rf ~/Library/WebKit/*

HTTPStorages include cookies/etc. Clearing may log you out of some web views inside apps. Safe? Yes, mildly-plausible tradeoff.

Always check the amount first

Before any rm -rf into the unknown, measure. du -sh a few paths, because the interesting folders (Caches, Application Support, Containers) vary wildly per machine. On mine:

  • Application Support can hold Tens of GB (that’s your real data — do NOT clear blindly)
  • Caches is usually a few GB to tens of GB (safe to clear)
  • Developer is routinely 30–60 GB (all rebuildable)

A disk analyzer lets you see the split before you act — you don’t have to fear-delete Application Support or Developer blind; you see the byte-labeled map, click the folder, inspect, then stage to Trash.

The DiskInsight approach to ~/Library

We built DiskInsight because the “don’t touch ~/Library” advice is too blunt. You should see the folder as folders:

  • Everything re-downloadable (caches, logs, DerivedData, simulator runtimes) is safe to clear
  • Everything unique (Application Support data, Containers’ real files) you’re never asked to delete anyway
  • And everything you do pick goes to the macOS Trash, reviewable and reversible — no app is ever silently deleted behind you

100% local, no telemetry, one-time price.

The 30-second version

  1. du -sh ~/Library/Caches — if it’s big, clear inside it (apps closed).
  2. Clear ~/Library/Logs/* and ~/Library/'Saved Application State'/*.
  3. If you’re a developer, add ~/Library/Developer (DerivedData — how-to).
  4. Never touch ~/Library/Application Support blind — that’s real data.

When in doubt: measure, don’t nuke. Then spend the reclaimed GB on something better.

Get DiskInsight Pro · $9.99 one-time to see what’s REAL inside ~/Library vs what’s just caches. Guide: full Mac cleanup.