Claude Code Artifacts: Share Live Pages from Sessions

Claude Code artifacts turn session output into a live, shareable web page at a private URL — updated in real time as Claude keeps working. Here's how they work.

claude-codeartifactsshareteamenterprise
↻ Updated 2026-11-04EAEvgenii ArsentevEvgenii Arsentev · PhD

Reviewed for accuracy by Evgenii Arsentev, PhD · 2026-11-04

Artifacts are live web pages that Claude publishes during your session. When you tell Claude to create an artifact (e.g., “show me a diff of this PR”, “build a dashboard based on the data you just fetched”, “compare these two UI designs”), Claude generates an HTML file and publishes it to a private URL on claude.ai. As you keep working, the artifact will automatically update. There’s no need to deploy or build anything — just let Claude handle it!

I use artifacts for reviewing PRs within my team. Rather than sharing a bunch of terminal output showing diffs, I share a link to a webpage that displays the diff with annotations for each chunk. My colleagues can then click on the link, view the diff, and provide feedback without having to sift through terminal outputs. This is a perfect example of how to use artifacts — to make information more visually accessible than it would be if you had to read it character by character.

ℹAll paid plans

Artifacts require a paid plan (Pro, Max, Ultra, Team, or Enterprise) and a session signed in with /login.

What is a Claude Code artifact, exactly?

It’s a standalone HTML file — just one file, no backend! You can access any information available to your session, including your code, data from other integrated tools, results from commands, etc. It doesn’t support storing form data or serving multiple request paths, but it does support making MCP connector calls to get dynamic data when rendering the page (so the page is “live”), and it can generate visualizations, diff annotations, mockups, or even track an investigation timeline as you wait for a lengthy process to complete. Artifacts aren’t meant to be full-fledged applications with backends — if you want that, don’t use artifacts; deploy your own infrastructure. Instead, think of artifacts as snapshots of work (with optional dynamism).

How do you create a Claude Code artifact?

Use simple language to describe what you want to see. Based on your description, Claude will determine if it can create the result you’re looking for. If so, Claude might choose to share an artifact on a relevant page. Simple requests are published immediately without asking for permission. In some instances (e.g., plan mode, pages with connectors or files to download, or public artifacts you’ve created), Claude will ask before publishing. After publishing, the page will open in your web browser.

Three prompts to try right now

  1. 1Make an artifact that walks through this PR with the diff annotated inline and color-coded by severity.
  2. 2Build a dashboard artifact of last week's deploy failures by service and keep it updated as you investigate.
  3. 3Make an artifact with four different layouts for the settings panel — lay them side by side with a one-line tradeoff under each.

You can use Ctrl+] to jump back to the last created artifact from the command line. You can disable automatic opening of browser for newly created code artifacts by setting the environment variable CLAUDE_CODE_ARTIFACT_AUTO_OPEN=0.

How do you update an artifact?

Ask Claude to edit your work. It will edit the HTML code behind the scene and republish the page to the same URL. If you are viewing this page, you should see the changes immediately. Every time you publish, it will create a version of the page. You can select a specific version using the Share button on top of this page. Use this feature if you would like to share a particular version of the page while you continue to improve it.

To edit an existing artifact, provide Claude the URL of the artifact and ask it to edit. If Claude doesn’t have the URL of the artifact, it will always generate a new one for you.

Update an artifact from a new session
Update https://claude.ai/code/artifact/<id> with today's numbers.

Paste the artifact URL directly into your prompt. Claude fetches the current page, applies the changes, and publishes a new version to the same link.

Who can see a Claude Code artifact?

This is a brand new artifact! You’re the first person to see it. To share this artifact with others, click on the Share button at the top of this page. If you’re on a Pro, Max, or Ultra plan, you can only share this artifact using a public link. Anyone with this link will be able to view the artifact without logging in. If you’re on a Team or Enterprise plan, you can choose whether to share the artifact with individual users or all users in your organization (who need to log into claude.ai to view the artifact). You can also set someone as an editor, which allows them to edit the artifact and publish updated versions from their own sessions. Note that if you’re on a Team or Enterprise plan, you’ll need to enable external sharing in your organization settings before you can share via public link. By default, external sharing is disabled.

✓Your gallery is at claude.ai/code/artifacts

Every artifact you've ever published lives there — title, emoji icon, and a version history. The page header on each artifact names you as the author, so teammates always know who published it.

What can you actually build? The best artifact use cases

The constraint is 'one HTML page, no backend'. Within that, the list is long. PR walkthroughs with annotated diffs are the most common. Dashboards built from data Claude already pulled through MCP tools — or live dashboards that call your MCP connectors each time a viewer opens the page to show current data. Side-by-side option comparisons — layouts, copy variants, API shapes. Investigation timelines that Claude fills in as a long task progresses. Meeting summaries with a clean visual format instead of bullet-point walls. If you'd normally paste the output into a doc or Slack and format it manually, an artifact saves that step and gives you a live, version-controlled page instead.

Artifacts vs regular file output: when to use which

Artifacts are great for sharing results with your colleagues without having to attach files, for displaying information in a visually appealing way (e.g., charts, comparisons, diff with colors), and for seeing the results change live as Claude continues to work. Files are ideal for generating outputs that need to be shared outside of your company, require backends or multiple routes, or produce data that will be used by other tools.

Note: Artifacts have changed a lot since their initial release and will likely continue to change. All the information in this post is correct as of October 2026. If Claude tells you that it cannot publish an artifact, make sure that you’re using a paid plan (Pro, Max, Ultra, Team, Enterprise) and that you’re logged in (/login). These are the most common reasons why users can’t publish artifacts.

Free course

Stop reading about AI — start building with it

The free Claude Code course: your first site, tool or game — no coding. No upsells, no cross-sells — nothing to buy here.

Start free →
EAEvgenii Arsentev

Author

Evgenii Arsentev

PhD · Founder & CEO, Dad4Kids

Reading is a good start

Want to actually build this?

Guides explain. The free course transforms — personalized, gamified, and built to get you shipping fast.

Start the free course →