Too many large files

What this means

Disk usage is heavily skewed. In most libraries a handful of files account for the majority of the space, and the rest is noise. That is good news: you do not need to review thousands of files, you need to find the few that matter.

Why it happens

Large files appear for predictable reasons:

• Video. Screen recordings, exports and raw footage produce very large files and are rarely cleaned up after a project ends.
• Disk images and installers. Downloaded, used once, never removed.
• Virtual machines. A VM disk is a single file that grows with use.
• Game installations. Often tens of gigabytes, and often unplayed.
• Archives. Downloaded collections that were expanded and kept in both forms.
• Application bundles. These are directories presented as single files, so an application can look small in Finder while occupying far more.

How to find them

Order files by size. This is the whole technique: the list you want is a sorted list, and any method that involves opening folders one at a time is strictly slower.

The Large File Finder produces that list directly. If you prefer to do it manually, Finder can sort a folder by size, but it only does so one folder at a time — which is why the automated version exists.

Judging a large file

Size is not a reason to delete. Before removing a large file, establish:

• What created it. Files inside application bundles and virtual machine packages belong to something. Removing them breaks it.
• Whether it can be recreated. A downloaded installer can be downloaded again. A recording cannot.
• Whether it is the only copy. Files on the internal disk that are also backed up elsewhere are safe to remove locally. Files that exist only here are not.

The alternative to deleting

For large files you still want, moving them is usually better than removing them. External drives and cloud storage both take the file off the startup disk without destroying it. A video archive that lives on an external drive costs you nothing but the drive, and it removes tens of gigabytes from the internal disk permanently rather than temporarily.

Keeping it from coming back

Large files accumulate at the end of projects, when the working files are no longer needed but nobody deletes them. A short review at the end of a project — what is finished, what can move to external storage, what can go — is more effective than a cleanup every few months.