Share a Claude Design on a private URL, not a public artifact.

Claude Design (beta) shares two ways: keep the design inside your workspace, or publish it as a public artifact. The middle case, one client, no accounts, is not there yet. It is a one-minute workaround: the design is HTML, Claude exports it faithfully, and a private host adds the gate.

Get started free

To share a Claude Design with someone outside your workspace, export it as Project HTML (Share, Export, Project HTML, standalone or zip) and publish the file 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 Design's own share menu offers workspace access or "publish as artifact", which converts the design to a public artifact; there is no private external link, password, or expiry option in the beta.

no account · 24 h link

Paste or drop the exported Project HTML and get a private link. Nothing to install.

How do you share a Claude Design privately?

Export, then publish. In Claude Design choose Share, Export, Project HTML (standalone file or zip), then upload that file to Stacktree via the dashboard, one curl, or the publish_html MCP tool. You get an unguessable URL, optionally gated by password or email domain, and the viewer needs no Claude account and no Stacktree account to open it.

What Claude Design's share menu actually offers

Claude Design is Anthropic's design surface on claude.ai, in beta as of July 2026: describe a page, get a polished interactive design with wired-in tweaks, iterate in conversation. The share menu has two audience settings. Workspace access keeps the design where it started, visible to you and the workspace members you add. Publish as artifact converts the file to a public artifact, which means the claude.ai artifact model applies: anyone with the link can open it, and there is no password or expiry.

The export column is generous, and one entry matters more than the rest: Project HTML. A design is an HTML document under the hood, so the export is the design, not a flattened picture of it. PDF and PowerPoint flatten the interactivity; PNG captures one element; the HTML is the real thing.

Then there is the destinations list: send the design to Claude Code, or connect Canva, Miro, Google Slides, HubSpot, Netlify, Vercel, Replit, Lovable, Wix, and others. Notice what every destination has in common: it publishes or edits the design somewhere public or somewhere that needs its own account. The list has deploy targets and design tools, and no private, client-shaped link.

The gap: one client, zero accounts

The person a design most often needs to reach is not "the internet" and not "the workspace". It is one client, who has no Claude account, should not need one, and should not be handed a public URL that anyone who finds it can open. That is the exact gap Claude's artifacts had before it, and the same workaround closes it, because both are HTML in the end.

Export the Project HTML, publish it to Stacktree, and send the link. Private by default: the URL is unguessable and appears in no listing. If the work is sensitive, add the gate: a shared password, or a magic-link check that the viewer owns an email at the client's domain. Set an expiry so the preview retires itself, or burn-after-read for a one-time reveal. When the design changes, update the same site and the link you already sent keeps working.

Three ways to publish the export

The dashboard route: drag the standalone HTML (or the zip) onto stacktr.ee and copy the link. The terminal route: one curl -F file=@design.html to the API. The agent route: connect the Stacktree MCP server and let Claude publish it for you, useful when the design has already round-tripped into Claude Code and lives in the repo. All three return the same thing: a live, private URL with the gates you chose.

Claude Design's native sharing vs. a hosted private link

Criterion	Claude Design built-in	Stacktree
Keep it in the workspace	Yes, the default; add workspace members.	Not the job; the hosted copy is for people outside.
Public link	Yes, publish as artifact (public, no gate).	Optional public slug; private is the default.
Private link for one client	No mode between workspace and public.	Unguessable URL by default, no viewer account.
Password or email gate	No.	Shared password, or email-domain magic link.
Expiry / burn-after-read	No.	Both, free.
Your own domain	No, claude.ai only.	CNAME plus TXT verify, auto SSL. Pro includes 5.
Client feedback without accounts	Commenting lives with the workspace design.	On-page feedback toolbar, no viewer account, agent-readable over MCP.
Same URL as the design iterates	Within Claude, yes.	Yes, update the site in place.

FAQ

Frequent questions

Can you share a Claude Design with someone outside your workspace? +

Not directly while it stays a design. The share menu offers workspace access ("only you can see this design" until you widen it) and Publish as artifact, which converts the file to a public artifact anyone with the link can open. There is nothing between those two: no password, no viewer email gate, no expiry. The out-of-band route is the Project HTML export: download the design as HTML, publish it to a private host such as Stacktree, and send that link instead.

How do you export a Claude Design as HTML? +

Share, then Export, then Project HTML. Claude Design offers it as a .zip or a standalone file. This is a faithful export rather than a conversion: a design is an HTML file under the hood (the project file is literally a .dc.html document), so what you download is the design as it renders, interactivity included.

Can you password-protect a Claude Design? +

Not natively. Workspace access is account-gated to your workspace, and a published artifact is public with no password option. To put a password on a design, export the Project HTML and publish it through Stacktree: toggle a shared password per link, or require viewers to verify an email at your client's domain via magic link. The viewer passes the gate in the browser and needs no Claude or Stacktree account.

Is publishing a Claude Design as an artifact public? +

Yes. The share menu is explicit: it converts the file to a public artifact, which follows the claude.ai artifact model, anyone with the link can view it, with no password and no expiry. Fine for a portfolio piece or a public demo; the wrong mode for client work in progress.

What export formats does Claude Design support? +

As of the July 2026 beta: PDF (instant, or re-formatted by Claude), Project HTML as zip or standalone, PowerPoint with editable text and shapes, PNG of a chosen element, and MP4 video for animation pages. There is also a destinations list that sends the design to connected apps: Claude Code plus connectable partners including Canva, Miro, Netlify, Vercel, Replit, Lovable, and Wix.

The destinations list already has Netlify and Vercel. Why host somewhere else? +

Those destinations deploy the design publicly; that is what they are for. None of them adds a viewer gate. If the design is client work, the question is not "how do I put this on the internet" but "how do I show exactly one person", and that needs a host where private is the default: an unguessable URL, an optional password or email-domain gate, an expiry, and no public index. That is the slot Stacktree fills.

Can the client comment on the design without a Claude account? +

Claude Design's built-in commenting lives with the design, inside the workspace. On a Stacktree-hosted copy you can switch on the feedback toolbar instead: the client annotates the live page in their browser with no account of any kind, and the comments flow back to you (or to your agent over MCP, which can edit the HTML and mark items resolved).

The design changed. Do I have to send a new link? +

No. Export the revised Project HTML and update the same Stacktree site; the URL stays identical, so the thread you already sent the client keeps working. This mirrors how the design itself iterates in Claude, and it works from the dashboard, one API call, or the update_site MCP tool.

Can I put a Claude Design on my own domain? +

Not on claude.ai. Designs live in the workspace and published artifacts live on claude.ai URLs. Publish the exported HTML to Stacktree and you can serve it from a domain you own: add a CNAME and a TXT record, SSL is automatic, and the domain can point at whichever site you choose. Pro includes five domains.

Does the viewer need an account to open the link? +

No. The unguessable URL is itself the credential. If you add a password or an email-domain gate, the viewer passes that gate in the browser; there is still no account to create, no workspace to join, and no seat to pay for.

Keep reading

Related guides

References

Sources and further reading

Send the design to one person, not the internet.

Export Project HTML, publish, gate it. Free first publish; no viewer accounts.