How to Back Up Claude Conversations (2026)

The reliable setup is two layers. Run Claude’s official Settings → Privacy → Export data occasionally as a full-account snapshot (expect a JSON archive, hours of waiting, a link that expires in 24 hours). For everything else, use the free XWX Exporter extension to save individual conversations as Markdown or PDF in one click — and pair it with the XWX Backup desktop app to batch-export whole libraries or back up on a schedule into a local Markdown vault. Everything below walks through each layer and when it matters.

It’s not paranoia; the failure modes are ordinary:

• Deletion is permanent. Claude has no trash folder and no undo. One misclick on the sidebar and the thread is gone for good.
• Projects conversations go missing. Claude Projects are the most-organized place for your work — and users have reported chats vanishing from them after outages or sync issues.
• Accounts get locked or lost. A forgotten password with an unreachable email, an organization migration, or a workspace admin removing your seat all cut off access to history that still technically exists.
• You can’t back up selectively. Anthropic’s export is all-or-nothing — there is no "download just this Project" option anywhere in the UI.

A backup only counts if it’s a copy you control, in a format you can read, stored somewhere other than the platform itself.

The official export and the desktop app aren’t rivals — they cover different gaps. The rest of this guide sets up both.

Anthropic’s built-in export is the only first-party copy of your entire account:

1. Click your initials at the bottom-left of claude.ai.
2. Open Settings → Privacy → Export data and confirm.
3. Wait for the email — it can take from minutes to hours.
4. Download the ZIP within 24 hours; the link expires.

What’s inside is a conversations.json file: complete, structured for machines, and impractical to read. It’s the right tool for "prove my account existed in 2026" and the wrong tool for "I need last Thursday’s architecture discussion as a document." Run it occasionally — monthly, or before closing an organization — and keep the archive in cloud storage or an external drive. Then treat everything below as the working layer.

Step 1 — Install the extension. Search for XWX AI Chat Exporter in the Chrome Web Store and click Add to Chrome. No account needed.

Step 2 — Open any Claude conversation on claude.ai. The extension detects Claude automatically — including Projects, Artifacts, and organization workspaces.

Step 3 — Click the floating button and pick a format. Markdown for your notes vault, PDF for sharing or records, Word if it’s headed into a report. Code blocks, tables, LaTeX, and thinking blocks survive the trip — that’s the entire reason to skip copy-paste.

Step 4 — (Optional) Save only part of the conversation. Toggle selection mode, then click or drag across the messages you want. Useful when a 60-message thread contains one 8-message exchange you actually need.

Per-chat saves cover the highlights. When you want the whole library — a Project’s worth of conversations, or everything under one organization before access ends — the XWX Backup desktop app (Windows) does it in one run:

1. Install XWX Backup and connect it to the extension once — the pairing stays on your machine, and no password is ever involved.
2. Pick Claude from the platform list — the dot next to each platform shows its login status, and batch export covers every conversation your logged-in session can reach, including Projects and organization workspaces.
3. Choose a count — e.g. the latest 200 — or open the conversation list, filter by date or Project, and tick exactly the ones you want.
4. Start. Progress shows added / skipped / failed per item, with pause and resume. Already-saved conversations are skipped automatically, so re-running never duplicates anything.

Every conversation lands as a Markdown file with YAML frontmatter — platform, model, timestamps, message count — in a local vault at ~/.xwx-backup/, with optional PDF or Word copies alongside.

A manual export is stale the moment you finish it. The scheduled option keeps the vault current without you:

• On the Backup page, enable Scheduled export and pick an interval — every 30 minutes, hourly, every 3, 6, or 12 hours, or daily.
• Each run is incremental: it fetches only new or changed conversations, compares content hashes against the vault, and skips the rest. A typical run moves a handful of files and takes seconds.
• The app wakes the browser when a slot fires, so the browser doesn’t need to stay open between runs. If the machine was off, the slot is skipped and the next run catches up — nothing back-fills, so duplicates are impossible.

This is the layer that survives busy weeks, which is the only kind of backup that does.

A backup you’ve never opened is a hope, not a backup. Once:

• [ ] Open a restored Markdown file in any editor — confirm the content is complete and the frontmatter is intact.
• [ ] Check that code blocks and tables survived formatting.
• [ ] Copy the vault (~/.xwx-backup/) somewhere else — another drive, cloud storage, or a synced folder. One copy is not a backup.
• [ ] Re-run a batch export a week later and confirm new conversations appear without duplicates.

After that, the scheduled runs do the rest. The files are plain Markdown on your disk — no proprietary store, no export lock-in — so they remain readable no matter what happens to this app, Anthropic, or your account.

• Developers — keeping debugging threads and architecture decisions in grep-able Markdown instead of a scrollback they can’t search; pairing it with Claude Code history (see turning Claude conversations into an agent knowledge base).
• Researchers and analysts — archiving literature discussions with citations intact, per Project.
• Consultants — batch-exporting a client workspace before engagement ends and access is revoked.
• Anyone who’s lost a Project — the scheduled vault means the next outage or misclick is an inconvenience, not a loss.