7 ways to reduce Mac System Data without deleting macOS
You can reduce Mac System Data without deleting macOS, reinstalling your Mac or emptying folders you do not recognize. The safest approach is to identify which files are growing, confirm what owns them and remove only data that is disposable or no longer needed.
System Data is a catch-all storage category, not a folder you can delete. It can include caches, logs, local snapshots and application-support files. Its reported size also changes as macOS recalculates storage, so judge cleanup by the usable space recovered, not just a smaller category label.
Before you start: record your available storage
Open System Settings > General > Storage and let the categories finish loading. Record both the System Data estimate and available space. On older macOS versions, storage information appears under About This Mac > Storage.
Make a current backup before removing application data or device backups. For each cleanup below, use the same sequence: identify the owner, confirm the contents, remove selectively and measure again.
| What you find | Best starting point |
|---|---|
| Storage grew after a long session or update | Restart and reassess |
| Old iPhone or iPad backups | Manage device backups in Finder |
| Large folders belonging to unused apps | Review app leftovers |
| Xcode or Docker consumes substantial space | Use development-tool cleanup controls |
| Large local snapshots | Check Time Machine and available space |
Leave /System, /usr and unfamiliar folders inside /private/var alone. Do not delete entire Library folders, disable System Integrity Protection or use blanket deletion commands to chase a storage number.
1. Restart to clear temporary storage pressure
Restarting can reduce Mac System Data when temporary files or swap usage have accumulated during a long working session. It will not remove old backups or abandoned application data, but it is a sensible first step because it requires no manual file deletion.
Save your work, quit applications and restart normally. Once you sign back in, let background activity settle before reopening Storage. If macOS has just updated, storage calculations may take additional time.
Do not manually delete swap files or sleep-related files from protected locations. macOS manages those files, and removing them while the system is running is not a safe substitute for restarting.
If the category shrinks but available space barely changes, the difference may be a recalculation rather than a meaningful cleanup. Conversely, recovered space can be useful even if the System Data label has not caught up yet.
Keep this method in perspective: restarting addresses temporary pressure. If storage quickly fills again, continue with the steps below to find the persistent contributor rather than repeatedly rebooting.
2. Delete obsolete iPhone and iPad backups
Removing an obsolete local device backup can reduce Mac System Data if that backup contributes to the category. These backups can contain valuable restore data, so verify the device name and backup date before deleting anything.
Connect the iPhone or iPad to your Mac, open Finder and select the device in the sidebar. In the General tab, choose Manage Backups. Review the entries and delete only backups you no longer need.
Keep a usable recovery option. An older backup may be worth retaining if it contains data from before a device replacement or a major change. Do not assume an iCloud backup exists or is current without checking it separately.
For inspection, local backups are commonly stored at:
~/Library/Application Support/MobileSync/Backup/
In Finder, choose Go > Go to Folder to open that location. The files inside are not meant to be edited individually. Use Finder’s backup-management controls instead of deleting pieces from a backup directory, which can leave the remaining backup unusable.
Deletion through device-management controls is not necessarily reversible through Trash. Check your recovery options first, then compare available space after the removal finishes.
3. Reduce Mac System Data by clearing selected app caches
Application caches are a reasonable cleanup target when they are large and rebuildable. Start with an app’s own cache or storage-management settings, especially for browsers, streaming apps and tools that download substantial temporary content.
For manual inspection, quit the relevant application and open:
~/Library/Caches/
The tilde means your home folder. This is your user Library, not /System/Library or the separate system-wide /Library directory.
Check folder sizes and identify the app that owns each candidate. Move only confirmed, disposable cache contents to Trash. Reopen the app and test its normal functions before emptying Trash. If a cache immediately returns, the app probably needs it for your current workload.
A cache folder is not the same as an Application Support folder. Application Support may contain databases, saved projects or other original data. A folder name that looks technical does not make its contents disposable.
Cache cleanup may temporarily slow an app while it rebuilds previews, indexes or downloaded resources. It can also remove offline content if the application stores that content as cache. If Finder refuses an operation, stop rather than changing permissions to force deletion.
4. Remove confirmed leftovers from apps you no longer use
Removing confirmed app leftovers can reduce Mac System Data without touching the operating system. The key is distinguishing abandoned files from data used by an installed app or another product from the same developer.
Start with the application itself. If its vendor provides an uninstaller, use that first, particularly for software with background services, drivers or system extensions. Dragging an app to Trash does not necessarily remove those components.
Afterward, inspect clearly related folders in locations such as ~/Library/Application Support/, ~/Library/Caches/ and ~/Library/Preferences/. Match the developer or application name, then check the contents before removing them.
Application-support folders deserve extra care. They can hold local documents, plug-ins, licence information or settings you may want if you reinstall. Do not bulk-delete Containers or Group Containers, where apps can store persistent and shared data.
Broomkit includes an app uninstaller with Trash-first cleanup, which allows you to review candidates before permanent removal. For more detail on identifying shared files and persistent data, follow the guide to removing Mac app files without leaving leftovers.
Test any remaining apps from the same vendor before emptying Trash.
5. Clear rebuildable developer artifacts
Developers can often reduce Mac System Data by targeting generated files rather than source code. Xcode build outputs, simulator resources and container-related storage can grow substantially, though macOS may classify them differently between systems.
In Xcode, inspect the Derived Data location through Settings > Locations. Quit Xcode before removing selected Derived Data folders for projects you can rebuild. Expect the next build to take longer.
Treat archives differently. Release archives and their debug symbols may be needed for distribution or crash investigation. They are not interchangeable with disposable build output. Remove unused simulators and runtimes through Xcode’s management interfaces rather than deleting unfamiliar directories.
For Docker, inspect disk usage and distinguish build cache, images and containers from volumes. A volume may contain your only copy of a local database. Avoid broad prune operations unless you understand exactly which resources they remove.
If your team writes an automated cleanup utility, specify protected paths and test it on disposable data. Proof’s continuous correctness audits connect signed requirements to code and CI checks, a relevant approach for verifying that a cleanup utility honors its deletion rules. It is not a Mac storage-cleaning service.
The Mac cleanup guide for Xcode and Docker covers development-specific storage in more detail.
6. Let Time Machine manage local snapshots
Before trying to reduce Mac System Data by removing local snapshots, check whether you actually need more available space. Snapshot size does not always represent storage that is unavailable for other uses.
Apple explains how Time Machine local snapshots work: macOS counts the space they use as available storage and automatically removes snapshots as they age or when space is needed. A large snapshot reading alone is not a reason to delete them.
Connect your Time Machine backup disk and allow a backup to complete. This preserves another recovery option, but completing a backup does not guarantee that every local snapshot immediately disappears.
If you still need manual removal, Apple documents temporarily turning off automatic backups. On recent macOS versions, open System Settings > General > Time Machine > Options, set the backup frequency to Manually, wait a few minutes and restore your previous schedule afterward.
Do this only after checking that you have a recent backup. Local snapshots provide useful recovery points, and you should not leave automatic backups disabled accidentally.
Not every APFS snapshot belongs to Time Machine. Avoid deleting unfamiliar snapshots through Terminal or Disk Utility simply because they appear in a storage inspection.
7. Remove oversized app logs, then fix the cause
Clearing an oversized application log can reduce Mac System Data, but rapid regrowth usually points to an underlying problem. An app repeatedly recording the same error may refill the space soon after cleanup.
Inspect your user log folder:
~/Library/Logs/
Look for unusually large files or accumulated logs clearly associated with a known application. Quit that app before moving old logs to Trash. If you are investigating a crash or working with support, preserve the relevant diagnostic files first.
Do not manually clear system logging databases or unfamiliar files under /private/var. Keep this step focused on identifiable, app-generated logs in your user account.
After cleanup, reopen the application and check whether the log grows unusually quickly. Updating the app or correcting the recurring error is more useful than scheduling repeated deletions.
A Disk Map or large-file finder can help locate the biggest candidates, but size alone is not permission to delete. A large database or project file may be irreplaceable, even when macOS places it in a broad storage category.
Verify the result before emptying Trash
The goal is to reduce Mac System Data safely, not make the category disappear. macOS and your applications will always need some supporting storage.
Reopen the apps affected by your changes and confirm that important documents, settings and local data remain available. Then review Trash and empty it only when you are confident you no longer need its contents. Files moved to Trash generally still occupy disk space until they are permanently removed.
Return to Storage and compare available space with your starting measurement. Allow time for recalculation rather than running several cleanups because the label has not changed immediately.
If storage is still unexplained, identify the largest remaining folder before taking further action. Do not escalate to deleting protected system files.
Frequently asked questions
Can I delete System Data itself?
No. It is a storage category, not one deletable folder. You can remove specific unnecessary files within it, but some of its contents are required by macOS and installed apps.
Why did System Data grow again after cleanup?
Apps regenerate caches, Time Machine creates recovery snapshots and active software writes new logs. Repeated rapid growth in one folder is worth investigating rather than treating all growth as a fault.
Do I need to reinstall macOS to reduce Mac System Data?
Usually not. Reinstalling is not a targeted solution for old device backups, app leftovers or developer artifacts, and an in-place reinstall can leave those files intact.
What size should System Data be?
There is no universal target. Installed apps, device backups and development workloads all affect it. Focus on available space, explainable growth and whether your Mac has room for normal work and updates.
Find the largest cleanup candidates with Broomkit
If manual folder inspection is slowing you down, Broomkit provides disk-map visualization, a large-file finder, cache cleanup tools and an app uninstaller with Trash-first cleanup.
Use those tools to identify the biggest candidates, review what owns them and preserve anything you cannot confidently classify. Every feature is unlocked during the three-day free trial, with no account or card required. Afterward, a one-time licence keeps the tools unlocked, without a subscription.
Every feature free for 3 days. No account, no card. Then a one-time licence — never a subscription.
Download Free for MacRelated guides
Sources: Proof’s continuous correctness audits · Apple explains how Time Machine local snapshots work. Published 5 October 2026.