# How to Move a Claude Project to Claude Code (4 Ways)

> Move a Claude project to Claude Code: there's no import button, so its instructions become CLAUDE.md and its files go in a folder. Four routes, free ones first.

Canonical: https://claudeprojectdownloader.com/blog/move-claude-project-to-claude-code
Last updated: 2026-11-19
Author: [Aarohan Niraula](https://claudeprojectdownloader.com/author/aarohan-niraula)

To move a Claude project to Claude Code, you copy it out by hand, because Claude Code on your computer has no import button for claude.ai projects. A project lives on Anthropic's servers, and Claude Code works from a folder on your disk. So the move is three steps: put the project's knowledge files in a folder, save its instructions there as `CLAUDE.md`, and start `claude` in that folder. Chats come along as Markdown files that Claude Code can read when it needs them.

There is one exception. Anthropic is moving some projects to a new version that opens at claude.ai/code, and it covers that case too.

Everything here is about your own projects, in a Claude account you can sign in to.

**Short answer**

- There is no command that opens a claude.ai project in the Claude Code terminal, VS Code extension or JetBrains plugin. You bring the contents over as files.
- Instructions become CLAUDE.md, knowledge files become ordinary files in the folder, and chats become Markdown notes you keep beside them.
- The free routes: copy things out by hand, or ask Claude inside the project to package them. Claude rewrites files when it does this, so check the long ones.
- Claude Project Downloader, the extension we make, saves a whole project as one ZIP with instructions.md, files/ and chats/. Rename one file and the folder is ready.
- The new version of projects at claude.ai/code is a different thing. It runs in the cloud, and Anthropic moves existing projects into it in stages.

## Can you move a Claude project to Claude Code directly?

It depends on which Claude Code you mean, because the name now covers two places.

**Claude Code on your computer** is the terminal tool, the IDE extensions and local sessions in the desktop app. It reads the folder you start it in. It can't see your claude.ai projects, and Anthropic's docs describe no way to link or import one. A [feature request for exactly this](https://github.com/anthropics/claude-code/issues/2511) has been open since June 2025.

**Projects at claude.ai/code** are the new version of projects, in beta. Anthropic's [projects page](https://support.claude.com/en/articles/9517075-what-are-projects) says it has "started moving existing projects for some Pro, Max, and Ultra users to the new version", and that "Everything in your project comes with it: your instructions, files, full chat history, and scheduled tasks." These run as cloud threads. The [Claude Code docs](https://code.claude.com/docs/en/claude-projects) say they are available at claude.ai/code, in the desktop app and in the mobile app, "not in the terminal CLI, the VS Code extension, or the JetBrains plugin".

So if you work in a terminal or an editor, you need the folder route whether or not Anthropic has moved your project.

![Table showing where each part of a Claude project goes. Instructions become CLAUDE.md on your computer and project instructions of up to 16,000 characters at claude.ai/code. Knowledge files become files in the folder, or Library files. Chats become Markdown notes, or the chat history Anthropic's move carries. Project memory is not carried to your computer. Connectors arrive automatically with the same Claude login in both.](https://claudeprojectdownloader.com/img/cpd/cpd-project-to-claude-code-map.png)

*From support.claude.com and the Claude Code docs, checked 2026-11-19.*

## What a Claude project holds, and where each part goes

A project has four parts, and each needs a home.

- **Instructions.** In Claude Code these go in `CLAUDE.md` at the top of the folder. The [memory docs](https://code.claude.com/docs/en/memory) say Claude reads that file "at the start of every session", which is the same job project instructions do in chat.
- **Knowledge files.** They become ordinary files. Claude Code opens them when a task calls for them, so they don't sit in the context window the way project knowledge does.
- **Chats.** There is nowhere to import them. Save the ones that matter as Markdown and keep them in the folder as reference.
- **Project memory.** Anthropic's [project management page](https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects) says "Each project has its own memory." It doesn't travel to your computer. Open **Memory** on the project's page, and copy anything you rely on into `CLAUDE.md`.

Connectors are the easy part. If you sign in to Claude Code with the same Claude account, the [MCP docs](https://code.claude.com/docs/en/mcp) say the connectors you added in claude.ai "are automatically available in Claude Code". Run `/mcp` to see them.

## Route 1: copy the project out by hand (free)

This works on every plan and needs nothing installed except Claude Code.

1. **Make a folder** for the project, with a `files` folder inside it.
2. **Copy the instructions.** Open the project on claude.ai, open its instructions, and paste the text into a new file named `CLAUDE.md` in the folder.
3. **Collect the knowledge files.** If you still have the originals on your computer or in cloud storage, use those. They are the real copies. Otherwise open each file in the project's knowledge panel and copy its text into a file of the same name. That works for text. It doesn't work for PDFs or images.
4. **Save the chats that hold decisions.** Each Claude reply has a Copy button. For a whole chat, see [how to export a Claude chat to Markdown](https://claudeprojectdownloader.com/blog/export-claude-chat-to-markdown).
5. **Start Claude Code in the folder:**

```
cd my-project
claude
```

Then ask it to read `CLAUDE.md` and list the files it can see, so you know everything arrived.

People often ask where the project files are on their computer. They aren't on it. [Where Claude keeps your project files](https://claudeprojectdownloader.com/blog/download-all-files-from-claude-project) explains that, and what each way of getting them out returns.

## Route 2: ask Claude to package the project (free)

Inside the project, ask Claude to put every knowledge file into a ZIP without changing anything, and to add the project instructions as a file. On plans with file creation this often works.

The catch is that Claude regenerates files. It doesn't copy bytes. A long document can come back shortened or reformatted, and a PDF comes back as text at best. Compare the long files with what the knowledge panel shows before you rely on them.

This route is good for one thing nothing else gives you: a handoff note. Ask Claude, in the project, to write down what was decided, why, what was ruled out and what is still open. Reasons matter most. Claude Code can read your code and files, but it can't know why you chose one approach over another unless something in the folder says so.

Claude's own **Settings → Privacy → Export data** is free too, but it's a poor fit here. Anthropic's [export page](https://support.claude.com/en/articles/9450526-export-your-claude-data) says exports "don't include the original files you uploaded", and what you get is JSON for the whole account, not one project as a folder.

## Route 3: download the project as one ZIP

[Claude Project Downloader](https://claudeprojectdownloader.com/) is a Chrome extension we make. Open the project on claude.ai, click the extension icon, and press **Download Entire Project**. You get one ZIP, named after the project, laid out like this:

```
instructions.md     the project's name, description and instructions
files/              the knowledge files
chats/              one Markdown file per chat, attachments in subfolders
```

To turn that into a Claude Code folder:

1. Unzip it where you keep your work.
2. Rename `instructions.md` to `CLAUDE.md`.
3. Run `claude` in the folder.

If you already have a repository, unzip into a subfolder such as `docs/claude-project/` instead, and copy the instructions you still want into the repository's own `CLAUDE.md`.

What to know before you count on it:

- **The free plan includes one full-project export in total.** After that it's Pro. Single files and single chats have a daily free allowance. Current prices are on the [Pro page](https://claudeprojectdownloader.com/pro).
- **Word documents come out as text.** Claude keeps only the extracted text of a `.docx`, so the ZIP has it as a `.md` file. PDFs are saved as PDFs. Images may be Claude's WebP preview, not your original.
- **Projects already on the new version export without instructions.** You get the conversation, the thread sessions and the Library files. Copy the instructions from the project's settings yourself.
- **It runs in Chrome on a computer**, on projects your signed-in account can open. It does nothing on the Claude Code side: no upload, no setup.

**Get Claude Project Downloader:** https://chromewebstore.google.com/detail/claude-project-downloader/leinefcadopiegfdgjddoilofknckkgh

## Make CLAUDE.md work in Claude Code

Instructions written for a chat rarely fit a coding agent unchanged. A few edits help:

- **Keep it short.** The Claude Code docs say to "target under 200 lines per CLAUDE.md file" because "Longer files consume more context and reduce adherence."
- **Cut the chat persona.** Lines such as "answer as a senior analyst" or "keep replies under 200 words" were for conversation. Keep the rules about the work itself.
- **Point to the files. Don't paste them in.** One line does it: "Background documents are in `files/`. Earlier decisions are in `chats/`. Read them when a task needs them." Pasting chats into `CLAUDE.md` spends context in every session.
- **Use imports sparingly.** `@files/spec.md` inside `CLAUDE.md` loads that file every session. Do it for one short file you always need, not for the folder.
- **Run `/init`.** With a `CLAUDE.md` already there, the docs say it "suggests improvements rather than overwriting it".

Two notes on file types. Claude Code reads PNG, JPEG, GIF and WebP images. It reads short PDFs whole, and the [tools reference](https://code.claude.com/docs/en/tools-reference) says PDFs over 10 pages are read in page ranges, which needs `pdftoppm` from poppler installed.

## Route 4: the new projects at claude.ai/code

If **Projects** shows in the sidebar at claude.ai/code, directly or under **More**, you have the new version. It's on Pro, Max and Ultra. The Claude Code docs say it isn't "offered on Team or Enterprise plans yet".

There are two ways a chat project gets there:

- **Anthropic moves it.** This happens in stages. Anthropic says it emails you first if you used the project in the last 30 days, and that other projects "stay on the current version for now".
- **You start it.** In the New project steps, the docs say that if the button reads **Get started**, you "first upgrade or archive the existing claude.ai projects it lists".

You can also build one from the folder you made above. Project instructions take "up to 16,000 characters". Files go in through **Add** in the project's Library, "up to 1,000 files and 2 GB at a time", and the docs note that uploads are copies, so later edits on your computer don't reach the project until you upload again.

Know what you're switching to first. A project there is one conversation with threads, not a list of chats, and it leaves the chat side of Claude. There's [no way to switch a project back to classic](https://claudeprojectdownloader.com/blog/claude-projects-disappeared#can-you-switch-claude-projects-back-to-classic), so save a copy before you upgrade one. Our guide to [Claude projects that disappeared](https://claudeprojectdownloader.com/blog/claude-projects-disappeared) shows where a moved project turns up.

## Moving a Cowork project or a single chat

**A Cowork project.** Anthropic's [Cowork projects page](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) says "Projects are only available in Cowork, not in Claude Code. Support for Claude Code is planned for a future update." If the project was made from a folder on your computer, the files are already on your disk: the same page says the folders and files "stay on your computer". Start `claude` in that folder, and copy the project's instructions into a `CLAUDE.md` there.

**One chat.** No command opens a claude.ai chat in Claude Code. `claude --teleport` pulls in cloud sessions from claude.ai/code, which are a different thing. Save the chat as a Markdown file, put it in the folder, and tell Claude Code to read it first. The reverse direction, getting a session out of Claude Code, is in [how to export a Claude Code conversation](https://claudeprojectdownloader.com/blog/export-claude-code-conversation).

## Frequently asked questions

### Can I import a Claude project into Claude Code?

Not with a button. Claude Code on your computer reads a folder and can't see claude.ai projects. Put the project's knowledge files in a folder, save the project instructions there as CLAUDE.md, and run claude in that folder. The new version of projects at claude.ai/code is separate, and Anthropic moves existing projects into it in stages.

### Can I use Claude projects in Claude Code?

Only the new version of projects, which is in beta on Pro, Max and Ultra. It works at claude.ai/code, in the desktop app's Code tab and in the mobile app. The Claude Code docs say it isn't available in the terminal CLI, the VS Code extension or the JetBrains plugin. Chat projects on the current version don't appear in Claude Code at all.

### Where are my Claude project files on my computer?

They aren't on your computer. Project knowledge is stored on Anthropic's servers and shown in the project's knowledge panel on claude.ai. To use the files in Claude Code you have to copy or download them into a local folder first, or use the original files you uploaded.

### Should I paste my project instructions into CLAUDE.md as they are?

Use them as the starting point, then trim. Remove lines about tone and reply length that were written for chat, keep the rules about the work, and add one line saying where the background files are. The Claude Code docs recommend keeping CLAUDE.md under 200 lines.

### How do I move a chat from Claude to Claude Code?

Save the chat as a Markdown file, put it in your project folder, and ask Claude Code to read it. There is no command that opens a claude.ai chat in Claude Code. If the chat is long, also ask Claude for a short handoff note with the decisions and the reasons, and keep both files.

### Does a project's memory move to Claude Code?

Not to Claude Code on your computer, which keeps its own memory files per repository. Copy what you need from the project's Memory page into CLAUDE.md. For projects Anthropic moves to the new version, its list of what comes along names instructions, files, chat history and scheduled tasks, so check the memory after a move.

## Related guides

- [How to download all files from a Claude project](https://claudeprojectdownloader.com/blog/download-all-files-from-claude-project)
- [How to export a Claude Code conversation](https://claudeprojectdownloader.com/blog/export-claude-code-conversation)
- [How to move a Claude project to another account](https://claudeprojectdownloader.com/blog/export-claude-project-to-another-account)
- [How to export a Claude chat to Markdown](https://claudeprojectdownloader.com/blog/export-claude-chat-to-markdown)
- [How to back up and export Claude projects and chats](https://claudeprojectdownloader.com/blog/back-up-claude-projects-and-chats)

## Related

- [Claude Project Downloader](https://claudeprojectdownloader.com/)
- [All guides](https://claudeprojectdownloader.com/blog)
