Recover deleted Claude Desktop conversations from Chromium cache

Someone deleted a critical conversation in Claude Desktop. Do not panic — the app is essentially Temu Chromium, and it aggressively caches everything from the server. Here's how to pull your data out of that cache.
Immediate steps
- Fully exit Claude Desktop (File → Exit / Menu → Quit). Use task manager to confirm no process remains.
- Copy the entire cache directory before doing anything else.
Cache location
Windows: %APPDATA%\Claude\Cache\Cache_Data\
macOS: ~/Library/Application Support/Claude/Cache/Cache_Data/
Linux: ~/.config/Claude/Cache/Cache_Data/
You'll see files named index, data_0 through data_3, and f_*. Filter the f_* files by today's date to reduce noise.
Extraction with Claude Code CLI
In a backup of the cache, set up a Python virtual environment and launch Claude Code CLI. Install dependencies:
pip install brotli zstd gzip deflate zip
pip install ccl_chromium_reader # or git clone and install from source
Use this prompt with Claude Code (replace <search phrases here> with your conversation UUID or keywords):
Claude, I have made a boo-boo and deleted very important stuff from my Claude Desktop install, I need you to help recover it!
We are trying to recover conversations and files from a Chromium blockfile cache. The cache files (index, data 0..data_3, f *) are in this directory.
Use the ccl_chromium_reader package to walk every cache entry, decompress the HTTP body, and write each response to its own file in a new "extracted" subdirectory.
Flag any entry whose decoded bodies contains <search phrases here>.
The extracted folder will contain JSON, HTML, and binary files. Your conversation is in whichever response body has a URL containing /chat_conversations/<uuid>. Generated artifacts (docx/pdf) come out as separate files.
Notes
- This is a cache, so everything is not guaranteed to be there — run the recovery as soon as you notice the deletion.
- The same approach works for the claude.ai website: close Chrome, locate its
Cache_Datadirectory, and follow the same extraction steps. - Kudos to cclgroupltd for the
ccl_chromium_readerpackage.
📖 Read the full source: r/ClaudeAI
👀 See Also

How to Fix OpenClaw Response Times by Reducing Context Bloat
A developer resolved 10-minute response times in OpenClaw by reducing injected workspace files from 47,000 characters to 16,000 characters through file restructuring and configuration changes, including setting bootstrapMaxChars to 8000 and adding compaction safeguards.

12GB VRAM Benchmarks: Running Qwen 3.6 and Gemma 4 Models on a RTX 4070 Super
A Reddit user shares detailed speed benchmarks for Qwen3.6-35B-A3B, Qwen3.6-27B, Gemma 4 26B, and Gemma 4 31B on a 12GB RTX 4070 Super using llama.cpp with optimized settings.

How to Troubleshoot OpenClaw Setup Issues: Multi-Agent and Model Response Problems
Struggling with setting up OpenClaw? Discover common problems with multi-agent configurations and unresponsive models, and learn how to solve them.

Fixing OpenClaw Agent Autonomy Issues: Skill Files, Tool Selection, and Cron Setup
A developer shares solutions for OpenClaw agents that stop working autonomously after initial setup. Key fixes include using external skill files instead of chat instructions, replacing browser tools with API-based tools or Puppeteer scripts, and properly configuring cron jobs.