Claude artifact not working for others? 9 causes and fixes
If a Claude artifact works for you but not for the person you sent it to, the cause is almost always access, not the page: it's still private, it's shared only inside your organization, the viewer needs a Claude account, or an Owner has External sharing turned off. Less often, the page loads but its live sections are empty because they depend on the viewer's own connectors. Here's how to tell which one it is.
Quick diagnosis
Open the link in a private browser window, signed out. What you see there is what an outside viewer sees. Then match the symptom:
| Symptom for the viewer | Likely cause | Fix |
|---|---|---|
| Asked to sign in, or access denied | The artifact is still private, or shared only with your organization | Open Share and change the audience |
| Asked to sign in on a link you thought was public | Artifacts from the Share dialog need a Claude account to open | Ask them to sign in, or publish the HTML somewhere that needs no account |
| Outside colleagues can't open a Team or Enterprise link | External sharing is off for the organization | An Owner turns it on in Organization settings → Artifacts |
| A link that used to work stopped | It was unpublished or unshared, External sharing was turned off, or a retention policy deleted it | Check Share; ask an Owner about the settings |
| The page loads but sections are empty or show an error | Those sections call connected apps through the viewer's own account | Viewer connects the app, or you publish a static snapshot |
| The viewer sees an older version | The share is pinned to a specific version | Switch Share to the latest version |
| Charts or fonts are broken on a corporate network | A firewall blocks the artifact domain or its CDNs | IT allowlists *.claudeusercontent.com and the CDNs |
1. It's still private
Every new artifact is visible only to its author. Copying the URL from your browser doesn't share it: the viewer has to be in the audience you choose under Share.
2. It's shared only inside your organization
On Team and Enterprise, sharing is limited to the organization by default. Viewers must sign in to claude.ai as members of your organization, and if a chat artifact came from a project, they also need access to that project. A client or a partner outside the org can't open it.
3. The viewer needs a Claude account
Anthropic's Help Center is explicit: people without a Claude account can't open or interact with an artifact shared from the Share dialog, even if they have the link, and even with External sharing on. The exception is a chat artifact published with the Publish button, which anyone can view without signing up. The Claude Code docs, on the other hand, describe Claude Code public links that open without signing in, so behavior depends on the artifact type. Test in a private window before you send.
4. External sharing is off
On Team and Enterprise plans, public sharing is off until an Owner turns on External sharing in Organization settings → Artifacts. If an Owner turns it off later, existing public links stop working until it's turned back on, without changing each artifact's audience. Even with it on, the Help Center says external sharing doesn't cover artifacts that use connected apps or ask Claude questions.
5. It was unpublished, unshared or deleted
Unpublishing a chat artifact revokes access immediately, and you can't publish that same artifact again: you'll need a new one. Owners can also set a retention period after which artifacts are deleted automatically, with separate periods for private and shared artifacts.
6. Live sections depend on the viewer
An artifact that pulls data from connectors runs each call through the viewer's own account. If they haven't connected that app, declined the permission prompt, or opened a public link without signing in, those sections stay empty or show an error. Ask Claude to add a fallback message to each live section, or share a static version with the data baked in.
7. The share is pinned to an old version
When you share, you can pin a specific version or always share the latest. If you pinned version 2 and kept iterating, the viewer still sees version 2.
8. A network filter blocks it
Claude loads each artifact from a sandboxed *.claudeusercontent.com origin and lets pages load libraries only from a few CDNs (cdnjs, jsDelivr, unpkg, and the Tailwind and jQuery CDNs). A corporate proxy that blocks those hosts breaks the parts of the page that depend on them.
9. You tried to change sharing from your phone
Sharing settings can't be changed in the iOS or Android apps. If you thought you made it public from your phone, check again from claude.ai or Claude Desktop.
When the reader is outside your organization
If the person is a client, a prospect or an investor, most of these causes come from the same place: Claude's sharing is designed for people who have, or can get, access to your Claude organization. When that isn't the case, publish the artifact's HTML to Outbox. Your recipient opens a normal web link with no account, you can add a passphrase and an expiry, and you get an email when they open it.
- Ask Claude to save the artifact's HTML to a file in your project (Claude Code otherwise writes it to a temporary folder).
- Publish it with the Outbox MCP server, the skill, the CLI or one API call.
- Create a share link for each person and send it.
Comparisons
Frequently asked questions
Why does my Claude artifact link say I need to sign in?
Either the artifact isn't shared with an audience that includes the viewer, or it was shared from the Share dialog, which the Help Center says requires a Claude account to open.
Why can't people outside my company open my Team artifact?
On Team and Enterprise, sharing stays inside the organization unless an Owner turns on External sharing in Organization settings → Artifacts.
I unpublished my artifact by mistake. Can I republish it?
Not the same artifact: the Help Center says an unpublished artifact can't be published again. Create a new artifact from the same content and publish that one.
How can I share an artifact with someone who has no Claude account?
Publish a chat artifact with Publish, if your plan offers it, or publish the HTML to Outbox and send a share link: recipients never need an account.
Related guides
Sources
Updated 2026-10-11.