Cursor Storage on Mac: Why It's Huge and How to Clear It

Cursor taking up too much space on Mac? Check these three places

When auditing developer storage on Mac, Cursor stores Agent chat history, worktrees, and extensions locally. Cursor says Agent conversations are the largest contributor for most users, but that does not tell you what is largest on your Mac. Measure first, then follow the path that actually accounts for the space.

• Agent history and local state: Cursor says old Agent conversations can make its local database grow to many gigabytes. Support commonly identifies ~/Library/Application Support/Cursor/User/globalStorage/state.vscdb; use it as a clue, not a guaranteed path for every version or setup.
• Agent worktrees: Cursor-managed checkouts are commonly under ~/.cursor/worktrees/. These contain project files and changes, so they are not simply disposable cache.
• Extensions and project data: extensions, dependencies, build output, and files in your repositories may also occupy space. Their cleanup does not use the chat-history workflow.

Read more: Cursor: Installation and startup — free up disk space · Cursor Community: reduce local Cursor storage while preserving history

How to find Cursor storage on a Mac without changing it

Quit Cursor with Cmd-Q for a steadier measurement. The following du commands report folder sizes; they do not remove or modify files. Start with the parent app-data folder and the Agent worktrees folder:

If the commonly reported database path exists, check it separately:

A missing result can mean the path is absent, named differently, or inaccessible; it does not mean Cursor uses zero space. The exact database path comes from Cursor support discussions, while Cursor’s current help documents the cleanup controls rather than promising one filesystem layout.

1. Record the reported sizes before cleaning.
2. If worktrees are largest, inspect them in Cursor’s Worktrees cleanup settings.
3. If the local database is largest, decide whether you want to retain old chats before using the chat cleanup commands.
4. If neither explains the total, inspect the broader Cursor folder and project locations instead of deleting unrelated data.

Read more: Cursor: Installation and startup — free up disk space · Cursor Community: reduce local Cursor storage while preserving history

How to clean Cursor chat history without losing everything

When the local chat database is the large item, Cursor’s documented workflow uses two commands in order. They do different things: the first removes old conversations you choose not to keep; the second compacts the database.

1. Open the Command Palette with Cmd-Shift-P.
2. Run Delete Old Chats… and choose a retention window.
3. Export chats you may need before deleting them. Cursor staff describes old-chat removal as permanent.
4. Run GC Agent KV Blobs and allow it to finish.

Deleting chats alone often removes entries but leaves the database file at its previous size. Cursor says GC Agent KV Blobs is the compaction step. Cursor support describes it as removing unreferenced Agent data while retaining chats that remain available; how much space it reclaims depends on how much data is no longer needed.

Cursor says each command can take a minute or two on large databases. Support discussions report longer waits for unusually large files. Compaction may need temporary free space, and there is no universal recovery amount or guaranteed file-size reduction. If your Mac is almost full, do not start until you have enough room for the operation to finish. When it completes, quit Cursor fully and measure again.

Read more: Cursor: Installation and startup — free up disk space · Cursor Community: reduce local Cursor storage while preserving history

How to free space from Cursor Agent worktrees

If ~/.cursor/worktrees/ is large, open Agents Window → Settings → Worktrees → Cleanup. Cursor currently documents a maximum of 25 worktrees and 50 GB total by default; older managed worktrees are removed first. The settings page lists worktrees and offers deletion of a specific one.

1. Open the worktree in Cursor and check its branch and Git status.
2. Commit, create a pull request, or bring back any changes you want to keep.
3. Only then remove the worktree from Cursor’s cleanup settings.

A worktree is an isolated Git checkout with its own files, dependencies, and changes. Deleting it can discard task work that has not been committed or brought back. Cursor also documents worktree settings in the classic editor; labels and available controls can vary by build, so check the current help page if your interface differs.

Read more: Cursor: Installation and startup — free up disk space · Cursor: Worktrees

What not to delete while troubleshooting Cursor storage

Do not manually delete or edit state.vscdb as a routine cleanup step. Cursor’s supported process lets the application remove selected older chats and compact data it no longer needs. Deleting the database yourself can remove local history and state rather than clean only disposable data.

• Do not assume state.vscdb.backup is disposable. Cursor’s current official guide does not list deleting it as a standard cleanup step; ask Cursor support about your exact version and situation.
• Do not remove a worktree because its name looks old. Inspect it for uncommitted changes and files you have not brought back.
• Do not run broad Terminal deletion commands copied from a forum. A wrong path can remove chats, settings, extensions, or project work.

A large file is a measurement, not a safety label. If you cannot identify its owner or consequence, leave it in place while you investigate.

Read more: Cursor: Installation and startup — free up disk space · Cursor: Worktrees

When Diskfern can help locate Cursor storage

Diskfern can map large folders and keep their paths visible while you investigate. Its developer-storage guide covers common tool data and shows how to move from a broad map to a selected location. That helps with discovery; it does not certify that a Cursor database or worktree is safe to remove.

Use a scan to locate a large path, inspect its contents and owner, and then choose the owning application’s cleanup controls. The related guides below cover Diskfern developer storage, Mac file search, and storage used by Claude Code and Codex.

Read more: Diskfern Developer Storage