How to Share a Claude Artifact as a Public Link

When people want to share a Claude artifact, most of them reach for Claude's own Publish button, and for a quick, throwaway share that's the right call. It stops being the right call once you need control over who sees the page and where it lives.

I built ShareMyPage for that second case, so the tool I recommend below is mine. Here is where each option fits.

Claude's Publish is fine for a throwaway share

Claude has a Publish option on artifacts that gives you a claude.site link. Use it when that's all you need.

It stops mattering when you want control. A published artifact carries Claude's branding, can't be password protected or scoped to your team, is tied to your Claude account, and has to be re-published to update. For anything you send to a client, a coworker or the public, you usually want the page on a link you control.

An HTML artifact copies out as one file

An HTML artifact is the easy case. Open it, use the artifact's copy control to grab the full document, and save it as an .html file.

A React or multi-file artifact is different, because what renders in Claude is built from components, not one HTML file. Ask Claude to "output this as one self-contained HTML file with the CSS and JS inline," and it hands you a single document.

ShareMyPage gives it a link you control

This is for you if:

• the artifact is going to a client, a coworker or the public
• you want to decide who can open it
• you want to update it without sending a new link

1. Save the artifact's HTML, or Claude's self-contained single-file version, as an .html file.
2. Open ShareMyPage and drop the file in.
3. Choose who can see it, copy the link and send it.

The page goes live immediately at a clean URL. It renders in a sandboxed frame, so whoever opens it is safe, and you can edit it later without breaking the link you already sent.

The real downside is that sandbox. It gives the page no localStorage and no cookies, so an artifact that remembers things in the browser forgets them on reload. If your artifact depends on that, test it at the link before you send it.

Choosing who gets in is the reason to switch

Some artifacts are demos for the world, others are drafts for a client or your team. This is what Claude's Publish can't do:

• anyone with the link, for an open page
• anyone with the link plus a password, when access should be limited. See how to password-protect a page.
• your workspace only, to keep it inside your company. See sharing pages with your team.
• just you, plus anyone you invite by email

Let Claude publish it for you

If you build with Claude often, skip the copying. ShareMyPage has an MCP server that lets Claude create the page itself. You say "publish this as a page," Claude calls the tool, and the link comes back in the same message.

The short version

• Use Claude's Publish for a quick share where branding and access don't matter.
• Use ShareMyPage when it goes to a client or your team, or needs a password.
• Connect the MCP server if you do this every week.

One tip: when the artifact is React, ask Claude for the single self-contained HTML file before you do anything else. Everything after that is one upload.

Have an artifact to share? Create a page on ShareMyPage and drop the HTML file in.