CacheCut Support

Why does CacheCut ask for permission first?

macOS sandboxes CacheCut, so it can only look inside folders you explicitly allow. On first launch, grant access to your startup disk — CacheCut can then find caches from your creative apps wherever they’re stored. You’re asked once; the grant is remembered.

Common questions

Will CacheCut delete my projects, grades or exports?

No. CacheCut only targets known cache and render-cache locations, and project files, galleries and databases are explicitly excluded and never offered for cleaning. Everything it does clear is moved to the Trash, not deleted outright — so a mistake is always one “Put Back” away.

CacheCut didn’t find a cache I know exists — what do I do?

Some apps (like DaVinci Resolve with a custom scratch disk) store cache in a location CacheCut can’t guess automatically. Use “Add Folder…” to point CacheCut at that location directly, and it will be scanned alongside everything else.

Why won’t CacheCut clear a cache for an app that’s still open?

Clearing a cache while its app is actively using it can cause problems for that app. CacheCut brings the blocking app to the front so you can quit it yourself — it doesn’t force-quit anything on your behalf.

I cleared caches, but my disk space didn’t change — why?

macOS only returns the space once the Trash is actually emptied. After a clean, empty your Trash from the Dock (or ⌘⇧⌫ in Finder) to reclaim it.