Guides · Caches

What Freshist cleans

27 kinds of cache, log and leftover data — each with the exact folder it lives in and how careful you should be with it. Only low-risk items are ever selected for you, and you see every file before anything moves.

Low risk

Pre-selected

Rebuilt automatically by macOS or the app that made it. Freshist selects these for you — you still see every item before anything moves.

  • ~/Library/Caches

    Caches apps rebuild automatically — first launches may feel slightly slower.

  • ~/Library/Logs

    Diagnostic log files. Safe to delete.

  • ~/Library/Logs/DiagnosticReports

    Old crash and diagnostic reports. Safe to delete.

  • ~/Library/Saved Application State

    Window-restore state — apps simply open with fresh windows.

  • ~/Library/Developer/Xcode/DerivedData

    Xcode build products — next builds recompile from scratch and take longer.

  • ~/Library/Developer/Xcode/iOS DeviceSupport

    Debug symbols from iPhones/iPads you connected — NOT device backups. Xcode re-downloads them when you plug the device in again.

  • ~/Library/Caches/go-build

    Go build cache — next builds recompile and take longer.

  • ~/Library/Caches/Homebrew

    Downloaded install archives. Homebrew re-downloads them if ever needed.

  • ~/Library/Caches/JetBrains

    IDE cache — IntelliJ/PyCharm/etc. rebuild it automatically.

  • ~/Library/Application Support/Code/CachedData

    Editor cache — VS Code rebuilds it on next launch.

  • ~/Library/Caches/com.apple.Safari + 3 more

    Web caches for Safari, Chrome, Firefox, Brave — rebuilt as you browse.

  • /Volumes/<drive>/.Spotlight-V100 + 6 more

    macOS index & metadata left on external drives (.Spotlight, .fseventsd, .DS_Store) — rebuilt when you reconnect the drive.

Medium risk

Review first

Safe to remove, but the tool that owns it re-downloads or rebuilds it on next use, which costs time and bandwidth. Listed, never pre-selected.

  • ~/.npm/_cacache

    Package cache — future npm installs re-download packages.

  • ~/Library/pnpm/store

    Shared package store — projects re-download dependencies on next install.

  • ~/.bun/install/cache

    Package cache — future bun installs re-download packages.

  • ~/.cargo/registry/cache

    Rust dependency download cache — cargo re-downloads crates on next build.

  • ~/.gradle/caches

    Build cache — next Gradle builds re-download dependencies.

  • ~/Library/Caches/CocoaPods

    Pod cache — next pod install re-downloads.

  • ~/Library/Caches/composer

    PHP dependency cache — Composer re-downloads packages on next install.

  • ~/.conda/pkgs

    Conda package cache — future installs re-download packages.

  • ~/Library/Caches/deno

    Deno dependency cache — re-downloaded on next run.

  • ~/.cache/torch

    PyTorch model/dataset cache — re-downloaded when next needed.

  • ~/Library/Caches/ms-playwright

    Test browser binaries — Playwright re-downloads them on next install.

  • /Library/Caches + 1 more

    System-wide caches under /Library — deleted permanently by the signed helper (not the Trash). Regenerated automatically.

High risk

Review first

Large stores — whole dependency repositories or downloaded AI models — that take a long time to get back. Listed, never pre-selected.

  • ~/.m2/repository

    Java dependency repository — LARGE; Maven re-downloads every dependency on next build.

  • ~/.cache/huggingface

    Downloaded AI models & datasets — LARGE; re-downloaded when a model is next used.

  • ~/.ollama/models

    Local AI models — LARGE; Ollama re-downloads a model when you next run it.

Everything in your user folder goes to the Trash, so you can undo. Root-owned system caches are the one exception — see what Freshist never deletes. Leftovers from uninstalled apps are covered in the Library folder guide.