How to host a Claude Artifact
If you just want a link, publish it inside Claude and you are done. That costs nothing, takes one click, and anyone can open the result without an account. A separate host adds a web address you control and a custom domain, and changes nothing else: the page is still one static file that cannot authenticate anyone or keep what they type. That limit is architectural rather than a missing feature, so no host removes it. If your thing needs to know who is looking, hosting is the wrong question and you need an app.
Last checked against Anthropic's documentation on . Claude changes often. If something here no longer matches the help centre, the help centre is right.
Put a Claude artifact on the web
-
Publish it inside Claude first
Open the artifact and use the Publish control. This gives you a link anyone can open with no account, which for most uses is the whole job. Do this before evaluating any other option, because it is free, instant, and the thing every other option is competing with.
-
Decide whether you actually need your own address
The reasons to move are a domain you control, a URL that survives the conversation, and analytics. Those are real reasons. If none of them applies to you, stop here.
-
Copy the artifact's HTML to a static host
An artifact is a single HTML page, so any static host will serve it: a hosting service, an object store, or a plain web server. There is no build step and no framework to configure.
-
Check what stopped working
Artifact storage is a claude.ai feature, not part of the HTML. A page that used persistent storage keeps its interface once moved and silently loses its data layer, so test the parts that save something before you send the new link to anyone.
-
Move to an app if you hit identity or data
If the page needs to know who is looking, keep what people type, or accept a file, no host fixes that. At that point the page needs a backend, and rebuilding it as an app is less work than trying to bolt one on.
Which kind of hosting you actually need
Four different questions arrive at this page, and only one of them is answered by a hosting product. Find your row first.
| What you want | What you actually need |
|---|---|
| A link to send someone so they can use the thing | Publish it in Claude. Free, instant, no account needed at the other end |
| The same, but at your own domain | A static host. This is the one row where a hosting product is the right answer |
| A page that remembers what visitors type into it | Not hosting. A static page cannot do this wherever you put it |
| A page that knows which visitor is which | Not hosting. This is the wall, and it is the reason most people end up here |
If you are in row one, the rest of this page is background. If you are in rows three or four, the hosting question is a detour and the last section is the one you want.
What publishing inside Claude already gives you
The option everything else competes with is the free one, and it is worth knowing exactly what it does before paying for an alternative.
share a link that anyone on the internet can open, with no claude.ai sign-in required
Share session output as artifacts, Claude Code documentation
That property is the one no account-based platform can match, including this one. Anthropic documents what each kind of visitor gets:
View and interact with any published artifact without signing up. Try all basic functionality without a Claude account.
Publish and share artifacts, Claude Help Center
Full access to view, interact with, and copy any published artifact. Can use AI-powered features within their usage limits.
Publish and share artifacts, Claude Help Center
Two conditions are worth knowing before you rely on it. On business plans the default is narrower:
Artifacts created on Team or Enterprise accounts can only be shared within your organization
Publish and share artifacts, Claude Help Center
On Team and Enterprise plans, public sharing is off until an Owner enables it for the organization.
Share session output as artifacts, Claude Code documentation
And a viewer who copies your artifact gets a fork rather than a window onto yours:
Your version is separate from the original, so nothing you do affects the artifact you started from.
Publish and share artifacts, Claude Help Center
What a separate host adds, and what it cannot
An artifact is one HTML file, so moving it somewhere else is genuinely easy: there is no build, no framework and no server to configure. What you buy is an address, and what you keep is every constraint the page already had.
An artifact is a capture of work, not an application.
Share session output as artifacts, Claude Code documentation
That is Anthropic describing its own design, not a criticism from us, and the documented limits follow from it:
An artifact is a static page. It can't store data submitted through a form or authenticate viewers itself.
Share session output as artifacts, Claude Code documentation
The CSP blocks scripts, stylesheets, fonts, and images loaded from any other host, along with fetch, XHR, and WebSocket calls.
Share session output as artifacts, Claude Code documentation
Relative links do not resolve, because nothing is deployed alongside the page.
Share session output as artifacts, Claude Code documentation
None of those change when the file moves. They are properties of a static page, so a host that promises to fix them is describing a rebuild, not a deployment.
One thing does change, and it changes for the worse. Artifact storage is a claude.ai feature rather than part of the file:
Persistent storage for artifacts is available on Pro, Max, Team, and Enterprise plans on Claude web and desktop.
Persistent storage for artifacts, Claude Help Center
Persistent storage is only available for published artifacts. During development and testing, storage operations will not succeed until the artifact is published.
Persistent storage for artifacts, Claude Help Center
So a page that saved anything keeps its buttons and loses its data layer the moment it is served from anywhere else. That failure is quiet, because the interface still renders. Test whatever saves before you send out the new link. What artifact storage can and cannot hold in the first place is covered in what Claude Artifacts can and cannot store.
The one exception to the no outside data rule
Anyone who tells you an artifact can never reach live data is a version behind. There is a real exception, and it comes with a condition that decides what it is good for.
Connector calls are the exception: the page hands them to claude.ai, which makes the network call itself.
Share session output as artifacts, Claude Code documentation
calls go through the viewing account's connected tools, so two people opening the same dashboard can see different data depending on what their accounts can access
Share session output as artifacts, Claude Code documentation
An artifact that calls connectors can't be shared to a public link on any plan.
Share session output as artifacts, Claude Code documentation
Read those three together and the shape is clear. A connector-backed artifact is a very good personal dashboard over data the viewer already has, and it is not a shared application: the data belongs to whoever is looking, and the page cannot be public at all. It is therefore not a hosting option, because the thing you would be hosting cannot have a public link.
When hosting is the wrong question
Rows three and four of the first table are not hosting problems. A page that needs to tell two people apart, keep what they enter, or take a file needs something running behind it, and that is true at every address you could put it at.
Homespun is where the same agent that built the thing can host it. People sign in with their email, so the app can tell who is who and every row remembers who created it; permissions are set per collection, so some people can approve and others can only submit; and the agent keeps read and write access to the collections it is allowed, so it can keep working on the data instead of handing you a page and walking away. It is free today, and there is no paid plan to buy.
The honest comparison, including the rows where staying on an artifact wins, is in Homespun vs Claude Artifacts. If you only wanted to send someone a link, publishing inside Claude was the right answer several sections ago.
Questions people ask next
Can I host a Claude artifact on my own domain?
Yes. An artifact is a single HTML page, so any static host will serve it at a domain you control, with no build step. You keep every limit the page already had, and any artifact storage it used stops working, because storage is a claude.ai feature rather than part of the file.
Do I need to host a Claude artifact at all?
Usually not. Publishing inside Claude gives you a link that anyone on the internet can open with no sign-in, at no cost. Hosting it elsewhere is worth doing for a domain you control, a URL that outlives the conversation, or analytics, and for very little else.
Does hosting an artifact somewhere else give it a backend?
No. Anthropic documents that an artifact is a static page that cannot store data submitted through a form or authenticate viewers itself. That is a property of the page, not of where it is served from, so moving it changes nothing about it.
Will artifact storage keep working if I move the page?
No. Persistent storage is provided by claude.ai for published artifacts on paid plans. A moved page keeps its interface and loses its data layer, and it fails quietly because everything still renders. Test whatever saves data before sending the new link to anyone.
What if I need people to sign in to the page?
No host adds sign-in to a static page. You need an application with a backend behind it. Homespun builds one from the same kind of prompt, with email sign-in, per-collection permissions and a database the agent can keep working on.
Primary sources
Every claim about Claude on this page comes from Anthropic's own documentation, quoted rather than summarised so you can check it yourself.