Start by identifying whether you use Claude Desktop, Claude Code, or the website. This guide concerns the Mac desktop app. Measure app-owned folders on your Mac; this guide does not establish which conversation or attachment data your installed version keeps locally.
Do not assume local data can be recovered by signing in again. Keep configuration, authentication, conversation state and local-only files. Quit the app, confirm the purpose of each candidate and preserve a recoverable copy before reviewing cleanup.
Where Claude Desktop stores data
When reviewing Claude Desktop storage, inspect these possible locations:
~/Library/Application Support/Claude/— main app data, databases, and session artifacts.~/Library/Caches/com.anthropic.claude*— short-lived cache files and compiled resources.~/Library/Logs/Claude/or similar — debug and crash logs.~/Library/Saved Application State/— inspect only a subfolder confirmed to belong to Claude; keep unknown restoration state and the parent directory.
These are locations to inspect, not an approved deletion list. Exact names vary by version; age, a version number, or a cache-like name does not prove a folder is safe to remove. Claude Code is a separate tool: do not apply Desktop paths or cleanup decisions to its configuration and sessions.
Step-by-step manual review
- Save work and quit Claude Desktop normally.
- In Finder, choose Go → Go to Folder and enter
~/Library/Application Support/. If a Claude folder exists, select that folder and choose File → Get Info (Command-I). Record its size, path and the date; do not move or delete it. Keep the entire Application Support parent directory. - Repeat the size check for individually identified Claude folders under
~/Library/Caches/and~/Library/Logs/. Record your macOS and Claude Desktop versions alongside each measurement. Identify configuration, authentication, databases and local-only state. Leave unknown files untouched; a folder named Cache or tmp is not sufficient evidence. - Only move individually verified disposable files to Trash, preserving their original paths and a backup.
- Check sign-in, existing conversations and your normal workflow before emptying Trash. If anything is missing, quit and restore the original files without overwriting new state.
Evidence limitation: the listed locations are not a version-specific recovery test. This guide does not promise cloud restoration of deleted local data.
Finder instructions: Go to a specific folder and Get file and folder information (Apple Support, reviewed September 29, 2026). A measured folder size is not an estimate of safely reclaimable space. If a folder is missing, record that result rather than creating it or searching unrelated data.
Using AI Agent Clean for Claude
AI Agent Clean’s AI Agent Clean module lists Claude Desktop alongside Cursor, Copilot, Windsurf, Gemini CLI, and more (see v1.0.1). Review the detected paths and size totals before selecting items. Detection does not establish that every file in a group is disposable; leave uncertain items unselected.
- Open AI Agent Clean → AI Agent Clean.
- Locate the Claude section in scan results.
- Review logs, caches, and update debris separately.
- Check the selected paths and the cleanup mode before confirming. Choose a recoverable workflow and preserve a backup; do not assume every cleanup action can be undone through Trash.
For developers running both Cursor and Claude, combine this guide with Cursor cache cleanup and inspect the matching scan results. A scan is not proof that every installed tool or storage location is covered.
- Keep the entire Application Support parent directory, whether Claude is running or closed.
- Exclude identity, authentication, and keychain-related data from cache cleanup.
- Local-only drafts not yet synced may be lost if you clear the wrong database — when in doubt, skip that category.
- Only consider individually verified cache files with a tested recovery method and a backup. Claude launching successfully does not prove that cleanup is safe or recoverable.
- AI Agent Clean never uploads file contents — scans stay on your Mac. See Privacy Policy.
macOS 14+ permissions
Grant access only to the folders you choose to review. If a folder is inaccessible, do not broaden permissions merely to chase space savings. Access permission does not establish that its contents can be deleted.
When to clear vs when to wait
Review storage when you have measured a disk-space problem. Sluggish responses alone do not establish that local cache is the cause. If you are troubleshooting an error, keep relevant logs and use the vendor’s support guidance before deleting files. Unknown files and local-only state should remain untouched.
FAQ
Is it safe to clear Claude Desktop cache on Mac?
Only files confirmed to be regenerable should be considered. Keep conversation databases, credentials, configuration and unknown files; do not assume cloud synchronization will restore deleted local data.
Will clearing Claude Desktop cache delete my chats forever?
Deleted local-only data may not be recoverable by signing in. Preserve important conversations and files before cleanup, and leave unknown databases untouched.
Where should I start in Finder?
Quit Claude, then open ~/Library/Application Support/Claude and related folders under ~/Library/Caches. Select each identified folder and use File → Get Info to measure it. If you are unsure what a file contains, keep it; you can review detected paths in AI Agent Clean without committing to cleanup.
Claude Code settings are not Desktop cache
If you also use Claude Code, preserve ~/.claude/settings.json, project .claude/settings.json and .claude/settings.local.json. They hold settings. Keep ~/.claude.json too: it contains sign-in and project state. These Claude Code files are separate from the Desktop cache discussed here.
Source: Anthropic's Claude Code settings documentation, reviewed September 23, 2026. The paths can change with configuration; this is documentation evidence, not a version-specific cleanup test.
Troubleshooting after cleanup
If behavior changes after cleanup, stop, quit Claude and restore the files you moved to Trash to their original locations. Preserve any newly created files before restoring a backup. If the original files are unavailable, consult vendor support; this guide cannot guarantee recovery.
Review disk usage when you have a specific storage problem; repeated deletion is not a substitute for identifying its cause.