Artifacts
Standalone, shareable outputs Claude renders beside the conversation — documents, code, and self-contained web pages you can publish and update.
Last verified August 21, 2026 · 1 source
An Artifact is output that gets its own panel rather than scrolling past in the conversation: a document, a piece of code, a chart, a self-contained web page. It persists, it can be revised in place, and it can be shared.
Why it is worth treating as its own entity
Artifacts started as a Claude-apps feature but are now also a documented Claude Code output path — a way to publish the result of a session as a page. That makes it a shared capability across two products rather than a feature of one, which is exactly the kind of relationship that gets lost when each product is documented separately.
What it is not
- Not a hosting product. An Artifact is a page attached to your account, not a deployment target with a custom domain.
- Not the same as Claude Design. Design is a research-preview product for visual work; Artifacts is the general output container.
What this page does not claim
Sharing scopes, retention, size limits and per-plan differences are not documented in the source checked. Treat the plan row as “available”, not as “identical everywhere.”
Plan availability
Anything left blank is not documented publicly, not a claim that it is unavailable. Compare every feature at once in the availability matrix.
- FreeIncluded
- ProIncluded
- MaxIncluded
- TeamIncluded
- EnterpriseIncluded
- APINot available
Sources
- 01Share session output as artifacts — Claude Code docsOfficialcode.claude.com
Page changelog
- VerifiedConfirmed as a documented Claude Code output surface in addition to the Claude apps.