Fix 'Not Enough Disk Space' When Installing Steam Games on Mac (2026)

If you've clicked Install on a Steam game only to see a red banner telling you there isn't enough room, you're dealing with one of the most common — and most fixable — Mac storage headaches. The steam not enough disk space mac error shows up for a handful of different reasons: the reported free space in macOS is genuinely low, Steam's internal download cache has grown enormous, your install library folder is on a volume with tight limits, or APFS local snapshots are temporarily consuming space that macOS will reclaim later. This guide walks through every real fix in order of effort, so you can get back to gaming without blindly deleting files you'll regret losing.

Why Steam Can't See Free Space That Appears to Exist

macOS Sequoia and the upcoming Tahoe release both use APFS, which reports available space differently from older HFS+ volumes. Time Machine creates local APFS snapshots that live on the same drive and are counted against available space from Steam's perspective, even though macOS can purge them automatically when real disk pressure appears. The result: Disk Utility or the menu-bar indicator might show 20 GB free while Steam sees only 6 GB available for a new game.

On Apple Silicon Macs (M1 through M4) this is especially common because the internal SSD is typically 256 GB or 512 GB — generous for daily work but tight once a handful of AAA games land on it. Intel Macs with spinning hard drives or smaller SSDs face the same math.

Step 1: Check What Is Actually Consuming Your Space

Before deleting anything, get a real picture of where your gigabytes went. Open the Apple menu, choose System Settings → General → Storage. The breakdown chart is a starting point, but the "System Data" bucket is often misleadingly large. Read what is actually taking up space on your Mac for a deeper look at why that number is inflated.

For a more granular breakdown, open Terminal and run:

du -sh ~/Library/Caches/* | sort -rh | head -20

That single command surfaces the biggest per-app cache folders without touching anything. Common culprits alongside Steam itself include browser caches, Xcode derived data, and old iOS simulator runtimes.

How to Clear Steam's Download Cache on Mac

Steam maintains its own download cache independently of the macOS cache system. This cache can reach several gigabytes after downloading, patching, and re-downloading games. Clearing it is safe — Steam re-creates it automatically — and it sometimes resolves the disk-space error immediately.

1. Open the Steam app.
2. In the menu bar, choose Steam → Settings.
3. Click Downloads in the left sidebar.
4. Click Clear Download Cache and confirm.
5. Steam will restart and prompt you to log in again. After that, retry the install.

Steam's download cache lives inside its application support folder at ~/Library/Application Support/Steam/download. If the GUI clear doesn't free enough space, you can quit Steam completely and delete the contents of that folder manually — leave the folder itself in place.

Purge APFS Local Snapshots

Local Time Machine snapshots are the silent space consumer most users never think about. macOS creates them on a schedule even if you have no external backup drive connected. To list what exists:

tmutil listlocalsnapshots /

To delete all local snapshots at once:

tmutil deletelocalsnapshots /

This is safe. If a Time Machine backup to an external drive or Time Capsule is in progress, macOS will simply re-create local snapshots afterward. For a Mac that never uses Time Machine at all, you can disable local snapshots entirely:

sudo tmutil disablelocal

Note: on macOS Ventura and later, disablelocal has limited effect — Apple consolidated snapshot management into the Time Machine pane in System Settings.

Where Steam Stores Games and How to Add a New Library Folder

By default, Steam places all game content inside ~/Library/Application Support/Steam/steamapps. If you have an external SSD or a secondary internal volume, you can direct new installs there instead of filling your main drive.

To add a library folder: open Steam → Settings → Storage. Click the + button, choose a folder on your external drive, and set it as the default. All future installs will land there. You can also move existing games without re-downloading: right-click a game in your library, choose Properties → Local Files → Move Install Folder.

Common Space Hogs Near Your Steam Install

The table below shows the folders most likely to be large on a Mac that has been used for development or media work alongside gaming. Sizes are typical ranges — your machine may vary significantly.

Clearing Developer and App Caches That Compete With Steam

Developers who also game on the same Mac are especially likely to hit Steam's disk-space error because the build toolchains leave enormous residue behind. A few specific culprits:

Xcode DerivedData

Xcode stores compiled build products under ~/Library/Developer/Xcode/DerivedData. This folder can silently grow to 30–50 GB. Open Xcode, go to Settings → Locations, and click the arrow next to the Derived Data path to reveal it in Finder, then delete its contents. Or from Terminal:

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

iOS and visionOS Simulator Runtimes

Each simulator runtime you've downloaded consumes 5–10 GB. In Xcode 15 and later, manage them under Settings → Platforms. Delete any runtime you no longer target.

npm and Homebrew Caches

Node package caches accumulate under ~/.npm and can be cleared with:

npm cache clean --force

Homebrew's download cache lives at $(brew --cache) — typically ~/Library/Caches/Homebrew — and can be pruned with brew cleanup. For a broader look at reclaiming developer storage, see how to clean up node_modules on Mac.

Rust, Maven, and Other Build Caches

Rust's cargo registry sits at ~/.cargo/registry. Maven's local repository lives at ~/.m2/repository. Both can exceed 5–10 GB on an active machine. Delete subdirectories for old project versions you no longer need.

When Steam Still Complains After Freeing Space

If you've freed several gigabytes and Steam still throws the error, check whether Steam itself is confused about which volume the library folder targets. Quit Steam, then open ~/Library/Application Support/Steam/steamapps/libraryfolders.vdf in a text editor to confirm the path listed there actually exists on your current machine (especially relevant after a migration or when an external drive isn't mounted).

You can also verify and repair your Steam library from inside the app: Steam → Settings → Storage, then select the library and click the three-dot menu to choose Repair Library Folder.

If the Storage Management screen in System Settings shows a large "System Data" number that won't budge, a tool like Crumb can audit all of these locations at once and show exactly what's safe to remove before you delete anything.

Keeping Space Under Control Going Forward

A few habits prevent the error from recurring:

• Uninstall games you've finished from Steam's Library list (right-click → Manage → Uninstall). Steam keeps your save data in the cloud for most titles.
• Enable Storage Optimization in System Settings → General → Storage so macOS automatically removes watched TV content and old iOS backups.
• Run brew cleanup monthly if you use Homebrew — old formula versions accumulate quickly.
• Schedule a quarterly scan of ~/Library/Caches and your DerivedData folder to prevent build artifacts from creeping back up.

Steam games are only getting larger — open-world titles now routinely demand 100–150 GB. Building the habit of auditing your storage before installs, rather than after the error appears, keeps your gaming library expanding without painful triage sessions.