How to Safely Clean Logs, Cache, and Temporary Files on macOS (Without Breaking Your System)

Over time, macOS silently accumulates logs, cache files, temporary data, and developer junk. If you use tools like Docker, VS Code, Chrome, XAMPP, or other dev utilities, this buildup can easily consume tens of gigabytes.

The good news?
You can safely clean most of it — if you know where to look.

This guide shows safe, proven commands to clean macOS without touching critical system files.

🚫 First: What You Should NEVER Delete on macOS

Before cleaning, it’s important to know what not to touch.

❌ Never delete these:

  • /System

  • /System/Volumes

  • /System/Library

  • /private/var (entire folder)

  • ~/Library/Application Support (entire folder)

Deleting these can break macOS or installed apps.

✅ What Is Safe to Clean on macOS

macOS separates system-critical data from temporary and cache data.
The following locations are safe to clean regularly:

Location Purpose Safe
~/Library/Caches App caches ✅
~/Library/Logs App & crash logs ✅
/private/tmp Temporary system files ✅
/private/var/tmp Temporary runtime files ✅
/private/var/log/*.log System logs (truncate only) ✅
Browser caches Chrome, Edge, Safari ✅
Dev tool caches VS Code, Docker ✅

🧹 Step-by-Step Safe Cleanup Commands

🔴 Before You Start

Close apps like:

  • Chrome

  • VS Code

  • Slack / Teams

  • Docker Desktop

1️⃣ Clear User Cache (100% Safe)

  rm -rf ~/Library/Caches/*

✔ Frees space
✔ Apps recreate cache automatically

2️⃣ Clear Temporary System Files

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

These are the same files macOS removes during a reboot.

3️⃣ Clean System Logs (Safe Method)

⚠️ Do not delete log folders — only empty log files.

 sudo find /private/var/log –type f -name “*.log” –exec truncate -s 0 {} \;

This keeps permissions intact and avoids system issues.

4️⃣ Clear User Logs

   rm -rf ~/Library/Logs/*

This removes old crash reports and unused app logs.

5️⃣ Clean Browser Cache (Chrome Example)

   rm -rf ~/Library/Application\Support/Google/Chrome/Default/Cache
   rm -rf ~/Library/Application\Support/Google/Chrome/Default/Code\ Cache
   rm -rf ~/Library/Application\ Support/Google/Chrome/Default/GPUCache

Chrome will rebuild these automatically.

6️⃣ Clean VS Code Cache (Very Common Space Hog)

    rm -rf ~/Library/Application\ Support/Code/Cache
  rm -rf ~/Library/Application\ Support/Code/CachedData
  rm -rf ~/Library/Application\Support/Code/User/workspaceStorage
  rm -rf ~/Library/Application\ Support/Code/logs

⚠️ Do not delete:

  • extensions

  • User/settings.json

7️⃣ Docker Cleanup (Biggest Space Saver)

Docker can silently use 10–30 GB.

   docker system prune -a –volumes

This removes:

  • Unused containers

  • Old images

  • Unused volumes

Active containers are not touched.

🧹 One-Shot Safe Cleanup (Recommended)

You can safely copy-paste everything below:

    # User cache & logs
  rm -rf ~/Library/Caches/*
  rm -rf ~/Library/Logs/*

# System temp files
sudo rm -rf /private/tmp/*
sudo rm -rf /private/var/tmp/*

# System logs (truncate)
sudo find /private/var/log –type f -name “*.log” –exec truncate -s 0 {} \;

# Chrome cache
rm -rf ~/Library/Application\ Support/Google/Chrome/Default/Cache \
~/Library/Application\ Support/Google/Chrome/Default/Code\ Cache \
~/Library/Application\ Support/Google/Chrome/Default/GPUCache

# VS Code cache
rm -rf ~/Library/Application\ Support/Code/Cache \
~/Library/Application\ Support/Code/CachedData \
~/Library/Application\ Support/Code/User/workspaceStorage \
~/Library/Application\ Support/Code/logs

👉 Restart your Mac after running this.

📆 How Often Should You Clean?

Monthly

    rm -rf ~/Library/Caches/*
  docker system prune -a

Quarterly

  • Run the full cleanup block above

Prev Post
Coding Agents: The Future of Software Development Automation

Leave a Comment