Clear System Data on a 256GB MacBook Air (2026 Guide)

If you own a 256GB MacBook Air, you already know the drill: a macOS update drops, a few large projects land, and suddenly the "Storage Full" notification appears with your disk showing a massive grey "System Data" block. This guide is your emergency checklist to clear system data on a 256GB MacBook Air — starting with the reclaims that return the most space first, so you can breathe again as quickly as possible.

Why "System Data" Gets So Big on Small-SSD Macs

macOS groups several categories under the System Data label you see in System Settings › General › Storage:

• User and system caches (~/Library/Caches, /Library/Caches)
• Log files (~/Library/Logs, /Library/Logs, /var/log)
• Temporary files in /private/var/folders
• APFS purgeable space (local Time Machine snapshots, iCloud placeholders)
• Developer derived data and iOS simulator runtimes

On a 512GB or 1TB drive, System Data quietly grows for years without hitting a wall. On a 256GB drive, even moderate use fills it up fast — especially after installing Xcode, keeping multiple browser profiles, or letting iOS device backups accumulate.

Before You Start: Check What's Actually Taking Space

Open System Settings › General › Storage and wait a few seconds for macOS to calculate each category. Note the sizes of System Data, Applications, and any media. This tells you where to focus first.

For a faster, file-level view, open Terminal and run:

du -sh ~/Library/Caches ~/Library/Logs ~/Library/Developer ~/Downloads

The numbers returned tell you which directories are your biggest offenders before you delete anything.

Emergency Checklist: Biggest Reclaims First

1. Delete Xcode DerivedData (Often 5–40 GB)

If you have ever installed Xcode, the DerivedData folder holds build artefacts that Xcode regenerates on demand. It is safe to delete entirely.

rm -rf ~/Library/Developer/Xcode/DerivedData

Also remove stale iOS Simulator runtimes you no longer need. In Xcode, go to Settings › Platforms and delete any simulator runtime that is outdated. From Terminal you can remove all unavailable simulators:

xcrun simctl delete unavailable

Simulator data lives in ~/Library/Developer/CoreSimulator and the runtime images themselves can be several gigabytes each.

2. Clear User Caches (1–10 GB, usually safe)

Applications write temporary data to ~/Library/Caches. Most of it rebuilds automatically on next launch. You can delete the contents of that folder — not the folder itself — while all apps are closed:

rm -rf ~/Library/Caches/*

Important: Close every app before running this. Some caches (notably for browsers and creative apps) can be large — several gigabytes — and are entirely safe to remove. Apps will simply rebuild what they need.

Do not touch /System/Library/Caches — that is owned by macOS and should be left alone.

3. Remove iOS Device Backups (2–20 GB per backup)

If you have ever backed up an iPhone or iPad to your Mac via Finder, those backups sit in:

~/Library/Application Support/MobileSync/Backup

Open Finder › Locations › [your iPhone], then click Manage Backups to delete old ones safely. Or delete backup folders directly from that path once you have verified you have a current iCloud backup for your device.

4. Delete Log Files (100 MB – 2 GB)

Logs are human-readable records of app and system activity. They are safe to delete if you are not actively debugging a problem.

rm -rf ~/Library/Logs/*

System-level logs under /Library/Logs require sudo and are generally smaller, but you can clear them too:

sudo rm -rf /Library/Logs/*

5. Purge Homebrew Download Cache (500 MB – 5 GB)

If you use Homebrew, old package downloads accumulate in its cache. This command removes anything older than the default 120-day window:

brew cleanup

To remove everything regardless of age:

brew cleanup --prune=all

6. Empty the Trash and Downloads Folder

This one is obvious but easy to forget when you are panicking about disk space. Right-click the Trash in the Dock and choose Empty Trash. Then open ~/Downloads and delete anything you no longer need — downloaded disk images (.dmg files), old installers, and ZIP archives are common culprits.

7. Remove Large Language Model Files (If Applicable)

Local AI tools like Ollama store model weights in ~/.ollama/models. A single large model can occupy 4–8 GB. If you have stopped using a model, remove it:

ollama rm <model-name>

Or browse the folder directly and delete the weight files you no longer need.

8. Delete Old Time Machine Local Snapshots

macOS takes local Time Machine snapshots even when your backup drive is not connected. To list them:

tmutil listlocalsnapshots /

To delete a specific snapshot (replace the date string with one from the list above):

tmutil deletelocalsnapshots 2025-12-01-120000

macOS marks snapshot space as "purgeable" and reclaims it automatically under pressure, but on a 256GB drive you may want to reclaim it manually right now rather than waiting.

What You Should NOT Delete

The Faster Way: Let a Tool Do It

The manual steps above work, but they take time and require knowing which paths are safe. Crumb is a native macOS menu-bar utility built specifically for this workflow. Its one-click Clean scans system caches, user caches, logs, temp files, and APFS purgeable space — then shows you exactly what it found and how much space each category occupies before you confirm anything.

The feature that genuinely earns its keep on a cramped 256GB drive is the "Is this safe to delete?" AI check: point it at any unfamiliar folder and it explains what the folder is, which app owns it, and the actual risk of removing it. That means you can confidently clean folders that the manual steps above do not even mention, without guessing. You can download Crumb and run one free cleanup to see how much it finds.

Ongoing Habits to Keep a 256GB Drive Livable

• Offload iCloud content. In System Settings › Apple ID › iCloud, enable "Optimize Mac Storage." This keeps local copies only of recently opened files and streams the rest on demand.
• Use streaming for media. Avoid downloading large video or music libraries locally when Apple Music and streaming services work perfectly on-demand.
• Run brew cleanup monthly. Package managers accumulate quietly. A calendar reminder costs nothing.
• Check Storage after every major Xcode update. Each Xcode release installs new simulator runtimes; old ones are not automatically deleted.
• Move large project archives to external storage. A USB-C SSD or NAS keeps project files accessible without occupying precious internal space.

Quick-Reference: Expected Space Recovery

Conclusion

A 256GB MacBook Air can stay perfectly usable with the right cleaning habits. The single biggest lever is almost always developer data — Xcode's DerivedData and simulator runtimes — followed by accumulated caches and forgotten iOS backups. Work through the checklist above in order, and you will typically recover 10–50 GB without touching anything important. Set a monthly reminder to run brew cleanup and check your Downloads folder, and you will rarely hit the wall again.