How to Clean System Data on macOS and Free Up Disk Space (Complete 2026 Guide)

Clean System Data on macOS and Free Up Disk Space Guide

Last Updated On - February 17th, 2026 Published On - Feb 17, 2026

Is your Mac showing 100GB+ of System Data and you have no idea what is consuming the space?

Recently, my Mac was showing 120.44GB of System Data. After a structured and safe cleanup process (without using any third-party cleaner tools), I successfully freed up 40GB+ disk space.

This complete guide will help you clean up System Data on macOS safely — especially if you are a developer using Docker, VS Code, Node, Composer, or similar tools.


What is System Data on macOS?

System Data is Apple’s grouped storage category. It may include:

  • Time Machine local snapshots
  • System cache files
  • Log files
  • Docker virtual machine disk images
  • Developer build artifacts
  • iPhone/iPad backups
  • Virtual memory swap files
  • macOS update leftovers

macOS hides these files under one label, which makes it difficult to identify the real storage usage.


Step-by-Step Guide to Clean System Data on macOS

Follow these steps carefully. These methods are safe and will not harm your applications or personal files.


Step 1: Restart Your Mac

Before starting cleanup:

  1. Restart your Mac
  2. Go to System Settings → General → Storage
  3. Check if System Data recalculates

Sometimes macOS misreports usage and corrects itself after reboot.


Step 2: Remove Time Machine Local Snapshots

If Time Machine is enabled and your external backup disk is not connected, macOS creates local snapshots on your internal disk.

Check local snapshots

Open Terminal and run:

tmutil listlocalsnapshots /

If multiple snapshots appear, they are consuming disk space.

Remove snapshots safely

sudo tmutil thinlocalsnapshots / 9999999999 4

This will not delete your external backups.

This step alone can free 20GB–60GB.


Step 3: Clean Docker Data

Even if Docker app size shows 1–2GB, its internal VM disk image may consume much more.

Ensure Docker is running

docker version

If you see an error like:

“Cannot connect to the Docker daemon…”

Open Docker Desktop from Applications and wait until it fully starts.

Check Docker disk usage

docker system df

Remove unused Docker data

docker system prune -a
docker volume prune
docker builder prune

If Docker is corrupted or not starting, check its storage directory:

du -sh ~/Library/Containers/com.docker.docker

If very large and you do not need old containers, quit Docker and remove:

rm -rf ~/Library/Containers/com.docker.docker

Restart Docker Desktop after deletion.



Step 4: Clean VS Code Caches

VS Code itself is small, but caches and workspace storage grow large.

Check usage:

du -sh ~/Library/Application Support/Code

You can safely remove:

~/Library/Application Support/Code/Cache
~/Library/Application Support/Code/CachedData
~/Library/Application Support/Code/User/workspaceStorage

Do not delete the entire Code folder if you still use VS Code.



Step 5: Clear Node, NPM, and Composer Cache

NPM Cache

du -sh ~/.npm
npm cache clean --force

Yarn Cache (if used)

du -sh ~/.yarn

Composer Cache

du -sh ~/.composer
composer clear-cache

These steps can free 5GB–15GB on development machines.



Step 6: Remove System Caches

Delete contents (not folders) of:

~/Library/Caches
/Library/Caches

Restart your Mac after cleaning.

macOS will automatically recreate necessary cache files.


Step 7: Delete Old iPhone or iPad Backups

Check for device backups:

~/Library/Application Support/MobileSync/Backup

Delete backups you no longer need.


Step 8: Virtual Memory Files (Do Not Delete Manually)

Located at:

/private/var/vm

Do not manually delete files in this folder.

Restart your Mac to reduce swap file size.


Step 9: Identify Largest Folders on Your Mac

To identify actual disk usage:

du -h ~ -d 1 | sort -hr | head -20

If Library appears large, drill deeper:

du -h ~/Library -d 1 | sort -hr | head -20

This will reveal the real space-consuming directories.


What You Should NOT Delete

Never manually delete:

/System
/usr
/bin
/sbin

Avoid random Mac cleaner applications. Everything in this guide uses built-in macOS tools.


Final Results After Cleanup

After following this process:

  • System Data reduced significantly
  • Recovered 40GB+ disk space
  • No applications were harmed
  • No data was lost

Frequently Asked Questions (FAQs)

Why is System Data so large on macOS?

System Data increases due to Time Machine local snapshots, cache files, Docker images, logs, and developer build artifacts. macOS groups these under one storage category instead of displaying them individually.

Is it safe to delete System Data on Mac?

You should never manually delete protected system folders like /System or /usr. However, removing local snapshots, clearing caches, pruning Docker volumes, and cleaning developer artifacts is safe when done properly.

How much storage can I recover by cleaning System Data?

Most developers can recover between 20GB to 80GB depending on accumulated system data. In real-world usage, freeing 40GB or more is common.

Do I need third-party cleaner apps?

No. You can safely clean System Data using built-in macOS tools and official terminal commands without installing third-party cleaner applications.


Final Thoughts

System Data on macOS is not mysterious — it is accumulated temporary files, snapshots, developer caches, and system artifacts grouped under one label.

By following this complete guide, you can safely clean System Data on macOS and free up storage space without using third-party tools.

For developers, regular maintenance every few months will prevent storage from growing out of control again.