How to share a Claude artifact with anyone

Claude artifacts are one of the nicer things to come out of AI tooling: you ask for a calculator, a dashboard, a landing page, and you get a working thing in a panel next to the conversation. Then you want to show somebody, and you discover the thing lives inside your chat.

The same shape of problem applies to ChatGPT canvases and Gemini’s generated pages. The output is real, self-contained HTML — it just has no address of its own.

First, use the built-in Publish button

Credit where it is due: Claude’s own sharing is good, and for a lot of cases it is all you need. Hit Publish in the artifact panel and you get a link that anyone can open — no Claude account required — and it keeps showing the latest version as you revise. If that covers your situation, stop here; you do not need another tool.

One gotcha worth knowing before you rely on it: that "no account required" applies to ordinary artifacts. If yours is an AI-powered artifact — one that calls Claude to do something when the visitor uses it — Anthropic requires viewers to sign in. So the exact artifact people most like to show off is the one most likely to hit a login wall for your audience.

Where publishing stops being enough

The limits are about control rather than capability. A published artifact is all-or-nothing public: there is no password, no restricting it to particular people, and no expiry date. It can also be indexed by search engines, which is a genuine problem if the thing is an unannounced product idea or a client’s work.

You also get no view counts, no way to collect feedback attached to the page, and a URL on someone else’s domain. And none of it helps with ChatGPT canvases or Gemini pages, which have their own separate arrangements.

• ✓Just showing a friend something you made → publish it in Claude, genuinely.
• ✓Client work, an unreleased idea, or anything you would rather not have indexed → host it yourself.
• ✓You want to know whether they opened it, or want their comments on the page → host it yourself.
• ✓It came out of ChatGPT or Gemini → publishing is not on the table; host it.

Getting the file out

Every artifact that renders as a web page is HTML underneath. Use the artifact’s copy or download control to get the source, paste it into a plain text editor, and save it with a .html extension — index.html is a fine name.

One thing to check before you save: artifacts sometimes reference libraries from a CDN. Those keep working once hosted, because the page fetches them over the network like any site. What will not survive is anything that expected to run inside Claude itself.

Giving it a real link

Upload the .html file to any host that serves files as pages. On FileShare Pro you drag it in and copy the link that comes back — the page then loads from a CDN edge, over HTTPS, on any device, with no account needed to view it.

Two things then become possible that were not before. You can replace the file in place when you revise the artifact, so everyone you already sent the link to sees the new version without you re-sending anything. And you can turn on comments, letting viewers leave feedback pinned to the page with just their name — which is what you actually wanted when you sent it around.

When an artifact will not work as a standalone page

A small number of artifacts assume a runtime that is not there once you export them — anything expecting a server, a database, or secret API keys. If your page needs one of those, hosting the HTML alone will produce a page that loads and then fails at the point it tries to call out.

The fix is upstream: ask Claude to rebuild it as a single self-contained HTML file with no backend. It is a common enough request that the models handle it well, and the result is a file you can host anywhere.