WHFS · Mac storage since two domains ago
Field notes on Mac storage and free space. Measured, not guessed; appraised against criteria, not slogans.
Planned additions across all four subject doors plus the kit, announced openly and dated as plans.
Measure, rank, act, verify, record: the five-stage order every Headroom guide follows and why it holds.
Why this publication exists, what each department holds today, and the standard we hold ourselves to.
Why macOS claims capacity it hasn't freed yet, how thinnables release on demand, and what this means buying drives.
Four ways to see how much room is left on a Mac drive, from About This Mac to df, and why two of them can disagree.
Why hourly local snapshots appear, when they thin, and the supported way to inspect or remove one.
Treemaps, column meters and terminal lists answer different needs; criteria to match an analyzer to your desk.
The System Data bucket gathers caches, logs, virtual memory and more; a plain tour of what lives inside.
Finder search, sorted views and du scans surface the space hogs; how to read results before deleting.
Two commands answer different questions: du weighs trees, df reports volumes; syntax, flags and interpretation.
A measured sequence for reclaiming space safely: measure, empty trash families, trim caches, move libraries.
An unsentimental look at cleaner subscriptions: what they automate legitimately, what fear marketing inflates.
Formatting choices, library relocation care, launch-key discipline and verification habits for offload duty.
Caches, snapshots, synced libraries and growing mail stores explain silent growth; here is how each behaves.
Which cache families tolerate deletion, which resent it, and the difference re-download time makes.
What TreeSize gave Windows admins, equivalent capabilities Mac users reach for, and the heritage connection here.
How this desk works. Measure first, delete second, log both numbers; the printable routine lives on the field kit page and its reasoning on the audit order note. Corrections land visibly: write [email protected], policy inside the editorial register. Common questions sit ready on the short answers shelf, and the mailbox rules are stated plainly on the privacy policy.
