How to export a Claude conversation to Markdown

Which method fits your case

If you came here for a single conversation in a readable file, skip to the third method.

Method 1: copy a single reply

Hover any Claude reply and click the copy icon below it. Claude puts the reply on your clipboard as Markdown, with headings, lists and fenced code blocks intact. Paste it into any editor.

This is the right tool when you want one answer. It stops being practical on a twenty-turn conversation: you copy each reply separately, your own prompts are left out, and you rebuild the order by hand.

Method 2: Anthropic's official data export

The export built into Claude covers your whole account. Anthropic documents the steps in its help center:

1. Click your initials in the lower-left corner of Claude.
2. Open Settings, then the Privacy section.
3. Click Export data.
4. Wait for the email, then download the archive while signed in. The link expires 24 hours after it is sent.

Two constraints come from Anthropic's own documentation. The export runs from the web app or Claude Desktop, not from the iOS or Android apps. On Team and Enterprise plans, only the organization's Primary Owner can run it.

The archive is built for portability, not for reading. Conversations arrive as JSON, all of them together. Getting Markdown out of it means running a converter over conversations.json, then finding the one chat you wanted in the output. Use it as a backup, and as the only method that covers conversations you have not opened in months.

Method 3: export the open Claude chat to Markdown with Markforge

Markforge is a free Chrome extension that converts the page you are on into Markdown. It ships a dedicated parser for Claude, so it reads the conversation structure and ignores the sidebar, the buttons and the rest of the interface.

1. Install Markforge from the Chrome Web Store.
2. Open the conversation on claude.ai. The address should look like claude.ai/chat/....
3. Click the Markforge icon in the toolbar, or press Alt+M.
4. Check the preview. The title and the Markdown are both editable before you save.
5. Click Copy to put the Markdown on your clipboard, or Download .md to save the file.

The whole conversation is in one file, prompts included, in the order they happened. Conversion runs in your browser: nothing is uploaded, and you do not need an account.

What the Markdown file looks like

Each turn gets a User or Assistant heading, and turns are separated by a horizontal rule. The file starts with YAML frontmatter that records where the conversation came from.

---
title: "Refactoring a date parser"
source: "Claude"
url: "https://claude.ai/chat/your-conversation-id"
description: "Can you help me refactor this date parsing function?"
---

# Refactoring a date parser

### User

Can you help me refactor this date parsing function?

* * *

### Assistant

The function mixes parsing and validation. Split them first:

The description field holds the first 200 characters of your first message, which makes the file easy to recognize later in a search. Code blocks in Claude's replies come out as fenced code blocks.

The frontmatter is a template you can edit in the extension settings. Available variables are {title}, {author}, {date}, {url}, {description}, {site}, {domain} and {tags}. Lines whose variable is empty are dropped, which is why a Claude export has no author or date line: the page does not expose them.

Limits worth knowing before you rely on it

• One conversation per click. Markforge exports the chat open in the current tab. For a bulk backup, use Anthropic's export.
• Extended thinking is left out. The parser removes Claude's thinking sections and keeps the final replies.
• Artifacts are separate. The export covers the conversation text. To keep an artifact, copy or download it from Claude's own artifact menu.
• Tables are flattened. Version 1.0.0 does not rebuild Markdown tables: each cell lands on its own line. If a reply hinges on a table, copy that reply with Claude's copy button.
• It reads what the page has loaded. On a long conversation, scroll to the top once so every message is present before you export.
• Shared links are not conversations. The dedicated parser matches claude.ai/chat/ addresses. A public share link falls back to generic page extraction, which is rougher.

Continue a Claude conversation in another assistant

A Markdown transcript is also the simplest way to carry a conversation from Claude to ChatGPT or Gemini. Export it, paste it into the new chat, and tell the model to continue from the last message.

Before pasting, check the token count at the bottom of the Markforge popup. It tells you roughly how much of the other model's context the transcript will occupy. The count uses a GPT tokenizer, so treat it as an estimate for other models. If the number is large, delete the turns you no longer need in the content field before copying. The full method is in how to move a conversation between assistants.

Where to put the file next

A Markdown export is useful when it lands somewhere you will find it again. If you keep notes in Obsidian, you can point Markforge at a folder inside your vault and skip the Downloads folder entirely: see how to save AI conversations to Obsidian.

The same one-click export works on the other assistants, each with its own parser: ChatGPT, Gemini and Grok.