Export Claude chat to XML for interchange
To export Claude chat to XML, install Download Claude conversations, open the thread on claude.ai, click the orange button, choose XML, then click Export. Chrome saves structured markup for systems that require XML rather than JSON. XML export is unlimited and free, with no account. For pages, the same dropdown has PDF.
How do I export Claude chat to XML?
Open the conversation on claude.ai in Chrome, click the orange button beside the message box, choose XML, then click Export. Download Claude conversations writes the file locally. That is how you export Claude chat to XML in version 1.16.2. claude.ai has no native Save as XML control in September 2026.
- Install Download Claude conversations from the Chrome Web Store.
- Reload claude.ai and open a real conversation URL, not the empty composer home.
- Click the orange download button to the right of the message box.
- Select XML. The last format you used is remembered. Use Select to tick only the messages you want.
- Click Export. Chrome downloads the XML through the browser download API. Or click Copy to put the XML on the clipboard.
No sign-in is needed to export Claude chat to XML. Single-chat XML exports are unlimited, anonymous, and send nothing to our servers. Google sign-in is asked only for PDF and bulk Export All. Mechanics: how it works.
If the orange button is missing, you are not on a conversation URL, the tab needs a reload, or the extension is hidden in the Chrome puzzle menu. Pin Download Claude conversations, then refresh claude.ai. XML export never appears in Claude Desktop or the Claude Code terminal.
One file vs many. The orange button exports the open thread as XML. For many XML files, open View and Download All Conversations and run Export All with XML selected: one ZIP, 3 chats a day on the free plan — see bulk Export All.
When should I export Claude chat to XML?
Export Claude chat to XML when the receiving system, pipeline, or legacy tool requires XML for structured interchange. Most developers should pick JSON instead. Markdown is for human notes. CSV is for spreadsheets. PNG is a picture. XML exists in the dropdown because some tools still ingest XML and will not accept JSON.
Do not export Claude chat to XML as a “more official” JSON. Download Claude conversations applies the same parse either way. The difference is the file shape, not extra fields magically appearing. If nothing you use requires XML, skip this format and use JSON.
We ship XML because some pipelines still require it, not because we think it beats JSON for every claude.ai export. The parse is the same: messages, sender, optional thinking and artifacts. Version 1.16.2 keeps XML as one of seven formats, free with no account, not a paid add-on.
People also search Claude Chat Downloader and Claude Conversation Downloader for the same listing. Export Claude chat to XML is that orange button. Legal pages may still say Claude Exporter. Those names are this product.
What does export Claude chat to XML keep?
When you export Claude chat to XML, Download Claude conversations writes the conversation structure — messages, sender, and available metadata — as XML markup. Thinking blocks, web search sources, tool / MCP steps, and artifacts follow the same options as Markdown and JSON: Thinking is a checkbox in the export panel, and tools and sources are switched on in Settings. XML is not a stripped-down cousin of those formats.
Artifact layout is Original, Inline, Nested, or Flat in version 1.16.2. Sender filter can limit the XML to all messages, human only, or assistant only. Metadata (title, timestamps, model) can ride along. Full toggle list: Chrome extension features.
| Element | In the XML? |
|---|---|
| Messages and sender | Yes, as markup |
| Metadata | Yes, when the Metadata toggle is on |
| Thinking blocks | If the Thinking toggle is on |
| Artifacts | Yes, in Original / Inline / Nested / Flat |
| Web search sources, tool / MCP steps | If you turn them on |
| PDF pages / visual chrome | No — XML is markup; pick PDF for pages |
If the thread is long, scroll until claude.ai has loaded earlier messages before you export Claude chat to XML. The extension can only serialize what the page has rendered. A half-loaded DOM produces truncated XML.
XML vs JSON if I export Claude chat?
JSON is the common developer pick. Export Claude chat to XML only when a downstream system requires XML. Download Claude conversations does not make XML “more complete” than JSON. Both can include thinking and artifacts. Neither is Anthropic’s account ZIP. Format hub: Claude chat export formats.
| Format | Pick it when |
|---|---|
| XML | A tool or schema that requires XML |
| JSON | Scripts, diffs, most modern pipelines |
| Markdown | Human-readable notes |
| Plain text | Zero markup |
| CSV | Spreadsheets, one row per message |
| Reading, printing, sending — PDF guide | |
| PNG | A picture of the thread |
Anthropic Settings → Privacy → Export data is JSON (a ZIP), not XML. PDF from the same panel is pages for people, not markup. Neither replaces export Claude chat to XML from the orange button. Do not expect this XML to match an unpublished Anthropic schema.
The extension runs only on claude.ai in Chrome. Claude Desktop and the Claude Code terminal do not get an XML button. Claude Code on the web (claude.ai/code) runs on claude.ai, so it exports like any chat. If a thread also exists on claude.ai, open it there and export Claude chat to XML. Terminal Claude Code’s /export is a different product path.
Can I export Claude chat to XML in bulk?
Yes. Open View and Download All Conversations, set Chat format to XML, filter the table, then click Export All. Chrome saves one ZIP with one XML file per chat. On the free plan that is 3 chats a day with Google sign-in, shared with PDF. Pro at $3.99 a month or $26.99 a year removes that cap for bulk XML.
The Dashboard lists claude.ai history with search by name, filters All conversations, New, Updated, and Previously exported, Chat and Cowork tabs, and project search. New means not yet exported with Download Claude conversations. Previously exported tracks chats you already saved. Export All is one ZIP of per-chat XML files, not a mixed-format archive.
The daily limit is per account. Three chats a day on the free plan, shared with PDF. If you select 40 conversations with 3 left, the whole batch is blocked, not cut short. Select fewer or use Pro. Single XML exports from the orange button stay unlimited.
You cannot mix XML and JSON in one Export All click. Pick XML for that run. Run Export All again with JSON if you need both shapes of the same claude.ai thread; the second run counts every chat again.
Does export Claude chat to XML need Pro?
No. Single-chat XML export is free and unlimited, with no account and no counter — same as Markdown, JSON, text, CSV, and PNG. Only PDF and bulk Export All have a free limit: 3 a day with Google sign-in. Pro is $3.99 a month or $26.99 a year through Paddle. Download Claude conversations does not treat XML as a paid-only format.
Bulk XML is where the limit shows up. Each chat in an Export All ZIP uses one of the 3 a day, and the count resets at midnight UTC. Pro removes it and restores on a new computer from the same Google account. Paddle is merchant of record; this team never sees card numbers.
You do not need Anthropic’s paid claude.ai plan. You need a login that can load the conversation in Chrome. Version 1.16.2, September 2026, still does not write Word or Notion. If that list changes, this page changes the same day.
FAQ: export Claude chat to XML
These FAQ items cover export Claude chat to XML in Download Claude conversations 1.16.2: JSON comparison, bulk Export All, cost, Desktop, PDF, and Pro. Each answer is a product fact. The FAQPage JSON-LD in the page head matches this list.
Is XML better than JSON for Claude chat exports?
Not generally. JSON is the more common choice for developers. Export Claude chat to XML when your downstream system requires XML for structured interchange. The parse from claude.ai is the same; the file shape differs.
Can I bulk-export Claude chat to XML?
Yes. The same Export All flow on the Dashboard supports XML and saves one ZIP with an XML file per chat. On the free plan it covers 3 chats a day with Google sign-in; Pro at $3.99 a month or $26.99 a year is unlimited.
Is XML a paid-only format?
No. XML exports of single chats are unlimited and need no account, like Markdown, text, JSON, CSV, and PNG. Only PDF and bulk Export All have a free limit of 3 a day. Pro is $3.99 a month or $26.99 a year.
Does export Claude chat to XML match Anthropic’s ZIP?
No. Anthropic Export data is a delayed account JSON ZIP. Download Claude conversations writes a per-chat (or per-selection) XML file immediately in Chrome. They are not the same schema.
Does export Claude chat to XML create a PDF?
No. XML is markup. For pages, pick PDF in the same panel; the seven formats are PDF, Markdown, JSON, plain text, XML, CSV, and PNG. PDF needs Google sign-in and counts toward 3 a day on the free plan.
Can I export Claude chat to XML on Desktop?
No. The Chrome extension injects only on claude.ai. Claude Desktop never shows the XML dropdown. Open the same thread on claude.ai in Chrome if it exists there.
Do I need Pro to export Claude chat to XML once?
No. You need no account at all. XML exports of single chats are unlimited on the free plan. Pro at $3.99 a month or $26.99 a year only lifts the 3-a-day limit on bulk Export All and PDF.