How to export and save your Claude chats — and whole projects — before you lose them
Here is a situation a lot of people recognize a few months into using Claude seriously. You have a project — carefully tuned custom instructions, a dozen knowledge documents, forty-odd conversations that built on each other. One day you go back to pull a decision out of week one, and the chat list just… keeps loading. Or you hit a plan limit and switch accounts. Or a conversation you needed is suddenly not where you left it.
And then the realization: there is no "Export project" button in Claude. There is no "download all my chats." The work is in there, but it is not yours in any portable sense. For something people increasingly use to think, write, and build, that is a surprisingly fragile place to leave months of work.
"Just use Claude's built-in export"
Claude does have an export — Settings → Privacy → Export data. It is worth understanding exactly what you get, because most people try this first and bounce off it.
What lands in your inbox is a ZIP with a conversations.json in it. Open it and you do not find readable transcripts. You find every message as a node with a parent_message_uuid pointer — a linked list you have to walk to reconstruct who said what, in order. There is:
- No per-project scope. It is everything or nothing — you cannot export just the one project you care about.
- No readable format. No PDF, no Markdown, no HTML. A raw graph, not a document you can open, search, or hand to someone.
- No real attachments. Files you uploaded and documents Claude generated come through as references, not bytes.
It is a compliance export — built so the data technically left the building — not an archive you would ever actually read. For "I want to keep this," it is the wrong tool.
What actually works: build the file in the browser
The reliable approach is a browser extension that reads the conversation through the same claude.ai session you are already logged into, and renders the output locally. That is what AI Chat Archive does — and unlike most Claude exporters, its PDF export is unlimited and free, with no daily cap (how it compares). There are three scopes, depending on what you are trying to rescue:
One conversation
Open the chat, click the extension, pick a format. You get a clean PDF / Markdown / HTML / JSON / TXT file in your downloads folder — with Claude's own typography, so artifacts, code blocks and thinking steps render properly instead of collapsing into a wall of text. This is the free tier; no account, no daily ritual. Step-by-step: how to export a Claude chat.
A whole project
On any claude.ai/project/<id> page, Project Export bundles the entire project into one ZIP — the custom instructions, every knowledge-base document, every conversation in the project, and the attachments, in their original bytes. It is the cleanest way to archive a finished project or hand one off. The ZIP is laid out so a human can navigate it:
<Project Name>/
README.md ← what's here, and what Claude doesn't expose
instructions.md ← the project's custom instructions
metadata.json
files/ ← knowledge-base docs + uploaded files
_INDEX.md
conversations/
<date>_<title>/
<title>.<ext>
attachments/ ← only when "Include attachments" is on
_INDEX.md ← every conversation: OK / skipped / failed
Project export covers Markdown, HTML, JSON and TXT (PDF is single-chat only). Full walkthrough: how to export a Claude project.
Everything you have
Batch Export is the "download all my Claude chats at once" answer: one click, one ZIP, every conversation in the account as its own file plus an index of titles, dates and status. It paginates cleanly through tens of thousands of chats and skips the empty ones. Project and batch export are the paid features — everything single-chat stays free.
Where do my chats go? Nowhere.
This is the part that should make you read the permissions, not just on our extension — on any of them. An export tool by definition reads your conversations. The question is what it does next.
AI Chat Archive does the rendering in your browser and writes the result straight to your downloads folder. No server we run ever sees a conversation. There is no account, no login, no upload, no analytics, no telemetry — there is nothing to leak because nothing is collected. Concretely, the extension requests permission for claude.ai only.
Compare that to the prompt many "AI chat exporter" extensions show on install: "Read and change all your data on all the websites you visit." For a tool whose entire job is to handle your private conversations, that is the wrong amount of access — and a real, repeatedly-raised objection. We scoped ours so the question does not arise. The privacy policy names every network destination the extension ever talks to, and why.
Which format should you pick?
- PDF — sharing, printing, "freeze it exactly like this." Generated locally, Claude-style typography.
- Markdown — Obsidian, Notion, grep, feeding it back into another tool later.
- HTML — a self-contained file you can open offline and read like a webpage.
- JSON — scripting and pipelines, but structured and readable, not Claude's raw graph dump.
- TXT — the bare minimum, for search indexes and compliance archives.
The honest summary
If you only ever need the occasional single conversation, the free tier covers you completely — in every format. If you have projects or a history worth keeping as a whole, that is what the paid tier is for, and it is a one-time license, not a subscription you have to remember. Either way the value proposition is the same: your Claude work becomes something you actually hold, in a file, on your machine, that nobody else ever touched.