How to Export Your Claude History and Keep It Usable
Direct answer: In Claude on the web or Desktop, use Settings → Privacy → Export data. Download the emailed export while signed in. Keep the original, save important deliverables separately, and turn a supported conversation JSON file into readable Markdown with Multiplist's Conversations Unpacker.
A good Claude conversation can hold the thinking behind an entire project. Getting a copy should help you return to that work, not leave you wondering which download contains what.
Open Multiplist's Conversations Unpacker when your export is ready. It converts supported Claude conversation data into readable files. You can keep those files yourself, or save selected work in Multiplist's portable memory vault so connected assistants can retrieve it later. Conversion and vault storage are separate.
The first useful question is: what are you trying to keep? A conversation, a finished document and Claude's remembered context need different treatment.
Claude documentation and the unpacker page checked October 25, 2026.
# Download your conversation history
For an individual Free, Pro or Max account:
- Open Claude on the web or in Claude Desktop.
- Open Settings → Privacy.
- Choose Export data.
- Wait for the email sent to your account address.
- Follow its link while signed in and save the download.
Generation can take a little time. The link expires 24 hours after delivery; request another export if it expires. Native iOS and Android apps cannot start the export. Anthropic's personal export instructions
Keep the original download unchanged, with its export date. Work from a copy when extracting or converting files. Avoid placing a whole account archive in a public repository or broadly shared folder.
# If the export button is missing
Check your role before searching for another download tool:
| Your situation | What to check |
|---|---|
| Using the native mobile app | Open Claude web or Desktop |
| Team or Enterprise member | Ask whether an Owner has enabled member exports |
| Team or Enterprise Primary Owner | Use Organization settings → Data and privacy → Export Data |
Member exports cover the user's own chats but omit uploaded-file contents. Primary Owners export organization data rather than using the personal button. Follow your organization's rules before taking work outside its systems. Organization export settings and roles
A missing button is not a reason to give an unfamiliar service your Claude password or session cookies.
# Save the finished files as well as the conversation
Imagine a fictional project conversation called Workshop outline. You want three things from it:
- The discussion that explains the audience and structure.
- The final outline you selected.
- A presentation file Claude created.
A readable transcript helps with the first two. It does not establish that the presentation's actual file bytes are included.
Anthropic's organization export guidance explicitly excludes generated Word, Excel, PowerPoint and PDF files. Download needed deliverables from the chat while they remain available. That guidance also excludes material deleted before the export, including deletions under retention settings. What organization exports leave out
For any archive, check the actual contents before deleting chats, leaving a workspace or discarding original files. Keep a small project folder containing the transcript, the deliverable and a note identifying which version you intend to use. An attachment name or link in the transcript is not the attachment itself.
# Make the downloaded conversations readable
If your download contains an archive, extract it first. Multiplist's current standalone unpacker accepts a supported conversations.json file, rather than the whole ZIP. Its page identifies Claude exports as a supported format; Anthropic's personal export instructions do not promise a fixed filename or archive layout.
At the unpacker, select the JSON file, enter the email address requested by the form and choose Unpack my conversations. Download the resulting ZIP and open a Markdown conversation from it. If your export has a different structure, check compatibility rather than renaming a file and assuming it will work.
This is a hosted upload, not a browser-only conversion. Review Multiplist's privacy policy and any requirements governing your material before sending it. Keeping the export locally remains an option.
Start with one familiar conversation. Check the speaker labels, message order, useful passage and any referenced files. The original export gives you something to compare against if a detail is missing.
For the complete conversion walkthrough and existing demonstration, see How to Make ChatGPT and Claude Data Exports Readable. That guide covers the unpacking process; this one helps you choose the right Claude export and preserve the pieces it may not contain.
# Chat history, memory and account migration are different
| What you need | Appropriate starting point |
|---|---|
| A copy of conversations and account data | Claude's data export |
| A finished spreadsheet, presentation or document | Download the actual file from its chat |
| Claude's remembered information about your work | Claude's memory controls |
| Selected conversations as readable files | A supported export and the Multiplist unpacker |
| Reusable sources for connected assistants | Save chosen material in your Multiplist vault |
Claude supports native memory export. Its current instructions describe Settings → Your Claude → Manage beside Your memory, with layout differences for older experiences. You can copy that remembered information into a local file. Memory import is experimental, so check what a receiving assistant actually retained. Anthropic's memory import and export guide
If remembered preferences are all you need, that native route may be sufficient. A memory copy does not substitute for the full discussion or finished files.
An exported archive also cannot be imported into another personal Claude account. Joining a Team or Enterprise organization has a separate eligible-account migration process; review its conditions rather than treating an export as an account-transfer package. Claude's account migration guidance
# Carry one useful conversation forward
You do not have to process every conversation before the export becomes worthwhile.
For the workshop example, open the transcript, find the chosen outline and keep the presentation beside it. If you want another connected assistant to continue the work, save that selected source in Multiplist and confirm it is there. Connect and authorize the tool where you intend to use it, then ask for the source by its recognizable title.
Downloading an archive does not synchronize future chats, and unpacking it does not automatically add it to a vault. Those boundaries let you choose what to keep and where to use it.
Related: Should you save AI chat summaries or full transcripts? · Check whether your assistant retrieved the saved source