Artifacts
PlatformDefinition
A separate, editable window in Claude's interface for substantial, self-contained deliverables -- a document, table, or piece of content -- that will be refined, reused, or shared, distinct from an inline chat reply. Matching a deliverable's lifecycle (one-off read vs. ongoing revision vs. shareable output) to the right output surface, rather than defaulting to one format, is the underlying judgment call.
Example Usage
A one-page client proposal that will go through several rounds of editing belongs in an Artifact, not buried as a long message in the chat scroll -- the separate window gives it the persistence and shareability the deliverable needs.
In Depth
Three Output Surfaces, Not One
Claude offers three distinct ways to deliver output, each suited to a different kind of deliverable:
| Surface | Best for |
|---|---|
| Inline response | Short answers, quick edits, conversational back-and-forth |
| Artifact | A separate, editable window for a substantial, self-contained deliverable that will be refined, reused, or shared |
| Structured data (tables, JSON) | Output feeding a spreadsheet, form, or downstream system |
An Artifact is not simply a longer chat message -- it is a persistent, editable, shareable space that exists outside the linear conversation thread, so the deliverable itself (a proposal, a report, a piece of drafted content) can be iterated on and handed off independent of the chat that produced it.
Matching Surface to Lifecycle
The choice of surface should track how the output will actually be used:
- A quick clarifying answer that will be read once and forgotten fits inline.
- A one-page proposal that will go through several rounds of editing and be shared with a client needs the separate, persistent space an Artifact provides.
- Data headed into a spreadsheet or another program needs the predictable, parseable shape of structured output.
Common Pitfalls
- Wrapping a two-line answer in an Artifact, which adds friction without benefit.
- Leaving a polished, iterate-and-share deliverable buried inline in the chat scroll instead of promoting it to an Artifact.
- Defaulting to one format for every kind of output rather than making a deliberate choice each time based on how the result will be used.
- Assuming an Artifact being well-formed (a clean table, valid-looking JSON) is the same as it being *correct* -- the surface controls presentation and shareability, not factual accuracy, which still needs the same validation as any other output.