Request your data export in Claude under Settings, then Privacy, then Export Data. Anthropic emails a link to a ZIP containing conversations.json. Drop that file into ChatExports and every conversation converts to Word, PDF, Markdown, CSV, or text on your own machine.
Short answer
Request your data export in Claude under Settings, then Privacy, then Export Data. Anthropic emails a link to a ZIP containing conversations.json. Drop that file into ChatExports and every conversation converts to Word, PDF, Markdown, CSV, or text on your own machine.
Step by step
Request the export: In Claude, open Settings, then Privacy, then Export Data. Anthropic queues the job and emails you when it is ready, usually within a few minutes on smaller accounts.
Download the ZIP: Open the email and download the archive. The link expires, so save the file locally rather than relying on the link later.
Drop it into the converter: Open ChatExports and drop the ZIP or the conversations.json inside it onto the page. Parsing happens in the browser tab.
Pick conversations and format: Search or filter the list, select what you want, then choose Word, PDF, Markdown, CSV, or text. Each conversation becomes its own file named from its title.
There is no download button inside Claude itself. The only complete route to your history is Anthropic's data export, and that export arrives as JSON rather than anything you can read comfortably. A downloader closes that last gap.
Why extensions fall short on Claude
Browser extensions that scrape the open conversation only see what Claude has rendered. Long threads are virtualised, so the earliest messages are not in the page at all until you scroll them back into view. That produces files missing their own beginning, which is the worst possible failure because it looks complete.
Extensions also cannot reach conversations you have not opened. If you have several hundred threads, clicking each one is not a workflow.
What the export contains
Claude's conversations.json holds every conversation on the account with:
Full message text for both sides, in order
Original timestamps for each turn
Attachment references and file names
Artifacts, including code and documents Claude generated
Project association, where the conversation sat inside a Project
Because it is the source data rather than the rendered page, nothing is truncated.
| CSV | Filtering and analysis in Excel or Sheets |
| Text | Grep, scripts, feeding into other tools |
Privacy
Your Claude history is unusually revealing: code from private repositories, drafts, strategy, sometimes client material under NDA. Uploading that archive to a server for a format conversion is a bad trade when the conversion needs no server. ChatExports reads the file from disk, converts it in the tab, and writes the results back as downloads. The archive never leaves the device.
Claude Code sessions
Terminal sessions from Claude Code are stored locally as JSONL under your home directory rather than in the web export. Those convert too, so a full record of an engineering week can include both the chat threads and the coding sessions.
Frequently asked questions
Does Claude have a built-in download button?
Not for conversations. You can copy a single response by hand, but the only complete route is the data export under Settings, then Privacy.
How long does Anthropic take to produce the export?
Usually minutes. Very large accounts can take longer, and the email arrives when the archive is ready.
Are deleted Claude chats in the export?
No. Deleted conversations are gone and no downloader can recover them. Export first if you plan to clear history.
Can I download all conversations at once?
Yes. Select all and the converter writes one file per conversation in a single pass, including archives with thousands of threads.