🟧

Export Your Entire Claude Chat History to Markdown

Claude has no full-history export button. Web2MD 2.0 lists all or selected conversations from your signed-in Claude account and saves them as structured Markdown, while preserving chat turns, code blocks, and supported Artifacts.

New: full-history export

Web2MD now loads your Claude conversation list directly — no need to queue chats one by one. Select all or filter the list, then export one .md with a table of contents or separate files organized by conversation date and source.

See the complete five-platform export guide

How to Export

  1. 1Install the Web2MD extension from the Chrome Web Store
  2. 2Sign in to Web2MD Pro and stay signed in at Claude (claude.ai)
  3. 3Open Web2MD and choose "Export all Claude conversations"
  4. 4Select every conversation or only the chats you want to back up
  5. 5Download one merged .md with a table of contents, or one Markdown file per chat with frontmatter

Claude Export Notes

  • •Bulk-export all or selected chats instead of opening them one by one
  • •Preserves Artifacts as fenced code blocks
  • •Per-chat files keep the original conversation date and source URL
  • •Works on Claude Code sessions and standalone Artifact pages, not just chats

FAQ

Can I export my entire Claude chat history at once?

Yes. Web2MD 2.0 lists the Claude conversations available in your signed-in account, then lets you select all or only the chats you need. Download one merged .md with a table of contents or one file per conversation. Bulk history export requires Pro; the $15 30-Day Pro Pass includes it without automatic renewal.

Can Web2MD export a Claude Artifact?

Yes — both kinds. Artifacts inside a conversation come out as fenced code blocks with the surrounding turns intact. A standalone Artifact page (claude.ai/code/artifact/… or a public /artifacts/ link) also converts: Web2MD reads the rendered page in your browser and emits the artifact's source, which a server-side fetcher cannot do because that page ships empty and renders client-side.

Does it work on Claude Code sessions?

Yes. Claude Code sessions and Cowork sessions convert with the same `## User` / `## Assistant` structure as a normal chat, so a debugging session keeps its code fences and turn boundaries when you move it into Obsidian or feed it back to another model.

Why not just use Claude's share link?

A share link publishes the conversation to a public URL — fine for showing someone a result, wrong for archiving private work or migrating between tools. Web2MD converts locally in your browser, so nothing is published and the output is a file you own.

Start Exporting Your Claude Conversations

Single-chat export is free. Full-history export requires Pro and is included in the $15 30-Day Pro Pass with no automatic renewal.

Install Web2MD Extension

Automate this with the web2md CLI & MCP →