Limited-time offerPro & Max plans — 20% off

Save 20% on monthly and yearly billing.

View plans

Troubleshooting · Checked October 9, 2026

How to Share a Claude Artifact Without Requiring a Login

A new Claude Artifact Share link asks every viewer to sign in, including when you chose Anyone with the link. If the page is ordinary static HTML, export that file and send a browser preview that does not require a Claude account.

Why does my Claude Artifact link ask for a login?

Anthropic's sharing article says artifacts start private, and a shared artifact still requires a Claude account. People without an account cannot open it, even with the link. The only exception written there is a legacy artifact published from a chat.

That is why a client can see a sign-in page after you set access to Anyone with the link. The label describes who among Claude users may open it. It does not publish an anonymous web page. Team and Enterprise plans add another gate: an owner has to allow sharing outside the organization, and the outside person still needs Claude.

Do not describe every Claude Artifact as login-only. Legacy chat artifacts made before September 16, 2026 still use Publish on Free, Pro, and Max. Those published links can be viewed without an account. The viewer is asked to sign up only when the artifact uses Claude.

New Share vs legacy Publish: who can open each link?

The split is the artifact's age and plan, not the words on the share button. Checked against Claude's help center on October 9, 2026.

New Artifact Share

No

Anyone with the link still requires a Claude account. The viewer must be signed in.

Legacy chat Publish on Free, Pro, or Max

Yes

Only artifacts made in a chat before September 16, 2026. Features that use Claude can still ask for sign-up.

Team or Enterprise sharing

Usually no

External sharing depends on an owner setting. Anyone with the link still needs a Claude account.

Email invitation

No

The invited person needs a Claude account that uses the invited email address.

HTMLShare static preview URL

Yes

Only a standalone static HTML file or ZIP. The link is noindex, not a private access control.

Fastest fix: export a standalone HTML version

Use this path only when the artifact is already a page the browser can run by itself. HTMLShare hosts that file. It does not log into Claude or pull the artifact out of your chat.

01

Check which artifact you have

Claude Design has an Export menu. A legacy chat artifact has copy and download controls in the artifact panel. A new chat artifact may not offer the same file export. Do not assume every artifact has one Export button.

02

Export a file that runs alone

From Claude Design, choose standalone HTML or Download as .zip. From a legacy artifact, copy or download the source only when it is ordinary HTML, CSS, and JavaScript. A React snippet that depends on the Claude viewer is not a finished page.

03

Pack separate assets as a ZIP

Keep CSS, JavaScript, images, and fonts next to the HTML with relative paths. Put index.html at the ZIP root, or inside one enclosing folder. Do not upload a source tree that still needs a build step.

04

Upload and review it yourself

Open the preview on a desktop width and on a phone before you send it. Guest uploads stop at 1 MB for HTML and 3 MB for ZIP, and the link expires after one hour.

Claude Design is the documented export. Anthropic says designs export as a ZIP, PDF, PowerPoint, or standalone HTML. PDF and PowerPoint stay in a document tool. For the HTML or ZIP path, see Claude Design hosting.

When exporting won't reproduce the Artifact

A static preview copies the page, not Claude's runtime. Leave these artifacts on Claude's own access rules, or rebuild them as an app you can deploy.

AI-powered Artifacts

If the page calls Claude to answer, generate, or coach, that runtime stays on Anthropic's infrastructure. A static file cannot make those calls.

Connected apps

Artifacts that read Gmail, Slack, calendars, or other connectors use the viewer's own connections inside Claude. HTMLShare does not connect those apps.

Stored or shared state

Journals, trackers, and collaborative data live in Claude's artifact storage. A preview link will not keep that database.

Server-side or secret calls

Anything that needs an API key, a backend, or a private data source should stay in Claude or move to an application host. Do not paste secrets into a static file.

Share a client preview without asking for a Claude login

The handoff is Claude static HTML, then HTMLShare, then an HTTPS preview URL, then client review. The client opens the rendered page. They do not join your Claude workspace, and they do not see the chat.

Current HTMLShare limits: guest uploads are 1 MB for one HTML file and 3 MB for a ZIP. A guest preview expires after one hour. Signed-in projects accept one HTML file up to 5 MB and 20 MB for the whole project. Free links last 1 day, Pro links last 30 days, and Max links stay up. A noindex preview is not password protection. Do not upload secrets or client-confidential files.

Common problems

Client sees the Claude login page

The link is a new Share URL, or a Team/Enterprise link. Export static HTML and send the HTMLShare preview instead of the claude.ai link.

Anyone with the link still asks for sign-in

That setting means any signed-in Claude user with the link. It does not remove the account requirement on new artifacts.

Shared Artifact is not available outside the organization

On Team and Enterprise, an owner has to allow external sharing. Even then, the outside viewer needs a Claude account.

HTML export renders blank

The file may be a component, not a document, or it may point at CSS and images that were not uploaded. Open it locally before you publish.

React-only snippet is not standalone HTML

Claude's viewer can compile a React artifact for you. A copied component without that viewer will not render. Ask for one HTML document, or use a Claude Design export.

Uploaded ZIP is missing index.html

HTMLShare opens index.html at the ZIP root or inside one enclosing folder. Rename the homepage or flatten a nested export folder.

It works in Claude, but live data does not

Connectors, Claude model calls, and stored records are not part of the static file. Keep those artifacts on Claude's share flow.

Guest preview link expired

Guest previews last one hour. Sign in and claim the preview, or publish again from a signed-in project.

A missing Artifact tool in Claude Code, or a published URL that says Page not found, is a different failure. Start with Claude Code Artifact tool missing. A public share that fails because the file is huge belongs on Claude Artifact too large to share.

FAQ

Common questions

Can I share a Claude Artifact with someone who doesn't have Claude?

A new Share link cannot be opened without a Claude account, even when access is set to Anyone with the link. A legacy chat artifact made before September 16, 2026 and published on a Free, Pro, or Max plan can still be viewed without an account. For a new artifact, export standalone static HTML or a ZIP and send an HTMLShare preview URL instead.

Why does “Anyone with the link” still require sign-in?

Anthropic's current sharing article says everyone needs a Claude account to open a shared artifact. Anyone with the link means anyone who is signed in to Claude and has the link. It does not mean an anonymous browser visitor.

Can old Claude Artifacts still be published publicly?

Yes, if they are legacy artifacts made in a chat before September 16, 2026. Free, Pro, and Max plans still show Publish. Anyone with that published link can view it without a Claude account, and they are asked to sign up only for features that use Claude. You cannot create new legacy artifacts.

What changed on September 16, 2026?

Artifacts made in a chat before that date are legacy artifacts. They keep the older Publish or Share & copy link controls. Artifacts created after that date use the new Share flow, and viewers need a Claude account.

Can I export a Claude Artifact as HTML?

It depends on the artifact. Claude Design can export standalone HTML or a ZIP. A legacy artifact can be copied or downloaded from the artifact panel. A new chat artifact does not have one universal Export button, so confirm you actually have a file that runs on its own before you upload it.

How is Claude Design export different from a chat Artifact?

Claude Design is a template product with an Export menu that includes standalone HTML and ZIP. A chat Artifact is created beside a conversation. Design files are the most direct path to a portable page. A chat Artifact may only be viewable inside Claude until you can copy a standalone HTML file.

Will an AI-powered Artifact work on static hosting?

No. Static hosting cannot run Claude model calls, connected apps, Claude-hosted storage, or server-side features. Those parts should stay on Claude's own sharing flow, or be rebuilt as an application with its own backend.

Does HTMLShare require the viewer to sign in?

No. The recipient opens a normal browser URL. They do not need a Claude account or an HTMLShare account to view a preview you already published.

Are HTMLShare preview links private?

No. Preview links are noindex, which asks search engines not to list them. Noindex is not a password, login wall, or access control. Anyone who has the URL can open it. Do not upload confidential files.

How long does a guest preview link last?

A guest preview stays live for one hour. Sign in and claim it before it expires if you need it longer. Free signed-in links last 1 day, Pro links last 30 days, and Max links stay up.

Send the page, not a Claude login

Upload the standalone HTML or ZIP, check the render, and share the preview URL. The viewer does not need a Claude account.

  • Works for static HTML and ZIP projects only.
  • Guest preview expires after one hour.