How to export a Claude project

To export a Claude project, save its instructions, reference files, conversations, and finished outputs separately. Request Claude’s account data export for the broader conversation record, then compare the saved files with your project inventory.

Start with the project version you have

The existing Projects interface groups chats with shared knowledge and instructions. Open Projects, select the project, and list the conversations you need.

As of November 2026, a new Projects beta is rolling out to some Pro, Max, and Ultra accounts. It appears at claude.ai/code and in Claude Desktop’s Code tab. A project there has one coordinating conversation with parallel threads.

For that beta, open each relevant thread from Overview to read its transcript. Copy any discussion you need into a local document, keeping its title and source link. The coordinator sees threads’ reports rather than every step they take, so its recap alone can miss details. The beta project guide explains this layout. DocMyChat doesn’t export Claude Code sessions.

If your project’s menu offers an export, compare its contents with the inventory below.

List the four parts you want to keep

Suppose an existing “Website refresh” project has six chats, a brand-guide PDF, a page-inventory spreadsheet, and custom writing instructions. Its outputs are a finished Claude Doc, a launch deck, and a redirect script. Save these four parts:

• Instructions: the exact writing rules, copied into a text file.
• Knowledge: both original reference files, with their recognizable filenames.
• Conversations: all six discussions, including the corrections that shaped the final copy.
• Outputs: the document, presentation, and script as usable files.

Make a short index with the project’s name, description, URL, and the date you saved the copies. Record each item’s source and local filename. Add saved memory or scheduled tasks if they matter.

Mark each item as saved content, a link, or still to collect. Links help you find material again but won’t replace files when you work offline.

Request the account archive and check your role

Claude’s account export includes conversation and user data. On the web or Claude Desktop, start at Settings → Privacy → Export data. The emailed download link lasts 24 hours. Follow the account-history export guide for the complete procedure.

Work accounts use different export permissions:

• Team and Enterprise members can export their own chats once an Owner or Primary Owner enables Allow members to export their own data. These exports omit uploaded-file contents.
• Primary Owners export organization data through Organization settings → Data and privacy. Owning a project is different from being the organization’s Primary Owner.
• Organization exports omit Claude-created Word, Excel, PowerPoint, and PDF files. Download needed deliverables separately while they’re available.

Find a known project conversation in the archive. Compare an early correction and the final reply with the same passages in the source chat. Work through your conversation list, keeping the saved instructions and originals beside the archive.

Copy the instructions exactly

In an existing project, open its instructions area. Set project instructions is the control for adding them, as shown in the project-management guide.

In the beta, click the gear in the project header and open Project settings → Memory → Project instructions.

1. Select the complete instruction text.
2. Copy it into a local text file, such as project-instructions.md.
3. Compare the first and last lines with the project.
4. Save the file beside your index.

Preserve exact constraints, examples, and exceptions. “Use the approved product names” is different from the actual list of approved names. Copying the field preserves that wording without asking Claude to reconstruct it.

Keep original knowledge files where possible

In the existing layout, the knowledge area is on the right of the project’s main page. In the beta, Overview → Library lists added files and files produced by threads.

Open each file entry and look at its actions. If Download is offered, save the file and open the local copy. Otherwise, collect the original from your computer, shared drive, repository, or the person who supplied it.

For a pasted text note that you can still read, copy the displayed text into a file and label it as a text copy. Don’t substitute a newly generated summary for the original knowledge document.

In the website example, keep the PDF as a PDF and the spreadsheet as a spreadsheet. Check the PDF’s page count and the spreadsheet’s sheet names against the source. A paragraph copied out of either file preserves only that paragraph.

Save readable copies of regular project chats

For existing project conversations on claude.ai, DocMyChat saves one chat or one reply at a time in desktop Chrome. It doesn’t export a whole project.

1. Open the first regular project chat in Chrome.
2. Click Export beside Share.
3. Choose Markdown, Word, or PDF.
4. For PDF, choose Save as PDF in Chrome’s print dialog.
5. Open the downloaded file and check the ending.
6. Repeat for each conversation on your list.

Word and Markdown download directly. The conversation export follows the branch currently displayed, so show the accepted exchange before saving. Keep separately named copies if another branch also matters.

For the example, match the six saved transcripts to the six chat titles in the index. Exporting the final copywriting reply alone would leave out the earlier discussion about prohibited claims and terminology.

Download the finished artifacts separately

Open each deliverable and use its native controls. A Claude Doc has Export options for Word, PDF, Markdown, and Google Docs. Decks export to PowerPoint or PDF, or to editable Google Slides. The artifact-type guide covers the other outputs.

In a DocMyChat transcript, published Docs and decks appear as titled links where they were made. Their content isn’t included. Keep the document and deck exports beside the conversation that produced them.

For included chat artifacts and files, the extension’s Artifacts ZIP keeps the latest version of each. It is flat, with no folders, and slashes in filenames become spaces. Slide HTML and JSON written only to build a published deck are omitted from both the ZIP and appendix. See the artifact download guide for the steps.

Keep any earlier draft you need separately. The latest-version ZIP is not a revision history.

Finish by opening the files you’ll use

For the website refresh, open the instructions, both references, six transcripts, final document, deck, and script. Check the approved homepage wording and the final redirect decision against the saved conversations.

Keep the account archive in its own dated folder. Organize the project copies into folders you create, with the index at the top.

Save another snapshot after an important change, using the chat-backup routine. Keep the source project until the copies contain the material you need.

Questions