Disclosure: this article links to CleanMyMac, a commercial product developed by MacPaw. We may earn a commission from purchases made through those links. CleanMyMac is Apple-notarized and distributed through the MacPaw Store, Setapp, and the Mac App Store. The largest reclamations described here involve offloading rather than cleanup, and no utility performs them for you.
Key takeaways:
- On a 256GB machine, cleanup and offloading are different strategies. Cleanup buys weeks; offloading is what actually resolves it.
- Work in order of size, not ease. One large library outweighs every cache on the machine combined.
- The biggest wins are usually photo libraries, old device backups, and development toolchains — none of which are junk.
- Storage is not upgradeable on current models. The constraint is permanent, so plan around it rather than fighting it.
- Optimize Storage only works on content that exists in iCloud. It cannot help with purely local files.
- If the machine refills within a month, it is undersized for your workload. That is information, not failure.
Why a small SSD is a different problem
Standard cleanup advice assumes the disk filled through neglect and that removing accumulated junk restores a comfortable margin. On a 256GB machine that assumption frequently fails. The volume is not full because of neglect — it is full because the operating system, your applications, and one or two genuinely large libraries do not fit comfortably in the space available.
That changes the approach. Clearing caches on a machine with 400GB free is housekeeping. Doing it on a 256GB machine that is 95 percent full is a stopgap that lasts until the caches rebuild, which they will, to roughly the size they were.
So this article is organized by size of reclamation rather than by ease. The first three sections cover where the space actually is on a small machine. The last section covers the structural change that stops it happening again, which is the part most guides omit.
Before anything: find out where it went
Do not start deleting. On a constrained machine the distribution is usually lopsided, and one category typically accounts for more than everything else combined.
df -h /System/Volumes/Datadu -sh ~/* 2>/dev/null | sort -rh | head -15du -sh ~/Library/* 2>/dev/null | sort -rh | head -15Those three commands take under a minute and will usually identify the dominant category immediately. Check local snapshots too, since a machine whose backup drive is rarely connected can be holding a substantial amount:
tmutil listlocalsnapshots /If enumerating this by hand is not how you want to start, a Mac storage optimizer maps the same territory visually in one scan. The commands cost nothing and tell you the same thing, so run them at least once — on a small drive, knowing the distribution matters more than any individual deletion.
The large reclamations
These are ordered by typical size on a constrained machine. Work down the list and stop when you have enough.
Photo library
On most personal machines this is the largest single item, and it grows continuously. Two options: enable Optimize Storage so that full-resolution originals live in iCloud with local copies removed, or move the library to an external drive entirely.
Optimize Storage is less disruptive and requires no hardware, but it means originals need a connection to access. Moving the library externally frees more and costs you access when the drive is elsewhere. Neither is free, and which is right depends on how you work.
Old device backups
Backups made through Finder persist indefinitely, including backups of devices you no longer own. On a small drive a single forgotten backup can be a meaningful share of the volume. Review these through Finder’s backup management rather than deleting the directory directly.
Development toolchains and build artifacts
If you develop on this machine, this category frequently exceeds everything else. Build output, simulator data, package caches, and container images accumulate without limit and none of them clean up automatically. They also all regenerate, which makes them among the safest large reclamations available.
The specific paths and commands are covered in the companion cleanup guide rather than repeated here.
Local snapshots
A machine whose Time Machine destination has not been connected in months keeps local snapshots longer than it otherwise would. Reconnecting the backup drive and letting a backup complete allows macOS to thin them normally, which is safer than deleting them manually and restores your backup coverage at the same time.
Downloads and archives
Unglamorous and frequently substantial. Installer disk images, archives already extracted, and downloaded media accumulate in Downloads and are rarely reviewed. Sort the folder by size and the result is usually immediate.
The smaller reclamations
Worth doing after the above, not before. Individually modest, collectively meaningful on a constrained drive.
| Category | Typical scale on a small machine | Recurs? |
|---|---|---|
| User caches | Moderate; concentrated in browsers and Electron apps | Yes — rebuilds continuously |
| Leftovers from removed apps | Varies; large if creative or developer software was ever installed | No — one-time per app |
| Mail attachments and local archives | Moderate to large on long-standing accounts | Yes |
| Language files and unused resources | Small | No |
| Trash | Whatever you last deleted | Yes |
The second row is the one that pays on an older machine. Applications removed over the years leave support files, preferences, and caches in four separate locations, and searching for them manually requires knowing names you have long forgotten. This is where a CleanMyMac app uninstaller module saves real time — it enumerates residue by scanning the locations rather than by searching names. It is developed by MacPaw and Apple-notarized. The manual procedure is in the companion uninstallation guide and costs nothing.
The part that actually solves it
Everything above reclaims space that will, in most cases, be consumed again. On a 256GB machine used for anything data-heavy, cleanup is maintenance rather than a solution, and treating it as a solution is why people repeat this exercise every few weeks.
The structural options are limited and worth being clear about.
External storage. A compact external SSD connected when needed, holding libraries and archives that do not need to be available constantly. This is the most effective option for photo libraries, video projects, and virtual machines. The cost is having to carry and connect it.
Cloud storage with local copies removed. Effective for documents and photos, and requires no hardware. The cost is connectivity dependence and an ongoing subscription.
Changing what lives on the machine. Sometimes the answer is that a category of work does not belong on a 256GB laptop — large media projects, virtualization, multiple development toolchains. Moving that work elsewhere is more productive than repeatedly reclaiming space for it.
Storage is not upgradeable on current MacBook Air models, so the capacity is fixed for the life of the machine. A cleanup that lasts three weeks is not a failed cleanup. It is the machine telling you its capacity does not match your workload, and that information is more useful than the reclaimed gigabytes.
What this won’t fix
None of this creates capacity. If your actual data exceeds what the volume holds, the only remedies are storing less locally or storing it elsewhere — cleanup redistributes the shortfall rather than removing it.
It also will not help if the volume is full of data you need daily. The techniques here move or remove things you can live without; if everything on the machine is in active use, the honest conclusion is that the machine is undersized, and no article can change that.
Frequently asked questions
Is 256GB enough for a MacBook Air?
It depends on whether your largest libraries live locally. For writing, browsing, email, and streamed media it is comfortable indefinitely. For a growing photo library, video projects, virtual machines, or development work with multiple toolchains, it gets tight quickly and stays tight. The distinction is what kind of data accumulates, not how heavily you use the machine. In the second case no cleanup routine solves it permanently, and offloading becomes a standing arrangement rather than an occasional task.
How much space does macOS itself take?
The system occupies a substantial portion of a small drive before you install anything, and that footprint has grown with each major release. Beyond the system, macOS needs working room for virtual memory, temporary files, and update staging — space you cannot use even though no file occupies it at a given moment. On a 256GB volume the practical capacity available to you is meaningfully lower than the advertised figure, and planning around the advertised number causes most of the frustration.
Does Optimize Storage actually help?
In specific circumstances, yes; in others, not at all. It removes local copies of content that exists in iCloud, keeping recent items available and fetching older ones on demand. For a large iCloud-synced photo library or Documents folder it can reclaim a great deal. For purely local files it has nothing to work with. It also makes those files dependent on a connection, which is a real trade-off worth weighing before enabling it on a machine you use offline.
Can I upgrade the storage in a MacBook Air?
No — storage in current models is not user-upgradeable, and the configuration chosen at purchase is permanent. This is why offloading matters more on these machines than on any other Mac: the constraint is fixed and maintenance does not change it. The practical alternatives are external storage connected when needed, cloud storage with local copies removed, or a higher-capacity machine. Cleanup buys time within the constraint rather than removing it.
Should I move my Photos library to an external drive?
It is often the largest single reclamation available on a small drive, and it works well if you accept the trade-off: the library is unavailable when the drive is disconnected. Move it carefully — quit Photos, copy rather than move, verify the library opens from the new location, then remove the original. Keep a backup independent of the external drive, because a single copy on a portable disk is not a backup and portable disks fail.
Why does my MacBook Air keep filling up again?
Because cleanup addresses accumulation, not the rate at which data arrives. If your photo library grows steadily, your projects are local, or your work involves large downloads, the volume refills at whatever rate it filled before. A cleanup that reclaims a lot and lasts three weeks is telling you the machine is undersized for the workload, not that the cleanup failed. The productive response is structural — move a category of data off permanently rather than repeating the exercise.
