You’re in control of a traditional file system, but with snapshots, clones, sparse files and other volumes sharing free space, APFS isn’t as simple.
A simple worked example showing the effect of snapshots and changes in hidden system files in consuming free space on APFS.
When Time Machine makes its backups to APFS storage, just what can and can’t you do? How can you prevent large temporary files from stealing space on storage?
Apple could have chosen to make APFS open source or to document it fully, to help third parties develop maintenance tools. It chose not to, but Disk Utility still doesn’t work as it should.
It depends whether you’re going to boot macOS from it, on the space required for snapshots, and how large they could become. And there’s more.
Have you found Time Machine docs helpful in solving problems? Do you know what “custom access” means in the Permissions section of Get Info?
Why Time Machine makes snapshots, and how they can grow and apparently consume free space. What you can and should do to manage this.
One likely cause of vanishing free space are large snapshots. So how can you tell why a snapshot is large, and how can you avoid it?
Snapshots are of great value, but can grow large if you don’t keep an eye on them. If you find Time Machine or another backup utility is storing large snapshots, here’s what to do.
Confused by this on APFS? So you should be, as it’s complicated by features like snapshots, sparse files, and the file system itself. There’s no single figure.