How to share a Claude artifact privately
Claude does not offer a private, gated link for artifacts. On Free, Pro and Max you can publish an artifact to a public URL that anyone can open. On Team and Enterprise you can share it inside your organization, where viewers must sign in. There is no middle option, one named recipient with no seat required, so sharing privately means hosting the HTML somewhere else.
That gap is the whole subject of this guide.
What Claude's sharing model actually allows
Anthropic uses two different words for two different things, and the distinction decides what you can do.
| Publish | Share | |
|---|---|---|
| Plans | Free, Pro, Max | Team, Enterprise |
| Audience | Anyone with the link | Members of your organization |
| Sign-in required | No | Yes |
| Available on the other plan group | Team and Enterprise cannot publish publicly | No |
Source: Anthropic Help Center, Publish and share artifacts, checked August 17, 2026.
The counterintuitive result: the more you pay, the smaller your audience. An Enterprise account cannot produce a link an outside client can open.
Live artifacts created in Claude Cowork follow a separate rule again: shareable only on Team and Enterprise, inside the organization, and per the documentation they cannot be published publicly on any plan.
What Publish does not cover
The list below is absence, not prohibition: Anthropic's documentation describes the publish flow and does not mention passwords, expiry dates, custom domains or view reporting.
| Requirement | Covered by Publish? |
|---|---|
| Public link, no account needed to view | Yes |
| Embed on another site, with an allowed-domains list | Yes |
| Password on the link | Not described in the docs |
| Expiry date | Not described in the docs |
| Your own domain | Not described in the docs |
| Who opened it, and when | Not described in the docs |
| Unpublish, then republish later | No, unpublishing is irreversible |
| Public link on Team or Enterprise | Does not exist |
Two documented traps worth knowing before you click anything.
First, unpublishing is permanent. Once you unpublish an artifact you cannot publish that same artifact again, you have to build a new one. And if the artifact used persistent storage, unpublishing permanently deletes all associated storage data, personal and shared. Treat that button as delete, not as a toggle.
Second, on Team and Enterprise, sharing an artifact also grants viewers access to any attachments and files in the conversation that produced it. Upload a client spreadsheet, generate a dashboard from it, share the dashboard, and the spreadsheet travels with it.
Three ways to share an artifact with one person
1. Publish it and send only that person the link. Free, instant, and the honest description is unlisted, not private: anyone who receives a forward can open it, and you have no way to know they did. Fine for a draft. Not fine for anything with a client's data in it.
2. Move the account to Team or Enterprise. Real authentication, real access control. It only works if the recipient is inside your organization, which rules out clients, investors and candidates.
3. Export the HTML and host it behind a gate. Copy the artifact code, save it as an .html file, and publish it on a host that supports password protection or an email check. This is the only path that produces a private link to a named outsider.
Choose option 1 if the content is public anyway and you just want it seen. Choose option 3 if the artifact is a deliverable: a proposal, a report, a dashboard with real numbers.
One thing does not export. Artifacts that call Claude at runtime, the AI-powered ones, depend on infrastructure that does not travel with the code. If your artifact makes model calls when someone interacts with it, hosting it elsewhere is not an option.
How to export an artifact's HTML
Before you start: the artifact open in Claude, a plain text editor, and a host to publish to.
- Open the artifact and click Copy to put the code on your clipboard.
- Paste it into a plain text file and save it with an
.htmlextension. - Open the file in a browser. You know it worked when the page renders exactly as it did inside Claude.
- Upload it to your host. You know it worked when the URL opens in a private window.
- Test on a phone. Artifacts are built in a wide panel and narrow screens expose layout assumptions.
If it breaks: styling gone means the artifact referenced an external stylesheet, so upload a .zip instead. A blank page means the artifact is JSX or React and needs a build step or a host that wraps it. Dead interactive parts mean it used Claude's AI capabilities, which do not export.
When you should just use Publish
Publish is the right answer more often than a vendor would like to admit.
If you are showing a prototype to a colleague, publishing takes two clicks, costs nothing, and works for people without a Claude account. Exporting and hosting is wasted effort.
If the artifact is a public demo or a portfolio piece, publish it and use the embed code: the allowed-domains field gives you more control over embedding than most hosts do.
If the artifact needs Claude at runtime, publishing inside Claude is not the better option, it is the only option.
Host elsewhere when the artifact is a deliverable that belongs to someone else, when you need to know whether it was read, or when your Team or Enterprise account leaves you with no public link at all.
Where I LOVE HTML fits
I LOVE HTML is a platform for publishing and sharing HTML pages, including AI-generated ones, built in Brazil and available in Portuguese, English and Spanish. It closes the gaps in the table above: the same HTML gets a link with a password, an expiry date, a custom address, a 25-version history and a record of who opened it and how long they read.
Pricing: the free plan covers 5 files; Pro is US$ 3 per month and Business US$ 10, with 100 and 500 files.
The honest limitation: publishing straight from Claude is one click and requires no account anywhere. Any external platform, including this one, adds a sign-up and an upload step. If your case is showing something public quickly, Claude's button wins.
FAQ
Can you password-protect a Claude artifact? Anthropic's documentation does not describe a password option. Gating requires hosting the HTML outside Claude.
Can Enterprise users publish a public link? No. On Team and Enterprise, artifacts can only be shared inside the organization.
Does the recipient need a Claude account? No for published artifacts: non-users can view and interact without signing up, and are only prompted to register for advanced features. Yes for artifacts shared internally on Team or Enterprise.
Can I unpublish and republish later? No. Unpublishing is permanent for that artifact, and it deletes associated persistent storage.
Is the Remix button gone? Yes. Copying the code into a new chat replaces it.
Primary source: Anthropic Help Center, Publish and share artifacts, checked August 17, 2026. Anthropic ships changes to this product frequently, so verify before relying on it.