Choose a chat, Project, or Artifact

Back to: Claude Documents & Artifacts Lab

Pick the smallest Claude workspace that fits the job before adding files or instructions.

Reviewed September 2026. Interface labels, file support, limits, and sharing options can vary by account, plan, and region. Check the linked first-party guidance in your own workspace.

The situation

A normal chat, a Project, and an Artifact solve different problems. A chat is a conversation. A Project groups related chats with shared knowledge and instructions. An Artifact is standalone output—such as a document, small app, calculator, or interactive explainer—that can be viewed and worked on beside the conversation.

Starting in the wrong container creates needless friction. A quick rewrite does not need a Project. A six-week policy review probably does. A calculator that colleagues will use should not remain buried in a transcript.

Do the work

1. Describe the outcome, how long the work will live, who needs it, and whether the source pack will be reused.
2. Use a normal chat for a bounded exchange with no durable shared context. Start a Project when several conversations need the same documents, terminology, or operating rules.
3. Plan an Artifact when the result must stand on its own or be interacted with. Write down its user and one action it should make easier.
4. Create a simple boundary: source material lives in project knowledge; task-specific direction belongs in the current chat; the Artifact contains only approved output.
5. Run a one-minute exit test. If you stopped using Claude tomorrow, could you export or copy the useful result into the system where it belongs?

WORKSPACE DECISION
Outcome:
Useful for: one hour | one week | ongoing
Shared source pack: yes | no
Several related chats: yes | no
Standalone or interactive output: yes | no
Choose: Chat | Project | Artifact
Why this is the smallest fit:

Quality check

• The choice is based on the work, not novelty.
• Long-lived sources are separate from task instructions.
• The intended Artifact has one named user and action.
• The final result can leave the chat.
• No confidential file was added before checking policy.

Keep current

Use these official sources when an interface label, retention choice, file type, or sharing option matters. Treat the lesson as a workflow—not a substitute for your organization’s policy.

• Anthropic: What are Projects?
• Anthropic: What are Artifacts and how do I use them?