If you've used Artifacts in Claude, you know the experience of having AI generate previewable React components, SVGs, or HTML widgets right in the sidebar. For a long time, though, Artifacts had an obvious shortcoming: the things it generated were hard to get out of Claude and show to anyone — let alone edit together. Anthropic has now filled that gap — Artifacts support public link sharing, and multiple people can edit the same Artifact at the same time (Anthropic and the press call it "multiplayer").

This article is based on Anthropic's official support documentation and cross-checked against several media reports, and it explains how to use the capability and how it differs from the easily confused Claude Code Artifacts.

What This Capability Actually Is

Anthropic's official support doc (support.claude.com/en/articles/9487310) describes Artifacts as turning ideas into shareable apps, tools, or content. The newly added capability breaks down into two independent things:

1. Public sharing (Publish & Share): click the publish button at the bottom of the Artifact panel to generate a public link that anyone can view without logging into Claude; you can also embed the Artifact into external web pages
2. Real-time multiplayer editing (Multiplayer): multiple people can edit the same Artifact simultaneously, similar to the live collaboration experience of Figma/Google Docs

Media outlets (AlphaSignal, VentureBeat, and others) all boiled the change down to one line: Artifacts are now multiplayer. The significance is that Claude's output has been upgraded from "something only you can glance at" to "a starting point for team collaboration."

How to Use It: From Generation to Sharing

Step 1: Generate an Artifact in Claude

Ask Claude to generate something that suits the Artifact format, as usual. The types most likely to trigger an Artifact:

• React / Next.js components (the most common)
• Small pages and widgets built with HTML + CSS + JS
• SVG graphics or Mermaid flowcharts
• Markdown documents

For example, just say: "Write me a React component that takes a date and renders a countdown card for it — make it look good." Claude renders the code into an interactive preview that appears in the Artifacts panel on the right.

Step 2: Click Publish to generate a public link

At the bottom of the Artifact panel, find the Publish button. Clicking it generates a publicly accessible link. Send that link to a colleague or client, and they can open it in a browser and see the fully runnable preview — no Claude account required, no source code to read.

If you want to embed it in your own blog, Notion, or Confluence, you can grab the embed code too.

Step 3: Invite others to edit together

Once multiplayer mode is on, collaborators can not only view but edit the same Artifact directly — rewriting copy, adjusting styles, adding interactions. Everyone's changes sync in real time, and you can see what the others are doing.

💡 Tip: multiplayer fits the "AI produces the first version + the team polishes it by hand" workflow. Let Claude lay down the structure and styling first, then have the designer tune the palette and the PM rewrite the copy — faster than asking the AI to regenerate from zero every time.

Step 4: Download or Remix

Beyond online sharing and collaboration, Artifacts also let you download content locally (HTML files, source files), or Remix someone else's Artifact into your own version. This path is very practical for developers who want to turn an AI-generated demo into real project code.

Don't Confuse It With Claude Code Artifacts

Anthropic also has a similarly named product, Claude Code Artifacts, which entered beta on 2026-06-18. The two are not the same thing:

Put simply: web Artifacts share "a thing the AI made"; Code Artifacts share "the process of the AI writing code." This article is about the former's multiplayer and public sharing.

Use Cases

• Interactive demos: a PM has Claude generate an interactive prototype, publishes the link, and sends it straight to design/boss/client for review
• Teaching/tutorials: a teacher turns runnable code examples into an Artifact; students open the link and start tweaking parameters to see effects
• Data dashboards: have Claude render data into React chart components and share them with the team for live viewing and tweaking
• Embedded widgets: embed an Artifact in an internal wiki so the team can use it anytime instead of each rewriting it
• Cross-functional collaboration: a designer tweaks the UI in multiplayer while a developer adjusts the logic, and the AI integrates both sides' changes

Things to Watch Right Now

• Rollout scope: multiplayer and public sharing are rolling out to Team and Enterprise plans first; for individual plans, follow the official announcements for timing
• Size/resource limits: for Code Artifacts, a single page has CSP restrictions and an approximately 16 MiB size cap (see third-party deep dives such as Digital Applied); Web Artifacts carry similar sandbox limits, and complex dependencies may not run
• "legacy Artifacts" retirement: in mid-May 2026, Anthropic notified Team/Enterprise admins that old Artifacts, custom Styles, and similar features would be adjusted over time — watch the official changelog to see whether features you rely on are affected
• Scrub it before sharing: once published, the link is publicly accessible; if the Artifact contains real business data, API keys, or customer information, remove them before you share

Bottom Line

Multiplayer + public sharing upgrades Claude Artifacts from "personal toy" to "starting point for team collaboration." The most immediate benefit: you no longer screenshot the React component Claude generated into Slack and then paste the code into GitHub — one link lets others see something that actually runs, and edit it together. If your team is already on Claude Team/Enterprise, run this capability through its paces today; the difference is immediately obvious.