Cursor and VS Code are filling 'System Data' on your Mac — how to clear the cache
Last updated June 14, 2026
Cursor and VS Code store render caches and workspace state under ~/Library/Application Support and ~/Library/Caches, which macOS lumps into 'System Data' and can reach many gigabytes. The caches are safe to delete — they rebuild on launch. Keep your settings and extensions. Tokki Clean targets exactly these editor caches.
Safe to delete
~/Library/Application Support/Cursor/CacheRender/GPU cache — rebuilds on launch.
~/Library/Application Support/Code/CacheVS Code cache — rebuilds on launch.
~/Library/Caches/com.todesktop.* / com.microsoft.VSCodeEditor caches — safe to clear.
What to never delete
~/Library/Application Support/{Cursor,Code}/UserYour settings, keybindings, snippets.
Do it in one click
Tokki Clean finds cursor / vs code cache for you, sizes it, shows an itemized preview, and sends removals to the Trash — free, native, nothing leaves your Mac.
Download free for macOSApple silicon · macOS 12+ · no account
Frequently asked questions
Is it safe to clear the Cursor or VS Code cache?
Yes. The Cache/GPUCache/CachedData folders rebuild automatically when you reopen the editor. Don't delete the User folder — that's your settings.
Why is Cursor inflating 'System Data' on my Mac?
macOS reports app caches under ~/Library as 'System Data'. Cursor's caches can grow large; clearing them shrinks that figure.