Repeated background
You keep explaining the same client, initiative, course or research topic.
Use a Project when the background should persist across multiple chats, but each question or deliverable still deserves its own conversation.
You keep explaining the same client, initiative, course or research topic.
You keep uploading the same files or referring to the same connected material.
Several chats should share context without becoming one very long conversation.
Project-only memory keeps the context self-contained. Shared Projects use it automatically. Remember that deleting a Project permanently removes its chats, files and instructions.
A well-organized Project separates standing context from individual pieces of work so future chats remain understandable.
Put guidance here when it should apply to every chat in this body of work. These instructions override your global Custom Instructions while you are inside the Project.
Store files, supported links and saved responses that you expect to reference repeatedly. Keep one-off material inside the relevant chat when it does not belong to the wider context.
Use a separate chat for each substantial question, analysis or output. This preserves shared context without turning the Project into one unmanageable conversation.
Choose how widely context can travel, understand what collaborators can see, and use Projects as a context container rather than as a substitute for every other reusable feature.
The choice determines whether a Project can draw on relevant personal context from outside the Project and whether its conversations can influence work elsewhere.
Collaborators can work from the Project's shared chats, files and Project instructions, giving the group one consistent body of background information.
Shared Projects automatically use Project-only memory. This keeps personal context outside the Project from being mixed into the shared workspace.
The owner manages whether access is invite-only or available through a supported sharing link. A single chat can also be shared without exposing the entire Project.
It becomes most valuable when the same files, history and instructions matter across several separate conversations. Keep distinct deliverables in distinct chats so the Project remains easy to navigate.
A few boundaries affect how Projects interact with other ChatGPT features and connected sources.
Existing eligible chats can be moved into a Project when they belong to that body of work. Chats created with a custom GPT cannot currently be moved into a Project.
Connected Apps can be used inside Project chats, although ChatGPT may ask before searching beyond the Project boundary. Supported Drive links and Slack channels can also become Project sources.
Deleting a Project permanently removes its chats, files and instructions. Review what needs to be retained or exported before removing the Project.