How-to
How to publish a Claude artifact
Three routes
Pick a publishing method
Claude’s own Share or Publish
Built into Claude. Viewers need a Claude account, except for legacy artifacts published with Publish.
Jump to steps ↓Most control, still in chatPagelive connector
Say “publish this” in Claude and get a noindex link anyone can open, without leaving the chat.
Jump to steps ↓No setupUpload the HTML
Export the artifact as an HTML file and upload it yourself. Works without connecting anything.
Jump to steps ↓Before you publish
A 60-second pre-flight check
- ✓ Preview the HTML outside Claude so you know it renders on its own: paste it into the free HTML viewer.
- ✓ Strip anything secret: API keys, internal URLs, client data you don’t want in the page source.
- ✓ Check it on a phone-sized window: most recipients open links on mobile first.
Artifact rendering blank or broken? Fix it first. Claude artifacts not working: common fixes.
Option 1
Claude’s own Share and Publish
As of October 2026, artifacts have a Share menu: “Only you”, “Anyone with the link” (anyone signed in to Claude), email invitations (beta, Pro and up), and your organization on Team and Enterprise. The Publish button, which makes a public page that opens without a Claude account, appears only on legacy artifacts (made in a chat before September 16, 2026) on Free, Pro and Max.
- 1. Open the artifact in Claude on the web or desktop.
- 2. Click Share (or Publish on a legacy artifact) and choose who has access.
- 3. Copy the link and send it.
Know the limits
- –“Everyone needs a Claude account”: a client without one can’t open a shared artifact, even with the link.
- –Publish (no account needed) exists only for legacy artifacts: made in a chat before September 16, 2026, on Free, Pro or Max. Once unpublished, it can’t be published again.
- –Artifacts that connect to your apps or use Claude can’t use “Anyone with the link”, and the page stays on Claude, not your own domain.
Source: Anthropic’s Share artifacts article. If your client doesn’t use Claude, those limits matter. Claude Publish vs. Pagelive, compared →
Option 2 · Recommended
Publish from inside Claude with the Pagelive connector
“Publish this as a Pagelive page.”Add the connector
In Claude (web or desktop), add Pagelive as a connector with the URL app.pagelive.io/api/mcp and approve it once.
Say “publish this”
With your artifact open, ask Claude to publish it as a Pagelive page. Claude sends the HTML over, no copy-paste.
Get your link
Claude replies with a live link, noindex by default, so search engines are told not to list it. On Solo, add a password or your own domain from the dashboard.
Option 3
Upload the HTML manually
- 1. In Claude, export the artifact as HTML (Design artifacts: Export, standalone HTML; legacy artifacts: download or copy the code).
- 2. Upload the file in the Pagelive dashboard. No account yet? The free publish tool takes a file or pasted HTML, and the homepage dropzone gives a no-signup link (live 7 days unless claimed).
- 3. You get the same link: noindex by default, with a view count, and a password on Solo and Team.
Protect it
Add a password for client work (Solo and Team)
A published artifact that contains pricing, scope, or anything confidential deserves a gate. On Solo and Team, flip on a password and only people with the link and the password get in. Passwords are hashed (PBKDF2), so we can’t see them, and the page stays noindex regardless.
Page settings
Viewers see a clean unlock screen, no Pagelive account needed.
Brand it
Put it on your own domain
A proposal at pages.youragency.com/acme-proposal lands very differently from a generic share URL. Solo includes up to 5 custom domains and custom slugs (Team includes 25). One domain hosts as many pages as you like.
After publishing
Track views and update the same link
Every published page shows a view count, and Free emails you the first time each page is opened. Solo and Team add the full breakdown (unique viewers, reading time, by day, country, and referrer, bot opens filtered out) and an email on every open. Republish anytime: the link never changes, and on Solo and Team version history keeps your previous edits.
Publishing FAQ
Not from Pagelive: pages are noindex by default, so we tell search engines not to list them. Worth knowing: the easy free ways to put an AI-built page online usually do the opposite and publish it as a public, indexable web page. If the artifact is client work, the private default matters.
Through Claude, usually yes: as of October 2026, Anthropic says everyone needs a Claude account to open a shared artifact, except a legacy artifact published from a chat. A Pagelive link is a normal web page: it opens in any browser, with no Claude account, app, or login (unless you add a password on Solo or Team).
Yes. Republish the new version and the link never changes, so a client mid-read never hits a dead URL. Solo and Team also keep the version history.
Free for 2 public pages. Solo is $15/mo ($150/yr): the whole product, including up to 5 custom domains and lead capture. Team is $49/mo per workspace, up to 10 members.
More guides: Claude artifacts: what they are, how to share and publish them · share an artifact without a login · are Claude artifacts public?. Publishing a client proposal? See AI proposal software.