In This Article
7 sectionsQuick answer
To export claude chats, open Settings, go to the Privacy section, and click "Export data." Anthropic then emails you a download link to a file (usually a ZIP of JSON) with your full conversation history. For a single chat, you can also copy-paste it or save it as a PDF from your browser.
Key takeaways
- The official export lives under Settings → Privacy → Export data on the web or desktop app (not mobile); Anthropic emails a time-limited download link, free on every plan.
- The account-wide export arrives as a ZIP of JSON — ideal for archiving and searching, but for a readable single chat use copy-paste or the browser's Save as PDF instead.
- Exporting a conversation saves its text only; documents, code, and artifacts Claude created have their own download and copy controls in the interface.
- On Team and Enterprise plans the account-wide export is usually run by the organization's primary owner, so individual members may not see the option.
- Always export and verify the file before deleting chats or your account — once the account is gone, so is your access to those conversations.
Export steps verified 31 July 2026 against the Claude Help Center.
If you have been talking to Claude for months, those conversations add up to something valuable: research threads, drafts, code, and ideas you may want to keep. Whether you are backing things up, keeping records, moving notes into another tool, or getting your data out before you close your account, it helps to know exactly how to export claude chats and what each method actually saves.
This guide walks through every real option, from the official account-wide data export to quick one-chat tricks, so you can pick the right one for the job. Claude currently spans models like Opus 5 and Sonnet 5, and the export works the same regardless of which one you chatted with — the request itself takes under 30 seconds to submit, and these steps are reviewed regularly so they stay accurate.
Key takeaway
Claude's official account-wide data export lives under Settings → Privacy → "Export data," where Anthropic emails you a ZIP of JSON containing your full conversation history — the request takes under 30 seconds to submit and is free on every plan, from Free to Pro ($20/mo) and Max ($100/mo).
Why you might want to export claude chats
Four reasons dominate: keeping a backup independent of your account, holding records for client or research work, moving notes into another tool, and getting a copy out before you delete the account or cancel a plan.
There are a few common reasons people decide to export claude chats:
- Backup and peace of mind. Conversations can hold work you would hate to lose. A downloaded copy lives on your own machine, independent of your account.
- Keeping records. For client work, research, or compliance, you may need an archive of what was discussed and when.
- Moving to another tool. Maybe you want your notes in Notion, Obsidian, or a plain folder of files. A local export is the starting point.
- Before you leave. If you are about to delete your Claude account or cancel your Claude subscription, export first. Once an account is gone, so is your access to those chats. Getting a copy out beforehand is the safe move.
Whatever the reason, the good news is that your Claude conversations are your data, and Anthropic gives you an official way to take them with you.
The official way to export claude chats (all conversations)
Run it from the web or desktop app — mobile does not offer it. Open Settings, go to Privacy, click Export data, then wait for the emailed download link, which is time-limited and tied to your signed-in account.
The main, supported method to download everything at once is the account data export, run from your settings. This is the option to reach for when you want your complete history rather than a single thread.
Here is the five-step flow to export claude chats through the official tool:
- Open Claude on the web app or Claude Desktop. (The export is run from these; the mobile apps for iOS and Android do not offer it.)
- Click your initials or profile in the lower-left corner, then choose Settings.
- Go to the Privacy section.
- Click Export data. You may be asked to confirm and, in some cases, choose a time range.
- Wait for the email. Anthropic processes the request and sends a download link to the email address on your account.
The export is not instant. It can take some time to prepare, and it arrives by email rather than downloading straight away in the browser. When the link comes through, it is time-limited and tied to your signed-in account, so download the file reasonably soon after you get the email rather than leaving it for weeks.

Because exact menu labels, file formats, and timing can change as the product evolves, treat the steps above as the shape of the process rather than a pixel-perfect script. If a label has moved, the Claude Help Center and Anthropic's Privacy Center are the authoritative places to confirm the current wording and requirements.
What the export includes and its format
The account export is designed to hand back your data, so it typically bundles your conversation history together with the account information tied to your profile. In practice this usually arrives as a compressed file (a ZIP) containing your chats in a structured format such as JSON.
When we ran the official export on our own account to archive a stack of research threads, the ZIP came back as JSON keyed by conversation — perfect for grepping across everything from a terminal, but genuinely unpleasant to skim by eye. The lesson we took from it: use the full export for the archive-everything, keep-it-searchable job, and fall back to print-to-PDF for the handful of individual chats you actually want to sit down and re-read. Trying to read the raw JSON as if it were a transcript is the fastest way to conclude the export "didn't work" when it worked fine.
JSON is great for archiving and for feeding into other tools, but it is not a pretty reading format. If your goal is a nicely formatted, human-readable copy of one conversation, the copy-paste or print-to-PDF methods below will serve you better than digging through the raw export.
One more note for teams: on Team and Enterprise plans, the account-wide export is usually handled by the organization's primary owner rather than each individual member, so if you are on a shared plan and do not see the option, that is why.
Quick methods to download a single Claude chat
For one conversation, skip the full export. Copying the text into a document takes seconds and works everywhere, while the browser print dialog and Save as PDF produces a clean, shareable file that mirrors what is on screen.
Not everyone needs the whole archive. Often you just want one conversation saved. These manual methods are faster than requesting a full export.
Copy and paste a conversation
The simplest way to download a claude chat is old-fashioned copy-paste. Open the conversation, select the text you care about, copy it, and paste it into a document, note, or email. It takes seconds, works everywhere, and gives you a plain-text record you fully control. The trade-off is that formatting can get messy for very long threads, and you have to do it one chat at a time.
Print or save as PDF
For a clean, readable copy of a single conversation, use your browser's print dialog. Open the chat, press Ctrl+P (or Cmd+P on a Mac), and in the destination menu choose Save as PDF. You get a self-contained file that looks close to what you see on screen — ideal for sharing a conversation, attaching it to a record, or keeping a tidy snapshot. This is our go-to when someone asks "how do I download a Claude chat" and just wants one nice file.

Downloading files and artifacts Claude created
Exporting a conversation saves its text, not its outputs. Documents, code, and artifacts carry their own download and copy controls in the interface, which is the cleaner route when you want the deliverable rather than the discussion.
There is an important distinction here. Exporting a conversation saves the text of the chat. But if Claude generated a document, a block of code, or an interactive artifact, those often have their own download or copy controls right in the interface.
So if what you really want is the spreadsheet, the script, or the report Claude built — not the surrounding discussion — look for the download or copy button on that specific output rather than exporting the entire chat. For anything Claude produces as a standalone deliverable, the artifact's own controls are the cleanest way to get the file out. This matters most for makers who lean on Claude for real work; if that is you, our guide on how to use Claude AI and Claude Projects covers organizing that output before you ever need to export it.
Third-party browser extensions
One-click Markdown and PDF exporters exist and can be genuinely convenient for bulk-saving readable copies. The catch is that anything able to export your chats can also read them, so check the maker, reviews, and permissions first.
You will also find browser extensions that promise to export claude chats to Markdown or PDF with one click. These can be genuinely convenient, especially for bulk-saving individual conversations in a readable format.
The catch is trust. Any extension that can read and export your chats can, by definition, see your chats. Before installing one, check who makes it, read recent reviews, look at the permissions it requests, and be cautious about anything handling sensitive conversations. We would not name-drop a specific tool here, precisely because the safe choice depends on vetting it yourself at the moment you install it. When in doubt, the official export plus print-to-PDF covers almost every real need without granting a third party access to your account.
Which method should you use?
Match the method to the outcome: the official export for a full backup or account closure, copy-paste for a fast plain-text record, print-to-PDF for a readable single chat, and the artifact controls when you only want the file.
Here is a side-by-side view so you can match the method to what you actually want to walk away with.
| Method | What it saves | Best for |
|---|---|---|
| Official data export (Settings → Privacy) | All conversations + account data, as a file (often ZIP/JSON) | Full backup, records, leaving your account |
| Copy and paste | The text of one chat you select | A fast, plain-text record of a single thread |
| Print / Save as PDF | One conversation as a formatted PDF | A clean, readable, shareable single-chat copy |
| Download artifact/file | A specific code file, document, or artifact | Getting a deliverable Claude built, not the chat |
| Browser extension (vetted) | Individual chats to Markdown/PDF | Bulk-saving readable copies (vet it first) |
Keeping your exported data safe
The download is an unencrypted copy of everything you discussed. Move it to an encrypted drive or trusted cloud folder rather than leaving it in Downloads, and confirm it opens cleanly before deleting any history.
Once you have your file, remember what it is: a plain, unencrypted copy of everything you discussed with Claude. Store it somewhere sensible — an encrypted drive or a trusted cloud folder — rather than leaving it in your Downloads folder forever. If the conversations contain personal or work-sensitive details, treat the export with the same care you would any other private document. Anthropic's Privacy Policy explains how your data is handled while it lives on their systems; your local copy is yours to secure once it leaves them.
And if you exported specifically so you could clean house, do it in the right order: get the export, confirm the file opens and looks complete, then proceed to clear out your conversation history or delete your Claude account. If you are worried about losing project context in particular, it is worth reading how to recover deleted Claude projects before you remove anything, since recovery options are limited once data is gone.
Frequently Asked Questions

Written by
Edith
Writing about Claude and the Anthropic toolkit — models, Claude Code, pricing, features, and fixes, in clear, practical, hands-on guides tested by daily use.
View all posts →


