macOS Beta Eating Storage? Here's How to Reclaim It

Running a macOS beta is a different experience from running a release. The OS itself isn’t necessarily larger, but the betas generate substantially more diagnostic data, log files, and crash reports. A Mac on the public release that uses 30GB of System Data routinely hits 80GB on beta, often within weeks.

If you’re on a developer beta, public beta, or AppleSeed feedback program, here’s how to keep storage in check without leaving the beta channel.

Why betas use more disk

A few specific reasons betas grow faster:

• Verbose logging is on by default. Apple wants detailed crash logs and performance data. Logs that would be 50MB on release routinely hit 1–2GB on beta.
• Crash reports are kept longer. macOS holds them locally for analysis and feedback submission rather than rotating them quickly.
• Symbol files and debug info. Some system components ship with full debug symbols on betas, which take more space than the stripped versions in releases.
• Snapshot retention. macOS keeps more APFS snapshots during beta to support rollback if a beta build is buggy.
• Feedback Assistant data. Each piece of feedback you submit retains attached diagnostic packages locally for at least 30 days.
• Beta installers stick around. Each new beta downloads a 12–14GB installer, and old ones aren’t always cleaned up.

Knowing what’s specific to beta makes the cleanup logical.

Step 1: Check what’s actually using space

System Settings → General → Storage. Wait a full minute for the bars to populate.

The categories most likely inflated on beta:

• System Data — usually 2–3x what a release install shows
• macOS — sometimes shows multiple beta installers cached
• Developer category if Xcode is installed

Click each for breakdown.

Step 2: Clear feedback diagnostic packages

Feedback Assistant attaches diagnostic data to each report you submit. Those packages stay locally.

Location: ~/Library/Application Support/com.apple.feedback/

You can move the contents to Trash safely. Feedback Assistant rebuilds what it needs and Apple already has the submitted versions on its servers.

If you’ve submitted a lot of feedback during this beta cycle, this folder alone can be 5–15GB.

Step 3: Trim log files

Beta logs are verbose. Locations:

• /private/var/log/ — system logs (don’t delete files; they rotate)
• ~/Library/Logs/ — user logs
• /Library/Logs/ — system-wide app logs
• ~/Library/Logs/DiagnosticReports/ — crash reports
• /Library/Logs/DiagnosticReports/ — system crash reports

The DiagnosticReports folders are the biggest gain. On a beta Mac, these often hit 2–5GB. Safe to empty entirely; macOS recreates as needed.

To clear:

rm -rf ~/Library/Logs/DiagnosticReports/*
sudo rm -rf /Library/Logs/DiagnosticReports/*

(Or just open the folders in Finder and drag contents to Trash.)

Skip the manual huntSweep finds every cache, log, and forgotten file in seconds. Download Sweep free →

Step 4: Clear sysdiagnose archives

Sysdiagnose is a comprehensive diagnostic tool macOS runs occasionally on betas to capture system state. Each archive is 200MB–1GB.

Location: /private/var/tmp/sysdiagnose_*

These are deleted automatically after 30 days but you can clear them sooner:

sudo rm -rf /private/var/tmp/sysdiagnose_*

If Apple has asked you to keep certain archives for a specific bug report, leave those.

Step 5: Trim Time Machine local snapshots

Beta macOS keeps more local snapshots than release does, partly to support beta rollback. They can total 30–60GB.

tmutil listlocalsnapshots /

Then either delete oldest:

tmutil deletelocalsnapshots <date>

Or all:

for snap in $(tmutil listlocalsnapshots / | awk -F. '{print $4}'); do tmutil deletelocalsnapshots $snap; done

macOS creates fresh snapshots on its schedule.

Step 6: Remove old beta installers

After installing a beta, the installer often stays in /Applications/ as “Install macOS [Name] Beta.app.” Each is 12–14GB.

Check /Applications/ for any “Install macOS” entries. Drag the older ones to Trash. Keep at most the current one if you might need it for re-installation.

Also check /Library/Updates/ for partial download files.

There’s a faster waySweep does the same hunt in seconds. Try Sweep free →

Step 7: Beta-specific symbol caches

Some beta-specific cache locations:

• /private/var/db/uuidtext/ — symbol cache for crash logs. Don’t delete this; it’s used to symbolize future crashes.
• ~/Library/Caches/com.apple.feedback/ — Feedback Assistant cache. Safe to clear.
• ~/Library/Developer/Xcode/iOS DeviceSupport/ if you use Xcode with beta iOS — old device support packages can be 5–10GB.

For Xcode device support, delete folders for iOS versions you no longer test against. Xcode redownloads if you reconnect a device on that version.

Step 8: General cleanup that applies everywhere

Beta or not, the standard offenders still grow:

• Downloads (~/Downloads/) — sort by date, delete old.
• Trash — empty all (right-click each in the Dock).
• Old iOS backups — ~/Library/Application Support/MobileSync/Backup/. Sort by date, keep newest, delete the rest.
• Slack cache — ~/Library/Application Support/Slack/Cache/
• Spotify cache — ~/Library/Caches/com.spotify.client/Data/
• Chrome cache — ~/Library/Caches/Google/Chrome/Default/Cache/
• Xcode DerivedData — ~/Library/Developer/Xcode/DerivedData/

Quit each app first, then clear.

Should you stay on beta?

A reasonable question to ask while you’re cleaning up:

• You’re a developer testing your apps: stay. The storage cost is the price of admission.
• You wanted to try new features early: storage cost is real, plus stability is variable. If the features aren’t critical to you, the public release is more comfortable.
• You enrolled accidentally and forgot to leave: System Settings → General → Software Update → Beta Updates → set to Off. Future updates pull from the release channel. You don’t immediately leave the current beta build, but you stop receiving new ones.

Leaving the beta channel mid-cycle doesn’t reduce current disk use, but it stops the growth.

Should you turn off beta updates entirely?

If you decide beta isn’t for you anymore:

System Settings → General → Software Update → click the (i) next to Beta Updates → choose Off.

You’ll continue running your current beta build until either:

1. The beta cycle finishes and you receive the corresponding release version, or
2. You manually downgrade (see our rollback guide).

The cleanest exit is to wait for the release version to ship, which auto-installs and converts you back to the release channel.

What not to delete on beta

A few things to leave alone:

• /private/var/db/uuidtext/ — needed for crash log symbolication
• /private/var/db/com.apple.xpc.launchd/ — system service state
• /System/ — protected by SIP anyway, but don’t try
• Any folder with a recent modification date you don’t recognize — could be active beta machinery
• ~/Library/Containers/ itself — only delete specific subfolder contents if you know what you’re doing

The general rule: if a folder is being actively written to (recent modification dates), don’t blanket-delete. Specific cache subfolders are safe; whole containers are not.

Skip the manual huntSweep finds every cache, log, and forgotten file in seconds. Download Sweep free →

Maintenance routine for beta users

If you’re committed to staying on beta, this routine keeps storage reasonable:

Weekly:

• Empty Downloads, Desktop, Trash
• Delete old DiagnosticReports
• Trim Time Machine local snapshots if not on a backup drive

Monthly:

• Clear Feedback Assistant cache
• Delete sysdiagnose archives older than two weeks
• Remove old beta installers from /Applications/
• Audit ~/Library/Logs/ for unusually large folders

Per beta release:

• Restart twice (clears more state than once)
• Run the full storage check after the new beta has been running for a day
• Submit any feedback you’ve collected, then clear feedback diagnostic packages older than 30 days

This keeps a beta Mac feeling close to release storage levels — typically within 10–15GB extra rather than the 50GB+ that beta Macs accumulate when not maintained.

Realistic expectation

Beta macOS will always use more disk than release macOS. The gap, after cleanup, is typically 10–20GB. Trying to get a beta down to release-level storage is fighting the OS’s actual job (collecting diagnostic data so Apple can fix bugs).

If 10–20GB extra is unacceptable on your storage budget, beta isn’t for that Mac. Move beta testing to a secondary device or wait for releases.