Stacktree
By · Founder, Stacktree · Last updated
use case

Share Claude artifacts on your own private URL.

Claude's Publish button covers one case: a public link on claude.ai. Anthropic's own help doc defines the edges: no password, no expiry, no custom domain, unpublishing is permanent, and Team and Enterprise artifacts cannot be published publicly at all. Stacktree hosts the same HTML with all of those filled in.

Get started free

To share a Claude artifact privately, export its HTML and publish it to a private-by-default host such as Stacktree, which returns an unguessable link you can gate with a password or an email-domain check. Claude's own Publish button creates a public link only: per Anthropic's help center, anyone with the link can view it, there is no password or expiry option, and once you unpublish an artifact you cannot publish that same artifact again. A dedicated host adds the gates, the expiry, and your own domain.

Paste the artifact's HTML and get a private link. Nothing to install.

How do you share a Claude artifact privately?

Use Stacktree. Either copy the artifact HTML out of Claude and upload it via the dashboard, or have Claude Code call publish_html directly through the MCP server. Stacktree returns an unguessable URL on its own domain (or yours, on Pro), and the viewer doesn't need a Claude account, or a Stacktree account, to open it.

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

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. Pro includes five domains. 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.

Claude's built-in publishing vs. Stacktree

Criterion Claude built-in publish Stacktree
Works inside Claude app Yes, primary use case. Via MCP: one-click connector on claude.ai, or from Claude Code.
Public link, no viewer account Yes, on Free, Pro, and Max. Optional; private is the default.
Stable URL across revisions Yes, published links update in place. Yes, update_site keeps the URL.
Private or gated link No. Public is the only mode. Private by default; password or email-domain gate on top.
Custom domain No, claude.ai only. Yes: CNAME plus TXT verify, auto SSL. Pro includes 5.
Expiry control No expiry option. Expiry scheduling and burn-after-read, free.
Take it down, put it back Unpublish is permanent; the same artifact can never be republished. Delete and republish freely.
Team / Enterprise external sharing Not available; org-only, org sign-in required. Any plan, no seats involved.
E2E encryption No. Yes, AES-GCM client-side, free.
FAQ

Frequent questions

Do Claude artifacts expire? +
No. Published claude.ai artifact links stay up until you unpublish them, and there is no expiry setting to change that. The only removal is manual unpublishing, which is permanent: Anthropic's help center states that once you unpublish an artifact, you cannot publish that same artifact again. Hosting the artifact's HTML on Stacktree gives you the timer explicitly: set an expiry, use burn-after-read for one-time viewing, or delete the link whenever you choose.
Can I password protect a Claude artifact? +
Not with Claude's built-in Publish, which has no password option; the published link is open to anyone who has it. Publish the artifact's HTML through Stacktree instead and you can toggle a shared password per link, or require viewers to verify a company email domain by magic link before the artifact loads. The gate sits on top of an already-unguessable URL.
Can I put a Claude artifact on my own domain? +
No. Published artifacts live on claude.ai, and the only domain setting in Anthropic's help center is which sites are allowed to embed the artifact. Publish the same HTML to Stacktree and you can serve it on a domain you own: add a CNAME and a TXT record, SSL is automatic, and the domain can be re-pointed at any of your sites. Pro includes five domains.
Can I publish a Claude artifact privately instead of publicly? +
Claude's Publish is public-or-nothing. Anthropic's help center describes it plainly: publishing "makes your artifact publicly available" and "anyone with the link can view and interact with it." There is no private mode, password, or access list. For a private version, take the artifact's HTML and publish it to Stacktree: unguessable URL by default, plus optional password or email-domain gates. Nothing is public unless you choose it.
What happens when I unpublish a Claude artifact? +
It is permanent. Per Anthropic: "Once you unpublish an artifact, you cannot publish that same artifact again," and unpublishing "also permanently deletes all associated storage data" if the artifact used persistent storage. You would need to create a new artifact to publish again. A Stacktree link is reversible in both directions: delete it now, republish later, or set an expiry so it retires itself.
How do I share a Claude artifact with a client without a login? +
Publish the artifact's HTML to Stacktree and send the link; the URL itself is the credential, so the client opens it with no account of any kind. If you need proof it stayed with the client, add an email-domain gate: the viewer confirms an @yourclient.com address via a one-time magic link, and still creates no account. Claude's public link also opens without a login, but it cannot be gated, expired, or kept off claude.ai's domain.
Why can't I publish my Claude artifact on a Team or Enterprise plan? +
Anthropic restricts it: artifacts created on Team or Enterprise accounts "can only be shared within your organization" and "cannot be published publicly," with viewers required to authenticate under the org account. So the plans most likely to produce client work are the ones that cannot hand a link outside the org. The workaround is the artifact's HTML: export it and publish it to a host like Stacktree, where the link opens for anyone you send it to, gated if you want it gated.
How do I share large HTML files from Claude? +
"How do I share large HTML files" is one of the most common questions in r/ClaudeAI, because the obvious routes fail: pasting into chat mangles the markup, and attaching the file makes recipients download-and-open it. Publish the file instead: drag it onto the Stacktree dashboard, POST it to the API, or let Claude publish it over MCP in one tool call. You get a live private link that renders in the browser like any other page.
How do I share a Claude artifact privately? +
Copy the artifact's HTML out of Claude (or have Claude Code write it directly to a file) and upload it to Stacktree. The dashboard, the API, or the MCP server all work. You get an unguessable URL that you can optionally lock by password or @company.com email domain. The viewer needs no Claude account and no Stacktree account to open it.
Do published Claude artifacts get indexed by Google? +
They can be. A published artifact is a public, password-less claude.ai page, and any public URL can end up indexed once it is posted or linked somewhere crawlable. Anthropic's help center offers no visibility control beyond unpublishing, which is permanent. A Stacktree link is unguessable, appears in no listing, and is served with crawler-blocking headers, so a private artifact stays out of the index.
Why not just use Claude's built-in publish button? +
For a public demo it is genuinely fine: one click, a stable link, and viewers need no account. You outgrow it the moment the page must not be public (client work, internal data), needs a password or expiry, should carry your domain rather than claude.ai, or was created on a Team or Enterprise plan, where public publishing is not available at all.
Can I keep the same URL when Claude revises the artifact? +
Yes. update_site replaces the content behind the same link, so a bookmark stays valid across every revision. Claude's published links also update in place, so this is parity, not a difference; the difference is what else the URL carries, such as the gate, the expiry, and your own domain.
What about images and inline assets? +
Inline (base64, data URIs) works out of the box. For sites with external assets, upload as a zip and Stacktree serves the bundle.
Does the viewer need a Stacktree account? +
No. The URL is the credential by default. If you add a password or email-domain gate, the viewer authenticates against that, and they never need a Stacktree account.
Are Claude artifacts safe to host publicly? +
Not by default. They often embed prompt context, API responses, or test data. Stacktree's private-by-default URL plus optional CSP defaults are designed for this risk surface.
Keep reading

Related guides

References

Sources and further reading

Get your Claude artifact off claude.ai.

Free first publish. No Claude account needed to view.

Sign up free →