How to export your Claude projects: every method (2026)
The short version: Claude.ai has no per-project export button. Your options are Anthropic's account-wide data export (one big dump of everything, in JSON), copying things out by hand (fine for a single short chat), or a browser extension that exports one project at a time as readable files. Each is covered below, including where it falls short.
If you keep real work in Claude Projects, you eventually want a copy of it on your own machine: the conversations, the project knowledge files, the custom instructions, and the artifacts Claude has written for you. Perhaps you are archiving finished work, moving to another tool, or you simply do not want months of thinking to live only inside one vendor's account. This guide covers every way to get that copy, honestly, including the limits of each.
Method 1: Anthropic's built-in account export
Anthropic provides an official export of your data. To use it, open claude.ai, click your initials in the corner, choose Settings, then Privacy, and look for the Export data button. The exact menu wording moves around as Anthropic updates the interface, but the export lives in your account settings.
After you request it, Anthropic emails you a download link. What arrives is a zip of JSON files covering your whole account, chiefly your conversation history.
What it is good for: a complete, official record of your account, straight from Anthropic. If you want a legal-grade copy of everything, start here. It is free and takes two clicks plus a wait for the email.
Where it falls short:
- It is one whole-account dump. You cannot export a single project, and nothing is organised by project. Finding one project's conversations means digging through the JSON yourself.
- It is JSON built for machines, not reading. There are no Markdown transcripts you can open and skim.
- Artifacts are not saved as separate, usable files. The HTML page or script Claude wrote for you stays buried inside conversation data rather than arriving as an .html or .py file.
- You wait for an email rather than getting the file straight away.
Method 2: Copy and paste by hand
The zero-tooling option: open each conversation, select the text, and paste it into a document. Open each artifact, copy its contents, and save it as a file with the right extension. Download each knowledge file, or copy its text out of the project's knowledge panel.
When it is fine: you need one conversation, or one artifact, right now. For a single short chat this is genuinely the fastest method, and it needs no tools and no trust in anything third party.
When it breaks down:
- Volume. A project with thirty conversations and a dozen artifacts turns into an afternoon of clicking, and in practice things get missed.
- Long chats. Claude.ai loads long conversations in sections as you scroll, so a single select-all often silently misses earlier messages.
- Formatting. Code blocks, tables and lists tend to lose their structure on the way into your document.
- Artifacts that went through several revisions: you have to check you copied the final version of each one.
Method 3: The Backup for Claude extension
Full disclosure: this is our extension, and this site is its home. With that said, here is plainly what it does and does not do.
Backup for Claude is a Chrome extension that exports one Claude project at a time as files on your computer. You open claude.ai, click the extension, pick a project, and it saves:
- a Markdown transcript of every conversation in the project, readable in any text editor,
- a JSON file with the complete structured data, including edits and branches,
- the project's custom instructions and knowledge files,
- each artifact as its own file with the right extension, an .html file as .html, a Python script as .py, in their final versions.
Everything runs inside your browser using the Claude session you are already signed in with. There is no server behind it and your data is never uploaded anywhere, which is also the promise in our privacy policy.
The honest limits:
- The free version exports a single project to Markdown. The one-time Pro upgrade adds JSON, artifact files, and backing up all projects in one go.
- It is Chrome only (and Chromium-based browsers that accept Chrome extensions).
- It reads the same data your browser already loads, through claude.ai's own interface. That interface is not officially documented, so when Anthropic changes it the extension needs an update. We maintain it actively, but that dependency is real and you should know about it.
Comparison at a glance
| Anthropic account export | Copy and paste | Backup for Claude | |
|---|---|---|---|
| Scope | Whole account only | Whatever you copy | Per project, or all projects (Pro) |
| Format | JSON dump | Whatever you paste into | Markdown, JSON (Pro) |
| Artifacts as files | No | One at a time, by hand | Yes (Pro), final versions |
| Knowledge files | Not as separate files | One at a time, by hand | Yes |
| Effort | Two clicks, then wait for an email | High, grows with project size | A few clicks, immediate |
| Cost | Free | Free | Free tier; one-time payment for Pro |
| Official | Yes | n/a | No, independent tool |
Which should you use?
- You want everything, officially, and do not mind JSON: use Anthropic's account export. It costs nothing and comes straight from the source.
- You need one conversation or one artifact: copy and paste. Do not install anything for a one-off.
- You want a specific project as readable files, with its artifacts and knowledge intact: that is the gap the extension exists to fill.
These also combine sensibly: an occasional account export as a belt-and-braces archive, plus per-project exports for the work you actually revisit. And if your goal is moving a project into another tool, we have a separate guide on moving your Claude projects to ChatGPT.
Frequently asked questions
Does Claude have a project export?
Not per project. Claude.ai offers an account-wide export in Settings under Privacy, which sends you a zip of JSON files covering your whole account. There is no built-in button to export a single project or to get readable Markdown files. For per-project export you need to copy things out manually or use a browser extension.
How do I save Claude artifacts as files?
Inside claude.ai you can open an artifact and download or copy it, one artifact at a time. That works fine for one or two. For a whole project's artifacts in one go, saved with correct file extensions in their final versions, use Backup for Claude, which writes them into an artifacts folder alongside the transcripts. The official account export does not produce separate artifact files.
Can I export a single conversation?
There is no one-click single-conversation export in any method, ours included. Your practical options: copy and paste the conversation (best for short chats, but note that very long chats load in sections as you scroll, so check you got all of it), or export the project that contains it and take the conversation from the Markdown transcript. The account export also contains every conversation, but inside a JSON dump you would need to search through.