How to Export Claude Conversations (Markdown, JSON, Text)

Two Kinds of Export, Two Different Jobs

People search for "export Claude conversations" for two different reasons. One is a backup: a complete copy of everything in the account, for safekeeping, compliance, or leaving a service. The other is a working export: one specific conversation as a file you can drop into a doc, a repository, a ticket, or another AI tool.

Claude.ai's built-in export is designed for the first job. It is not a good fit for the second, which is where manual copying or an extension comes in. Knowing which job you are doing saves a lot of fiddling.

The two jobs also run on different schedules. A backup is something you do occasionally and hope never to need: a full snapshot that you store somewhere safe. A working export happens in the flow of work, often several times a week, at the moment a conversation produces something that needs to live outside the chat. If the working export takes more than a few seconds, people skip it, and the useful output stays trapped in a thread that will be hard to find in a month. Optimize the backup for completeness and the working export for speed.

The Native Account Export, Step by Step

According to Anthropic's help center, individual users export like this:

1. Open claude.ai in a browser or the Claude Desktop app (exports are not available in the iOS or Android apps).
2. Go to Settings > Privacy.
3. Click Export data.
4. Wait for an email with a download link. There can be a short delay while the export is prepared.
5. Download within 24 hours while signed in. If the link expires, request a new export.

A few details that catch people out:

• Team and Enterprise members can export their own chats only if an Owner has enabled member exports. Primary Owners export organization data from organization settings instead.
• Uploaded file contents are not included for Team and Enterprise member exports, per the help center. Keep originals of anything you uploaded.
• No re-import. Exported data cannot be imported into another personal Claude account.
• Memory is separate. Anthropic suggests asking Claude to write out its memories of you verbatim and saving that text if you want a copy.

The help center does not commit to a specific file format, so treat the archive as machine-readable data that you may need a script or viewer to browse comfortably.

Choosing a Format: Markdown vs JSON vs Plain Text

A sensible default: Markdown for anything a person will read, JSON for anything a program will read, plain text only when the destination cannot handle the other two.

Exporting a Single Conversation

For one chat, you have three realistic options:

• Copy individual responses. The copy control on each response is fine for one or two answers. It gets tedious for a whole thread, and you lose your own prompts unless you copy those separately.
• Select and copy the page. Works in a pinch, but tends to pull in interface text and breaks code formatting.
• Use an extension. A browser extension can export the full conversation, both sides, in a clean format with one click.

Whatever method you use, check the result before you rely on it. Long code blocks, tables, and artifacts are the most likely parts to come out mangled.

What Is Actually Worth Exporting

Exporting everything feels safe but creates an archive nobody opens. Be selective about working exports:

• Decision records. Threads where you made a choice you may need to justify later.
• Reusable explanations. A clear walkthrough you want to share with a teammate or revisit.
• Final artifacts. Specs, drafts, and code that left the chat and went into real work.
• Prompt patterns that worked. Better saved as reusable prompts, but an export captures context.
• Research threads with sources. So you can verify claims later without re-running the research.

Skip quick lookups, abandoned experiments, and anything you would never search for. Also think before exporting sensitive material: an exported file sits on your disk or in a shared drive without the account protections of the original.

Exporting a Chat to Use in Another Tool

A common reason to export is to move work somewhere else: into a repository, a notes app, a ticket, or another AI assistant. Each destination wants something slightly different.

The AI-to-AI case deserves a warning. Pasting a whole exported conversation into a new chat brings back every superseded draft and tangent, and it costs usage on every following message. A short brief built from the export almost always works better. See how to move a Claude conversation to a new chat for a template.

The other warning is about privacy. Once a conversation is a file, it can be synced, forwarded, and indexed in ways the original chat could not. Before exporting threads that include customer data, credentials, or internal financials, decide where the file is allowed to live, and redact what does not need to travel.

An Archiving Habit That Takes Two Minutes

A lightweight routine beats a heroic quarterly cleanup. Here is one that works for most solo users and small teams:

1. When a thread produces something that leaves the chat, export it as Markdown right then.
2. Name the file with date and topic, for example 2026-11-03-pricing-page-decisions.md.
3. Add three lines at the top: what the thread decided, where the output went, and what is still open.
4. Save it next to the work it supports (the repo, the project folder), not in a generic "AI chats" dump.
5. Run a full native account export periodically as a backup, and store it somewhere private.

A filled-in header for step three can be this short:

Decided: Three-tier pricing (Starter/Growth/Scale), monthly only.
Output: Copy shipped to /pricing on 2026-11-03.
Open: Revisit annual discount after 60 days of data.

Six months later, those three lines are often more valuable than the transcript under them.

Where ClaudeKit Fits

ClaudeKit, a free browser extension for claude.ai, adds chat export as Markdown, JSON, or plain text for the conversation you are viewing. It covers the working-export job that the native account export does not. Exports are created locally in your browser, and ClaudeKit does not require an account.

Use both. Run the native export from Settings > Privacy as an occasional full backup, and use a per-chat export when a specific conversation needs to live somewhere else. If you only need one or two key messages rather than a whole thread, pinning them in ClaudeKit's Workspace panel may be enough. See how to pin important Claude responses.