A shared Claude artifact won't open

Why it happens

1. They don't have a Claude account (the most common cause)

Claude changed how artifacts are shared on 16 September 2026. Artifacts made in a chat before then are now called legacy artifacts; you can still publish them, but you can't make new ones. New artifacts use a Share button, and Anthropic's help centre is explicit: "Everyone needs a Claude account. People without one can't open a shared artifact, even with the link." Your viewer isn't doing anything wrong. The sign-in page is the expected result.

2. It's shared inside your organization only

On Team and Enterprise plans, artifacts stay inside your organization by default. The sharing menu offers "Only people invited", "Anyone at [your organization]" and "Anyone with the link", and the last one only appears once an Owner has turned on External sharing. A client outside your org who gets an org-only link can't open it, and even with "Anyone with the link" they still need a Claude account.

3. An admin turned External sharing off

Anthropic's admin guide says turning External sharing off stops existing public links from working until it's turned back on, except for artifacts allowed individually. If a link that used to work suddenly stopped for everyone outside your company, ask your Claude Owner whether the setting changed.

4. The artifact uses Claude or your connectors

Artifacts that connect to your apps or call Claude can't use "Anyone with the link" at all. For invited viewers, the parts that use Claude or connectors may show an error instead of your data.

5. It was unpublished, or the chat was deleted

Unpublishing a legacy artifact revokes the link for good: you can't publish the same artifact again, so the old link never comes back. Several guides also report that deleting the conversation removes the artifact's public version.

6. A sharing error inside Claude

Some people report errors such as "This version can't be shared publicly" when sharing from Claude Code, including on artifacts that should qualify. Those are reported on Anthropic's public issue tracker; if you hit one, report it there and use a workaround below in the meantime.

Fix it

• The viewer uses Claude anyway: ask them to sign in with the same email you invited, or share with "Anyone with the link" (they still need an account).
• Team or Enterprise: ask an Owner to turn on External sharing, then set the artifact to "Anyone with the link". Note that the setting applies across the org, and turning it off later breaks every public link at once.
• The viewer has no Claude account, or you need a link that lasts: host a copy of the page. In Claude, open the artifact and copy its code (or download it), then publish it on a static host. That gives you a normal web address that opens in any browser with no sign-in. Our guide to hosting a Claude artifact walks through it step by step, including how to turn a React artifact into one HTML file.

Check it worked

Open the link in a private (incognito) window where you aren't signed in to anything. That is exactly what someone without a Claude account sees. Check it on a phone too: Anthropic notes that sharing settings can't be changed in the Claude iOS or Android apps, so make changes from the web or the desktop app.

How Flatpage handles this

Flatpage isn't affiliated with Anthropic. It hosts the HTML you give it as an ordinary web page: anyone with the link can open it, no account needed, and nothing from your Claude chat or its attachments is published. The link belongs to you rather than to an organization's sharing setting, and when Claude gives you a better version you paste it into the same site, so the link stays the same. What doesn't move across is anything that calls Claude or your connectors while the page runs.