There are two genuinely different reasons people search for "export Claude conversation," and most guides answer only one of them. If you want to save one conversation right now — a piece of analysis, a long piece of writing, a code review — you want a fast, single-chat method. If you want everything in your account as a backup, you want Anthropic's official export tool. They're not the same process, and using the wrong one wastes time.
This guide covers both, plus a wrinkle specific to Claude that most export tutorials skip entirely: Artifacts.
Method 1: Single Conversation, via Share Link (Fastest)
This is the right choice when you know exactly which conversation you want and don't need the rest of your account history.
Step 1 — Generate a share link
Open the conversation in Claude, click Share near the top of the chat, then Copy link. On mobile, tap the Share icon inside the conversation. The link only works if the conversation is set to public — Claude will prompt you to confirm this when you generate it.
Step 2 — Extract the text
Paste the link into chatgptext.com/claude-extractor. The tool reads the shared page and renders the full exchange in your browser — no Claude login required on your end, since the share link itself carries the permission.
Step 3 — Choose your format and download
- .txt if you just want the words, no formatting
- .md if you're archiving into Obsidian, Notion, or a GitHub repo and want headings/code blocks preserved
- .json if you're a developer who wants to parse the conversation programmatically (each message is a separate object with a role and content field)
- .html if you want something that looks like the original chat when you open it later
Everything happens client-side in your browser. Nothing is uploaded to a server in the process.
Method 2: Your Entire Account, via Claude's Official Export
If you want a complete backup — every conversation you've ever had, not just one — use Anthropic's built-in tool instead of a share link.
Go to Settings → Privacy → Export data. Claude packages a ZIP file of your full conversation history as JSON and emails you a download link when it's ready (this can take a few minutes for large accounts). This is the right call before deleting your account, switching to a different AI tool, or just doing periodic backups.
The catch: the output is raw JSON, structured for machines, not for reading. If you want your entire history in a readable format rather than one conversation at a time, you'll need to process that JSON export yourself or run individual conversations through a tool like the one above.
The Artifacts Problem Nobody Mentions
If your Claude conversation includes an Artifact — an interactive document, code sandbox, or generated app that Claude built inline — a text or markdown export of the conversation will capture the artifact's code or content, but not necessarily its rendered, interactive behavior. A React component Claude built for you exports as source code, not as a working app.
If the artifact itself is the valuable part (not just the conversation that produced it), copy the artifact's content separately using the copy button inside the Artifact panel before you export the surrounding conversation. Don't assume a full-conversation export automatically preserves it in a usable form.
Which Method Should You Actually Use?
| Situation | Best method |
|---|---|
| Saving one specific conversation | Share link + extractor |
| Backing up your whole account | Official export (Settings → Privacy) |
| The conversation includes an Artifact you want to reuse | Copy the Artifact separately first |
| You need it in Markdown for Notion/Obsidian | Share link + extractor, .md format |
| You're a developer parsing chats programmatically | Either — .json from the extractor for one chat, official export for bulk |
Frequently Asked Questions
Does the share link expire?
No — once created, a Claude share link stays active until you manually unshare it from Settings → Privacy → Shared chats.
Can I extract a conversation that isn't shared publicly?
No. Both methods require either a public share link or being signed into the account that owns the conversation. There's no way to extract someone else's private conversation.
Does this work with Claude Projects?
Individual conversations inside a Project can be shared and extracted the same way as any other conversation. Project-level context (custom instructions, uploaded files) isn't included in a single-conversation export — only the message thread itself.
Will formatting like code blocks and bullet points survive the export?
Yes, in .md and .html formats. The .txt format strips formatting down to plain characters by design, which is useful if you're pasting into something that doesn't support markdown.
Extract your Claude conversation now — free, no sign-up.
Try the Claude Extractor