Claude Artifacts
How to share Claude artifacts without a login
The short answer
Can someone open a Claude artifact without an account?
Mostly no, as of October 2026. Anthropic’s sharing article says: “Everyone needs a Claude account. People without one can’t open a shared artifact, even with the link. The only exception is a legacy artifact published from a chat.” A legacy artifact is one made in a chat before September 16, 2026, and Publish makes it public to anyone with the URL. That public part is a problem of its own for a confidential proposal.
[ answer ]
A Claude share needs a Claude account, and the one exception is a public page. The fix is to publish the artifact’s HTML as a link-gated, noindex link: no account for your viewer, and on Solo and Team, a password on top.
Native Claude sharing and its limits
A Claude account to open it
As of October 2026, “Everyone needs a Claude account.” Your client signs in to Claude, or can’t open the artifact at all, even with the link.
Publish is legacy only
The one no-account route is Publish on a legacy artifact (made in a chat before September 16, 2026, on Free, Pro or Max). New artifacts don’t get it.
Not your brand
A Claude share lives on Claude, not your domain: no logo, no premium impression for your client.
A published link is public
A published legacy artifact opens for anyone with the URL, and they can pass it on. That’s the part most people miss.
A risk most people miss
A “shareable link” can be a public link
A client-ready link should be the opposite of public. It should be link-gated (only people with the URL get in), password-gated when it’s sensitive, and noindex so it never surfaces in search.
See how Pagelive keeps it private →Illustrative demonstration of default behaviour. No real customer data.
Client-ready links with Pagelive
No login for viewers
Your client clicks the link and the page opens in any browser: no Claude account, no app, no sign-up.
Your branding
On Solo, a clean link on your own domain without the Pagelive badge: your logo, your name. It looks like your studio sent it.
Password + noindex
Every page is noindex by default on an isolated content plane. On Solo and Team, lock it with a PBKDF2-hashed password.
Tracked opens
Every page shows a view count. Solo and Team show when the client opened it, how long they read, and from where.
Public vs password-protected sharing
Public link (no gate)
A landing page, a marketing demo, a portfolio piece: content you want anyone to find and Google to index.
Password-protected link
A client proposal, pricing, a pitch deck, an investor update: anything confidential that should open only for the people you sent it to, and never on Google.
With Pagelive every page is noindex by default, so search engines are told not to list even a link with no gate, and on Solo and Team a password adds the gate when it matters.
How Pagelive keeps it private →Branded delivery
Custom domains and a white-label impression
Know when a client opens it
Sharing FAQ
For a Pagelive link, no. It opens in any browser: your client never needs Claude, an app, or any login. If you add a password (Solo and Team), they just enter that one password. For an artifact shared through Claude, as of October 2026 they do, unless it is a published legacy artifact.
No, pages are noindex by default. Pagelive sends the robots meta tag and X-Robots-Tag header that tell search engines not to list the page, so a client-facing artifact stays out of search results unless you explicitly opt it into indexing.
Yes. You can unpublish the page at any time so the link stops serving, or, on Solo and Team, add (or change) a password to re-gate it. Because every page lives on the isolated content plane, a single flip at the edge takes it down.
More guides: Claude artifacts: what they are, how to share and publish them · how to publish an artifact · are Claude artifacts public?. Sharing with clients every week? See one page per client.