ChatGPT Projects give ongoing work a home. Instead of scattering a research job, client brief, study plan, or writing assignment across unrelated chats, you can keep its conversations, reference material, and instructions together. The useful part is not the colored folder in the sidebar. It is the shared context that follows each conversation inside that project.
This guide follows OpenAI’s current Projects documentation and ChatGPT release notes. The interface and limits can change, so check those pages if your account shows different controls. The workflows below are recommendations, not claims of personal product testing.
What a ChatGPT project contains
A project brings four types of context into one workspace: chats, uploaded or linked sources, project instructions, and project memory. They do different jobs. Chats hold the working history. Sources supply documents or saved material. Instructions define how ChatGPT should respond in that project. Memory lets an eligible chat refer to relevant context from other conversations in the same project.
That separation helps when one subject needs several threads. A product launch project might have one chat for audience research, another for a launch calendar, and another for editing campaign copy. Each conversation stays readable, while the project provides common files and guidance. This is usually cleaner than forcing every task into one enormous chat.
Projects are available on free and paid ChatGPT subscriptions.
Build the source layer before starting more chats
OpenAI documents several ways to add project sources. You can upload PDFs, spreadsheets, documents, and images, or paste text. You can also save a useful ChatGPT response back to the project as a source. In a private project, supported Google Drive files or folders and Slack channels can be added by link. Connected apps may also be used from a project chat, although ChatGPT may ask before searching outside the project.
Do not turn the source list into a junk drawer. Keep the smallest set that reliably defines the work. For a recurring report, that might be the approved metric definitions, the latest source dataset, and a short style guide. Remove superseded drafts when retaining them would make it unclear which version governs. In a shared project, deleting a file removes it for every member, so agree on replacements before cleaning up common material.
File capacity depends on the owner’s plan. The current Help Center lists 5 files per project for Free, 25 for Go and Plus, and 40 for Pro, Business, Enterprise, and Edu. It also says users can create an unlimited number of projects. These are product limits, not a reason to fill every available slot. If you hit the cap, OpenAI recommends removing older files, combining material, or splitting the work into separate projects.
Write project instructions that can survive many chats
Project instructions belong in Project settings. They apply only within that project and override global custom instructions there. Keep them focused on durable behavior rather than the next small task. State the role ChatGPT should take, the intended audience, preferred output shape, source rules, and what to do when information is missing.
For example, instructions for a policy research project might say: “Write for non-specialist managers. Distinguish quoted policy from interpretation. Cite the supplied source for each material claim. If the files conflict, name the conflict instead of choosing silently. Use short sections and finish with unresolved questions.” The prompt in each chat can then describe the immediate assignment.
Review instructions when the work changes. A project that moves from exploration to final publication may need stricter citation and approval rules. Do not bury passwords, credentials, private keys, or sensitive personal data in instructions. For more detail on the difference between account-wide preferences and local guidance, see our ChatGPT custom instructions guide.
Project memory is not the same as general memory
When creating a project, users can choose default memory or project-only memory when the required memory settings are enabled. Existing projects that predate project-only memory cannot simply be converted through a global switch. OpenAI says you need to create a new project for that mode, although eligible conversations can be moved between projects.
Project-only memory creates the clearest boundary. Previously saved personal memories are not referenced. Chats may reference other conversations inside that project, but not general ChatGPT chats or another project. There is no separate list of “project memories” to inspect. If a particular conversation should stop influencing the project, OpenAI’s documented remedy is to move or delete that conversation.
Default memory behaves differently. Saved memories may be used, and project chats can refer to other chats in that project. For non-Enterprise subscriptions, including Business, conversations outside the project may also be referenced when account memory is enabled, except where a project-only boundary applies. In Enterprise and Edu workspaces, project chats remain contained within the project even under default memory. Our current ChatGPT memory guide covers the wider account controls.
Memory is selective context, not a database guarantee. Keep the controlling fact in a source or repeat it in the task prompt when an answer depends on it. Temporary chats cannot be added to projects.
Move chats without importing confusion
An existing eligible chat can be dragged onto a project or moved through its menu. After the move, it inherits that project’s instructions and file context. Chats created with a GPT cannot be moved into a project, according to the current help article. If Move to project does not appear, start a fresh conversation inside the project.
Before moving a chat, read its earlier messages for assumptions that conflict with the destination. A conversation based on an old brief may keep referring to it even after gaining the new project’s sources. Add a transition message that identifies the governing source and asks ChatGPT to list any unresolved conflict before continuing. You can later remove a chat from the project through its menu.
Search matters once a project grows. OpenAI’s July 14, 2026 release note says sidebar search can find chats, projects, images, and documents on web, iOS, and Android, with filters by content type. Our unified ChatGPT search guide explains that broader retrieval workflow.
Sharing, roles, and what collaborators can see
OpenAI says project sharing is available globally on web, iOS, and Android for Free, Go, Plus, and Pro, as well as Business, Enterprise, and Edu. Sharing options still differ by workspace. Consumer users can invite individuals. Business, Enterprise, and Edu can also invite workspace groups, subject to workspace controls. Owners may also use link sharing where available.
There are two collaborator access levels. Chat access lets a member view and interact with project chats, files, and instructions but not invite others. Edit access also permits changes to instructions and files and allows invitations, but an editor cannot remove existing members. The owner controls the project name, member permissions, removals, and deletion.
Shared projects are visible workspaces, not private folders with a common prompt. Members can see project chats and files, download files, and view the member list. Each new, moved, or branched chat is associated with its author. Work is not synchronous inside one conversation: a member branches a chat to explore a different direction while preserving the original.
Once a project is shared, its memory automatically becomes project-only and cannot return to default memory. Members may move their own chats out, archive them, or delete them; after removal, other members and the owner lose access to that chat. If the owner deletes the project, its files, chats, and instructions become unavailable to collaborators unless something was copied beforehand.
Privacy boundaries and accidental sharing
Project-only memory prevents context from crossing the project boundary, but it does not make every item private from collaborators. A member who moves a chat into a shared project exposes that chat to the project’s members. A file added there may inform answers that everyone in the project can read. People with file access can download those files. Review a chat and its attachments before moving it, and confirm the member list before uploading confidential material.
For shared projects on personal plans, OpenAI says training occurs only if every contributor and the owner has “Improve the model for everyone” enabled. For organization products, OpenAI’s business data privacy page says inputs and outputs from Business, Enterprise, and Edu are not used to train models by default. Workspace policies and applicable retention controls still matter. Ask your administrator which plan, settings, and compliance rules govern the actual workspace.
A single-chat share link is narrower than sharing a project. For a chat in a personal project, the viewer sees that chat, not the other project chats, files, instructions, or history. A chat shared from a shared project cannot be viewed until the recipient joins that project. Even narrow sharing can reveal everything in the chosen conversation, so inspect it first.
A practical organization workflow
- Define the boundary. Name the project for one durable outcome, not a whole department or your entire life. Decide whether the content requires project-only memory before creation.
- Add a short source index. List each source, owner, effective date, and purpose in a plain document. This makes stale or conflicting material easier to spot.
- Set durable instructions. Describe audience, evidence standard, output conventions, and how uncertainty should be reported. Keep task-specific details in chat prompts.
- Use one chat per deliverable or question. Separate research, drafting, calculations, and final review when their histories would otherwise become tangled.
- Save decisions, not every answer. Add an approved summary or decision note to project sources when later chats must rely on it. Label the date and status.
- Run a weekly cleanup. Archive finished threads, move unrelated chats, replace obsolete files, and check membership. Do not delete shared sources without warning collaborators.
- Review before sharing or publishing. Open cited sources, check calculations, remove private details, and have the responsible person approve the final result.
Plan and workspace differences to remember
All qualifying plans include Projects, but model rate limits, tool access, file capacity, and collaborator capacity follow the subscription. The current consumer collaboration limits are 5 files and 5 collaborators for Free, 25 files and 10 collaborators for Go and Plus, and 40 files and 100 collaborators for Pro. Business, Enterprise, and Edu currently support 40 files and up to 100 people in a workspace project.
Enterprise adds administrative controls that consumer projects do not provide, including role-based controls related to sharing and Compliance API support for listing shared users or isolating a project. Those controls do not replace careful membership review. If a control is missing, it may have been disabled by the workspace administrator rather than removed from ChatGPT.
Frequently asked questions
Can ChatGPT Projects use conversations outside the project?
It depends on memory mode and plan. Project-only memory cannot use outside conversations. Under default memory, non-Enterprise plans may reference outside chats when memory is enabled, while Enterprise and Edu project chats remain contained within the project.
Can I change an existing project to project-only memory?
OpenAI says no. Create a new project with project-only memory, then move eligible conversations that belong there. Sharing an existing project also changes it to project-only memory permanently.
What can an editor change in a shared project?
An editor can update project instructions, upload or remove files, and invite others. Editors cannot remove existing members. The owner retains full permission and deletion controls.
Does deleting a project keep a backup for collaborators?
No. Deleting a project permanently removes its chats, files, and instructions and cannot be undone. Collaborators lose access unless they made an allowed copy beforehand.