Running out of room? Start with the steps that free the most space for the least risk, and check what each one really frees.
By MacMonitor · Published · Updated · macOS 26; app requires macOS 14 or later
Short answer: open System Settings → General → Storage to see what is using space, then empty the Trash, delete old installers and large files you no longer need, remove apps you stopped using with their leftovers, and clear iOS backups and developer caches. Files you move to the Trash still use space until you empty it.
Open System Settings → General → Storage. The bar at the top splits your disk into categories such as Applications, Documents, iCloud Drive, Photos, Developer and System Data. Click the ⓘ next to a category to see the files behind it. Start with the biggest category rather than the one that looks most like clutter.
.dmg) and packages (.pkg) in Downloads are rarely needed once an app is installed./System, /Library/Apple or /private/var, your Photos library's internal folders, and files that live only in iCloud (deleting those removes them from every device and frees nothing on your Mac).There is no single free-space percentage that fits every workload. Check the requirement shown by Software Update or your installer, and leave room for your normal builds, downloads and swap. A cleanup candidate total is not a promise of that much new free space.
A storage warning usually arrives at an awkward moment: you are installing an update, copying a video, or trying to finish a project. Before cleaning anything, write down what needs space and whether the Mac can currently finish that task. The installer’s stated requirement is a better starting point than a generic rule about keeping a certain percentage free.
Next, record the available-space figure and the time you checked it. This gives you something concrete to compare after cleanup. Do not add together the Documents total, a folder scan and a cleaner’s headline: they can describe overlapping files. If Downloads contains your largest video, that video may already be counted inside Documents or another storage summary.
Those actions solve different problems. Deleting an unwanted file makes sense when you no longer need it. Moving an important project to another disk can help when you need the project but use it infrequently. Removing a downloaded copy through an app’s supported control can help when the original remains available elsewhere. Check what each command actually does before choosing it.
For example, suppose you find an old video project and its exported movie. Keeping the export does not necessarily preserve the editable project, source clips, fonts and linked audio. Open the project and identify its dependencies before archiving it. This is an illustrative decision, not a claim that every project can be reduced to one file.
A cloud-synced folder deserves the same care. A Delete command can propagate to other devices, while a supported Remove Download command may keep the cloud original. Read the service’s wording and confirm that the upload completed. A file’s familiar icon is not proof that an independent backup exists.
This sequence is slower than selecting every category, but it makes failures easier to understand. If an app loses an offline download after one targeted change, you know which change to investigate. A dozen simultaneous removals leave you guessing.
Moving a file to the Trash changes its location without necessarily returning its blocks to available storage. Storage settings may also need time to recalculate. On APFS, files can share underlying data, and snapshots can preserve older blocks. A logical file size, a scanner’s allocated-size estimate and newly available space therefore answer different questions.
Do not respond to a disappointing chart by deleting protected folders. First confirm that you emptied only the Trash items you intended, then compare the same available-space measurement again. If the difference remains unclear, investigate one known large item or the application that owns it. Avoid treating a category label as a folder that can be emptied.
Recurring growth needs a different approach from a one-time cleanup. Note which folder grows, what you were doing, and how quickly it changes. A browser profile, build output, backup, game download and virtual machine can all produce different patterns. Repeating the same cleanup every morning can hide the cause without solving it.
For a developer, check whether old build outputs or unused model downloads are accumulating. For a photo workflow, inspect imported originals and exported copies. For a household Mac, check separate user accounts with each owner’s permission. Do not remove another person’s files simply because a disk-wide view can measure them.
It can remove a constraint when a nearly full startup disk prevents normal work, but it is not a general performance repair. If plenty of space is available and an app remains slow, examine its workload, CPU activity and memory pressure. More aggressive deletion is not a diagnosis.
An external drive is useful for files you want to keep, provided the connection, capacity and backup arrangement fit the job. Work out whether you need archive storage or an active working disk. Moving the only copy of a project creates a new storage location, not a backup.
Stop when the original task works and your remaining choices are uncertain. Keep a short record of what moved, what was deleted and where the backup lives. A smaller, understandable cleanup is easier to maintain than a large unexplained number.
The Dashboard shows how much you can review, broken down by Junk, Build Caches, Model Vault, Large & Old, Duplicates and Idle Apps. Every list shows sizes before you choose anything, in-use caches are not preselected, and most removable items go to the Trash. If you change your mind, Put Back can restore supported recorded Trash moves without overwriting replacement files. Read any reported failures; permanent removal cannot be undone.