TL;DR
Open the artifact, click Share, choose Anyone with the link, and send it. As of November 11, 2026, Claude's sharing page says most artifacts shared that way open with no Claude account. Claude Docs are the exception, and a client with only the link can't comment or edit. If they need to respond on the page, export the HTML and give it a collaboration link.
What changed (and why older advice says the opposite)
From September 16 to early November 2026, "Anyone with the link" meant anyone signed in to Claude. A client with no account hit a sign-in screen, and this post was written to get around it. By November 11, Claude's Share artifacts page said: "Most artifacts shared with 'Anyone with the link' open without a Claude account or sign-in." We found no release note for the change, so if a guide or an AI answer still tells you everyone needs an account, it's working from the old page. The full current rules are here.
Option 1: share it so anyone with the link can open it
This is now the fastest route for a client who only needs to look.
- Open the artifact in Claude and click Share.
- Under who has access, pick Anyone with the link. On Team or Enterprise, if it's grayed out, an Owner has to turn on External sharing (or allow this one artifact).
- Copy the link.
- Open it in a private browser window, where you're signed in to nothing. This is exactly what your client will see.
- If every part of the page loads and works, send the link.
Step 4 is the one people skip, and it matters more than it used to. Claude's page says link-only visitors can view the artifact but the parts that use Claude or your connected apps don't work for them, and people who aren't signed in can't see data the artifact stores. A self-contained page is fine. A page built on those features can open half empty.
Why it might still ask your client to sign in
If the private-window test hits a sign-in screen, it's one of these:
| What you see | Why | Fix |
|---|---|---|
| The Anyone with the link option is missing or gray | Team or Enterprise with External sharing off | Ask an Owner or Primary Owner |
| The link opens for you but not for them | You shared with invited people or your org, not the link | Change access to Anyone with the link |
| It's a Claude Doc | Docs open only for people signed in to Claude, view only | Option 2 |
| The option won't apply to this artifact | It connects to other websites, or holds an uploaded file still being checked | Option 2 |
| It opens but parts are blank | It uses Claude, connectors or stored data | Option 2, or rebuild those parts as static content |
Option 2: take the HTML out when they need to comment or edit
This works for any artifact, Docs included, and for output from ChatGPT or Gemini too, because an artifact is a web page underneath. It's also the only route here where someone with no Claude account can respond on the page: Claude's link-only visitors "can't see or add comments."
- In the Claude chat, ask for the whole thing as one self-contained HTML file: "Give me the complete artifact as a single HTML file with the CSS and JavaScript inline."
- Save it as a file ending in
.html. (Not sure what you're holding? Here's what that file is.) - Put it somewhere that serves web pages: a static host, or a collaboration tool if you want comments. The options are compared here.
- Open the link in a private window and click through the interactive parts before you send it.
The export is a prompt, not a button, so read the result. A page that fetched outside data or called Claude from inside won't behave the same once it's out of Claude.
Two older routes that still work
- Legacy artifacts (made in a chat before September 16, 2026) can still be Published on Free, Pro, Max and Ultra to a link anyone can use with no account. Unpublishing is permanent: you can't publish that artifact again.
- Claude Code artifacts have a public link that "anyone on the internet can open," per the Claude Code docs. On Team and Enterprise an Owner enables it first. Public-link visitors can't comment there either.
Which route to use
| Your client needs to... | Use | Client needs an account? |
|---|---|---|
| Look at a self-contained page | Option 1, Anyone with the link | No |
| Look at a Claude Doc | Option 2 | No |
| Comment on the page or tweak copy | Option 2 with a collaboration link | No |
| Comment inside Claude | An email invite with the Commenter role | Yes |
| See it on your own domain | Option 2 with a host that supports one | No |
How Coedit fits
For a client who only needs to look, Claude's own link is now enough, and we'd tell you to use it. Coedit is for when they need to answer. Paste the exported HTML in and you get one link where viewing and commenting need no account, comments pin to the element the client means, and people you allow can change copy and styling without code. Every human and agent change lands in one version history, and paid plans put the link on your own domain. Coedit never generates anything. Claude made the page; Coedit is where the person without a Claude account works on it with you.
FAQ
Q: Can someone without a Claude account open my Claude artifact? A: Usually, yes. Share it with "Anyone with the link" and, per Claude's sharing page as of November 11, 2026, most artifacts open with no account or sign-in. Claude Docs are the exception, and parts that use Claude or your connected apps won't work for them.
Q: Why does my Claude artifact still ask my client to sign in? A: Check four things: it's shared with invited people or your org instead of the link; it's a Claude Doc; your Team or Enterprise Owner hasn't turned on External sharing; or it uses Claude or stored data that only signed-in people can see.
Q: Can my client comment on a Claude artifact without an account? A: No. Link-only visitors can't see or add comments. Commenting needs an email invite with the Commenter role and a Claude account on that address. To collect comments from people with no account, export the HTML to a collaboration link.
Q: Will the exported page work exactly like it did in Claude? A: Usually for self-contained pages, but not always. Pages that call Claude from inside, or that load outside data, may behave differently. Test the link in a private window before you send it.
Q: Do I need to pay to share a Claude artifact with someone outside Claude? A: No. "Anyone with the link" is on every plan, free static hosts exist, and Coedit's free plan covers real client work. Custom domains are on paid plans.