# Claude artifact not working for others? 9 causes and fixes

> Your shared Claude artifact opens for you but not for them: org-only sharing, sign-in, External sharing off, unpublished, connectors. Causes and fixes, sourced.

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:

## 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.

## Comparisons

- [Outbox vs Claude Artifacts](https://out-box.dev/en/guides/vs/claude-artifacts)
- [Outbox vs Display.dev](https://out-box.dev/en/guides/vs/display-dev)

---

Updated 2026-10-11. HTML version: https://out-box.dev/en/guides/claude-artifact-not-working-for-others