Can someone open a Claude artifact without a Claude account?

Yes, if you use Claude's public Publish link — it opens in a browser without an account. But the page is still hosted by Claude, and on Team or Enterprise plans artifacts can often only be shared inside your organisation.

Why does my shared artifact go out of date?

If you shared it by downloading the HTML and hosting that file, the copy is frozen at the moment you exported it. Editing the artifact in Claude does not touch the file you already uploaded, so the two drift apart until you re-export and re-upload.

Is there a free way to host a Claude artifact myself?

Yes. GitHub Pages, Netlify Drop, Cloudflare Pages and Tiiny.host all host a single HTML file for free. They give you a hosting subdomain rather than a chat preview card, and Tiiny's free links can expire, but they all work.

Guide

How to share a Claude artifact with someone who doesn't have Claude

Claude built you something that works — a calculator, a dashboard, a little interactive report — and now you want to send it to a colleague or a client who has never opened Claude in their life. The catch is that an artifact does not really exist as a file you can attach. It is worth understanding what it is before choosing how to share it.

What a Claude artifact actually is

An artifact is a small self-contained web app — usually a single HTML file with its styling and scripts bundled in — that Claude writes and then runs for you inside the Claude window. When you interact with it, you are using a live page rendered in that panel. Nothing about it is automatically a link the outside world can reach; it is tied to Claude until you deliberately get it out.

The two things Claude itself offers

1. The public “Publish” link

Claude can publish an artifact to a public URL that anyone can open in a browser with no account. This is the fastest route and, for a lot of people, the end of the story. Two honest limits: the page stays hosted by Claude, so it carries Claude’s branding and lives on Claude’s terms; and on Team or Enterprise plans, artifacts can often only be shared inside your own organisation, which is precisely no help when the person you need to reach is a client or a supplier.

2. Download the HTML and put it somewhere

You can export the artifact’s HTML and host that file yourself. This frees you from Claude entirely. The catch is that a downloaded copy is frozen: it captures the artifact exactly as it was the second you exported it. Keep tweaking the artifact in Claude and the file you already sent quietly falls out of date, because nothing connects the two.

Free ways to host it yourself

You do not need to pay anyone to put a single HTML file on the web. All of these genuinely work:

GitHub Pages. Free and dependable. Commit the HTML to a repository, switch Pages on, and you have a real URL. The address looks technical and it is a few steps if you have never used Git, but it costs nothing and does not expire.
Netlify Drop or Cloudflare Pages. Drag the file (or a folder) onto the page and get a URL back. Free and reliable. You get a hosting subdomain rather than anything branded, and no preview card when the link is pasted into a chat app.
Tiiny.host. The simplest upload of the lot — pick the file, get a link. Worth knowing that on the free tier links can expire, so it suits a quick share more than a permanent one.

If you just need the artifact visible to one person once, reach for one of these first. They are free and they do the job.

The “always the latest version” problem

Here is the frustration that sends most people looking for something better. Every self-hosted option above shares a frozen copy. You send the link, then you fix a number or reword a heading in the artifact, and now the version your client is looking at is wrong. Re-exporting and re-uploading gives you a new file — and often a new URL — so you are back to chasing people with “actually, use this one instead.” When a static copy drifts from the live artifact, the link stops being trustworthy.

What SendPage adds for this case

SendPageis built around that one problem. You paste the artifact’s HTML and get a link that colleagues open with no Claude licence, in any browser. When you change the artifact, you paste the new HTML and the link stays the same — so the copy your client has never goes stale, and there is no follow-up message with a replacement URL. You can also password-protect the link when it is meant for internal eyes only.

If the artifact came from Claude, you can skip the copy-and-paste entirely and let Claude publish the link straight from the conversation through the MCP connection.

One honest caveat: SendPage hosts the page, not a server. If your artifact is only a front end that expects to talk to a live database or a private API, hosting its HTML will not conjure that backend into existence — for that you still need a real application host. For the common case, where the artifact is a self-contained page, it is exactly the fix.

Step by step: share it as one link

Open the artifact in Claude. Click into the artifact panel so the finished page is showing.
Copy or export its HTML. Use the copy or download control — the single HTML file is the whole app.
Paste it into a paste-to-link tool. GitHub Pages, Netlify Drop, Cloudflare Pages, Tiiny.host or SendPage all turn that HTML into a hosted page.
Share the single link. The recipient opens it with no Claude account. When the artifact changes, paste the new HTML.

The short version

An artifact is an HTML mini-app that lives inside Claude. Claude’s Publish link is the quickest way out but stays tied to Claude and may be org-only on business plans. Free hosts like GitHub Pages, Netlify Drop, Cloudflare Pages and Tiiny.host all work if a frozen copy is fine. The moment you need the shared version to keep matching the artifact you keep editing, that is the gap SendPage was built to close — as long as the artifact is a self-contained page and not a front end for a backend you still have to run.