Claude artifacts
Claude’s own Publish button hands you a public link, and if public is what you want, that is the right answer — use it and pay nobody.
This page is for the three cases where it is not the right answer: the artifact has a client’s figures on it, the work is not announced yet, or you are on a Team or Enterprise plan and there is no Publish button to press in the first place.
Worth being precise about, because this is someone else’s product and it has been rebuilt more than once. Everything in this section is quoted from Anthropic’s own documentation, read on 12 September 2026.
“Anyone with the link can view and interact with it.” There is no password to add, no list of people to limit it to, and no expiry. One switch, two positions. It also files the artifact under Artifacts in your sidebar, which is the copy that outlives the conversation you made it in.
Non-users “view and interact with any published artifact without signing up”, and are asked to sign up only for the advanced features that call Claude itself. If you have read elsewhere that a Claude link requires the recipient to have Claude access, that is out of date — and it is still printed on pages currently ranking for this search.
“Artifacts created on Team or Enterprise accounts can only be shared within your organization—they cannot be published publicly.” Viewers have to authenticate with a Team or Enterprise account of their own, and where the artifact came from a project, have access to that project too. A sensible default for an account a company pays for — and the reason anyone on those plans is reading this page, because the artifact you need to send a client is precisely the one that button will not send.
“Once you unpublish an artifact, you cannot publish that same artifact again. You’ll need to create a new artifact if you want to publish it later.” Unpublishing also permanently deletes any storage the artifact was using. So the built-in link is not something to put up provisionally and take down if it turns out to be the wrong call.
Every one of these ends with a page someone can open, so “can it be private” is a yes for nearly all of them and settles nothing. The useful question is whether the document is publicly reachable at any point on the way there.
| Route | Public on the way? | Who can open it | Where it lives |
|---|---|---|---|
| Claude's Publish buttonFree, Pro, Max | It is the public step | Anyone with the link, no account | Anthropic's domain |
| Share inside your workspaceTeam, Enterprise | No | Colleagues, signed in to your org | Anthropic's domain |
| Download, compress, uploadAny | No | Whoever the host lets in | The host you chose |
| Import from the artifact's linkFree, Pro, Max only | Yes — required first | Whoever the host lets in | The host you chose |
| Publish from the conversationAny | No | Private until you widen it | pagegoat.com/sites/… |
Rows three and four are the same product either way — the difference is entirely in how the file gets there, and it is a bigger difference than it looks. Host an HTML file online compares the hosts themselves, artifacts aside.
“Import from URL” is the convenient-looking option: paste the artifact’s address, the host fetches it, nothing is downloaded. Here is what the step before it says, in the instructions of the service that ranks third for this search:
“Open the artifact in Claude and press Share, so the link is publicly reachable, then copy it.”
To be fair to them, the same sentence goes on to offer the download button instead, and the page says so plainly rather than hiding it. But the documented happy path — the one the big button is for — routes your document through a publicly reachable URL, however briefly, and for anything client-facing that is the wrong default to be nudged into. It is also simply unavailable if you are on Team or Enterprise, where there is no public link to paste.
The other path costs a step of its own: “Compress it into a ZIP and drop that on the upload box, because a loose .html file is not accepted.” So a single self-contained page — which is what an artifact usually is — has to be downloaded, put in an archive on its own, and unpacked again at the other end. Here a bare .html is accepted as it is.
Connect Pagegoat to Claude once, as a custom connector, and Claude can publish the page itself. The HTML goes from the conversation to your account directly: nothing is downloaded, nothing is compressed, and the artifact is never made publicly reachable at any point on the way.
You
Publish that dashboard to Pagegoat and give me the link.
Claude
It’s live: pagegoat.com/sites/q3-dashboard. Visibility is private — only people you invite can open it. Say the word and I’ll put a password on it or make it public.
Private is the default because it is the only default that is safe to be wrong about: widening a link is one more sentence, and un-sending one that went out public is not a thing anybody can do for you. From there the page behaves like any other page here — a password checked on the server before the document is sent, a named list of people, or public with a switch that keeps it out of search results. None of those change the address, so the link you have already sent keeps working.
The same connector updates it later, which is the part worth planning around: ask for a change in the same conversation and the page is replaced behind the address it already has. The six steps to connect Claude.ai take about a minute, and ChatGPT, Claude Code and the rest use the same address.
True of every host on this list, including this one, because none of it is anybody’s hosting to fix.
They run in a sandbox Claude provides, where the build step happens. Ask for a self-contained HTML version with inline JavaScript instead of JSX, then publish that — one sentence in the same conversation.
An artifact using the AI-powered capabilities, shared storage or file handling stops working the moment it leaves Anthropic’s runtime, because the thing it calls is not there. Those are worth keeping as artifacts.
A document sent through the connector is capped at 2 MB, which is a lot of HTML and not a lot of embedded images. Past that, upload it from the web app instead and nothing else changes.
Publishing needs a paid plan, from $2.99 a month, and the connector says so rather than failing quietly. Claude’s own Publish button is free, which is the honest comparison to make if public is acceptable.
And one thing that is missing rather than broken: there are no custom domains here. A page lives at pagegoat.com/sites/followed by a slug you choose, and if the artifact needs to sit on your company’s own address, the hosts that sell that are the right answer and this is not. What you get instead is the thing they mostly do not have: nobody outside the list you decide on can read the page, enforced before the document is sent rather than after.
No, and this is the detail pages on this subject most often get wrong. Anthropic's documentation says non-users can view and interact with any published artifact without signing up, and are prompted to sign up only for advanced features like the AI-powered ones. A copy hosted anywhere else needs no account either, because by then it is an ordinary web page. The exception is Team and Enterprise: an artifact shared inside an organisation requires the viewer to authenticate with a Team or Enterprise account of their own, and if the artifact came from a project, to have access to that project too. That is the case where a client cannot open what you sent, however you word the email.
Not with Claude's own Publish button, which has one setting and that setting is public: anyone with the link can open it, and there is no password, no named-people list and no expiry to add. A middle ground has to come from wherever you host it, and the question worth asking of a host is when the artifact becomes reachable, not just what it can do afterwards. Publishing from inside the conversation over Pagegoat's connector never makes it public at any point — Claude sends the HTML straight to your account and hands the link back in the same turn, and pages are created private, so the default outcome is a link only invited people can open. Widening it later is one sentence.
Treat the chat as the only copy until you have deliberately made a second one. An artifact lives inside the conversation that produced it, and publishing files it under Artifacts in your sidebar rather than turning it into something on your machine. Anthropic also documents that unpublishing is one-way: once you unpublish an artifact you cannot publish that same one again, and any persistent storage it used is permanently deleted along with it. A page hosted on your own account is unaffected by all of that, because it is a separate copy of the HTML sitting on a server — it keeps serving whether the original conversation still exists, whether the artifact was ever published, and whether your Claude subscription is still running.
Not as they stand, and this limitation belongs to nobody's host in particular. React artifacts run inside a sandbox Claude provides, where the build step happens; a static host serves files and has no equivalent. The fix is one sentence in the conversation — ask for a self-contained HTML version with inline JavaScript rather than JSX components, then publish that. The same applies more firmly to an artifact that calls Claude itself: anything using the AI-powered capabilities, shared storage or file handling stops working the moment it leaves Anthropic's runtime, because the thing it is calling is not there. Those are worth keeping as artifacts. Reports, dashboards, calculators and ordinary pages travel without complaint.
Yes, and without the link changing. Ask for the edit in the same conversation and Claude replaces the contents behind the address that already exists, so the URL you sent yesterday shows today's version instead of becoming one of three near-identical links nobody can tell apart. Who may open it is equally changeable after the fact: moving a page between private, password-protected and public never alters its address, so you can send it to a named list first and open it up when the work is announced. You are not locked into the conversation either — the page is the HTML you gave it, so it can be edited or re-uploaded from the web app just as easily.
One paste to connect, and the link comes back in the conversation. Publishing starts at $2.99 a month.