Fix 'Not Enough Disk Space' on Mac: 2026 Guide

You usually notice the problem at the worst possible moment. A macOS update won't install. Xcode refuses to build. Final Cut export fails near the end. AirDrop stalls. Finder says there isn't enough room, even though you already deleted a few files and emptied a folder or two.

On a Mac, not enough disk space rarely means only one thing. Sometimes the drive is completely packed. Sometimes the pressure is coming from app caches, old installers, iPhone backups, local snapshots, or sync tools that stage data before they move it anywhere. And sometimes the primary mistake is waiting until the warning appears, because by then macOS has already lost the breathing room it likes to have.

This is the workflow that works. Start with quick triage. Then check for a commonly overlooked category: app leftovers in ~/Library. If you're a power user, inspect snapshots, caches, and developer tooling. After that, put a simple routine in place so you don't end up back here next month.

Table of Contents

• Why "Not Enough Disk Space" Is More Than an Annoyance
• First Response Diagnose and Reclaim Space Fast
  • Start with what macOS already knows
  • The fastest safe wins
  • What to remove before you uninstall apps
• Find and Remove Hidden App Leftovers
  • Why dragging an app to Trash isn't enough
  • What you can remove and what you should leave alone
• Advanced Techniques for Power Users
  • Check the real disk picture in Terminal
  • Time Machine local snapshots
  • Cloud sync caches and staging space
  • Other stubborn cases worth checking
• Building a Proactive Storage Maintenance Habit
  • For casual users
  • For developers
  • For admins managing multiple Macs
• Stay in Control of Your Mac's Storage

Why "Not Enough Disk Space" Is More Than an Annoyance

You notice it in the middle of real work. A macOS update refuses to install. Final Cut export fails near the end. Xcode starts throwing strange errors. Mail stops downloading attachments. The warning says storage is full, but the true problem is that macOS has run out of working room.

A Mac needs free space for swap, temporary files, app updates, indexing, caches, and all the short-lived data created while you work. Once that cushion gets too small, performance drops and failures start looking unrelated. Apps hang. Installs stall. Large file operations die halfway through. On a nearly full disk, macOS can feel unstable even when the hardware is fine.

The fix is not random deletion.

What works is a tiered approach based on how the Mac is used. Casual users usually lose space to media, Downloads, Messages attachments, and old backups. Developers burn through storage with simulators, containers, package caches, and multiple toolchains. Admins often deal with log growth, sync clients, shared installers, and stale support files spread across user accounts. If you want a broader framework for MacBook storage management by usage pattern, start there and then apply the cleanup method that fits your machine.

One category gets missed all the time: app leftovers. Dragging an app to Trash removes the main bundle, but many apps leave behind support files, caches, containers, logs, helper data, and updater components in Library folders. Some of that data is harmless and small. Some of it grows for months. I see this constantly on Macs that look clean in Applications but are still missing tens of gigabytes.

A few common myths make the problem worse. Emptying Trash helps, but it rarely solves serious pressure by itself. Buying more iCloud storage does not guarantee more local free space, because many apps still keep local copies, caches, and staging data. "System Data" is not magic either. It is often a mix of understandable categories that just are not obvious at first glance.

The right workflow is straightforward:

• Casual users: reclaim space from obvious large files first, then check for leftover app data.
• Developers: audit build artifacts, simulators, containers, package managers, and local snapshots.
• Admins and multi-user Macs: check logs, shared caches, sync tools, installer debris, and old account data.

The trade-off is simple. Fast cleanup gets you breathing room. Careful cleanup keeps the Mac stable and avoids deleting files that apps or macOS will just rebuild badly. The goal is not to remove everything you can find. The goal is to remove the right data, in the right order, with enough understanding of why it exists.

First Response Diagnose and Reclaim Space Fast

When a Mac throws a not enough disk space error, the first job is to stop guessing. You want a quick view of what category is consuming space, then you want the safest high-yield actions first.

Start with what macOS already knows

Open System Settings > General > Storage. Let it finish calculating. Don't click around too quickly, because the first numbers can be misleading while macOS is still indexing categories.

What I'm looking for here isn't perfect accuracy. I'm looking for shape. Is the pressure coming from Applications, Documents, System Data, Mail, Messages, or Photos? That tells you where to work next.

Then open Finder and check these locations in this order:

1. Trash
2. Downloads
3. Applications
4. Movies
5. Desktop
6. Any external-project folder you use for video, design, or development

Vendor guidance for disk-space errors recommends a simple first-pass method: run built-in cleanup, then sort installed apps by size and remove non-essential large software, because that usually hits bigger space consumers than temporary-file cleanup alone, as noted in Dell's disk cleanup guidance. The macOS equivalent is the same mindset. Hunt the biggest objects first.

If you want a more structured walkthrough of Apple's built-in tools, this guide to MacBook storage management is a good companion while you're working through System Settings.

The fastest safe wins

These are the actions that usually free space fastest without creating fresh problems.

• Empty Trash for real: A lot of people move files to Trash and assume the job is done. It isn't. Until you empty it, the space usually isn't back.
• Purge Downloads: .dmg installers, ZIP archives, duplicate PDFs, and old exports pile up here. Old disk images are especially common on Macs because app installs often start with a download and a drag-to-Applications step.
• Sort Applications by size: If you've got GarageBand content, old games, creative suites, or unused developer tools sitting there, you'll usually get more space back from one uninstall than from cleaning a hundred temp files.
• Search for large files in Finder: Use Finder search, choose This Mac, then filter by File Size. Look for giant video exports, .ipsw files, VM images, duplicate archives, and abandoned project folders.

Delete installers and exports with confidence. Be cautious with anything that looks like a library, a bundle, or a folder inside ~/Library, because that's where cleanup gets less forgiving.

A quick Finder trick that works well in a panic: switch to list view, sort by size, and inspect obvious dead weight before you touch anything system-related. Large movie files, stale project exports, and downloaded installers are usually low-risk deletions.

A short video can help if you prefer seeing the process rather than reading it:

<iframe width="100%" style="aspect-ratio: 16 / 9;" src="https://www.youtube.com/embed/phFdXb9-xEQ" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>

What to remove before you uninstall apps

Before you start yanking apps out of /Applications, check for the easy, boring clutter around them.

Item	Why it matters	Safe action
Downloaded .dmg files	They often remain after the app is installed	Delete if you don't need the installer
ZIP archives	They duplicate extracted content	Delete once extracted and verified
Old exports	Video, audio, and design apps generate huge outputs	Move off the Mac or delete
iPhone or iPad backups	Local backups can be surprisingly large	Review in Finder or device-management settings
Duplicate media	Common after imports and edits	Consolidate or archive

What usually doesn't work is pecking away at tiny temporary files while a huge app bundle or project cache is eating most of the drive. If you're still getting the not enough disk space warning after the steps above, the next place to look is the category people skip most often: leftovers from apps you've already removed.

Find and Remove Hidden App Leftovers

Dragging an app into Trash feels complete. On macOS, it often isn't. The app bundle is gone, but related files can still sit in ~/Library for months or years.

Why dragging an app to Trash isn't enough

Many apps store data outside the app itself. That's normal macOS behavior. Preferences, caches, containers, logs, saved application state, support files, helper data, and updater remnants often live in separate library folders.

The result is familiar. You remove the app, but the Mac doesn't feel any lighter. That's because the actual footprint wasn't only the .app file.

Some of the most common leftover locations are:

• ~/Library/Application Support for app databases, assets, and support files
• ~/Library/Caches for downloaded assets and temporary working data
• ~/Library/Containers and ~/Library/Group Containers for sandboxed apps
• ~/Library/Preferences for settings files
• ~/Library/Logs and ~/Library/Saved Application State for operational leftovers

If you don't normally browse hidden files, this walkthrough on how to show hidden files on Mac makes those library folders easier to inspect safely.

App leftovers are one of the most underdiagnosed sources of Mac storage waste because they don't show up as an obvious app you can simply uninstall.

What you can remove and what you should leave alone

Manual cleanup works, but only when you're disciplined. The mistake people make is deleting every folder with a vaguely familiar app name. That can break settings for an app you still use, wipe wanted documents inside a container, or remove shared support files that more than one app expects.

A safer mental model is this:

• Good candidates: support files for apps you've fully removed, stale caches, old logs, abandoned updater data
• Use caution: containers, group containers, and anything with active app data
• Hands off unless you know exactly why: broad system folders, Apple-created items, and anything you can't confidently identify

I usually treat leftovers in two passes. First, identify apps I know are gone. Second, confirm the remaining files are tied to those apps and not still in use by something current. That takes longer than dragging folders to Trash, but it avoids creating new troubleshooting sessions.

A lot of "cleaner" apps fail here because they treat everything as disposable junk. On a Mac, context matters. A cache may be harmless to delete. A container may include something you care about. That's why app leftovers deserve their own cleanup pass, not a blind sweep.

Advanced Techniques for Power Users

If you've already done the obvious cleanup and your Mac still claims it doesn't have enough room, it's time to stop relying on category summaries. Terminal, local snapshots, and sync caches clarify the cases that Finder doesn't make obvious.

Check the real disk picture in Terminal

Start with two commands:

df -h
du -sh ~/* 2>/dev/null

df -h shows filesystem-level free space. du -sh ~/* gives you a quick size view of top-level folders in your home directory. If Documents looks modest but Library is huge, you've already narrowed the hunt.

From there, drill deeper:

du -sh ~/Library/* 2>/dev/null | sort -h

This won't explain everything, but it will reveal patterns. Giant caches. Bloated mobile backups. Massive container folders. Old simulator data. It's far more useful than clicking around Finder blindly.

For cache-specific cleanup patterns, this guide on how to clear app cache on Mac is useful when ~/Library/Caches turns out to be the hotspot.

Time Machine local snapshots

APFS snapshots are one of the classic "where did my space go?" causes on modern Macs. Time Machine can keep local snapshots that don't always feel visible from normal browsing, especially when you're trying to reconcile Finder's view with actual free space pressure.

List local snapshots with:

tmutil listlocalsnapshots /

If you need to remove a specific one:

sudo tmutil deletelocalsnapshots YYYY-MM-DD-HHMMSS

Replace the timestamp with the snapshot identifier from the first command.

I treat this as a scalpel, not routine housekeeping. Snapshots are useful. They exist for a reason. But when a Mac is cornered and you're trying to finish an install or export, checking snapshots can explain stubborn storage pressure that simple file deletion didn't solve.

If the drive still looks full after you deleted large files, check snapshots before you assume macOS is lying.

Cloud sync caches and staging space

A lot of users think "I'm copying it to the cloud, so local storage shouldn't matter." That's not how many sync tools behave. They often need local working room first.

Google Drive users have hit not enough disk space errors while copying into shared folders because the sync client stages the transfer in local cache before it lands in the synced destination, as discussed in this Google Drive support thread. The same pattern shows up in other sync-heavy workflows.

That changes the fix. The destination may be remote, but the bottleneck is local staging data. If a sync client is the trigger, check:

• Offline availability settings: too much content pinned locally
• Cache growth: large queues, failed transfers, or staged uploads
• Duplicate local mirrors: one folder in your home directory, another inside the sync app structure
• External-drive assumptions: the app may still use the internal disk for temporary work

Other stubborn cases worth checking

Not every not enough disk space alert is purely about capacity. Microsoft support notes that some "not enough disk space" cases can come from system or driver issues rather than raw storage, and also points out a filesystem limit where FAT32 can't copy a single file larger than 4 GB, even if the drive appears to have space, according to Microsoft's troubleshooting guidance. On a Mac, that usually matters when you're writing to an external drive.

For power users, the short list of non-obvious checks looks like this:

• External drive format: FAT32 is still a trap for large-file transfers
• Developer debris: old Xcode archives, simulators, Homebrew cache, Docker images, VM disks
• Swap pressure: when memory is tight, disk activity can spike and make the machine feel storage-bound
• Stuck caches or logs: some apps leave behind huge transient data after crashes or failed updates

This is the point where broad "just clean your Mac" advice stops being useful. You need to identify the exact class of space consumer, then remove it deliberately.

Building a Proactive Storage Maintenance Habit

The Macs that stay out of trouble are not the ones that get a frantic cleanup once a year. They are the ones with a little headroom and a routine that matches how they are used. That routine should look different for a casual user, a developer, and an admin, because the junk they create is different.

For casual users

A typical personal Mac fills up through slow accumulation. Downloads piles up. Photos libraries grow. Creative exports sit around long after they were shared. App leftovers also add up over time, especially on Macs where apps get installed for one task and forgotten.

A simple habit works:

• Check Downloads on a schedule: installers, ZIP files, duplicate PDFs, and attachments rarely need to stay there forever.
• Review large libraries: Photos, Music, iMovie, and other media apps can consume space unnoticed for months.
• Empty Trash with intent: deleting a file is not the same as reclaiming the space.
• Look at Storage settings before the Mac is full: category changes usually show up before the warning does.

Weekly is fine for heavy use. Monthly is fine for lighter use. The exact timing matters less than consistency.

For developers

Developer Macs need a project-closeout habit. Otherwise, old toolchains and test environments linger long after the work is done, and they rarely live in obvious folders.

These are the usual storage hogs:

Area	Typical waste
Xcode	Derived data, archives, simulators, device support files
Docker	Old images, stopped containers, unused volumes
Homebrew and package managers	Cached downloads and old dependencies
Virtual machines	Large disk images that linger after a project ends
Local datasets	Test fixtures, exports, and duplicate snapshots

I use a simple rule here. If a project is archived, shipped, or abandoned, clean the environment attached to it the same day. That includes build products, containers, VM disks, and app support files tied to tools you no longer use. This is also where app leftovers matter more than many developers expect. Removing an IDE, database tool, or menu bar utility often leaves caches, logs, containers, and support data behind in ~/Library.

For admins managing multiple Macs

Admins need policy, not heroics. If users regularly hit low-space alerts, the issue is usually recurring workflow pressure, weak cleanup habits, or software that keeps local working data longer than anyone realized.

Resilio's documentation makes the reserve-space point clearly. Its agent can stop activity before a disk is fully packed, based on a free-space threshold, as explained in Resilio's free-space threshold guidance. Many sync and backup tools behave this way for good reason. They need breathing room for temp files, staging, indexing, and recovery.

That changes how admins should respond:

• Set a minimum free-space expectation: users should know the disk is not supposed to run to the edge.
• Standardize uninstall practice: removing an app should include its leftover support data when appropriate.
• Review high-churn apps: sync clients, media tools, and design apps often create hidden local growth.
• Build cleanup into support workflows: storage review should be part of offboarding, device refresh, and project rollover.

Buying larger drives helps, but it does not fix waste. Good storage hygiene comes from matching the cleanup routine to the kind of Mac and the kind of work being done.

Stay in Control of Your Mac's Storage

A full Mac doesn't need random deletion. It needs order.

The workflow is straightforward when you stop treating every byte the same. First, reclaim breathing room with the safest wins: Trash, Downloads, large files, and oversized apps. Next, deal with the storage category most Mac users overlook, which is leftover support data from apps that are long gone. If the problem still doesn't make sense, inspect the advanced layers: snapshots, caches, sync staging, developer artifacts, and external-drive format issues. Then turn all of that into a routine that fits the kind of user you are.

That's the shift. You move from reacting to the not enough disk space alert to understanding why it happened.

A well-managed Mac feels different. Updates install without drama. Exports finish. Builds complete. Finder stops throwing warnings at the worst possible time. And when space starts tightening again, you know exactly where to look first.

---

If you regularly install and remove apps, Crufti is a focused way to clean up the leftovers that macOS app removal often leaves behind. It scans eleven ~/Library locations, shows related files with size details and match confidence, moves selected items to Trash for easy undo, and keeps everything local on your Mac with zero telemetry.