How to Free Up Space on a 256GB MacBook Safely (Without Deleting Your Work)
To free up space on a 256GB MacBook without deleting your work, offload inactive archives and heavy project assets to an external SSD or cloud storage, clear APFS local snapshots, purge developer caches (Xcode DerivedData and package managers), and remove duplicate files. Never delete active System Data or move active photo libraries manually without checksum verification.
A 256GB MacBook Air or Pro is an exceptional machine, but macOS itself, essential applications, and development tooling routinely consume 70–90 GB out of the box. Once your drive hits 90% capacity, macOS begins struggling to allocate temporary memory, triggering beachballs and sluggish performance.
The instinct for many users is to panic and start deleting older projects, personal photos, or video clips. That is a mistake. Here is the non-destructive playbook to safely liberate 40 to 90 GB while keeping all your files safe.
Step 1: Check True Storage vs. Purgeable Space
macOS often reports a disk as full even when tens of gigabytes are marked as Purgeable. Go to Apple Menu () → System Settings → General → Storage. Wait 10 seconds for macOS to index.
Notice how much space is consumed by "System Data" versus "Documents". Purgeable space is space macOS promises to free when an app demands it, but macOS frequently delays reclaiming it until crashes occur.
Step 2: Remove Hidden Local Snapshots
If you have Time Machine configured, macOS creates hidden local snapshots whenever your backup drive is disconnected. These snapshots freeze deleted files on your drive, preventing the space from being freed!
To view your active local snapshots, open Terminal.app and run:
If you see a list of dated snapshots (e.g., com.apple.TimeMachine.2026-10-24-142010.local), you can safely thin them with:
Step 3: Clear Developer Build Artifacts and Simulator Caches
If you write code or use Xcode, development caches are often the hidden culprit behind 30–60 GB of disk consumption.
- DerivedData: Every build accumulates temporary files in
~/Library/Developer/Xcode/DerivedData. Deleting the contents of this folder will only cause Xcode to rebuild fresh files next time, safely freeing 10–40 GB immediately. - Old Simulators: When Xcode updates, it leaves behind gigabytes of old simulator phone images. Clean them with:
~/Library/Developer/ parent directory, as it contains your customized settings and device profiles.
Step 4: Offload Cold Files (Don't Just Delete Them)
Instead of deleting past client archives, downloaded disk images, and 4K video footage, establish an orbit tier. Move files you haven't opened in 60+ days to a portable USB-C SSD (such as a Samsung T7 or Crucial X9) or your cloud drive.
Crucial Safety Rule: Never delete the local file until the external copy has been verified. Standard drag-and-drop can silently fail on hidden file permissions or network drops. This is why Nebula checks every byte of both copies to make sure they are 100% identical before moving the local file to the 7-day Trash safety net.
Step 5: Enforce a 20 GB Free-Space Floor
Your Mac requires breathing room for smooth daily multitasking. If your free space drops below 15 GB, your MacBook will struggle. Always keep at least 20 GB free as an inviolable buffer.
Automate Safe Offloading with Nebula
Nebula identifies files you haven't opened in months, streams them safely with SHA-256 validation to your external SSD, NAS, or Cloud, and lets you restore in one click.
Join the Mac Waitlist — Founding Offer ($9.99)