Share Claude artifacts on your own private URL.

How to share Claude artifacts privately

The short version: don't rely on Claude's Publish button if the link needs to stay private. 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.

Why move artifacts off Claude.ai

Claude's built-in publish flow is brilliant for casual sharing inside the Claude ecosystem. But the moment one of these is true, you outgrow it:

• The viewer doesn't (and won't) have a Claude account.
• You want the URL on yourco.com, not claude.ai.
• You need a real expiry, short or long, not the default behaviour.
• You want to lock the artifact behind a password or company email gate.
• Your agent iterates on the artifact and you need the URL to stay stable.
• The artifact contains internal data and "viewable by anyone with the link plus a Claude account" doesn't feel like enough.

The 30-second workflow

1. Open the artifact in Claude. Click the menu → "Copy HTML" (or have Claude Code write it to disk).
2. Paste into the Stacktree dashboard, or curl -F file=@artifact.html https://api.stacktr.ee/sites. With Claude Code: publish_html({ file: "artifact.html" }).
3. Stacktree returns stacktr.ee/p/<token>. Send it.
4. Optional: set a password, an email-domain gate, or an expiry.

The bigger upgrade: replace-in-place

Claude's built-in artifact viewer shows whatever's in the current Claude conversation. Stacktree URLs are independent: they point to the content the agent last published. The implication: when Claude (or Claude Code) revises the artifact, it can call update_site with the same slug, and the URL you sent yesterday now shows today's version. Same bookmark, new content. No "see V3" follow-up.

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. Claude's Publish feature creates a public claude.ai link with no password, and Anthropic's own help docs note that published artifacts may be indexed by search engines. Anthropic says it blocks crawlers and serves no sitemap for shared content, but pages have still surfaced in Google when share links were posted publicly. 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 you password-protect a Claude artifact?

Not with Claude's built-in Publish, which offers no password and no access list. 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.

Can Claude artifacts expire?

Published artifact links never expire on Claude.ai and can't be set to. You can unpublish a version manually, but you cannot republish that same artifact afterward, and you cannot put a timer on it. A Stacktree link supports a real expiry from minutes to years, and delete_site burns the URL immediately when you are done.

How to make a shared Claude artifact private again

On Claude.ai you make a shared artifact private by reopening the conversation and choosing Unpublish, or by deleting the chat, which unpublishes every artifact it produced. Note that once unpublished, that exact artifact version cannot be published again. If you publish through Stacktree instead, you keep direct control: call delete_site(slug) to revoke the link now, or set an expiry up front so it goes private on its own.