know.2nth.ai › Agents › Claude artifacts
agents · surfaces · Anthropic

Claude artifacts.

Anthropic's publishing surface for Claude: private pages and typed documents, made from chat, the Artifacts tab, Claude Code or mobile. They can hold data, show it to the people you choose, and call those people's own connected apps. They have no server of their own. The limits below are the ones Anthropic documents, as of November 2026.

Anthropic · Claude surface Reference explainer Hot · quarterly review

A place to publish what Claude made.

An artifact is a page or a typed document that lives on claude.ai, opens for the people you share it with, and runs on their own Claude plan and connections. It is not a hosted app with a backend.

Artifacts started as a side panel in chat: Claude writes a page, you look at it, you iterate. That is still the core use. What has changed is that artifacts now come in typed templates (Docs, Slides, Design, Data, Sheets, Whiteboards, Motion), can be shared with specific people or an organisation, and can read and write through the connected apps of whoever is looking at them.

Two things are easy to get wrong when you read older guides. Several third-party guides still say artifacts cannot store data, or cap them at 20 MB. Those statements describe the legacy kind of artifact only. The second is that "artifact" now covers more than a web page: a Docs document is an artifact too.

Legacy artifacts still work. You can't make new ones that way.

Artifacts made in a chat before 16 September 2026 are legacy artifacts. They keep working and can still be published and shared. They cannot be newly created.

New

Templates and hand-built pages

  • 100 MB and 25,000 documents per artifact, whichever comes first
  • Uploads: 20 MB per file (2 MB for SVG), 5,000 files and 1 GB per artifact
  • Connectors and calls to Claude available as described in section 05

Which template is on which plan.

Availability and export formats as the Help Center lists them. The Help Center marks only Sheets, Whiteboards and Motion as beta. Check the status of any template you plan to depend on, because beta status can change.

Template Plans Exports to Status
DocsAll plans, including FreeWord, PDF, Markdown, Google DocsNot marked beta
SlidesAll plans, including FreePowerPoint, PDF, Google SlidesNot marked beta
DesignAll plans, including Free.zip, PDF, PowerPoint, standalone HTMLStandalone Claude Design closes 14 Dec 2026
DataPro, Max, Ultra, Team, EnterpriseNot statedNot marked beta
SheetsPro, Max, Ultra, Team, EnterpriseNot statedBeta
WhiteboardsPro, Max, Ultra, Team, EnterpriseNot statedBeta
MotionTeam and EnterpriseMP4Beta

The Docs template, the parts that matter for sharing.

Docs is the template most people will hand to colleagues. Its sharing rules are stricter than a page's.

Roles

Owner, editor, commenter and viewer. Anyone can comment with @Claude in a comment.

Opening a shared doc

Sign-in is required. A link viewer gets view-only access.

Deletion

Deleting a doc is permanent. There is no trash to restore from.

Audit gap

Doc edits and comments are not yet recorded in the Compliance API. Don't rely on the Compliance API for doc activity until Anthropic says otherwise.

Your data, your connectors, your limits.

An artifact runs in the viewer's browser and calls out only where it is allowed to.

Connectors

Reads and writes go through each person's own connected apps, custom connectors included. Pro and above, on web and desktop. First use needs approval. Tools that need approval for each action are not available to artifacts.

Calls to Claude

A call from an artifact counts against the viewer's own plan limits.

Storage

Personal or shared. Shared storage shows the same data to everyone who opens the artifact.

Viewers see different data

Because connectors run as the viewer, two people can open the same page and see different data.

Who can open it, and what outside people lose.

Sharing depends on your plan and your admin's settings. The Help Center has the full plan-by-access table; the rules below are the ones that most often catch people out.

The rules that bite

Each artifact can be shared with up to 50 outside invitees. Pending invitations expire after 30 days.

An artifact that connects to other websites cannot use link sharing or email invitations.

Claude and connectors do not work for outside viewers. An outside viewer sees the page and its data, not the assistant.

The switches an admin has, and the one they don't.

Per-template toggles

Admins can switch each template on or off for the organisation.

External sharing

A separate switch controls whether artifacts can be shared outside the organisation.

Artifact connectors

One organisation-wide switch. There is no per-app limit, so an admin cannot allow artifacts to reach some apps and not others.

Usage

Artifact use draws on seat limits or, for usage-based Enterprise, API rates.

Claude Design residency

Claude Design does not support data residency requirements.

Publishing a session's output as a page.

Claude Code can publish a session's output as an artifact. It is a narrower thing than a claude.ai artifact.

What a Claude Code artifact is

One self-contained page with no backend. It cannot serve multiple routes or authenticate viewers itself. Sources can be .html, .htm or .md. The rendered page is capped at 16 MiB.

Its content security policy allows Google Fonts and five public CDN hosts. Network calls reach only the page's own origin, so any other outside call has to go through a connector.

Available on Pro, Max, Team and Enterprise. It is not available in sessions on Amazon Bedrock, Google Cloud or Microsoft Foundry, or in API-key sessions. Content is stored on Anthropic-operated infrastructure under the retention policy. Admins see claude_artifact_* audit events, and three Compliance API endpoints cover artifacts.

Connector calls from a Claude Code artifact need Claude Code v2.1.209 or later. The /slides and /design commands need v2.1.265 or later.

When an artifact is the right surface, and when it isn't.

Honest tradeoffs. For the full argument on whether an artifact should be your long-term home, see the decision leaf.

Use an artifact if…

It fits

  • The people looking at it all sit inside one Claude organisation
  • The data lives in a system the page reads through a connector
  • Nothing needs to run while the page is closed
  • You want a view you can regenerate in an afternoon

Where the data sits, and what POPIA asks.

Residency. Claude Code artifact content is stored on Anthropic-operated infrastructure. The Team and Enterprise admin guide gives no residency commitment for artifacts. Treat personal information in artifact storage as a POPIA Section 72 cross-border transfer, the same position this tree takes on Claude inference. See the residency validation page.

Cost. There is no hosting line item, which makes an internal tool look free in rand terms. The cost moves to seat limits, and a heavy shared dashboard shows up there.

Where this leaf links into the rest of the tree.

Primary sources.

Checked 21 November 2026. Artifacts change often; verify against these pages before you depend on a limit.