Your MacBook is out of storage. Here's the honest fix.

You know the notification. "Your disk is almost full." It shows up at the worst possible moment — mid-export, mid-import, the second you try to update macOS — and it never shows up when you have time to deal with it.

If you're reading this, you've probably already tried the obvious things: emptied the Trash, deleted a few old downloads, maybe uninstalled an app you never used. You bought yourself a day. Then the warning came back.

This is the honest, complete version of the fix — everything that actually reclaims space on a Mac, ranked by how much it gives you and how long it lasts. We'll do the free cleanup first, because you should. Then we'll talk about why the cleanup is a treadmill, and the one change that gets you off it.

First: find out what's actually eating the disk

Before you delete anything, look at the map. On macOS, open the Apple menu → System Settings → General → Storage. You'll get a colored bar and a list of categories — Applications, Documents, System Data, Photos, and the one that surprises everyone, "System Data."

Give it a minute to calculate. The number that matters isn't the total — it's which category is biggest, because that tells you where the space actually went. On most working MacBooks the culprit is one of four things:

• Photos & video libraries synced locally (often 100–400 GB)
• A creative app's cache or scratch — Final Cut, Logic, Lightroom, Xcode (frequently 50–200 GB of "System Data")
• Downloads and old project folders you forgot about
• Local backups and snapshots macOS keeps quietly in the background

Sort your Documents by size in Finder (View → as List, then click the Size column) and you'll usually find the top ten items account for more than half your used space. Storage problems are almost never a thousand small files. They're five big ones.

The cleanup, ranked by how much it gives back

1. Empty the caches the big apps hide (biggest quick win)

The single largest recoverable chunk on a creative Mac is almost always an application cache, and macOS files it under the mysterious "System Data," so you never see it in an obvious folder.

• Xcode hoards DerivedData and old device-support files. A working iOS developer routinely finds 40–80 GB in ~/Library/Developer/Xcode/. Deleting DerivedData is safe — it regenerates.
• Adobe Lightroom and Photoshop keep multi-gigabyte Camera Raw caches.
• Final Cut Pro and DaVinci Resolve generate render files and optimized media that can dwarf the original footage. Deleting generated render files inside a library is safe; the app rebuilds them on demand.
• Logic Pro and other DAWs bounce huge temp files and freeze files.

This is the one category where you can reclaim 50–150 GB in ten minutes without losing anything you can't regenerate.

2. Turn on Optimize Storage — then understand its catch

Apple's built-in Optimize Storage (in that same Storage settings pane) will offload full-resolution Photos and old email attachments to iCloud, keeping only lightweight previews on the Mac. It genuinely helps, and you should turn it on.

The catch nobody mentions: it only offloads what iCloud is willing to hold, and it silently re-downloads the moment you open a project that needs the full file. So on a Mac you actually work on — where you open those big libraries every day — Optimize Storage gives you the number back in settings but not on the disk. It's real relief for a photo hobbyist and near-zero relief for a working editor.

3. Find and kill duplicate and forgotten large files

Downloads folder, Desktop, and old ~/Movies exports are where terabytes go to be forgotten. Sort each by size. That "final_v3_ACTUAL.mov" from a job you delivered in March is 40 GB and you will never open it again — but you also can't quite bring yourself to delete it, which is exactly the problem we'll come back to.

4. Remove local snapshots and old backups

macOS keeps local Time Machine snapshots on the internal disk between backups. They're supposed to purge automatically under pressure, but a disk that's been full for weeks often has stale ones. Making sure your Time Machine drive is connected and current lets macOS release them.

Every step above is worth doing. Together they can hand a full MacBook back 100–200 GB. And if your storage problem is a one-time mess, that's the end of it — you're done, close the tab.

The part where the cleanup stops working

Here's the uncomfortable pattern. If cleaning up bought you a week and the warning came back, you don't have a mess problem. You have a capacity problem, and no amount of deleting fixes a capacity problem.

The reason is arithmetic. Storage requirements have grown faster than the SSDs Apple ships:

• A Sony FX3 shooting 4K in ProRes generates roughly 800 MB per minute — a single wedding day is over a terabyte.
• An iPhone 16 Pro filming ProRes hits 80 GB in a ten-minute session.
• A Logic Pro session with sample libraries and stems runs 20–50 GB per song.
• An Xcode project with a couple of simulators and DerivedData sits at 60 GB and grows every build.

The MacBook on your desk shipped with 512 GB or 1 TB. Two projects and it's full again. You are not messy. You are running a professional workload on a disk sized for a consumer one — and Apple charges $200 to $400 per storage tier to make it bigger, soldered in, non-upgradeable, at the moment of purchase and never again.

So people reach for the obvious answer: an external drive. And then they hit the second wall.

"Just use an external SSD" — and why it usually disappoints

The advice is right. The execution is where it falls apart, because most portable SSDs are built to win a 30-second benchmark, not to hold a working library.

A typical bus-powered USB-C drive sustains 1,000 MB/s for about half a minute, heats up, then thermal-throttles down to 200–400 MB/s for the rest of the transfer. Plug your Lightroom catalog or Final Cut library onto one of those and everything you do — scrubbing a timeline, culling photos, loading samples — happens at the throttled speed, not the advertised one. It feels like working over a slow network drive, because effectively you are.

That's why the external-drive advice so often ends with people dragging the library back onto the internal SSD and returning to square one. The drive was never the problem. The chassis was.

The fix that ends the treadmill

The real solution is boring and permanent: move your active working libraries off the internal SSD onto external storage that is genuinely as fast as internal storage — so there's no penalty for living there — and keep the MacBook's built-in disk nearly empty, holding only the OS and apps.

That's the entire reason we built Case X. It runs USB4 + NVMe and sustains 3,500 MB/s — the same class of speed as your MacBook's internal drive — through a 90-minute session, not a 30-second benchmark, because the whole aerospace-grade aluminum body is the heatsink. There's no throttle cliff to fall off. A four-stream 4K timeline plays back on it without dropping frames. A Logic session with the sample library on it loads instantly. Working off Case X feels identical to working off the internal disk, which is the whole point — if it feels the same, you'll actually keep your projects there.

And because it attaches to the MacBook instead of dangling off a cable, it lives on the machine as a permanent extension rather than a dongle you unplug and lose.

The move that fixes "my MacBook is always full" isn't a bigger internal disk or a faster cleanup routine. It's keeping the internal disk empty on purpose and doing your real work on external storage that's fast enough that you never notice it's external.

Once your workflow looks like that, the "your disk is almost full" warning simply stops appearing — not because you got disciplined about deleting things, but because your working set no longer lives on the small, expensive, un-upgradeable disk. It lives on the drive you sized for the job.

What we'd actually do, by workload

We wrote the long version of each of these, but here's the short one:

• Photographers & video editors — keep the catalog/library on Case X, scratch and cache too. The internal SSD holds Lightroom/Final Cut and nothing else. The full editor workflow →
• Music producers — sample libraries and project folders on the drive; the internal disk stops being the bottleneck on load times. The producer setup →
• Developers & AI builders — DerivedData, containers, model weights, and datasets on external; the laptop stays lean and fast. How builders run it →

The pattern is identical across all three: one fast drive holds the working set, the internal SSD stays mostly empty, and storage stops being something you think about. That's the version of "fixing" a full MacBook that doesn't come back in a week.

See Case X → · Configure yours →