Claude moved Projects to claude.ai/code — here’s how to keep a complete copy
You open a project you’ve worked in for months and Claude greets you with a tour: “I moved everything from your project here.” The address is now claude.ai/code/project/…. Your old chats sit in a Threads panel; the knowledge files you uploaded are in a Library; the Cowork tasks you ran are in there too; and when you pick up an old chat, the conversation carries on as a thread.
It’s a better workspace. It’s also a new shape, and anything that saved your project the old way — one transcript per chat plus a folder of knowledge files — now misses part of it. There is still no “Export project” button in Claude.
What a complete copy of a new-style project contains
- Instructions — the project’s custom instructions.
- The Library — every file in it, byte for byte, in its folders.
- The project conversation — the main thread where Claude coordinates the project.
- Every thread — and when a thread continues an older chat, that chat’s original messages come first, then the new replies.
- Imported chats you haven’t continued yet, each on its own — nothing appears twice.
- Cowork tasks — the full transcript plus the files the task produced.
- Files Claude attached to a reply — saved with the thread they belong to.
See it on a demo project
Below is the real extension on a fictional project (“Aurora Notebook launch”). Click the button the way you would in Claude; the archive tree at the end is the actual ZIP it produced.
See exactly what you get
Pick a scenario, click the button — and see the real result.
A whole Claude project, one ZIP
Works on the new Claude Projects (claude.ai/code/project) and classic projects alike.
- Instructions and Library files, byte for byte
- Every thread, imported chat and Cowork task
- Files Claude attached to its replies
Demo with fictional data — every button, progress bar and file shown is the extension’s real output.
The ZIP, folder by folder
Aurora Notebook launch/
README.md ← what’s here, and what Claude doesn’t expose
metadata.json
instructions.md ← the project’s custom instructions
files/ ← the Library, original bytes, folders kept
aurora-product-brief.pdf
launch-plan.csv
launch-checklist.md
conversations/
…_Aurora Notebook launch — Project conversation/
…_Launch plan/ ← a thread that continues an older chat
Launch plan.html
outputs/launch-checklist.md ← the file Claude attached to its reply
…_Beta feedback themes/
…_Pricing ideas/ ← an imported chat
…_Summarize beta survey/ ← a Cowork task
outputs/beta-survey-themes.csv
_INDEX.md ← every conversation and whether it exported OK
Pick Markdown for Obsidian or Notion, HTML to read offline, JSON for scripts, or TXT. Step-by-step instructions live in the docs: how to export a Claude project. Classic projects at claude.ai/project/… export the same way — and now include their Cowork tasks too.
What isn’t in the ZIP
Being clear about the gaps matters more than a long feature list. Automatic project Memory, scheduled-task definitions and connector settings aren’t exported. A file that only ever lived in a finished task’s sandbox — never delivered and never saved to the Library — can’t be recovered, and the archive says so in _INCOMPLETE.md instead of silently leaving it out. Files attached to replies are saved as they are in the Library when you export.
One thread at a time, for free
Whole-project export is part of the paid plan. Any single thread — including its original chat context — exports free as PDF, Markdown, HTML, JSON or TXT, so you can check the result on your own project before deciding.
Questions
Can I export the new Claude Projects (Beta)?
Yes. Open the project at claude.ai/code/project/<id>, click the AI Chat Archive “Export project” button and pick Markdown, HTML, JSON or TXT. You get one ZIP with the instructions, every Library file, the project conversation, every thread, imported chats and Cowork tasks, built locally in your browser. Project export is a paid feature; a single thread exports free.
Are the chats from before the upgrade included?
Yes. A thread that continues an older chat exports with that chat’s original messages followed by the new replies. Imported chats you haven’t continued are exported on their own, so nothing appears twice.
Does the export include the project’s Library files?
Yes. Every accessible Library file is saved in its original bytes under files/, keeping its folders. Files Claude attached to a reply are also saved with that thread, as they are in the Library at export time.
Is Claude’s project Memory included?
No. Automatic project Memory, scheduled-task definitions and connector settings aren’t part of the export. Instructions, Library files, conversations, threads and Cowork tasks are.
Can I export just one thread?
Yes, for free: open the thread and use the Export button to save it as PDF, Markdown, HTML, JSON or TXT.