How Anthropic splits artifacts
This is the detail that catches people out, so it is worth reading Anthropic's own wording. Its page on publishing and sharing artifacts splits artifacts into two groups by where they were made, and gives them opposite rules. Checked 7 October 2026.
| How it was shared | Can a non-user open it? |
|---|---|
| Published from chat, with the Publish button (Free, Pro and Max plans, previous chat experience) | Yes. Anthropic says “anyone with the link can view and use it without a Claude account”, and that they are asked to sign up only for features that use Claude. |
| Shared from the Share dialog (the new Claude experience, Claude Design, Slides, Docs and Claude Code) | No. Anthropic says everyone needs a Claude account, and that people without one “can’t open a shared artifact, even with the link”. |
| Invited by e-mail address (beta, on Pro, Max, Team and Enterprise) | No. Anthropic says the person needs a Claude account with the address you invited, and must create one first if they do not have it. |
Two things to know before you send either kind
First, a shared chat artifact brings the conversation's files with it. Anthropic writes that viewers “also get access to any attachments and files in the conversation that created it”, and advises thinking about that before sharing from a conversation with sensitive documents in it.
Second, your reader may not see what you see. Anthropic documents that viewers use their own access: an artifact that pulls from connected apps uses the viewer's connections, not yours, and shows an error where they lack access. A client with no Claude account has no connections at all.
The route that always works
In the artifact window, view the underlying code and download the file. Anthropic documents both, and lists single-page HTML websites among the things artifacts commonly are.
Check it is one self-contained file: styles, scripts and images inline, or assets at absolute URLs.
Upload it to HTMLRadar and send the link. It opens in any browser, on any device; the reader needs no account and nothing to install.
Colleagues at a Team or Enterprise company
These are the three things people ask for when they try this inside Claude.
| What you need | How it works here |
|---|---|
| Anyone at the company opens it, without a Claude licence | The link opens in any browser for an address at your domain that confirms a code. Readers need no account and nothing to install. |
| It always shows the latest version | Replace the file from the dashboard, or have Claude replace it through the connector. Every link you already sent shows the new version, with the same address and settings. |
| An update reaches everyone | Nobody needs a new link, and what they have read so far stays on the record. You see who opened the new version and which sections they read. |
- Company domains
- The link asks for an e-mail address before the page opens. An address outside your company’s domains is refused there, and the page is never served to it. List more than one domain if your company uses several.
- One-time code
- Turn the one-time code on as well. A domain rule alone lets in anyone who types a company address; the code proves the reader can open that inbox.
- Microsoft 365
- On HTMLRadar’s Team plan, colleagues on Microsoft 365 can sign in with their work account instead of waiting for a code.
- If it travels
- A code proves someone could open the mailbox at that moment, not who read the page afterwards. If a link travels further than you meant, switch it off and it stops opening at once.
Your company’s web pages, in one place.
When more than one person sends pages like this, HTMLRadar’s Team plan puts them in one place: who sent what, who read it, and which parts they read. An admin sees every colleague’s pages and links, who opened each one and how long they spent on each section, and can download it all as a CSV file. Work sent through the team stays with the company when someone leaves, and its links can be switched off.
Where HTMLRadar helps, and where it does not
It helps with the ordinary case: a deck, a proposal, a report or a one-pager that Claude wrote as a page. You get a link with no sign-in wall, and because it is your link rather than Anthropic's, it also tells you who opened it, which sections they read and how long they stayed. A published artifact does not report that.
When it does not help
It does not help when the artifact is only interesting because it is running inside Claude. Anything that asks Claude questions, reads a connected tool, or saves data between visits needs Anthropic's infrastructure and a signed-in viewer. Exporting the HTML gives you the shell without the behaviour.