Why Is My Mac Drive Filling Up So Fast?

You bought a 256GB or 512GB Mac and told yourself it would be plenty of space. Then one day you open a file or try to download something and macOS stops you cold: your disk is almost full. Where did all that space go?

You’re not alone, and you’re not imagining it. macOS silently consumes storage in a surprising number of ways, many of them invisible in Finder. Here’s what’s actually going on.

1. Time Machine Local Snapshots

Even if you don’t have an external drive connected, macOS keeps local Time Machine snapshots right on your internal drive. These are point-in-time backups that macOS stores in case you later connect a backup drive or need to recover a deleted file.

The catch: they can consume anywhere from a few gigabytes to 50–100GB, and they don’t appear as regular files in Finder. You can list them from Terminal:

tmutil listlocalsnapshots /

macOS is supposed to purge old local snapshots automatically when you’re running low on space, but this process can be slow — and it doesn’t always kick in before you hit a wall. If you’re in a crunch, you can delete individual snapshots with tmutil deletelocalsnapshots <date>, but be careful: this removes a restore point.

2. APFS Snapshots and Clones

macOS has used the APFS (Apple File System) since 2017, and it has some powerful (but sometimes storage-hungry) features. APFS creates snapshots automatically during major system updates, when you run certain backup apps (like Time Machine or some third-party tools), and occasionally in the background.

These snapshots are essentially frozen copies of your file system at a moment in time. They share data with your live system via a technique called copy-on-write, which makes them very efficient at first — but as you make changes to files, the snapshot holds onto the old data. Over time, a snapshot that started at nearly zero can grow to several gigabytes.

Most users never see APFS snapshots in Finder. They live outside the normal file tree. Disk Utility can show some of them, but not all.

3. System Cache Growth

You might not think about it, but every app you use writes cache files to your drive. So do many background processes. These caches are stored in two main locations:

/Library/Caches/ — system-wide caches
~/Library/Caches/ — your user-specific caches

On a fresh Mac, these folders are nearly empty. After a year or two of normal use, they can easily reach 10–30GB or more. Some specific offenders:

Spotify: Stores gigabytes of offline tracks and buffer data
Slack: Keeps a local cache of every file, image, and message thread you’ve viewed
Photos: Caches previews and thumbnails for every photo in your library
Xcode: (More on this below) generates enormous build caches

macOS doesn’t clean these automatically. Some apps rotate their caches on their own schedule; others just keep growing.

4. Large Mail Attachments

If you use Apple Mail, it downloads every attachment from every email it has synced: PDFs, images, Word documents, ZIP files, everything. These are cached locally at ~/Library/Mail/.

For most people this is measured in gigabytes. If you receive a lot of files at work, or have been using the same Mail account for years, it can reach 10–20GB or more. The problem is that Mail doesn’t give you an obvious way to clean this up. You can free space by going to Mail > Preferences > Accounts and adjusting sync settings, or by deleting old emails with large attachments.

5. The Downloads Folder Is a Graveyard

Your ~/Downloads/ folder is where files go to be forgotten. Installers (.dmg, .pkg), ZIP archives, PDFs you opened once, videos, disk images — they all accumulate here over months and years.

A fresh Mac installer image alone is around 15GB. If you’ve downloaded a few macOS updates, some app installers, and various files over the life of your Mac, this folder can easily hold 20–50GB of things you no longer need.

The fix is simple: open the Downloads folder, sort by size, and delete anything you don’t recognize or no longer need.

6. App Updates and Electron Bloat

Have you ever wondered why Slack uses 500MB? Electron apps (Slack, Figma, Visual Studio Code, Discord, and many others) each bundle their own copy of the Chromium browser engine. That alone can be 200–400MB per app. Multiply by a dozen apps and you’re at several gigabytes just for the runtimes.

Beyond the apps themselves, these programs accumulate significant local data:

Slack stores your entire message history cache locally
Figma caches every project file you’ve opened
VS Code stores extensions, language servers, and build artifacts

App updates also don’t always clean up after themselves. Old versions may leave behind data folders, support files, or caches that persist after you’ve moved to the new version.

7. Xcode and Developer Tool Artifacts

If you do any iOS or macOS development, Xcode is almost certainly eating your disk. Three main areas to know:

DerivedData (~/Library/Developer/Xcode/DerivedData/) is where Xcode stores build products, index files, and compiled frameworks for every project you’ve ever opened. It’s not uncommon for this folder to reach 30–80GB on an active developer’s machine.

Simulator runtimes are downloaded for each iOS version you target. Each one is 5–10GB. Delete old ones you no longer need with:

xcrun simctl delete unavailable

Archives (~/Library/Developer/Xcode/Archives/) stores every app archive you’ve built for distribution. Each one can be 1–4GB depending on the app.

If you’re not a developer, you can skip this section. But if you are, this is often the single largest source of unexpected disk usage.

8. iCloud Drive Confusion

The “Optimize Mac Storage” feature in iCloud Drive is genuinely useful, but it can create a confusing picture of your available space. When enabled, macOS offloads older or larger files to iCloud and keeps only lightweight placeholders on your drive. These placeholder files show up in Finder with a cloud icon — they look like files, but downloading them requires an internet connection.

The confusion arises in two ways:

Finder looks fuller than it is: Files show up but aren’t actually taking local space. Your “available” disk space may look misleadingly low.
The “Other” category in Storage: macOS’s storage breakdown often lumps iCloud-related metadata, downloads in progress, and eviction candidates into the vague “Other” category, making it hard to understand what’s really happening.

If you’re troubleshooting storage, temporarily turning off iCloud Drive optimization can help you get a clearer picture of what’s actually on your disk.

9. How to Investigate Your Storage

The best starting point is built into macOS:

macOS Ventura and later: Apple menu > System Settings > General > Storage
Older macOS: Apple menu > About This Mac > Storage

This gives you a color-coded breakdown: Applications, Documents, Photos, System, Other. Click “Manage” to see more detail and get recommendations.

The most confusing category is usually “System Data” (sometimes called “Other”). This is a catch-all for anything macOS doesn’t know how to categorize — including Time Machine local snapshots, APFS snapshots, caches, and various system files. It’s often the biggest slice of the pie and the hardest to understand.

macOS’s built-in tool is a good starting point, but it doesn’t show you individual files, it doesn’t explain why something is there, and it doesn’t help you decide what’s safe to delete.

Stop Guessing — Let AI Figure It Out

Instead of manually hunting through folders and running Terminal commands, let a tool do the work. DiskCopilot scans your entire drive, shows you the biggest files and folders in a clear visual breakdown, and lets you ask AI whether each one is safe to delete.

You don’t need to know what DerivedData is, or whether a cache folder is safe to remove, or why your System category is 80GB. DiskCopilot’s AI assistant understands macOS internals and gives you plain-English answers.

Download DiskCopilot for free — it takes less than a minute to scan your drive and you’ll know exactly where your storage went.