How to export a Claude conversation

The short version

1. Open the conversation in Claude. Confirm that it contains only material you are comfortable making accessible through a public link.
2. Create a public share link. Use Claude's sharing control and open the resulting link once to verify that the conversation is visible without your account.
3. Paste the link into ThreadSift. Open the ThreadSift exporter, submit the link, review the extracted conversation, and choose TXT, Markdown, or Excel.

This workflow is designed for public Claude share pages. It does not bypass permissions and cannot read chats that are private, deleted, or available only after signing in.

Prepare the conversation before sharing

Read through the thread before creating its public link. A long conversation may contain personal details, client information, internal instructions, pasted documents, or facts that became irrelevant later in the exchange. Remove or avoid sharing anything that should stay private. If only part of the discussion matters, consider starting a new Claude conversation that contains a concise summary of the useful material, then share that cleaner version.

Give the conversation a descriptive title when possible. A good title makes the downloaded file easier to identify months later. “Vendor research — July findings” is more useful than “New chat,” especially when several exports land in the same folder.

Choose the right Claude export format

There is no universally “best” format. The right choice depends on what happens next. TXT is an excellent archive copy. Markdown retains lightweight document structure for editing and publishing. Excel makes a conversation easier to audit message by message. For important work, downloading both Markdown and Excel can give you a readable source document plus an analysis-ready table.

What a good Claude transcript should preserve

A reliable export should keep the chronological order of the conversation and distinguish your prompts from Claude's replies. It should also preserve the structure that makes longer responses understandable: headings, paragraphs, numbered steps, bullet lists, links, quotations, tables, and code blocks. ThreadSift shows a preview before download, so scan the beginning, middle, and end rather than checking only the title.

Complex interactive elements on a provider page may not translate perfectly into a portable document. If a response depends on an external artifact, attachment, or live interface, download that item separately and note its relationship to the transcript. A transcript captures the conversation; it is not necessarily a backup of every linked resource.

Organize Claude exports for future use

Use filenames that include the subject and date, such as claude-product-research-2026-08.md. Store related attachments nearby, and add a short note explaining why the conversation mattered. For team handoffs, record who reviewed the output and whether any claims still need verification. AI responses can be useful working material, but an export does not make them authoritative.

If you plan to quote or publish part of the exchange, verify factual claims against primary sources. Also review the conversation for accidental disclosure. A public link can be accessible to anyone who receives it, so disable the share at the provider when it is no longer needed.

Privacy, storage, and practical limits

ThreadSift requires no sign-up. It has no application database that stores submitted share links or extracted conversation histories. It reads the public page when you request an export and prepares the file for download. That design reduces retained application data, but it does not change the privacy status of the source: the Claude link itself is public until you revoke it through the provider.

Public page formats can change. If extraction fails, first confirm that the share URL still opens in a private browser window. Then create a fresh public link and retry. ThreadSift is an independent export utility and is not affiliated with Anthropic or Claude.

Frequently asked questions