Claude Artifact Won't Publish or Share? Causes and Fixes

You click Publish and nothing useful happens, or the button is not there at all. You share a link and the other person lands on a sign-in page. The share dialog says "This version can't be shared publicly". Artifacts changed a lot in 2026: newer artifacts use a Share menu with access levels, older chat artifacts keep their Publish button, and Claude Code publishes its own kind of artifact. Each kind follows its own rules, which is why the same click works for one person and fails for the next. This guide sorts the causes by symptom, gives Anthropic's own steps to unpublish, and ends with the fix that works in every case: putting the same HTML on a web address you control.

First: which kind of artifact do you have?

Anthropic's help pages now describe three kinds, and the fixes differ:

• Newer artifacts. Everything you create in Claude today. They start private to you, and a Share button sets who has access. On Pro and Max the choices are Only you and Anyone with the link, and you can add specific people by email. On Team and Enterprise they are Only people invited, Anyone at your organization and Anyone with the link, and artifacts stay inside the organization by default. Claude Design designs are artifacts of this kind.
• Legacy artifacts. Artifacts from chats made under the old system. They keep working and can still be shared, but you cannot make new ones. They show Publish on Free, Pro and Max, and Share & copy link on Team and Enterprise. Publishing gives the page a public claude.ai link (third-party guides show the form claude.ai/public/artifacts/ followed by an ID) and adds it to Artifacts in your sidebar.
• Claude Code artifacts. Pages Claude Code publishes from a session to a private URL on claude.ai (claude.ai/code/artifact/ followed by an ID), shared from the Share control in the page header.

Causes and fixes, by symptom

The person you sent the link to gets a sign-in page

Anthropic's help center sets one rule for shared artifacts: everyone needs a Claude account. People without one cannot open a shared artifact, even with the link, and Anyone with the link means anyone signed in to Claude who has the link. The only exception it names is a legacy artifact published from a chat, which anyone can view and use without an account.

Claude Code artifacts have their own documentation. A public Claude Code link opens for anyone without signing in, but on Team and Enterprise plans public sharing is off until an Owner turns it on, and a page shared within the organization requires viewers to sign in as members.

Fix: Anthropic lists no exception for newer artifacts, so a page meant for clients, customers or anyone outside Claude belongs on a normal web host. The fix section below shows how in a few minutes.

Anyone with the link is missing or unavailable

• Team and Enterprise: Anyone with the link is available only when an Owner has turned on External sharing under Organization settings > Artifacts, or has allowed that one artifact individually. For Claude Code artifacts, Anthropic states that public sharing is off by default on Team and Enterprise.
• Artifacts with apps or Claude inside: artifacts that connect to your apps or use Claude cannot use Anyone with the link, whatever your plan.

Fix: ask an Owner to allow external sharing for that artifact, or host the HTML yourself.

There is no Publish button

That is expected, not a fault. Only legacy artifacts on Free, Pro and Max show Publish. Team and Enterprise legacy artifacts show Share & copy link, and every newer artifact uses Share with an access setting. Look for Share in the upper right corner of the artifact.

"This version can't be shared publicly", or the artifact is too large

For Claude Code artifacts, Anthropic documents a hard limit: the rendered page must be 16 MiB or smaller, and large embedded images are the usual cause when a publish fails for size. For artifacts made in a claude.ai chat, Anthropic's help center documents no size limit. Stacktree, an HTML hosting service, cites third-party reports that public sharing fails above a rendered size of about 16 MiB and quotes the error "This version can't be shared publicly. Publish a new version or change the shared version, then try again." The same message also shows up in a GitHub issue about a 25 KB Claude Code artifact on a Max plan, so the error does not always mean the page is too big.

Fix: if size is the cause, make the page lighter. Embedded images are part of the page itself, so compress them or ask Claude to draw diagrams in SVG or CSS instead of pictures, then publish a new version. If the message stays on a small page, check the sharing settings above or contact Anthropic support. On VibeDeploy a single file can be up to 100 MB, so a heavy page uploads fine, although your visitors on phones will still thank you for shrinking it.

You unpublished it and cannot publish it again

That is how unpublishing works. Anthropic says you cannot publish an artifact again after you unpublish it, and unpublishing also permanently deletes any personal and shared storage data the artifact used. The old link no longer gives access.

Fix: create a new artifact from the same content and publish that, or put the HTML on your own host, where a page you took down can simply be deployed again.

Claude Code says it cannot publish, or writes a local HTML file

Claude Code publishes artifacts only when every condition holds: a Pro, Max, Team or Enterprise plan; a session signed in to claude.ai (sessions on an API key, a gateway token or cloud-provider credentials cannot publish); Anthropic's API rather than Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry; an organization without customer-managed encryption keys, HIPAA or zero data retention; and a recent Claude Code CLI or desktop app. When one is missing, Claude writes a local HTML file without a link or says it cannot publish. If the terminal shows "Artifacts need a claude.ai login", sign in with /login. On Team and Enterprise, an Owner can also turn artifacts off for the whole organization.

Fix: sign in with /login, or keep the local file and deploy it yourself. With VibeDeploy added to Claude Code, "deploy this file to VibeDeploy" does it from the same terminal.

The shared page looks broken

Claude Code serves artifacts under a strict Content Security Policy. A page can load typefaces from Google Fonts and scripts from five public CDNs, but external images and all other external scripts, stylesheets and fonts are blocked. Relative links do not resolve, and an artifact is one self-contained page with no backend. A page that depends on any of that will not work as an artifact, however good it looks on your own machine.

Fix: host it as a real site, where several pages and external images just work. A server or a database can run next to it too, as the fix section below explains.

A link that used to work stopped working

Three documented reasons. A Team or Enterprise Owner turned off External sharing, which stops existing public links, except for artifacts the Owner allowed individually, until it is turned back on. An Owner set a retention policy for artifacts, which Claude Code's documentation describes as automatic deletion after a set period. Or it was a public link to a project in the standalone Claude Design site, which closes on 14 December 2026; Anthropic says those links no longer work after it closes.

How to unpublish or stop sharing, per Anthropic

These are the steps Anthropic documents, by kind of artifact:

• Legacy artifact published from a chat (Free, Pro and Max): click Unpublish. That revokes access, permanently deletes the stored data the artifact used, and you cannot publish that artifact again.
• Legacy chat artifact on Team or Enterprise: in the Artifact shared dialog, click Unshare.
• Newer artifact: open it, click Share, and under Who has access choose Only you (Pro and Max) or Only people invited (Team and Enterprise). To remove one person, open their access level and select Remove.
• Claude Code artifact: use the Share control in the artifact's page header. Claude Code's documentation describes sharing there, including which version viewers see, and gives no separate unpublish steps.
• As a Team or Enterprise Owner: turning off External sharing blocks existing public links at once, except for artifacts an Owner allowed individually. To remove outside access to one artifact, go to Organization settings > Artifacts, find it under Published artifacts, open its menu, select Manage outside access and remove the person.

What a published artifact link can and cannot do

It can:

• Open without an account, in two cases. A published legacy chat artifact opens for anyone with the link and can be embedded on websites you list under Allowed domains, through Get embed code; a Claude Code artifact shared with a public link opens without signing in.
• Stay current. A Claude Code artifact updates in place when Claude republishes it, and you choose which version viewers see. On a public link, a viewer who is not signed in, or who is outside your organization, sees the label "Content is user-generated and unverified." instead of your name.

It cannot:

• Answer on your own domain. Anthropic's help pages describe no custom domain for artifacts.
• Be a full website. Claude Code's documentation calls an artifact one self-contained page with no backend that cannot serve multiple routes, and says that for a hosted internal tool with a backend you should deploy it on your own infrastructure instead.
• Come back after an unpublish. An unpublished artifact cannot be published again.

The fix that works every time: publish the HTML on your own address

An artifact is HTML, and HTML runs on any web host. Moving it takes a few minutes, in one of three ways.

From a Claude chat, with the connector. Add VibeDeploy as a custom connector: Customize > Connectors > Add custom connector, URL https://mcp.vibedeploy.be/mcp. The full connector setup has every step, including the OAuth option to pick. Then, in the chat with the artifact, say "Publish this artifact as my-page". Claude sends the HTML to VibeDeploy and replies with a link like https://my-page.vibedeploy.be that anyone can open, with no Claude account involved. Claude's help center says the Free plan includes one custom connector.

By upload. Legacy artifacts have controls at the top of the panel to view, copy or download the code; newer template artifacts export through Export. Save the HTML as index.html and upload it in the dashboard. If Claude said it saved your page to /home/workdir/artifacts/index.html, that path is in Claude's sandbox, not on your computer, and the linked guide shows how to get the file out.

From Claude Code. Unless you name a location, Claude Code writes an artifact's page to a temporary directory outside your project. Ask it to save the page into your project folder, add VibeDeploy once with claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp, sign in with /mcp, and say "deploy this page to VibeDeploy".

Want your own domain? Say "Connect www.example.com to my-page", or add the domain in the dashboard; SSL is issued automatically. The custom domain guide for Claude artifacts walks through the DNS side.

Once the page lives on a normal host, the artifact rules above stop applying. There is no account wall and no 16 MiB rendered limit, pages can link to each other, external images load, and if the page later needs a server or a database, your AI can run a container next to it with deploy_app (container data is not yet included in snapshots). Every deploy of the site's files is kept as a version, and an earlier one is one click away in the dashboard within your plan's restore window. VibeDeploy runs on its own cluster in Belgium.

Keep it private: a password instead of a Claude account

Sometimes the point of an artifact link was privacy: a client preview, a draft, an internal page. On VibeDeploy, Maker and up include private and password-protected sites. In the site's visibility settings, choose With a password and set one, and visitors get a password prompt before any page is sent; the check runs on the server, not in a script inside the page. Only me keeps a draft visible to you alone while you are logged in, and invite-only gives access to specific email addresses. Maker costs EUR 15 a month for three sites, and prices include VAT where it applies. More on private sites and the pricing page; the 14-day trial needs no card.

Sources

• Anthropic Help Center, Share artifacts: sharing options per plan, who can open a shared artifact, Publish and Share & copy link on legacy artifacts, Unpublish, Unshare, stopping sharing, embedding with Allowed domains. Checked 13 October 2026.
• Anthropic Help Center, What are artifacts and how do I use them?: legacy and newer artifacts, downloading and exporting. Checked 13 October 2026.
• Anthropic Help Center, Artifacts admin guide for Team and Enterprise plans: External sharing and its exception for artifacts allowed individually, allowing a single artifact, removing outside access, artifacts with apps or Claude inside. Checked 13 October 2026.
• Claude Code Docs, Share session output as artifacts: private URLs, sharing and public links, the 16 MiB rendered-size limit, page constraints, availability requirements, public sharing and retention on Team and Enterprise. Checked 13 October 2026.
• Anthropic Help Center, Migrate from standalone Claude Design to Claude: public links after the standalone site closes. Checked 13 October 2026.
• Stacktree, Claude artifact too large to share (13 September 2026): the 16 MiB threshold it cites from third-party reports, and the error text. Not confirmed by Anthropic. Checked 13 October 2026.
• GitHub, anthropics/claude-code issue 85550: the same error on a 25 KB artifact, closed on 15 August 2026. Checked 13 October 2026.
• InstaPods, What are Claude artifacts?: the claude.ai/public/artifacts link format. A third-party guide. Checked 13 October 2026.