Just the projects you need.
Choose one project or many instead of sorting through a whole-account archive.
Your projects. Your files.
Claude Project Exporter
Take the whole project with you.
Export Claude & ChatGPT Projects.
Claude today. ChatGPT coming soon.
Save your classic Claude projects as local ZIP archives: conversations, knowledge files, instructions and indexes, together.
MVP features are free. Chrome Web Store link coming soon.
Project export / Claude
Select what matters.
Projects across your workspaces
Field notesPersonal workspace · selected
Product researchTeam workspace · selected
↓ Field notes.zip
Field notes--project-id/
├ conversations/ → Markdown + JSON
├ files/ → original knowledge files
├ instructions.md
└ index.md + index.json
├ conversations/ → Markdown + JSON
├ files/ → original knowledge files
├ instructions.md
└ index.md + index.json
Markdown + raw JSONObsidian-friendlyLocal processingFree MVP export
Leave the copy-paste behind
A project is more than a chat.
Your research lives across conversations, uploaded knowledge and instructions. Keep that context together when you make a backup or move your workflow.
Bring the supporting files.
Export project instructions and original knowledge files where Claude exposes them.
Open it in your own tools.
Readable Markdown, raw JSON and optional Obsidian folders. Files you can organize yourself.
Built for project export
The useful pieces, together.
Choose across workspaces
Load accessible classic Claude projects and multi-select what to export.
Two transcript formats
Markdown for reading and raw JSON for further processing, in each project archive.
Knowledge & instructions
Original knowledge bytes, instructions and indexes with final paths and outcomes.
Obsidian, ready
YAML frontmatter and wikilink indexes, organized in distinct project folders.
Keep your place
Rate-limit aware retries and confirmed-download checkpoints for interrupted exports.
Room for large projects
Automatic ZIP parts around 500 MiB, with an archive manifest and merge guide.
Classic Projects only. Memory, Beta/Cowork and conversation attachment bytes are not included. See scope and limits →
A different export workflow
Pick projects. Keep readable files.
Official account export is useful for an account-wide request. This extension is built for taking selected projects into your own workflow.
| Your workflow | Official Claude export | Claude Project Exporter |
|---|---|---|
| Choose the scope | Account data and chat history; workspace access rules apply. | Select individual classic projects across accessible workspaces. |
| Get the files | An email link after processing. | Local ZIP downloads from your signed-in browser. |
| Keep working | Download the account export before its email link expires. | Markdown + JSON, instructions and accessible original knowledge files. |
| Use in Obsidian | An account archive to organize yourself. | Optional YAML frontmatter, project folders and wikilink indexes. |
Official workflow: Claude’s export documentation. Read the full comparison →
How it works
From project to local archive.
Start in Claude.
With the extension installed, open claude.ai while signed in. Click Export Projects or the toolbar icon.
Select your projects.
Load projects across workspaces. Select the ones you need and optionally enable Obsidian friendly.
Keep the tab open.
Allow downloads and save your ZIPs. Retain every part and use Resume if interrupted.
Free first
Start with the free MVP.
Pro checkout coming — MVP features available now (free). These are planned Pro prices, not a current export paywall.
$7.99 / month
A month at a time.
For a flexible project-export workflow.
$49 / year
Make backup a habit.
A yearly option for ongoing work.
$79 once
A one-time option.
A planned lifetime license for project export.
No checkout or payment collection. View the pricing preview →
Keep it local
Your chats don’t need another server.
The exporter uses your signed-in claude.ai session. Export processing stays in your browser, and ZIPs download to your machine.
No API key. No telemetry. No chat upload to us.
Privacy & permissions →Know what you’re keeping.
The extension reads from Claude to create your export. Local checkpoints retain project and filename metadata so you can resume; transcript and file bodies are not stored there.
Missing originals are reported as failures. A preview is never passed off as your original file.
Next on the roadmap
ChatGPT Projects.
Coming soon.
One project-export workflow is the goal. Classic Claude Projects is available in the MVP; the ChatGPT adapter is planned.
Explore the ChatGPT roadmap →Classic Claude ProjectsMVP available
ChatGPT ProjectsComing soon
Pro checkoutPlanned
A few useful answers
Before you export.
Do I need an API key?
No. The extension reads projects through your existing signed-in claude.ai browser session. It does not ask for an API key or your account password.
Can I put the export in Obsidian?
Yes. Enable Obsidian friendly before exporting, then extract into your vault root. Notes include YAML frontmatter and indexes use wikilinks. Project and item identity suffixes keep same-name content separate. Extract all ZIP parts into the same destination using the merge guide.
Does it export ChatGPT Projects?
Not yet. ChatGPT Projects is Coming soon. The current provider supports classic Claude Projects; no ChatGPT access or API key is requested today. There is no announced release date.