Add to ChromeClaude conversation extractor for clean files
A Claude conversation extractor reads the chat open on claude.ai and writes Markdown, JSON, text, XML, or PNG instead of a copy-pasted wall. Download Claude conversations is that Chrome extractor: orange button, then Export. It does not run in Claude Desktop or Claude Code. Three extractions are free; Pro is $3.99/mo or $26.99/yr.
What is a Claude conversation extractor?
A Claude conversation extractor parses the rendered claude.ai thread and writes a real file. Download Claude conversations is that Chrome tool: it is not a screenshot utility and not Anthropic’s account ZIP. People type extract, export, or download for the same orange button on claude.ai.
Developers and researchers often search Claude conversation extractor because extract implies structure: sender, content blocks, fences, tables, artifacts. Download Claude conversations does that parse in the tab you already opened. Reviewers may say Claude Conversation Downloader or Claude Exporter; those labels still mean this Chrome listing, rated 5.0 on the Chrome Web Store.
The extractor is not a Claude Desktop plugin and not a Claude Code CLI. If the query was terminal history, use /export — guide: Claude Code export. If the query was the Mac/Windows app, see export Claude Desktop chat. This page is claude.ai in Chrome only.
Same button, different verbs. Extract Claude chat, export Claude chat, and download a Claude chat all land on Download Claude conversations. The product-shaped export write-up is export Claude chat. This guide stays on what the extractor reads and what it drops.
How do I extract a Claude chat on claude.ai?
Install Download Claude conversations, open the conversation URL on claude.ai, click the orange button beside the message box, pick a format, and click Export. The Claude conversation extractor writes the file locally through Chrome’s download API. Google sign-in runs once, before the first extraction, to count the 3 free exports.
- Add the Chrome listing (Download Claude conversations, version 1.13.0 as of September 2026).
- Reload claude.ai and open the thread — the extractor needs a conversation URL, not the empty home composer.
- Click the orange button to the right of the message box.
- Choose Markdown, JSON, plain text, XML, or PNG.
- Click Export. The Claude conversation extractor does not upload the chat body to our servers.
If the orange button is missing, pin the extension, refresh the tab, and confirm the URL is a real chat. The Claude conversation extractor injects only on claude.ai. It will not appear in Claude Desktop, in Claude Code, or on other websites. Incomplete files usually mean the long thread had not finished rendering; scroll or wait, then extract again.
The extractor remembers the last format you used. If you wanted Markdown and received JSON, open the dropdown before Export. Hitting the 3-export gate shows a Pro prompt at $3.99/mo or $26.99/yr — that is expected, not a failed parse. Google sign-in on first extract Claude chat is required so a reinstall cannot reset the free count.
Need the step list with print and ZIP alternatives? Use how to download a Claude chat. Need method comparison including Print → Save as PDF? Use how to export a Claude chat. This extractor page assumes you want a structured file of the open thread.
What does a Claude conversation extractor pull?
The Claude conversation extractor reads the message tree claude.ai already drew: human and assistant turns, fenced code with language tags, tables, links, and optional thinking. Artifact layout is Original, Inline, Nested, or Flat. Copy-paste from the same page drops that structure; the extractor keeps it in Markdown, JSON, and XML.
Thinking blocks are a toggle. Turn them on when you need Claude’s visible reasoning in the extracted file; leave them off when you only want the final answer. Metadata can include titles, timestamps, and model. Sender filter can keep all messages, human only, or assistant only. Those controls live in the same widget as format. Feature list: features.
The extractor reads the conversation the page already rendered in your claude.ai tab. Code fences, tables, and artifact layouts (Original, Inline, Nested, Flat) are parsed there, then the file is built locally. We do not ship PDF.
PNG is the exception: it is a picture of the thread, not a parse you can grep. Use PNG when you need a visual Claude conversation extractor output for a ticket or a slide. Use Markdown or JSON when you need searchable text. Neither PNG nor Markdown is a PDF; print remains the PDF-like workaround on print / PDF.
The extractor cannot pull a chat Chrome has never loaded. Private mode, a logged-out tab, or a conversation that exists only in Claude Desktop will not yield a file. Open the thread on claude.ai while signed in, then run the Claude conversation extractor. Offline export works only after that page has loaded; there is still no server round-trip to generate the bytes.
Which formats can a Claude chat extractor write?
Markdown, JSON, plain text, XML, and PNG — the same five whether you extract one Claude chat or run Export All. Download Claude conversations does not add Word, Notion, or native PDF in 1.13.0. Format choice does not change the 3-export quota; each finished file counts as one extraction.
| Format | Extractor result | Typical next step |
|---|---|---|
| Markdown | Readable .md with fences and tables | Notes vault — Markdown |
| JSON | Message tree for scripts | Parse or diff — JSON |
| Plain text | Linear chat, no markup | Paste into anything — formats |
| XML | Structured markup | Interchange — XML |
| PNG | Image of the thread | Visual copy — PNG |
JSON from the Claude conversation extractor is not the same shape as Anthropic’s account-level Export data ZIP. The extractor file is per chat (or per bulk selection) from the page. The ZIP is a delayed account archive. Do not feed one into a script expecting the other. Hub: all formats.
Can I extract Claude conversations in bulk?
Yes. Open View and Download All Conversations, filter, then click Export All. The Claude conversation extractor writes one file per selected chat. Each file spends one of the 3 free exports unless the account is on Pro at $3.99/mo or $26.99/yr.
Filters on the browse page: All, New, Exported, and Project. New means the Claude conversation extractor has not saved that chat yet. Exported marks history you already extracted so a later bulk run can skip it. Project matches claude.ai project grouping. Search finds conversations by name before you commit Export All.
Bulk is not a lesser parse. Thinking, Metadata, artifact layout, and sender options match the single-chat widget. Walkthrough with quota warnings: bulk Export All. If you wanted one emailed ZIP of the entire account, that is Settings → Privacy → Export data, not this extractor.
Three free extractions total. Export All does not get a separate allowance. Selecting 25 chats spends 25 exports if every file completes. Use New/Project filters, or upgrade to Pro ($3.99/mo or $26.99/yr) before a large Claude conversation extractor run.
Claude conversation extractor vs copy-paste?
Copy-paste is fine for one short Claude answer and fails on code and tables. Anthropic Export data is the account backup ZIP. The Claude conversation extractor sits in the middle: this thread or a bulk selection, structured file, immediately, on claude.ai in Chrome.
| Method | Best for | Output | Limit |
|---|---|---|---|
| Claude conversation extractor | This chat or bulk, now | MD / JSON / TXT / XML / PNG | 3 free exports; Google sign-in; Chrome on claude.ai |
| Anthropic Export data | Full account backup | JSON ZIP via email | Slow, not per-chat Markdown |
| Copy-paste | One short answer | Selected text | Code and tables break |
| Print to PDF | Visual page copy | PDF of the webpage | Sidebar; fences often split |
Print is not an extractor. It captures the webpage, including chrome you do not want in a notes file. The Claude conversation extractor strips that chrome and keeps message structure. If you still need a PDF after extracting Markdown, convert the .md yourself; we do not emit PDF from the widget.
Is a Claude conversation extractor safe to use?
This Claude conversation extractor uses your existing claude.ai session the same way the site does. It does not automate the account or send chat bodies to our API. Google sign-in counts 3 free exports and restores Pro. Paddle handles payment. We are not Anthropic; their Terms still apply.
A Cloudflare Worker sees subscription status: free-export count and Pro or not. It does not receive the extracted Markdown, JSON, text, XML, or PNG. Files never leave the browser except into Chrome’s download folder. Full boundary: how it works. Anyone asking “is a Claude chat extractor safe” should look at that split — billing on the worker, chat in the tab.
We cannot promise “zero network.” claude.ai, Google, and the worker all exist. We can say chat bodies are not uploaded to us. Follow Anthropic’s Terms of Service. Download Claude conversations is an independent Chrome extension, not an official Anthropic product. Support email is on the site footer.
Mobile browsers and Claude Desktop are unsupported. A Claude conversation extractor that is a Chrome content script cannot run there. Do not expect a Safari or Firefox listing from this page in September 2026. Use desktop Chrome on claude.ai. Team policies that block extensions will also block this extractor.
FAQ: Claude conversation extractor
These FAQ items answer Claude conversation extractor and extract Claude chat questions: bulk Export All, Desktop, Claude Code, PDF, Google sign-in, and the 3-export quota. Answers reflect extension 1.13.0 on claude.ai. The FAQPage schema in the document head matches this list.
What is a Claude conversation extractor?
A tool that reads a claude.ai conversation you have open and writes Markdown, JSON, plain text, XML, or PNG. Download Claude conversations adds the orange button that does this parse locally in Chrome.
Is extract Claude chat different from export Claude chat?
No — same job, different verb. Extract, export, and download all hit the same orange button and the same five formats on claude.ai. This page stresses what the parser keeps.
Can I extract a Claude chat without installing anything?
Only by copy-paste, which loses fences and tables, or by Anthropic Export data, which is an account ZIP. A structured Claude conversation extractor needs to read the page; that is the Chrome extension.
Does the extractor support bulk conversation extraction?
Yes. View and Download All Conversations, then Export All. Each file counts toward 3 free exports. Pro at $3.99/mo or $26.99/yr removes the cap. Filters: All, New, Exported, Project.
Is a Claude chat extractor safe to use?
This one reads the logged-in claude.ai session and builds files locally. Conversation text is not sent to our servers. We are not Anthropic; you remain under their Terms of Service.
Do I need Claude Pro to extract a chat?
No. Any claude.ai plan that can open the thread in Chrome works. The first 3 Claude conversation extractor files are free on our side. Anthropic’s paid plan is unrelated to our 3-export quota.
Does the Claude conversation extractor run in Desktop?
No. Claude Desktop never gets the orange button. Open the same chat on claude.ai if it syncs, or copy-paste / official ZIP. The extractor is Chrome-only for claude.ai.
Can a Claude conversation extractor write PDF?
No. Formats are Markdown, JSON, plain text, XML, and PNG. Print the claude.ai page if you need a PDF-like snapshot. PNG is an image, not a PDF.
Does extract Claude chat work in Claude Code?
No. Claude Code uses /export or JSONL on disk. This Claude conversation extractor is a Chrome content script for claude.ai, not a terminal hook.
How many free extracts does the extractor allow?
Three per Google-signed account, shared with Export All. Reinstall does not reset the count. Pro restores from the same Google account via Paddle billing.
What does the Claude conversation extractor skip?
Page chrome, the composer, and anything not rendered in the conversation. It also skips chats that never loaded in Chrome. Claude Desktop-only threads and Claude Code JSONL are out of scope.