Claude Export Help Center

Practical guidance for local exports, Pro controls, and recovery.

Understand what stays local

Keep conversation content in your browser by default and choose deliberately when a feature sends anything elsewhere.

Step by step

How to do it

  1. 1

    Normal exports are created locally in your browser; Claude conversation content is not sent to the Claude Export backend for that work.

  2. 2

    Review an export before sharing it, especially when it includes artifacts, long threads, or sensitive material.

  3. 3

    Use the Privacy page for the full data map, and use Contacts for license or support questions without including passwords or keys.

Keep going

Document controls Make a polished client-ready document Use templates, ranges, headings, a cover page, and redaction when the export is going beyond your own notes. Pro License help Activate or recover Claude Export Pro Turn on a purchased license in the browser profile you use, or restore it after changing devices. Pro

Need a human answer?

Support can help with exports and licenses.

Share the safe details of the failed step; keep keys, passwords, and private conversation content out of your message.

Contact support