VS Code & Cursor Disk Usage on a Mac: Cache & Extensions

VS Code & Cursor Disk Usage on a Mac: Cache & Extensions
Short answer

VS Code and Cursor store caches, logs, extensions and per-workspace data under ~/Library/Application Support (Code / Cursor) and ~/.vscode / ~/.cursor. Caches, logs and old workspace storage are safe to clear, and extensions re-download. On a busy dev Mac with many projects this adds up to several gigabytes.

Where it lives

WhatLocationSafe?
Caches & logs~/Library/Application Support/Code/{Cache,logs}Yes
Workspace storage.../User/workspaceStorageYes — old ones
Extensions~/.vscode/extensions, ~/.cursor/extensionsRe-download

Cursor mirrors VS Code's layout, so both share the same clean-up spots.

What's safe to clear

Your settings and keybindings live in settings.json/keybindings.json — not the cache. Clearing caches won't touch them.

Sweep it with the rest

Editor caches sit alongside the wider dev pile — node_modules, Docker, Homebrew. MacCleaner surfaces them together with real sizes so you reclaim the whole thing at once. Full sweep: the developer guide.

Frequently asked questions

Is it safe to delete VS Code cache?

Yes. Caches, logs and old workspaceStorage regenerate or are stale. Extensions re-download. Your settings.json and keybindings.json are separate and untouched.

Where does Cursor store its data on a Mac?

Like VS Code: ~/Library/Application Support/Cursor (caches, logs, workspace storage) and ~/.cursor/extensions. The same clean-up spots apply.

How much space do VS Code and Cursor use?

With many projects, caches, logs, workspace storage and extensions add up to several gigabytes on an active developer Mac.

Reclaim the space in two taps

MacCleaner scans read-only, shows every file before anything is touched, marks the safe groups, and lets you choose Trash or permanent. Free for up to 500 MB of cleanup a day.

Download for Mac