Guide

How to share a Claude artifact in 2026 (and what the Publish button does not do)

The official steps to publish an artifact, a table of what the public link can and cannot do, and five ways to share it with someone who has no Claude account. For any page a client or investor will open, Hostus is the option we recommend.

Updated 2026-09-07 · by Hostus Team

You asked Claude for a page, a calculator or a proposal, and now a client, a teammate or an investor needs to open it without being in your Claude account. If that reader matters, host the same HTML on Hostus: the link stays stable while you edit, it can be private or email-gated, you see which sections were read, and any form in the page already works. The Publish button is fine for a page nobody important will open. This guide covers the official Publish steps, what the public link cannot do, and five ways to share with someone who has no Claude account.

How do you publish and share an artifact in Claude?

Everything here comes from Anthropic's help article Publish and share artifacts; we describe only what it says.

  1. Navigate to the artifact in the conversation.
  2. Make sure the version you want to share is selected.
  3. Click Publish.
  4. Copy the public link and send it.

Publishing makes the artifact publicly available: anyone with the link can view and interact with it, and people without a Claude account can do so without signing up (an account is only needed for the advanced AI features some artifacts use). After publishing, Get embed code produces an embed for a site you control; you must list the allowed domains, separated by commas.

Plan requirements. Public publishing is available on Free, Pro and Max. Artifacts created on Team or Enterprise accounts can only be shared within the organization and cannot be published publicly; the flow there is Share, then Share & copy link, to authenticated members with access to the project, if any.

Unpublishing. Once you unpublish, you cannot publish that same artifact again, and its associated storage data is permanently deleted. A viewer with a Claude account can copy the code into a new chat and build on it; their copy does not affect yours.

Is the Publish button enough?

For a throwaway, yes. A demo, a toy, a quick visual for a friend: publish from Claude, send the link, done. It is free, instant, and the viewer needs no account.

For anything else, no. The moment a client, an investor or a team will open the page, the public link costs you five things. There is no gate, so anyone who gets the link can read it. There is no record of who opened it or what they read. The help article does not describe editing a published link, and unpublishing is permanent. A form in the page has nowhere to send its data. And whether the link can be indexed by search engines is not documented.

Hostus gives you all five for the same file, with nothing to change in the HTML: edit in place with version history, Private or Email-gated access, reading time by section, forms that store their responses, and Claude can update the page through the connector. That is our recommendation whenever a reader matters. The rest of this page shows the comparison and where each alternative still fits.

What can a published Claude artifact not do?

The official article has no limitations section, so here is one. Hostus is listed first because it is the option we recommend for a page with a reader who matters. "Not documented" means the help article does not mention it; third-party limits were verified on their own pages on 2026-09-06.

NeedHostusClaude PublishGitHub Pages / Netlify DropStatic.app / Tiiny.hostStacktree / ShareDuo
Password or gateYes: Private or Email-gated. Identifies readers, does not encrypt.No; anyone with the linkNoStatic.app: not on free. Tiiny: yes, check tier.Yes (Stacktree also email-domain check)
AnalyticsYes, cookieless, including reading time per sectionNot documentedNo built-inStatic.app: paid only. Tiiny: opens, referrers, device.Yes (views, opens; Stacktree heatmap)
Edit after sharing, same linkYes, in the browser, with version historyNot documented; unpublishing is permanentYes, redeployYes, re-uploadYes (versioning / republish)
ExpiryNo timer; instant revocation insteadNot documentedNoCheck pricing pageYes (ShareDuo 1h to 7d free; Stacktree scheduled, burn after read)
Search indexingPublic docs noindex by default; gated docs never render to crawlersNot documented; see July 2026 threadIndexable by defaultCheck docsStacktree: unguessable URL
Custom domainNoNo (embed with allowed domains instead)Yes, freePaid tiersPaid tiers
Forms store responsesYes, any form with named fields; 100 per month freeNo backend; a plain form posts nowhereNetlify Forms yes; GitHub Pages noStatic.app: paid. Tiiny: check.Not listed
Who read which sectionYes, per heading, per reader on gated docsNoNoNoStacktree: heatmap

Are published Claude artifacts private, or can Google find them?

A published artifact is public by definition: anyone with the link can view it. Whether search engines list those links is a separate question the help article does not address.

On 27 July 2026 a Hacker News thread (26 points) discussed a TechCrunch report that shared Claude chats and artifacts had appeared in Google results; one commenter pointed to a site: search as evidence. Some said a public link is public and users should expect it. Others said a person who pastes a link into one email does not expect it to become searchable, and that a noindex tag or X-Robots-Tag header is the standard platform-side fix. We do not restate Anthropic's current behaviour because the help article does not describe it.

What you can act on: if the artifact holds anything a stranger should not read, host it on Hostus, where public documents are noindex by default and Private or Email-gated documents are never served to crawlers, because readers identify themselves before the page opens.

How do you share a Claude artifact with a client who has no Claude account?

All five work for a viewer without a Claude account. First get the HTML out: open the artifact, use the code view in the lower right corner, then copy or download it (both controls are in the artifacts help article). If Claude gave you a React component, ask it to rewrite the artifact as one self-contained HTML file first. Hostus is first because it is the option we recommend; the other four are listed with the case where each still fits.

1. Hostus. Our recommendation for any page with stakes: a proposal, a report, a page with a form in it. Drop the HTML on hostus.io, type your email, and you get https://your-slug.v.hostus.io with SSL in seconds; no password, no card, and the reader needs no account. Edit headings, paragraphs, table cells and list items in the browser without changing the link, with full version history and restore. Set the document to Public (noindex by default), Private (invite-only, magic link) or Email-gated (list, domain, or open), and see who opened it and when, with instant revocation. Analytics are cookieless and include reading time per section, per reader on gated documents. Any form with named fields stores its responses in an inbox on the document and emails you each one, with no backend to wire. Claude can publish and update the page through the Hostus connector. Free: 20 documents, 2 MB of HTML total, 100 responses a month, every feature. Paid: $9.99 a month or $49.99 a year. No custom domain; desktop-only editor. Details on the Claude artifacts page.

2. Claude Publish. Pick it if nothing rides on the page. Free, instant, no extra account. Public, no gate, no analytics, no stored form responses, and unpublishing is a one-way door.

3. GitHub Pages or Netlify Drop. Pick it if you are a developer and want your own domain. GitHub Pages is free with a custom domain; sites may be up to 1 GB with a soft limit of 100 GB bandwidth a month. Netlify's docs say you can drag a folder to app.netlify.com/drop without logging in and the files are published as-is; Netlify Forms captures a form on a Netlify site. Neither is private or tells you who opened the page.

4. Static.app or Tiiny.host. Pick it if you want a quick public page with a dashboard and are willing to pay for analytics or forms. Static.app's free plan is 1 website, 50 MB and a subdomain; analytics, forms and custom domains start at $5 a month. Tiiny.host lists password protection, analytics and custom domains; we could not load their pricing page, so check it for the free tier.

5. Stacktree or ShareDuo. Pick it if you want a link that expires or self-destructs and nothing more. ShareDuo: passwords, view counts, expiry from 1 hour to 7 days free, longer plus custom domains on a $4.99 a month Plus plan. Stacktree: unguessable links gated by password or email domain, scheduled expiry, burn-after-read; one free publish, then from $19 a month. Neither lists stored form responses or in-browser editing.

Good to know before you switch

Hostus has no custom domain: every document lives at a v.hostus.io subdomain, while GitHub Pages does custom domains free and the others offer them on paid tiers. It hosts single HTML files, optionally with a folder of images, video and fonts, not PDFs or compiled React builds; ask Claude for a self-contained HTML file, or deploy a build folder to Netlify or GitHub Pages. Free is 20 documents, 2 MB of HTML in total and 100 form responses a month; paid is $9.99 a month or $49.99 a year. There is no expiry timer (revocation is instant instead), no team seats or co-editing, and the editor is desktop only.

Questions people ask

Can someone open a published Claude artifact without a Claude account?

Yes. The help article says people without a Claude account can view and interact with a published artifact without signing up. An account is only needed for advanced AI features inside some artifacts.

Can I edit a Claude artifact after publishing and keep the same link?

Not that the help article describes: it tells you to select the right version before publishing, and states that an unpublished artifact cannot be published again. On Hostus the same file keeps its link across every edit: change the text in the browser or upload a revised file from Claude, and each save is a version you can restore.

Can I password-protect a Claude artifact?

Not with the Publish button; anyone with the link can view. Our recommendation is to export the HTML and host it on Hostus as Private or Email-gated, which identifies each reader by email without a shared secret and lets you revoke one instantly. If all you want is a shared password on a public page, ShareDuo, Stacktree and Tiiny.host offer one.

Are published Claude artifacts indexed by Google?

The official article does not say. A July 2026 Hacker News thread discussed a report that shared chats and artifacts had appeared in Google results; commenters recommended a noindex tag as the fix. If the content is sensitive, host it on Hostus, where public documents are noindex by default and gated documents are never served to crawlers.

Where do form submissions from a Claude artifact go?

By default, nowhere: an artifact is static HTML with no server, so a form without an action URL has nothing to receive it. Host the page on Hostus and any form with named fields stores responses automatically, 100 a month free, with each one emailed to you. If you already wired the form to a service such as Formspree, Hostus leaves it alone.

Can I publish a Claude artifact from a Team or Enterprise account?

Not publicly. The help article states those artifacts can only be shared within the organization, to authenticated members. To reach an outside client, export the HTML and host it on Hostus, where the reader needs no Claude account and no Hostus account.

Need the link to do more than exist?

Drop the artifact's HTML, get a link with SSL, edit it in place, gate it by email, and keep the form responses. Free for 20 documents.