How to Export Claude Conversations: Full Backups and Individual Chats
This guide covers two ways to export Claude conversations: download a dated JSON backup with Claude's official tool, or save the current chat and selected responses as Markdown, JSON, or PDF.
These two methods serve different needs: Claude’s official export is better for periodic account backups, while AI Exporter is better for saving, organizing, or sharing important conversations as you go. Use the table below to choose.
| What do you want to do? | Recommended method |
|---|---|
| Back up all Claude data from a date range | Claude’s official export |
| Save the entire conversation currently open | AI Exporter Quick Exports |
| Save only a few prompts and responses | AI Exporter Custom Export |
| Export a Claude conversation on Android | Edge for Android + AI Exporter |
| Add it to Obsidian or a local knowledge base | Markdown |
| Pass it to a script or local AI agent | JSON or Markdown |
| Share it or preserve images and layout |
Method 1: Export a JSON backup with Claude’s official tool
This method is best for your first Claude data backup or for periodically saving recent conversation history to your computer.
Step 1: Open Settings
Sign in to Claude on a computer, click your avatar or initials in the bottom-left corner, and select Settings.

Step 2: Find Privacy and Export data
Select Privacy in the left sidebar. Scroll to Your data, then click Export data.

Step 3: Choose a date range
Claude lets you choose the date range for your conversation history:
- All: export your complete history, ideal for your first full backup
- 30 days: export the last 30 days
- 90 days: export the last 90 days
- Custom: choose your own start and end dates
After choosing a range, click Export in the top-right corner. The page shows that the export includes Conversations, Users, and Projects.

Step 4: Wait for Claude’s email
Claude does not download the file immediately in your browser. Once the export is ready, it sends an email to your account address with a link to download a JSON ZIP archive.
The download link expires after 24 hours. Download it promptly, check your spam folder if necessary, and stay signed in to the corresponding Claude account while downloading.
What can you do with Claude’s official JSON export?
The official ZIP is closer to a raw backup than a readable chat document. Keep the original ZIP unchanged and include the date in its filename, for example:
claude-backups/
├── 2026-07-claude-export.zip
└── 2026-08-claude-export.zipTo add this history to Obsidian, you can have Claude Code or a local script read the JSON and convert each conversation into a separate Markdown file:
Claude JSON ZIP
↓
Claude Code splits and organizes conversations
↓
One Markdown file per thread
↓
Add to Obsidian or a local knowledge baseThe official method lets you choose a date range, but not specific threads before exporting. If you only need two or three important conversations, downloading another batch of JSON is inconvenient. That is where the second method works better.
Method 2: Export the current thread or selected responses
If you only want to save the conversation in front of you, you do not need to package a batch of historical data. You can use AI Exporter instead.
Disclosure: AI Exporter is a browser extension we develop. It exports the current page or selected messages on demand; it does not replace Claude’s official account backup.
Before you begin, install the AI Exporter browser extension.
Click the extension icon and choose a quick export
Open the Claude thread you want to save, then click the AI Exporter icon in your browser toolbar. The dropdown provides two types of export:
- Quick Exports: save the entire current conversation as PDF, Markdown, Text, Docx, Image, or JSON
- Custom Export: select specific messages before previewing and exporting them
To keep the full thread, click the format you need. When the export finishes, check that the first message, some content in the middle, and the final response are all present.

Use Custom Export when you only need a few responses
Long conversations often include several failed attempts, while only the final solution is worth keeping. Click Custom Export, select the prompts and Claude responses you need, then choose an export format.
The resulting file is shorter and contains less noise when you add it to a knowledge base or give it to another AI.
Frequently asked questions
Can I export Claude conversations on Android?
Yes, but not through the official export feature in the Claude Android app. Claude’s official data export is currently available only on the web and Claude Desktop; its iOS and Android apps do not include this option.
Android users can use Microsoft Edge, which supports extensions:
- Install or update Microsoft Edge for Android.
- Search for AI Exporter in Edge.
- Before installing, verify the extension’s green camera icon and name to avoid similarly named products.
- Sign in to Claude in Edge and open the conversation you want to save.
- Launch AI Exporter from Edge’s extensions menu and choose an export format.

Should you choose Markdown, JSON, or PDF?
| What you plan to do next | Recommended format | Why |
|---|---|---|
| Obsidian or local notes | Markdown | Easy to edit, search, and link |
| Script analysis or a local AI agent | JSON or Markdown | Easy to parse the message structure and text |
| NotebookLM or another AI that supports PDFs | Keeps a multi-turn conversation in one continuous document | |
| Share with colleagues or clients | Easy to open with stable formatting | |
| Preserve images and visual context | Keeps text and images in the same document |
Standard PDFs exported by AI Exporter contain selectable text, so most AI tools with PDF support can parse them directly. OCR is mainly useful for screenshots, charts, and other image content inside the file.
Which fields matter in AI Exporter’s JSON?
The top level of an AI Exporter JSON file is an array of messages. Each object represents a user message or a Claude response, while contents stores text, images, Thinking, and other data by content type.
Here is a simplified example of the actual structure:
[
{
"id": "claude_msg_user",
"chatGroupId": "conversation_example",
"role": "user",
"model": "claude",
"displayModel": "Claude",
"contents": [
{
"type": "markdown",
"content": "Please review this project proposal."
}
],
"created_at": "2026-07-24 10:30:00",
"updated_at": 1784860200000
},
{
"id": "claude_msg_assistant",
"chatGroupId": "conversation_example",
"role": "assistant",
"model": "claude",
"displayModel": "Claude",
"contents": [
{
"type": "thinking",
"content": "Organizing the proposal's goals, risks, and implementation steps…"
},
{
"type": "markdown",
"content": "## Conclusion\n\nThis proposal can be improved in three areas…"
}
],
"created_at": "2026-07-24 10:30:18",
"updated_at": 1784860218000
}
]These are the fields you will use most often:
| Field | Purpose |
|---|---|
id | Unique identifier for the message |
chatGroupId | Associates messages that belong to the same conversation |
role | Distinguishes user prompts from Claude responses |
model / displayModel | Identifies the message as coming from Claude |
modelId | Optional; appears when the page can identify the specific model |
contents | Stores the different content segments within a message |
created_at / updated_at | Creation and update timestamps |
The contents field is the most important. Common content types in Claude conversations include:
contents.type | Stored content |
|---|---|
markdown | Claude’s main response, headings, lists, tables, code blocks, and convertible Artifact content |
thinking | Thinking content provided by the page and visible at export time |
image | User-uploaded images, with the address stored in imageUrl |
text | Text extracted from attachments, or a description of an attachment that cannot be expanded |
html_widget | Code and display settings for interactive components generated by Claude |
The shared message schema also supports types such as attachment and sources, but their presence depends on the platform and current page content. When processing Claude JSON, reading role and contents is usually enough to get started.
In practice, use Claude’s official export for periodic history backups, then export important threads as needed: choose Markdown for a knowledge base, JSON for programmatic processing, and PDF for sharing or preserving visual context.