Share Claude artifacts on your own private URL.

How to share Claude artifacts privately

The short version: if the viewer does not use Claude, Claude's own sharing leaves you a public link with no lock. Export the artifact's HTML, publish it to a private-by-default host, and send the unguessable link. With Stacktree that is one step in the dashboard, one curl, or one publish_html call from Claude Code. The viewer opens it with no Claude account and no Stacktree account, and you can layer a password, an email-domain gate, or an expiry on top.

What each way of sharing a Claude artifact does

Claude changed how artifacts are shared in September 2026. As of October, these are the options, per Anthropic's help center and the Claude Code docs:

So the question to ask is who the viewer is. If they have Claude, Claude's own sharing works. If they are a client without it, the built-in choice is a public link with no lock. The permission prompt Claude Code shows the first time is covered in what "new artifacts stay private until you share them" means. The same rules for ChatGPT, Gemini and Copilot are side by side on who can open what your AI made.

Questions people search mid-publish

Three questions that tend to get googled while Claude's own publish dialog is still open, answered plainly.

Why is Claude telling me to upload a file to claude.ai?

Because you asked it to publish or share the artifact. The dialog wording, publishing "uploads the file below from this task to claude.ai", is a permission step: the page Claude built exists only inside your task, and uploading the HTML to claude.ai is how it becomes a link. Nothing is uploaded until you approve, and the new page stays visible only to you until you share it; on Pro and Max, sharing means a public link anyone can open, or an email invite to someone with a Claude account. If that file should not sit on a public link, publish it to Stacktree instead: Claude uploads the same HTML to a private, unguessable URL, with a passcode on top if you want one.

The private route is one connector away: on claude.ai, open Settings → Connectors → Add custom connector and paste https://api.stacktr.ee/mcp. From then on, "publish this to Stacktree" in any chat returns a private link. In Claude Code, npx stacktree-install wires up the same publish_html tool.

Are Claude artifacts public?

Not until you share them. A new artifact is visible only to you. What sharing does next depends on where you share it: a Claude Code public link opens for anyone, with no sign-in; on claude.ai, "Anyone with the link" and email invites both ask the viewer to sign in to Claude. Older chat artifacts that were published are public to anyone with the link. None of these carry a password or an expiry. If the page needs to stay restricted after it is shared, publish the same HTML through Stacktree, where the link is unguessable by default and can require a passcode or a verified company email address before it renders.

The distinction that matters is public-by-link versus gated. A claude.ai link is not listed anywhere, but it is a bearer credential with no lock: whoever holds it gets in, and it can be forwarded without you knowing. A gate turns "hopefully only the client has this" into "only the client can open this".

Is there a list of public Claude artifacts?

No. Published Claude artifacts are not collected in any public directory, and there is no browsable index at claude.ai/public/artifacts; the artifacts space on claude.ai shows your own work, not everyone's published pages. A published artifact is unlisted, reachable only by its exact URL. Unlisted is not the same as private, though: the link can be reshared freely, which is the gap Stacktree closes with passcodes and email-domain gates on top of an unguessable URL.

Why move artifacts off Claude.ai

Claude's built-in sharing is good at two jobs: a page for people who already use Claude, and a public link anyone can open. The gaps are everything in between, and Anthropic's own docs are candid about them. You outgrow it the moment one of these is true:

• The viewer is a client without Claude, and the page must not be public. The only no-account option is a public link with no lock.
• You want a password or a company email gate in front of it.
• You want the URL on yourco.com, not claude.ai.
• You need it to expire after the engagement, or burn after one view.
• You might want to take it down and put it back later: unpublishing on claude.ai is permanent, and the same artifact can never be published again.
• You are on a Team or Enterprise plan where an Owner has not turned on external sharing, so the artifact cannot leave the organization.
• You want to know whether the client opened it, and how closely they read it.

The 30-second workflow

1. Once: on claude.ai, open Settings → Connectors → Add custom connector and paste https://api.stacktr.ee/mcp.
2. In the chat with the artifact, ask Claude to publish it to Stacktree. Claude uploads the HTML itself with publish_html.
3. Claude replies with stacktr.ee/p/<token>. Send it.
4. Optional: set a password, an email-domain gate, or an expiry.

No connector? Click the artifact menu → "Copy HTML" and paste into the Stacktree dashboard, or curl -F file=@artifact.html https://api.stacktr.ee/sites. In Claude Code, run npx stacktree-install once and publish_html({ file: "artifact.html" }) works there too.

Can I put a Claude artifact on my own domain?

No, not through Claude: published artifacts live on claude.ai, and the only domain control in Anthropic's help doc is an allowlist of sites permitted to embed the artifact. If the page is a deliverable, the domain is part of the deliverable, and claude.ai/artifacts/... says "generated in a chat" where report.yourco.com says "this is our work." Stacktree serves the same HTML on a custom domain: add a CNAME and a TXT verification record, SSL is provisioned automatically, and the domain can be re-pointed at any of your sites as projects change. Solo includes one domain, Studio ten. Revisions still land in place: the agent calls update_site and the URL you sent keeps showing the latest version, which is also true of Claude's published links; the domain and the gates are what the claude.ai link cannot carry.

What about sensitive artifacts?

Agent-generated HTML often embeds real data: API responses, customer rows, prompt context. Stacktree treats this as the default case, not an edge case:

• Unguessable URL. The token is the credential. No directory listing, no search indexing, no robots crawl.
• Optional shared password. A second factor on top of the unguessable URL.
• Email-domain gate. Magic-link verification against @yourco.com (or any domain).
• End-to-end encryption. AES-GCM in the browser; the key lives in the URL fragment; Stacktree only sees ciphertext.
• CSP defaults. Sensible Content-Security-Policy so a careless <script src> can't exfiltrate session data.

Do published Claude artifacts get indexed by Google?

They can be. Claude's Publish creates a public claude.ai link with no password, and any public URL can end up in a search index once it is posted or linked somewhere crawlable. Anthropic's help doc offers no visibility setting beyond unpublishing, and unpublishing is a one-way door. A Stacktree link is the opposite: the token is unguessable, there is no directory or listing, and the host serves the headers needed to keep crawlers out, so a private artifact stays out of the index.

Can I password protect a Claude artifact?

Not in Claude. The Share menu offers a Claude sign-in or a public link, and no password. Publishing through Stacktree instead lets you toggle a shared password per link, or require viewers to verify a @yourco.com email via magic link before the artifact renders. Either gate sits on top of the already-unguessable URL, and the viewer still needs no Claude or Stacktree account.

Do Claude artifacts expire?

No. A shared artifact link has no expiry setting; it keeps working until you change who it is shared with. Email invitations lapse after 30 days only if nobody accepts them. Older published chat artifacts stay up until you unpublish them, and that is permanent: per Anthropic's help center you cannot publish that same artifact again, and any storage data it used is deleted. A Stacktree link supports a real expiry from minutes to years, burn-after-read for one-time viewing, and delete_site to revoke the URL the moment you are done, with nothing stopping you from publishing again later.

How to make a shared Claude artifact private again

For a newer artifact, open the Share menu and narrow the audience back to just you. For an older published chat artifact, unpublishing is the only way, and it is final: the same artifact cannot be published again afterwards. If you publish through Stacktree instead, you keep direct control in both directions: call delete_site(slug) to revoke the link now, republish whenever you like, or set an expiry up front so it goes private on its own.