Updated 21 November 2026. We re-read Anthropic’s and OpenAI’s own help pages for Projects today. File limits, sharing and memory have all changed since our June version, so the numbers below replace the old ones.

Yes, ChatGPT has Projects like Claude, and both are now available on free accounts. A project is a named workspace that keeps instructions, uploaded files and past chats for one subject, so you stop re-briefing the AI in every new conversation. For agency client work the real differences are in three places: how many files a project holds, who can share it, and how memory behaves inside it. ChatGPT lets you share projects on every plan, up to 100 collaborators on higher tiers. Claude shares projects only on Team and Enterprise plans, with view and edit permission levels.

This post is about Projects for agency client work. If you are choosing between the apps’ free plans, read our free plans guide. If you are choosing a paid plan for plugin development, read our paid-plan comparison. For the wider reasons people moved from one tool to the other, see why the builder crowd switched from ChatGPT to Claude.

ChatGPT Projects vs Claude Projects: what is different?

FeatureChatGPT ProjectsClaude Projects
Available on free accountsYesYes, up to 5 projects
Number of projectsUnlimitedFree: up to 5. Paid plans: no cap mentioned in the help article
Files per projectFree 5, Go and Plus 25, Pro, Business, Enterprise and Edu 40 (10 uploaded at once)Not specified in the help article
Project instructionsYes, apply only inside the project and override global custom instructionsYes, apply to all chats in the project
SharingFree, Go, Plus, Pro, Business, Enterprise and EduTeam and Enterprise, unless an admin turns it off
Permission levelsChat access or edit accessCan view or can edit
CollaboratorsFree 5, Go and Plus 10, Pro 100, Business, Enterprise and Edu workspace projects up to 100Added by name or email, no number stated
Memory in a projectDefault memory or project-only memory; shared projects always project-onlyEach project has its own memory; a toggle controls whether account memory is used
Large knowledge basesNot described on the help pageOn paid plans, retrieval mode turns on automatically when knowledge nears the context limit

Sources, read 21 November 2026: OpenAI’s using projects in ChatGPT and Anthropic’s how to create and manage projects.

Does ChatGPT have projects like Claude?

It does. OpenAI’s help page says projects are included with every qualifying ChatGPT plan, and that credits or usage charges apply to project chats the same as regular chats. Instructions are added in Project settings and apply only inside that project. Files are uploaded to the project and used as context across its chats. The part that is different from Claude is what ChatGPT does with the rest of your history: in default memory, saved memories are referenced and chats can draw on other conversations in the same project. On most plans, chats can also reference conversations outside the project unless the other project is set to project-only.

For agency work, that last behaviour deserves a decision. Client A’s notes should not leak into Client B’s answers. ChatGPT’s project-only memory setting stops saved memories being referenced in project chats and stops chats referencing conversations outside the project, and OpenAI says shared projects always use project-only memory. Turn project-only on at creation for every client project.

How do Claude Projects work for client management?

Anthropic’s help page describes a project as a knowledge base plus instructions. Files, documents, text or code snippets you add become context in every chat in that project. Chats do not share context with each other unless the information is in the knowledge base. You set instructions with “Set project instructions” and Claude applies them to all chats in the project. Free accounts can create up to five projects.

Memory is scoped sensibly. Each project has its own memory. Claude uses that project’s memory plus your memory from chats outside projects, but not memory from other projects. If you want a project walled off further, turn off “Use account memory” on the project’s page. That is the equivalent of ChatGPT’s project-only memory, and for client work we would turn it off on every project that holds one client’s material.

On paid plans, when project knowledge approaches the context window limit, Claude automatically enables a retrieval mode that expands the project’s capacity. That is useful for a client with years of audit history. It also means answers can depend on what was retrieved, so ask narrow questions of large knowledge bases.

Can I share a project in Claude?

Yes, on Team and Enterprise plans, unless your admin has switched sharing off. Open the project, click “Share project”, add people by name or email, choose a permission level and click Share. “Can view” lets a member read the contents, knowledge and instructions and chat in the project but not edit it. “Can edit” lets them change instructions and knowledge and update member settings. On individual plans there is no sharing. Anthropic’s pricing page lists project sharing and collaboration on Team and Enterprise, with Team seats from $20 per seat a month billed annually ($25 billed monthly) in US dollars before tax.

The practical consequence for an agency: if more than one person touches a client, individual Claude plans do not give you a shared client workspace. You need Team seats, or you keep client context somewhere shared and paste it in. ChatGPT is more permissive here, since sharing works down to the Free plan, but the collaborator caps are small until Pro (5 on Free, 10 on Go and Plus, up to 100 on Pro and workspace plans).

Claude vs ChatGPT for project management

Neither Projects feature is project management software. There is no task board, no due dates and no time tracking. What they manage is context. If someone searches “Claude vs ChatGPT for project management”, the honest answer is that both help you write briefs, summarise threads and draft status updates inside a client’s context, and neither replaces your task system. Our own setup keeps tasks in a project tool and uses the AI workspace as the place where the client’s rules, history and reference files live. If you want the AI to read and update your task system directly, that is an integration job, and we describe how we wired it in the MCP and WP Fusion stack post.

What is the difference between a Claude chat and a Claude project?

A normal chat starts from nothing but your account settings and memory. A project chat starts with the project’s instructions and knowledge already loaded, and it uses that project’s own memory. Use a plain chat for a one-off question. Use a project when the same background matters across many chats: a client’s stack, voice and rules; a codebase’s conventions; a recurring report format. A chat inside a project can still be started fresh, with only the instructions and knowledge as context, which is useful when a long thread has gotten heavy.

Are Claude projects private?

On an individual plan a project is yours alone, because sharing is only on Team and Enterprise. On those plans, project members see its contents, knowledge and instructions according to their permission level. Whether your conversations are used for model training is controlled by account and plan settings that we did not re-verify for this update, so open the privacy settings for your plan and read the current wording before putting contracts or unreleased plans in any project. On ChatGPT, a shared project always uses project-only memory, which limits how far its content travels inside your own account.

How should an agency set up a client project?

The setup below works in either tool. It is how we structure it, and you can adjust it.

  1. One project per client, named with the client and the scope. “Acme: support” and “Acme: content” can be separate if the rules differ.
  2. Write instructions as rules, not an essay. Stack and versions, voice, things never to suggest, escalation rules. Keep it short enough that you can read it in a minute.
  3. Upload five to ten files, not fifty. Brand guide, stack notes, a plugin and theme list, the last audit, a glossary. ChatGPT’s limits are 5 to 40 files depending on plan, so use an index file that names what is in each document.
  4. Turn on the memory isolation setting. Project-only memory in ChatGPT, account memory off in Claude.
  5. Keep a session log. After a meaningful conversation, add the decisions and outcomes to one running document in the knowledge base. Memory features help, but a document you can read and correct is more reliable than memory you cannot inspect.
  6. Review quarterly. Delete outdated files and re-read the instructions. An out-of-date brand guide is worse than none.

Use the same discipline for sensitive details: put the minimum in the project, never credentials or customer personal data, and keep the source of truth in your systems. For how we turn project context into monthly client reporting, see care plan reports clients actually read.

Which one keeps client work organised better?

There is no clean winner, and the choice follows from who needs access:

  • Several people touch the same client, and you want it cheap and simple: ChatGPT. Sharing works on every plan, workspace plans allow up to 100 collaborators, and Business is $20 per user a month billed annually on OpenAI’s pricing page.
  • You work solo, or the team shares through Claude Team seats: Claude. Project memory is scoped cleanly, there is a view-only permission level, and retrieval mode extends large knowledge bases on paid plans.
  • You use both: Keep one tool as the home of each client and do not duplicate files across them. Two copies drift apart.

We would not pick on file limits alone, since 25 or 40 files covers most clients. We would pick on sharing, on memory isolation, and on which tool the team already uses for coding. If your developers live in Claude Code, a Claude Team plan keeps the whole workflow in one vendor. For how that role looks in practice, see Claude Code as an agency team member.

What an example setup looks like across three clients

Here is a hypothetical agency with three kinds of client, to show how the choices above play out. It is an illustration, not a case study.

  • A retainer client with a developer, a support lead and a writer all involved. This is a shared-project case. Three or more people need the same context, so a ChatGPT workspace plan or Claude Team seats earn their cost. The project holds stack notes, the plugin list, the brand voice sheet and a session log. Project-only or isolated memory is switched on so nothing leaks to other clients.
  • A one-off build with one developer. A personal project is enough. The knowledge base is the brief, the design handoff and the repository structure. When the build ships, export the useful parts into the handover notes and archive the project.
  • A client with sensitive material, such as unreleased plans or contracts. Put the least possible in any AI project, and keep the originals in your own storage. Check the privacy settings of the plan first. If the contract forbids third-party processing, do not use a project for that material at all.

The common thread is that the project holds working context, not records. The record of truth stays in your own systems, with the project as a convenience layer on top.

What do Projects not do?

It helps to be plain about the limits, because a lot of disappointment comes from expecting a team member rather than a workspace.

  • They do not know today’s state of the client’s site. Live analytics, current tickets and the latest deploy have to be pasted in, or connected through an integration.
  • They are not version control. Replacing a document means removing the old one and adding the new one, and nothing tells the model which is authoritative unless you do.
  • They do not enforce roles beyond the permission levels. ChatGPT offers chat or edit access and Claude offers view or edit. Neither gives you per-document permissions, so do not put a document in a shared project that some members must not see.
  • They do not replace your task system or your documentation. Treat them as a fast way to apply that information, not a place to store it.
  • They can be wrong with confidence. A project makes answers more consistent with your context. It does not make them verified. A person still checks anything that reaches a client.

How do you move a client project from one tool to the other?

Agencies end up switching, or running both. The move is easier if you plan it from the start, and the key is that your instructions and knowledge base should exist outside the tool as plain files.

  1. Keep the instruction text in your own notes. A short text file per client is enough. Pasting it into the other tool takes a minute.
  2. Keep the knowledge files in your own storage with clear names. The project holds copies, and your folder holds the source.
  3. Keep the session log as a document. It is the only part that is hard to recreate, so it matters most to export.
  4. Do not rely on chat history as an archive. If a decision matters, it belongs in the log or in your task system.
  5. After the move, run one real task in the new tool and compare the answer with what you would have expected. Adjust the instructions, because a different model reads the same words differently.

A short checklist before you rely on a client project

  1. Is the memory isolation setting on for this client?
  2. Is anything in the knowledge base a secret, a credential or personal data that should not be there?
  3. Do the instructions fit on one screen, and would a new team member understand them?
  4. Is every file current, with a date in its name?
  5. Does everyone with access need it, at the permission level they have?
  6. Does your client contract allow this use of their material?
  7. Is there a named person who reviews and updates the project each quarter?

If you answer no to any of these, fix it before the project becomes part of how the team works. A tidy project that two people trust is worth more than a large one nobody checks.

When is a project the wrong tool?

Three cases come up often. First, a quick question with no recurring background: a plain chat is faster, and you avoid cluttering the workspace. Second, work that needs exact, current data, such as billing figures or today’s error rate: pull the data from the source and paste the relevant slice, because a stale uploaded export will produce confident, outdated answers. Third, anything that must be reproducible, like a compliance statement or a security assessment: write it in your normal documents with review, and use the AI to draft or check, not to hold the authoritative version.

A good test is to ask what would happen if the project vanished tomorrow. If the answer is “we would lose a convenience”, the project is being used correctly. If the answer is “we would lose the only copy of something”, move that something to your own systems today.

Common mistakes people report

Checked 21 November 2026, paraphrased from public threads and guides. Some of these predate the limits above, so we mark them.

  • Hitting the ChatGPT file cap. A December 2024 thread on OpenAI’s community forum, ChatGPT projects – 20 file limit, complains that a fixed file count is unusable for big codebases. The caps have since changed to 5, 25 or 40 by plan, but the advice holds: summarise and combine files instead of uploading many.
  • Uploads freezing before the stated limit. A Pro user describes hitting a 10-file limit despite a larger allowance. We could not confirm it as a bug, and OpenAI’s help page notes only 10 files can be uploaded at once, which may explain some cases.
  • Claude project instructions followed only some of the time. A DEV Community guide to Claude Projects problems reports instructions being ignored about half the time and suggests shorter, specific instructions. Treat that as one reporter’s experience, not a measured rate.
  • Stale files still being referenced. The same guide describes old file versions staying in play after edits. Delete the old file, upload the new one with a dated name, and say which one to use.
  • Cross-client leakage through memory. The help pages themselves describe the risk: ChatGPT default memory can reference conversations outside a project on most plans, and Claude uses your memory from non-project chats. Use the isolation settings above.

Frequently asked questions

Is ChatGPT Projects free?

Yes. OpenAI lists projects on the Free plan with 5 files per project and up to 5 collaborators. Plus and Go allow 25 files, and Pro and workspace plans allow 40.

Are Claude Projects free?

Yes, with a limit of five projects on free accounts. Paid plans have no cap mentioned in Anthropic’s help article.

Can two people work in the same Claude project?

Yes, on Team and Enterprise plans, with “can view” or “can edit” permissions. Individual plans cannot share a project.

Do Claude or ChatGPT remember across chats in a project?

Both keep project-scoped memory. Claude gives each project its own memory and lets you turn off account memory. ChatGPT offers default and project-only memory, and shared projects are always project-only.

Which should an agency pick?

Pick by sharing needs and by where your developers already work. ChatGPT is easier for wide sharing. Claude fits teams already on Claude Team seats and Claude Code.

How often do these limits change?

Often. OpenAI’s help page lists limits by plan and Anthropic’s does not list file counts. Re-check both pages before you commit a client workflow to either.