
How to Publish a Claude Artifact as a Standalone Webpage
Two ways to put a Claude artifact on a real URL: Claude's own Share link (Publish, for legacy chat artifacts), or pasting the code into dochost for a plain standalone link.
Ask Claude for a landing page, a quiz, a chart, or a small calculator and it often answers with an artifact — a live preview panel running actual HTML, CSS, and JavaScript. That's not a mockup. It's a working webpage that happens to be trapped inside a chat window. Getting it out onto a URL someone else can open takes one of two routes, and which one you pick depends on where you want the page to live.
What does "Publish artifact" actually mean in Claude?
It depends on when the artifact was made. Claude changed artifact sharing on 16 September 2026, and its Share artifacts help article (updated 4 November 2026) now describes two flows:
- Artifacts made since 16 September 2026 have a Share button, not Publish. You choose who has access. Setting it to Anyone with the link is the closest thing to publishing.
- Legacy artifacts, made in a chat before that date, still show Publish on Free, Pro, Max and Ultra (and Share & copy link on Team and Enterprise). You can still publish and share them, but you can't make new ones.
Either way, it's worth being precise about what a public link does and doesn't include:
- Only the artifact travels — not the conversation. Your prompts, Claude's replies, and anything else in that chat stay where they are. (One exception on Team and Enterprise: sharing a legacy chat artifact also gives viewers access to the attachments and files in that chat.)
- Most links open without an account. Claude's Help Center says most artifacts shared with Anyone with the link open without a Claude account or sign-in, and a published legacy artifact always does. Docs are the exception: they open only for people signed in to Claude. Dashboards and artifacts that keep their content in Claude's storage show little until the visitor signs in, and parts that use Claude or connected apps don't work for signed-out viewers.
- Anyone holding the URL can open it. There's no allowlist on a link-for-anyone share, so it reaches whoever the person you sent it to forwards it to. If you need named people only, Claude now has email invites (beta, Pro and up); they sign in with the invited address.
- Legacy Publish is a one-way door. Per Claude's Help Center, once you unpublish a legacy artifact you can't publish it again, and its stored data is deleted. Newer artifacts don't have that catch: changing Who has access back to Only you is a setting you can flip again.
For most artifacts — a demo, a template, a portfolio piece — that's fine. For a client deliverable with numbers in it, it may not be, and the options are covered in are Claude artifacts public? and the standalone-URL route below.
Option 1: Claude's own Share link (or Publish, for legacy artifacts)
Claude has sharing built in, and for a lot of cases it's the shortest path.
For an artifact made since 16 September 2026: open it, click Share, under Who has access choose Anyone with the link, then copy the link. On Pro, Max and Ultra the choices are Only you or Anyone with the link, plus email invites. On Team and Enterprise you can share with your organisation or named colleagues, and Anyone with the link only appears if an owner has turned on External sharing.
For a legacy chat artifact (Free, Pro, Max, Ultra): open it, click Publish, and copy the public link. Anyone can open it without a Claude account. Signed-in Claude users can copy it into their own chat and build on it, without touching your original.
A few things worth knowing before you rely on it:
- Not every artifact can go out on a public link. Artifacts that connect to other websites can't use Anyone with the link, and Docs always ask the viewer to sign in.
- Team and Enterprise depend on an owner. If External sharing is off, a link only works inside your organisation. If an owner turns it off later, existing links stop working until it's back on.
- Unpublishing a legacy artifact is one-way. Once you unpublish, you can't publish that same artifact again, and its stored data is deleted. If there's any chance you'll want the link back, don't unpublish casually — what to do before you click.
- Embedding needs an allowlist. For a published legacy artifact, Get embed code gives you a snippet, and you list which domains are allowed to embed it.
- You can't change sharing on mobile. The Claude iOS and Android apps can't change sharing settings; use the web or Claude Desktop.
If the link opens cleanly for the people you're sending it to, stop here — the built-in flow is exactly that, and it keeps things a copy can't, like comments, edit access and the parts of an artifact that call Claude.
When you want a plain standalone URL instead
Sometimes the Claude-hosted link isn't the right shape for the job:
- You're on a Team or Enterprise plan without External sharing and need the page visible to people outside your org — a client, a customer, the public.
- Your reader lands on a Claude sign-in screen — a Doc, a dashboard, or an artifact that keeps its content in Claude's storage.
- You want the page to read as your document, not a Claude artifact — a clean standalone page you'd put in a proposal, a QR code, or a support reply.
- You want control Claude's sharing doesn't offer: a custom slug, password protection, or a link that expires on its own.
For those cases, remember what an artifact actually is: code. You can take the code anywhere.
Option 2: copy the code, paste it, get a link
- Grab the artifact's source. In the artifact panel, switch from the preview to the code view (or use the copy button) and copy the full HTML.
- Paste it at dochost. You get a live preview immediately — it should look identical to what you saw in Claude, because it's the same code running in a real browser context.
- Click publish. You get a short link, no account required. Send it, embed it in an email, put it behind a QR code — it's just a URL.
The important property: the interactivity survives. Published pages run inline JavaScript exactly as written, so the quiz still scores answers, the calculator still calculates, the chart still animates. CDN-referenced libraries and fonts load too. The only thing that breaks is a reference to a file that exists solely on someone's local disk — which artifacts almost never contain, since Claude builds them self-contained by design.

Or skip the copy-paste: one-click from inside Claude
If you do this more than occasionally, the dochost Chrome extension collapses the three steps into one. It detects HTML and Markdown in your Claude (and ChatGPT) conversations and adds a publish button right there — click it, get the link, no tab-switching or clipboard step. It works anonymously, same as pasting by hand.
Prompting tips: get an artifact that publishes cleanly
Most artifacts publish fine as-is, but a couple of phrases in your prompt make the output more portable:
- Ask for "a single self-contained HTML file." This tells Claude to put everything — markup, styles, scripts — in one document instead of describing a multi-file project. One file is one paste.
- Inline CSS and JavaScript are good here. Normally you'd split them out; for a page that lives at one URL,
<style>and<script>blocks inside the file are exactly right. - CDN links are fine. If Claude pulls in Tailwind, Chart.js, or a Google Font from a CDN, leave it — those URLs resolve for every visitor. What you don't want is
src="./app.js"pointing at a file that doesn't exist outside the chat. - Test in the preview before sharing. The paste preview is the same rendering your visitor gets. If a button works there, it works at the link.
If Claude's answer is a Markdown document rather than an HTML artifact — a spec, a report, a table-heavy brief — the copy-paste route works the same way but renders through the Markdown pipeline instead. That case has its own walkthrough: share Claude's Markdown as a clean page.
How long the link lasts
A free link lives for 7 days (3 if you publish it as private), with or without an account — plenty for a review round or a demo. If the artifact is something people will keep opening — a tool your team uses, a page linked from elsewhere — a paid plan makes it permanent and adds the custom slug and password options mentioned above.
Claude's Help Center doesn't describe an expiry for its shared links: they last until you change who has access (or, for legacy artifacts, unpublish), and on Team and Enterprise until an owner turns External sharing off. Different trade-off, not strictly better or worse.
Can you embed a published artifact in an email?
Not as a working artifact, and the reason is the email client rather than Claude. Mail apps strip <script> and almost all of them refuse <iframe> outright — Gmail, Outlook and Apple Mail included — so an interactive page cannot run inside an inbox no matter where it's hosted. Claude's embed code for published legacy artifacts has the same ceiling, plus its own domain allowlist, and an allowlist has nothing to point at in an email.
What actually works is the two-part version everyone ends up at: a static image in the email — a screenshot of the artifact, or a chart exported as PNG — wrapped in a link to the live page. The recipient sees something in the message and lands on the working version in one tap. If the destination is a page on your own site rather than an inbox, that's where embedding does work, and the iframe generator builds the snippet for you.
Do Claude artifacts use tokens?
Building and editing one does. Viewing a published one does not, and that difference is the whole reason people ask.
- Creating costs output tokens. An artifact is Claude's reply — the HTML, CSS and JavaScript are generated text, so a 600-line page is priced like 600 lines of any other answer.
- Editing re-reads it. The artifact's current contents sit in the conversation, so every later turn in that chat carries it. A long artifact you keep tweaking gets more expensive per turn, not less, and it is the usual reason a productive artifact conversation starts feeling slow.
- Opening a shared link doesn't spend your usage. For most link-shared artifacts the reader just gets the page. If the artifact itself calls Claude, Claude's Help Center says that usage counts against each person's own plan, not yours, and signed-out viewers can't use those parts. A page you paste into dochost uses no Claude tokens at all.
- Remixing does cost the remixer. When a Claude user copies a published legacy artifact into a new chat and customizes it, that's their conversation spending their usage.
So if what you actually want is "lots of people should look at this without burning anything," a published link — Claude's or a standalone one — is already the cheap path. The token cost lives in the making, not the reading.
Which route should you take?
Use Claude's Share link (or Publish for a legacy artifact) when the audience is fine landing on a Claude-hosted page and it opens for them — especially if they should comment, edit, or use the parts that call Claude. A side-by-side is on Claude artifact sharing alternative.
Use copy-paste (or the extension) when you want a neutral, standalone URL: client deliverables, readers who hit a sign-in screen, public pages from a Team/Enterprise account without External sharing, anything that needs a password or a custom slug, or a page whose lifecycle you want in your own hands. Claude artifact to link walks through it.
Related questions
- Are Claude artifacts public? — what a shared link exposes, and to whom
- How to unpublish a Claude artifact — stopping sharing, and the one-way door for legacy artifacts
- How to download a Claude artifact — which file you get, and why React artifacts won't open
- How to turn a Claude artifact into a PDF — why printing from the chat gives you the transcript instead
- Skills vs Projects vs Artifacts — three features, three different jobs
Bottom line: a Claude artifact is already a working webpage — the only question is where it lives. Claude's Share link (or Publish, for a legacy artifact) puts it on a Claude link; copying the code and pasting it into dochost (or using the extension's one-click button) puts it on a plain standalone URL, JavaScript and all.
Author
Categories
More Posts

How to Share a Mermaid Diagram as a Link
The fastest way to turn Mermaid code into a rendered diagram anyone can open in a browser — no screenshots, no repo, and no account required.

How to Publish a Page From Gemini CLI, Codex, Cursor, VS Code or Windsurf
Five coding assistants, one MCP server. The exact install command or config file for each — including the Gemini CLI extension — what the first tool call looks like, and how to ask for a page and get a link back without leaving the terminal.

How to Unpublish a Claude Artifact — and When You Only Get One Shot
Newer artifacts: click Share and set access back to Only you, which you can undo. Legacy published artifacts: click Unpublish, which is permanent and deletes their stored data.
Newsletter
Join the community
Subscribe to our newsletter for the latest news and updates