How Many Claude Projects Should You Have?
Make one project for each context with its own audience, rules and source files, such as one per client or one per product. Don't make one per task, and don't put everything into a single project. If two pieces of work would need different instructions, they need different projects.
Here's my current work. Help me decide how to organize Claude Projects. [List each client, product or recurring job, with its audience and main documents.] For each item, tell me which project it should go in. Split items only if their instructions or files would conflict. Merge items that share an audience and documents. Give me a table with: project name, what goes in it, its one-line instructions, and the files to upload. Flag any item that shouldn't be in a project at all.
- One for everything
- One per client or product
- One per task
Try it now
- 1Open **Projects** in the left sidebar and look at what you have, including chats sitting outside any project.
- 2Create one project for your busiest context with + New Project.
- 3Move related chats in: click the dropdown arrow next to a chat's name, choose Add to project, and pick it in the Move chat window.
- 4Star the project you use most from its three-dot menu. You'll know the split is right if you stop having to correct tone or audience in your first message.
Use it when
Use this when you're setting up projects for the first time, or when answers start picking up the wrong tone or facts from a different client. Agencies and consultants should split by client from the start, to keep each client's material apart.
Skip it when
Don't create a project for a single question or a short task. A normal chat with a file attached does that. And don't split work that shares one audience and one set of source files, because you'd then have to keep two copies of the same documents up to date.
Why it works
Instructions and knowledge apply to every chat in a project, so one set of rules has to fit everything inside. Anthropic's help center also says each project keeps its own memory, and project chats don't use memory from other projects, which gives you real separation between contexts. Free accounts are limited to five projects, so on that plan you need to choose. On paid plans, RAG searches the whole knowledge base, and Anthropic's tip is to group related documents in the same project.
Example
You're a freelance copywriter with two retainers: a bank that needs formal, compliance-checked copy, and a skate brand that wants the opposite. Sharing one project means rules that contradict each other. You make two projects, each with its own instructions and tone guide, and turn off Use account memory on the bank's project. Your own admin stays in plain chats.
Going further
On Team and Enterprise, the split also controls access. You share a project with Can view or Can edit, by person, by list, or with the whole organization. Connectors work only in private projects on those plans, so a shared project can't use them. Archive finished projects from the three-dot menu instead of deleting them: conversations stay accessible, and sharing and knowledge stay intact. An archived project has to be unarchived before it can be deleted.
Common mistakes
- Keeping one "Work" project, so a rule for one client bleeds into another's answers.
- Making a project per task, then copying the same files between ten of them and letting them drift apart.
- Sharing a project with your organization and then finding its connectors no longer work.
- Assuming separate projects mean total separation. New memories saved in a project can still surface elsewhere unless you turn off Use account memory.
Sources
- Create and manage projects, Claude Help Center
- What are projects?, Claude Help Center
- RAG for projects, Claude Help Center
- Use connectors, Claude Help Center
- Chat search and memory, Claude Help Center
Checked 6 November 2026. Products change often, so confirm details with the vendor.