Does Claude have an export feature?

Yes, account-wide, under Settings → Privacy for individual users and Team plan Primary Owners. There is no per-conversation or per-project export.

Is my conversation data uploaded?

No. Parsing and rendering run in a Web Worker on your machine. There is a browser test that fails the release if any conversation data crosses the network.

Will this work with a Claude Projects export?

Project conversations included in the account export convert the same way.

Do I need the Obsidian plugin?

No. The output is plain Markdown and works in any vault.

Your Claude conversations, in your vault.

Tool · Claude → Obsidian

Anthropic gives you your conversations as a JSON file and stops there. Every existing route from that file to Obsidian is a command-line tool, a Python script, or asking Claude to write you one. That is fine if you live in a terminal and useless if you do not.

Drop the JSON in below. You get one Markdown note per conversation, with frontmatter, working internal links, and an index — ready to drop straight into your vault.

What you get

One note per conversation, with a filename safe on Windows, macOS, and Linux.
YAML frontmatter carrying the title, the real source timestamps, and the conversation id, so Dataview queries work.
Code blocks with their language intact, so syntax highlighting works in your vault.
Tables that are still tables, and math left as math rather than mangled into plain text.
Attachments written alongside the notes with relative links. Claude sometimes stores extracted text rather than the original file; where that happens it is labelled, not passed off as the original.
An index note linking every conversation.
A skipped report listing anything not rendered, with a reason. Your message count is shown to you at the end and it has to add up.

Getting your Claude export

Open Claude in a browser, go to Settings → Privacy → Export data, and confirm. Anthropic emails you a download link after the export is processed. The download contains your conversation and account data.

Screenshot pendingClaude settings showing the Export data control

Why not just use a script

You can, and if you are comfortable with Python you probably should. The scripts are free and several are good.

They also require you to install a runtime, trust an unreviewed repository with the full text of every conversation you have had, and fix it yourself when the export format shifts. Claude's export has no branch tree, uses ISO timestamps, and marks the user as human rather than user — small differences that quietly break tools written for ChatGPT's format and then produce output that looks fine but is wrong.

This runs in your browser with nothing installed and nothing uploaded, and the fidelity rules are tested against a fixture suite on every change.

Dropping it into your vault

The download is a folder. Move it into your vault, or point Obsidian at it as a new vault. Links and attachments are relative, so it works either way, and nothing needs a plugin to display correctly.

Screenshot pendingConverted Claude conversations open in an Obsidian vault, showing a note with a code block

Questions

4 answered

Does Claude have an export feature?: Yes, account-wide, under Settings → Privacy for individual users and Team plan Primary Owners. There is no per-conversation or per-project export.
Is my conversation data uploaded?: No. Parsing and rendering run in a Web Worker on your machine. There is a browser test that fails the release if any conversation data crosses the network.
Will this work with a Claude Projects export?: Project conversations included in the account export convert the same way.
Do I need the Obsidian plugin?: No. The output is plain Markdown and works in any vault.