Mac storage full with system data: how to free space on macOS 13 or later

What System Data actually is

Apple's own definition is short. The Storage screen describes System Data as files and data used by the system, such as log files, caches, VM files, and other runtime system resources. That covers a lot of ground. Logs grow when macOS and apps record events. Caches grow when apps keep copies of things so they load faster. VM files are memory swap files that macOS uses when RAM runs short.

Here is the frustrating part. Apple says you can't manage the contents of this category. You can't open it, sort it, or pick items to delete. Your only moves are indirect. You remove the large things that feed it, or you let macOS clear the pieces it considers safe.

How big is too big for System Data

There isn't a normal size. No primary survey measures how many Mac owners hit System Data bloat. The public evidence is a handful of user reports. One Apple Community user had a 13-inch MacBook Air running macOS 14.3 with about 250 GB of total storage. After importing about 35,000 photos and 750 videos into Apple Photos, System Data grew to about 100 GB, later cited as 106 GB. The expected size was about 15 GB.

Treat that as a warning sign, not a rule. If System Data takes up a large share of your drive and you can't explain why, it's worth checking. If the number is small, leave it alone. Big numbers after a known event, such as a photo import, a new Xcode version, or a macOS update, are the easiest to explain.

Write down the System Data figure before and after each step you take. Those notes show which step moved the number. They also help if you later ask Apple Support or your IT team for help, because you can say exactly what changed.

What running out of space costs you

Nobody has measured what this problem costs Mac users. No study tracks lost hours, money, or grades. What exists is anecdote and retail pricing. So read the costs below as the ways a full disk slows you down, not as statistics.

Time is the first cost. A nearly full startup disk makes apps stall, saves slow down, and updates refuse to install. Apple's guide also says that when you move a file to the Trash, its space does not become available until you empty the Trash. A clean-up that skips the Trash frees nothing.

Money is the second cost. If the honest answer is more storage, the price difference matters. 9to5Toys lists the 13-inch M5 MacBook Air at regular prices shown in the table below. Apple's buy page lists the same storage options without prices, so check the live price on Apple's page before you decide.

Third is the risk of bad fixes. Some guides tell you to run sudo rm -rf on /private/var or on log folders. That can break things you can't easily restore. Apple does not endorse it. Skip it, even if a forum post says it worked for someone else.

Fourth is a blocked update. Apple's guide suggests that starting in Safe Mode clears certain system caches. Those caches rebuild as needed. That may free enough temporary room to install a macOS update, which is often the moment people finally notice the problem.

Why System Data keeps filling up

Big photo and video libraries

Photo libraries are the easiest case to explain. The Apple Community example shows how a large import can push the number up sharply. The thread does not confirm a single cause. The number later dropped to about 13 GB with no settings changed, and the user said it appeared to correct itself.

That matters for your plan. A spike can settle on its own, but you shouldn't count on it. If your System Data stays high after a few days, move on to the steps below and check the other causes.

Developer tools and simulators

Xcode is the clearest developer case. One developer on Apple's forums reported that Xcode simulators stayed on disk after deletion in Devices and Simulators and in Disk Utility. Removing Xcode and its Developer folder, then reinstalling, regained about 80% of a 1 TB disk. That is one user's report. It is not an Apple recommendation.

A forum reply says platforms that use space in CoreSimulator can be removed from the Other Installed Platforms section in Xcode settings. Command-line options exist too, but they erase simulator data. Read the next sections before you run any of them.

Local Time Machine snapshots

Third-party guides name local snapshots as a hidden cause. Apple's Time Machine page doesn't mention them. It says the oldest backups are deleted when your backup disk is full. It doesn't explain what happens on the startup disk. Treat snapshots as a suspect to check, not a confirmed cause.

Caches and logs that never get trimmed

Apps write caches, and macOS writes logs. Most of the time they stay small. When they don't, the usual cause is one app stuck in a loop or one cache that never gets trimmed. Apple says macOS clears safe items when space is needed, including temporary database files, interrupted downloads, staged macOS and app updates, and Safari website data.

Fix it without buying anything

Work from safe to risky. Each step stands on its own. Stop when you have enough room, then check the Storage screen again to see the new numbers.

1. Open Apple menu > System Settings > General > Storage. On macOS 13 or later, this screen shows categories and sizes. On older macOS, use Apple menu > About This Mac > Storage.
2. Empty the Trash. In Finder, press ⇧⌘⌫ or choose Finder > Empty Trash. Apple says space returns only after you empty it.
3. Clear Downloads. Sort by size, move large files you no longer need to the Trash, then empty the Trash again.
4. Turn on Optimize Storage from the Storage screen. Apple says it removes Apple TV movies and shows you already watched, and keeps only recent email attachments.
5. Delete old iPhone and iPad backups you no longer need. Check each backup's date first, because a backup may be your only copy.
6. Remove apps you don't use. Drag them to the Trash, then empty the Trash. Apple lists unused apps as a storage fix.
7. Restart in Safe Mode only if you still need room for an update. On Apple silicon, shut down, hold the power button until Loading startup options appears, choose your disk, hold Shift, then click Continue in Safe Mode.
8. Restart normally, wait a day, and check the number again. In the Apple Community example, the figure fell without any settings change.

Clean up Xcode leftovers safely

Start with Xcode > Settings. Look for the Other Installed Platforms section and remove any simulator platform you no longer use. Use the Xcode interface first. It is the least risky option, and it keeps you in control of what gets removed.

The command line can clean up more. The forum thread lists xcrun simctl runtime list to show installed runtimes, and xcrun simctl delete unavailable to remove runtimes that no longer work. A note in the thread says those commands erase all simulator data and applications.

DerivedData is the next place to look. It holds build output that Xcode rebuilds when you build again. Quit Xcode first. Then open Finder, press ⇧⌘G, and enter ~/Library/Developer/Xcode/DerivedData. Move the contents to the Trash, then empty the Trash. The next build takes longer on a large project.

Check Time Machine local snapshots without guessing

Start with read-only checks. Open Terminal and run man tmutil to read the manual for your exact macOS version. Then run tmutil listlocalsnapshots / to list any local snapshots on the startup disk. Listing changes nothing on your Mac.

Deleting snapshots is where the advice gets shaky. Some guides recommend purge commands, but one user reported that deleting snapshots did not raise free space. The purge flag is also disputed for newer macOS versions. If snapshots are your suspect, read the manual for your version and back up first.

Mistakes people make with System Data

• Forgetting to empty the Trash after each delete. Apple says the space does not return until the Trash is empty.
• Deleting random files in ~/Library or /private/var. Much of that data exists for a reason, and some apps rebuild it only with their own help.
• Trusting a cleaner app's junk list without reading it. Vendor blogs promote their own tools, so check each item first.
• Reading one number as the whole story. Check Applications, Photos, Mail, and developer folders too.
• Buying a bigger drive before you find the cause. A clean-up often recovers space for free, and a bigger drive only delays the next full warning.
• Deleting old backups before you confirm you have another copy of that data.

Where Lazur helps, and where it doesn't

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. It can point at things and guide you one click at a time. It does not clear caches, delete snapshots, or click buttons for you. You make every change.

Lazur is most useful as a guide through the Storage screen. Keep the Storage page open, hold ⌥ ⌘, and ask what each category means. Ask where Optimize Storage is, and Lazur draws a circle and a label around it. Ask how to remove an Xcode platform, and Lazur walks you through it while it waits for each click.

Lazur can also help with the routine. Ask it to set a reminder in Apple Reminders for a storage check next week. Hold fn to dictate your notes into the cursor in any app, so your Day 1 and Day 7 numbers are written down without extra typing.

For research, Lazur can run a background job in its own Chrome tabs and return a summary and a report. Use it to gather Apple's current pages for your macOS version. Still open the pages yourself. A summary is not a source.

Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer and are not stored. Content is never used to train AI models. There is a free trial with no credit card, and current plans are on the pricing page.

When to stop and ask for help

If System Data stays high after the safe steps, stop guessing. Back up the Mac first, then contact Apple Support. Bring your Day 1 note with the before and after numbers. That note makes the conversation faster, and it shows exactly what you already tried.

Some people reach for a cleaner app or a new drive as the first step. That can work, but it skips the question of cause. Find out what is filling the disk first. Then pick the fix that matches it.