How to export Claude chat history and keep a readable copy

What Claude’s export is for

Claude’s export includes conversation data and user data, but it is not an export-to-Markdown feature. Treat the ZIP as your source archive. To browse chats as notes, use a separate converter or importer and inspect the output.

Anthropic currently says individual users on Free, Pro, and Max can export from Settings → Privacy on the web app or Claude Desktop. Team and Enterprise members can export their own data only if an organization owner enables the permission; primary owners use organization settings to export organization data. Claude for iOS and Android do not offer the export action. Because workspace permissions and product policies can change, confirm the official Claude export instructions for your plan before starting.

Keep chat history distinct from project resources and uploaded files. Anthropic says a Team or Enterprise member export does not include uploaded file contents. Check your archive before deleting or reorganizing anything.

Request your Claude data

1. Open Claude on the web or Claude Desktop and sign in to the account whose conversations you need.
2. Open Settings, then Privacy.
3. Select Export data. If you are in a Team or Enterprise organization and the option is absent, ask an owner whether member exports are enabled.
4. Wait for the export email. Claude says a small delay is possible. Use the link while signed in to the account that requested the export.
5. Download the ZIP within 24 hours of the email arriving. If the link expires, repeat the request.

Keep the source archive safe

Keep one unchanged ZIP, then extract a copy to inspect. The archive may contain structured records rather than finished notes. Check a few files before conversion and avoid copying unrelated account data into a shared vault.

For a Claude Project conversation, separate the discussion from its resources. A note may mention a project brief or artifact without containing that file. Open important references while source access remains available, save files you are allowed to retain separately, and check whether the transcript makes sense without them. For a handoff, add a clear pointer to the related file.

For ordinary chats, keep speaker turns in order and inspect code, tables, links, and non-English text. The notes help you find work; the untouched ZIP remains your source.

Use a converter or import tool carefully

You can use a local converter that supports the files in Claude’s export, or an importer that explicitly accepts the official ZIP or JSON data and writes Markdown notes. Check its supported input, how it treats attachments, and where it writes files before selecting a large batch. Start with a few recognizable chats, compare each note to its source, and expand only when the result is right.

Chatlog supports importing older Claude history from the official export ZIP or JSON through its Settings. Select the chats you want and choose a Markdown folder, Obsidian, or Notion as the destination. Automatic capture handles new and continued Claude activity while Chrome is open and Chatlog is enabled; it does not scan the old sidebar history. The popup’s Save conversation action saves one open chat. For a Notion-only setup, a local Markdown folder is optional. Notion is a separate destination, so account for its handling of the content you send there. Historical imports during the 14-day trial are limited to 25 unique chats per provider.

Understand the limits of a readable copy

Markdown preserves text structure, not Claude’s full interface. A chat can reference a file, artifact, project, or image without the original being present in the note. Do not assume every binary or interactive preview will be saved. Check important files individually and keep separate copies.

A readable notes import is separate from restoring history inside Claude. Chatlog’s import writes selected conversations to your chosen notes destination; it does not restore them into a Claude account. Keep the official ZIP as your account-data archive and use Claude’s own account settings for account changes.

Fix common problems

There is no Export data option. Confirm you are on Claude web or Desktop. Team or Enterprise members should ask an owner to enable member exports; primary owners use organization settings. Claude’s export help describes these availability rules. The link fails? Sign in to the requesting account. It expires after 24 hours, so request another if needed. A file is missing? Check export scope and keep the original until you have confirmed the data you need.

Readable-copy checklist

• The downloaded ZIP is saved separately and remains unchanged.
• You checked a few source records before running a full conversion or import.
• Several resulting notes preserve the chat titles, speaker turns, and message order.
• You checked code, tables, links, and important files.
• Your notes are in the intended destination.

Frequently asked questions

Can I export Claude chats from my phone?

Claude’s current help page says exports are available from the web app or Claude Desktop, not from the iOS or Android apps.

Does the Claude export arrive as Markdown?

No. Claude sends a ZIP download. Use a compatible converter or importer to create readable notes, and inspect the output before relying on it.

Does an export include uploaded files and project content?

Coverage depends on the export type. Anthropic says Team and Enterprise member exports exclude uploaded file contents. Check the archive and retain separate copies of important resources.

Does importing my ZIP restore conversations in Claude?

No. Chatlog imports selected conversations as notes in your chosen destination; it does not restore history into a Claude account. Keep the ZIP as your separate archive.