How to Free Up Space for Games on a 256GB MacBook (2026 Guide)

If you want to free up space for games on a MacBook, a 256 GB drive fills faster than you'd expect — especially once macOS system data, Xcode caches, and a handful of creative apps settle in. Modern games like Baldur's Gate 3 demand 120 GB on their own, and even lighter titles from the App Store routinely land at 15–40 GB each. This guide walks through exactly where that storage goes and how to reclaim enough headroom to install and actually play what you want, without nuking anything important.

Where Does Your 256 GB Actually Go?

Before deleting anything, it helps to see the landscape. macOS Sequoia and Tahoe both surface a breakdown under Apple menu > System Settings > General > Storage, but the categories (Applications, System Data, Documents) are broad. The table below shows the real culprits that accumulate silently on a developer or power-user machine.

Step-by-Step: How to Clear the Biggest Space Wasters

Work through these in order — the first few steps alone often recover 30–80 GB on a machine that has been in daily use for more than a year.

1. Purge Xcode Derived Data and Old Simulators

Derived Data is rebuilt automatically the next time you open a project in Xcode, so it is always safe to delete. Open Terminal and run:

1. Check the current size first: du -sh ~/Library/Developer/Xcode/DerivedData
2. Delete it: rm -rf ~/Library/Developer/Xcode/DerivedData
3. Remove old device support files you no longer need: open Xcode, go to Window > Devices and Simulators, then delete simulators for iOS versions you don't target.
4. Delete orphaned Simulator runtimes via the command line: xcrun simctl delete unavailable

If Xcode caches are ballooning regularly, see why Xcode takes up so much space for a deeper explanation of every folder involved.

2. Clean Homebrew's Download Cache

Every time Homebrew downloads a package it stashes a compressed copy in its cache directory. These accumulate invisibly. Run:

1. brew cleanup --prune=all — removes all cached downloads and outdated formula versions.
2. Confirm the size recovered: du -sh $(brew --cache)

3. Delete node_modules You No Longer Need

Old JavaScript projects are notorious for carrying enormous node_modules trees that are never touched again. Find them all with:

1. find ~ -name "node_modules" -maxdepth 5 -type d 2>/dev/null
2. For any project you're no longer actively working on, delete its node_modules folder. Running npm install or pnpm install will regenerate it in seconds if you ever return to the project.

For a more structured approach, the guide on cleaning up node_modules on Mac covers safe bulk removal strategies.

4. Clear Rust and Java Build Artifacts

Rust's Cargo keeps every downloaded crate in ~/.cargo/registry and every compiled artifact in a per-project target/ directory. Check the sizes with:

• du -sh ~/.cargo/registry
• find ~ -maxdepth 5 -name "target" -type d 2>/dev/null | xargs du -sh 2>/dev/null

You can safely delete individual project target/ directories (they are always rebuilt by cargo build) and trim the registry cache with cargo cache --autoclean if you have the cargo-cache crate installed.

For Maven projects, ~/.m2/repository holds every downloaded JAR. You can prune it manually or run mvn dependency:purge-local-repository against specific projects to remove only their artifacts.

Manage App Caches in ~/Library/Caches

Browser caches, Slack's file cache, and dozens of other apps park data in ~/Library/Caches. The folder is safe to clear while the relevant apps are closed — each app regenerates its own cache on next launch. You can inspect individual subfolder sizes with:

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

Delete only the subfolders belonging to apps you recognize. Avoid removing com.apple.* caches while system processes might be using them; instead, quit those apps first or target specific third-party caches. A tool like Crumb can audit all of these at once and show what is safe to delete before you remove anything.

Move or Delete iOS and iPadOS Backups

Local iPhone backups live at ~/Library/Application Support/MobileSync/Backup and can reach 50 GB on a device with a lot of photos. If you use iCloud Backup as your primary backup method, local backups are redundant. To remove them:

1. Open Finder, press Shift-Command-G, and paste ~/Library/Application Support/MobileSync/Backup.
2. Inspect the dated folders — each one is a full device backup.
3. Delete backup folders for devices you no longer own, or all of them if iCloud Backup is enabled on your current devices.

Games Themselves: Choose What Stays Installed

On a 256 GB drive, you simply cannot keep a large library of installed games at once. The practical approach is to treat your MacBook like a console with limited cartridge slots:

• Steam: Right-click any game in your library and choose Manage > Uninstall. Your save data is stored in ~/Library/Application Support/Steam/userdata and is not deleted with the game. You can re-download anytime.
• App Store games: Delete them from Applications as normal. Re-download is free. Save data syncs via iCloud if the game supports Game Center.
• Epic Games Launcher: Use the library view to uninstall titles while preserving save data, which the launcher manages separately.

Keep only the one or two titles you're actively playing installed, then rotate. A 60 GB game uninstalled immediately frees 60 GB — the single largest lever you have on a 256 GB drive.

Enable Optimized Storage (with Caveats)

macOS includes a built-in Optimized Storage feature under System Settings > General > Storage > Optimize Storage. It can automatically offload old films, TV episodes, and rarely used App Store app data to iCloud when local space is low. This is useful for media files but does nothing for developer caches or game binaries. Enable it as a safety net, but don't rely on it as a substitute for the manual steps above.

Establish a Routine to Keep Space Clear

One-time cleanup is not enough on a 256 GB machine used for both development and gaming. Build a lightweight habit:

• Run brew cleanup --prune=all once a month.
• Delete Xcode Derived Data after major Xcode version upgrades or at the start of each quarter.
• Review node_modules directories in old project folders every few months and delete those you are not returning to.
• Before installing a large game, check your available storage in System Settings and quickly audit the top five entries in ~/Library/Caches with a du command or a dedicated app.

With discipline on these fronts, a 256 GB MacBook can realistically keep 30–60 GB free at all times — enough headroom for one or two large titles without compromising the development work that likely lives alongside them.