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.

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 once you do, anyone who has the link can view it. 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?

Artifacts are private to your conversation until you publish them, and public afterwards. Anthropic's help center says publishing "makes your artifact publicly available" and "anyone with the link can view and interact with it"; there is no password, expiry, or private setting on a published link. 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 publish flow is genuinely good at its one job: a public link anyone can open, no account needed. The gaps are everything around that link, and Anthropic's own help doc is candid about them. You outgrow the Publish button the moment one of these is true:

• The page must not be public. Publish has one mode, and per Anthropic "anyone with the link can view and interact with it."
• 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 artifacts "cannot be published publicly" at all: they stay inside the org, behind org authentication.

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 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.

Do Claude artifacts expire?

No. Published artifact links stay up on claude.ai until you unpublish them, and there is no expiry setting to change that. The one removal mechanism is manual and permanent: per Anthropic's help doc, once you unpublish an artifact you cannot publish that same artifact again, and if the artifact used persistent storage, unpublishing deletes that data too. 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

On Claude.ai you make a shared artifact private by unpublishing it, and you should treat that as final: the same artifact cannot be published again afterwards. There is no way to pause a link and restore it. 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.