To publish a Claude artifact, open it in claude.ai, click Publish in the top-right corner of the artifact panel, and copy the link. Anyone with that link can open the artifact in a browser, no Claude account needed. That is the whole flow on Free, Pro and Max plans for artifacts made in chat.

The catch in September 2026 is that there are now three different buttons depending on where the artifact came from and which version of Claude you are on: Publish (chat artifacts on the previous experience), Share (the new Claude experience and Team/Enterprise plans), and the Share control on a Claude Code artifact page. They produce different URLs and have different rules about who can open them. This guide walks through each one, then covers the one mistake you cannot undo: unpublishing.

I checked every step below against Anthropic’s Publish and share artifacts help article and the Claude Code artifacts docs on 19 September 2026. We build InstaPods, a host for small apps, so we care about this because a lot of our users arrive with an artifact they want online.

Which publish option do you have?

Which Claude artifact publish option you get depends on two things: where the artifact was made and which plan you are on. Use this table to find your row, then jump to that section.

Where the artifact was madeButtonPlansLink formatViewer needs a Claude account?
Chat (previous experience)PublishFree, Pro, Maxclaude.ai/public/artifacts/<id>No, only for AI-powered features
Chat (new Claude experience)SharePro, Max (rolling out)Share linkYes, per the help center
Chat on Team / EnterpriseShare & copy linkTeam, EnterpriseShare linkYes, sign-in required
Claude Code sessionShare (page header)Pro, Max, Team, Enterpriseclaude.ai/code/artifact/<id>No, for a public link

If you do not see a Publish button in a chat, you are most likely on the new Claude experience, which Anthropic says is “rolling out gradually to Pro and Max plans”. The Share button replaces it.

How to publish a Claude artifact with the Publish button

The Publish button is how Free, Pro and Max users make a chat artifact public on the previous Claude experience. It takes three steps:

  1. Open the conversation and click the artifact so it shows in the side panel.
  2. Click Publish in the top-right corner of the artifact panel.
  3. Copy the link and send it wherever you want.

The link looks like https://claude.ai/public/artifacts/<uuid>. The UUID is random, so nobody finds the page unless you share it. Published artifacts also appear in the Artifacts section of your sidebar, which is the easiest place to find a link again later.

Two details from the help center are worth knowing before you share it widely. First, the link is tied to the version you published: if you keep iterating in the chat, people with the link still see the version you published. Second, viewers without an account can view and interact with the page, but they are “prompted to sign up only for advanced features like using AI-powered capabilities”, and anyone who does use those features spends their own usage limits, not yours.

For what that URL can and cannot do (indexing, link previews, the API question), see what is a claude.ai/public/artifacts URL.

How to share an artifact on the new Claude experience

On the new Claude experience, a Claude artifact is shared from a Share button instead of published. The steps from Anthropic’s help article:

  1. Open the artifact and click Share.
  2. Choose who can open it. On Pro and Max the choices are Only you or Anyone with the link. Team and Enterprise add specific people, Only people with access and Everyone in your organization.
  3. Choose whether viewers see the latest version or a specific version.
  4. Copy the link.

The version choice fixes the old Publish flow’s biggest annoyance: you can let the shared link follow your edits instead of freezing it.

The trade-off is the audience. The help center says “Everyone who opens these artifacts needs a Claude account”, so a Share link is a poor fit for a client or a customer who has never used Claude. On Enterprise plans an Owner also has to turn on External sharing before anyone can pick “Anyone with the link”. One more line from the help article to read before sharing: shared artifacts give viewers access to files attached in the original conversation.

How to publish an artifact from Claude Code

A Claude Code artifact is published to a private page first and made public second. You ask Claude Code for one (“make an artifact that walks through this PR”), it writes an HTML or Markdown file and publishes it to a claude.ai/code/artifact/<id> URL that only you can see. Per the Claude Code docs, it needs a Pro, Max, Team or Enterprise plan and a session signed in with /login; API-key sessions cannot publish.

To make it visible to others, open the page in your browser and use the Share control in the header:

Asking Claude to change the page republishes it to the same URL, and anyone with it open sees the update in place. The page limits are real, though: one self-contained HTML page, no backend, 16 MiB maximum, and scripts only from a short list of CDNs. An artifact that calls MCP connectors cannot be shared publicly on any plan.

Unpublishing is permanent, so think before you click

Unpublishing a Claude artifact cannot be reversed. Anthropic’s wording is direct: “Once you unpublish an artifact, you cannot publish that same artifact again.” Unpublishing also permanently deletes any data the artifact stored, both personal and shared.

In practice this bites people who unpublish to fix a typo. The old link is dead for good, and the only way to share again is to copy the code into a new chat, let Claude recreate the artifact, and publish that, which mints a new UUID. Every place you pasted the old link (docs, emails, a client’s bookmarks) now points at nothing.

If you might need to change the page later, publish from the Share flow with “latest version” selected, or keep the source somewhere you control so the link is not the only copy.

Can you embed or put a published artifact on your own domain?

A published Claude artifact can be embedded on another site, but it cannot move to your own domain. After publishing, a Get embed code button appears; you list the allowed sites, comma-separated, and paste the snippet into your page. The embed still loads from claude.ai, so Anthropic is still hosting it: you are placing a window onto their page, not moving it.

If you want the page at your own address, with your own title, favicon and link preview, the source has to leave Claude. Open the artifact’s code view, copy the HTML or JSX, and host it anywhere that serves static files. We walk through three ways to do that, with the tradeoffs, in how to deploy a Claude artifact as a real website.

The shortest of those is our own: paste the source into the Pasted source tab at InstaPods Import and click Deploy. You get a live URL with SSL in about a minute and can add a custom domain after. Plans start at $3/mo, and adding a card gives a one-time $10 credit, which covers about three months on that plan.

When Claude’s own publish is the right call

For most artifacts, Claude’s built-in publish is the right choice and you do not need a host. It costs nothing extra, takes three clicks, and the link works for anyone. It is the better option when:

Move it off claude.ai when it becomes something people depend on: a page for customers, a tool you want on your own domain, or anything where a dead link would cost you. If you are still deciding what an artifact can be in the first place, start with what are Claude artifacts.