DevCleaner
Menu
Skip to content
Browse guides

How to Clear Claude Code and Claude Desktop Cache on Mac

Separate Claude desktop cache and CLI diagnostics from settings, credentials, conversations and pending updates.

On this page

Measure desktop and CLI data separately

Claude Desktop and Claude Code store different kinds of data. Start with read-only checks; a missing directory simply means that location is not used by your installation.

du -sh "$HOME/Library/Application Support/Claude" 2>/dev/null
du -sh "$HOME/Library/Caches/com.anthropic.claudefordesktop" 2>/dev/null
du -sh "$HOME/.claude" 2>/dev/null
claude --version

Keep credentials, settings and conversations

LocationContentsDecision
~/Library/Application Support/Claude/Cache, Code Cache, GPUCacheDesktop renderer cachesRegenerable after quitting
~/.claude/debug, shell-snapshotsDiagnostics and generated shell snapshotsReview and clear when no CLI session is running
~/.claude/projectsConversation transcripts and project stateKeep if you need to resume sessions
~/.claude/settings.json, ~/.claude.jsonPreferences, account and configuration stateKeep
com.anthropic.claudefordesktop.ShipItUpdater staging and older update filesLeave alone while an update is pending

A large .claude directory does not mean it is all disposable. Do not delete the entire directory or broad Application Support tree. Project memories and transcripts are useful work, not renderer cache.

Clear a specific desktop cache

Quit Claude Desktop, finish any update, and use Finder → Go → Go to Folder. Paste the exact cache path, inspect its contents and move only that cache to Trash. Relaunch Claude to rebuild it. Review the result before emptying Trash; moving files there does not free disk space yet.

~/Library/Application Support/Claude/Cache

Review CLI diagnostics without resetting Claude Code

Finish CLI sessions before removing generated diagnostics. Inspect individual files under debug and shell-snapshots rather than sweeping settings, project transcripts or installed plugins. Backups can help recover configuration mistakes, so decide whether you still need them before deleting.

DevCleaner separates Claude desktop cache, diagnostics, CLI cache and session transcripts. Transcripts are Warning and remain opt-in. Updater staging is excluded from automatic cleanup so an update waiting to install is not cancelled. See the safety model and the AI storage overview.

FAQ

Can I delete the entire .claude folder?
Avoid that for routine cleanup: it can remove settings, project conversations and other state. Inspect generated cache and diagnostic directories instead.
Does deleting Claude cache clear my chats?
Deleting a specific renderer cache differs from deleting transcripts or project state. Keep .claude/projects and desktop account/state directories if you need conversations.
Why should I keep ShipIt updater files?
A pending desktop update can be staged there. Removing those files before installation can cancel the update.

References and scope

Reviewed against DevCleaner 1.14.5 and the references below on October 4, 2026. Locations can change with tool versions and custom settings. The examples are inspection steps and deliberate cleanup actions, not a measured claim about how much space your Mac will recover.

Review the space before cleaning

DevCleaner separates built-in Safe caches from Warning and Danger items. Safe Quick Clean is free; deep cleanup requires Pro on new Free installations. See Free and Pro features.

Download DevCleaner ↓
macOS 14+ · Developer ID signed · notarized by Apple