Claude got very good at producing finished things. Interactive dashboards, landing pages, calculators, little games, working prototypes. They appear in the artifact panel, and then comes the practical question: how do you get this in front of someone who was not in the conversation?
There are more answers than you would expect, and the right one depends on who is receiving it. Here is the full menu, including the sharp edges the Claude docs do not dwell on.
Option 1: the built-in Publish button
Open the artifact, hit Publish, copy the link. Anyone can open it without a Claude account. For a quick "look what I made" to a friend, this is the answer and you can stop reading.
For work, the fine print starts to matter:
- The link is public. No password, no expiry, no access control of any kind. Anyone who has (or finds, or gets forwarded) the URL sees the page.
- It is dressed as Claude, not as you. Your client sees claude.ai chrome around the work you are billing them for.
- Team and Enterprise plans cannot publish at all. External sharing is disabled on exactly the plans used by people who most need to share with clients. The Publish button simply is not there.
- No feedback channel. Reactions come back through whatever channel you sent the link on, detached from the thing itself.
Option 2: copy the code, host it yourself
Every artifact has a copy button. HTML artifacts copy out as a complete page you can drop onto any static host: GitHub Pages, Netlify, Vercel, an S3 bucket, whatever you already use. You get a permanent URL, your own domain if you have one, and total control.
The cost is the workflow. Copy, save to a file, create a repo or a site, deploy, then repeat every deploy when Claude revises the artifact, which it will, because iteration is the whole point. For one page shipped once, fine. For the third revision this afternoon, tedious. Our comparison of free static hosts goes deeper on the options here.
Option 3: paste it into a private sharing link
In between those two: copy the artifact code, paste it into a sharing tool, get a controlled link. This is the use case we built commentable around, so here is precisely what that flow gives you:
- The page is encrypted in your browser before upload. The decryption key rides in the link fragment and never reaches our server, so the page is readable only by people you send the link to.
- You can add a password and an expiry date. Client work stops being one forward away from public.
- Your logo and your name on the page, not ours or Anthropic's. Free, not a paid feature.
- People you share with can pin comments directly on the page, no account needed. Feedback arrives attached to the exact element it is about.
This also works on Team and Enterprise plans, because copying code out of an artifact is always allowed. The publishing restriction only applies to Claude's own hosting.
Option 4: skip the copy-paste entirely (MCP)
If you share artifacts often, the copy-paste step itself can go away. Claude supports connectors (MCP servers), and commentable ships one. Once connected, you say "publish this as a commentable link" in the conversation and Claude hands you back the finished URL, encrypted, branded, with comments on. When you revise the artifact, Claude updates the same link instead of minting a new one, so the URL you already sent your client quietly gets the new version.
This is our favorite way to work and the reason the product exists. The artifact never touches your clipboard.
Choosing between them
| You are sharing with | Use |
|---|---|
| A friend, publicly, no stakes | Built-in Publish |
| A client, or anyone paying you | A private link with password and your branding |
| The whole internet, permanently | Copy the code to a static host |
| Reviewers who need to give feedback | A link with pinned comments |
| Anyone, several times a day | The MCP connector |
One habit worth forming regardless of tool: share a link, never a file. An artifact saved as an attachment is dead on arrival half the time, and the other half it opens without the fonts and scripts it needed. The page working is the whole demo. Send the URL.