How to Host a Claude Artifact at Your Own Link

hdply · 2026-09-08

Claude's artifacts are one of the nicest ways to get a working web page out of a conversation: ask for a dashboard, a proposal, a landing page, and you get a rendered HTML artifact you can click around in. Claude can also publish that artifact so people outside the chat can open it. This guide is about the gap between that built-in publishing and hosting — when the built-in link is enough, and how to move the same HTML to a link you control when it is not. Details below are from Claude's help center as of 2026-09-08.

What "Publish" gives you, and what it does not

On the artifact, a Publish button creates a public link anyone can open without a Claude account. That is genuinely useful for a quick "look at this". The constraints:

The address is Claude's, not yours. It is a claude.ai link with an identifier you do not choose. There is no option to name it, and no way to put it on a subdomain or domain of yours.
Team and Enterprise cannot publish publicly. Per the help center, publishing is available on Free, Pro and Max plans; Team and Enterprise accounts can share artifacts within their organization only. If your company account is where you do the work, the public link is simply not there.
Unpublishing is one-way. Once you unpublish an artifact you cannot publish that same artifact again; you would create a new one.
Viewers cannot edit. The published page is a snapshot. To change it, you edit in Claude and republish; to build on someone else's, you copy the code into a new chat.

For a demo you will discard tomorrow, none of that matters. For a proposal you send to a client, a page you will keep updating, or anything from a Team workspace, it does.

The HTML is already yours

An artifact is a self-contained HTML document — that is what makes it render in the side panel. Open the artifact, use the copy or download control to get its code, and you have a file that any static host can serve unchanged. Everything the artifact does in Claude, it does anywhere else: the styles and scripts are inline, and there are no assets to bring along.

Putting it at your own link

With hdply: paste the artifact's HTML into the box on the homepage and press the button. The page is live at a name.hdply.com address immediately, with HTTPS, and you have not created an account. That link lasts an hour — enough to check it on a phone and send it. A free account keeps it for good (six pages free), gives you a browser editor for changes, keeps every version so a bad edit is one click from undone, and lets you pick the subdomain.

Two behaviours worth knowing. New pages are hidden from search engines until you turn indexing on, which is the right default for something you are sending to a handful of people. And if you keep iterating in Claude, you paste the new version over the old one in the editor — the link does not change.

If you would rather not paste at all: hdply has an MCP server. Connect it to Claude Code or Claude Desktop and "publish this page" becomes something Claude does itself, at a URL it reports back in the conversation.

Things that break outside the chat

Artifacts are written for a preview pane, and a few habits show up when they leave it. Placeholder image URLs that never existed; navigation links pointing at #; a layout that assumed a wide panel and collapses badly on a phone; the occasional truncated file that stops before </html>. None of these are hard to fix, and all of them are covered in publishing AI-generated HTML. Check the phone view before you send the link: most recipients will open it on one.

Side by side

	Claude "Publish"	hdply
Address	claude.ai link, not chosen by you	name.hdply.com, you choose the name
Available on Team / Enterprise	Internal sharing only	Yes (it is just HTML)
Edit after publishing	Republish from Claude	Browser editor, same link
Version history	No	Yes, restorable
Unpublish	Permanent for that artifact	Delete or re-deploy any time
Hidden from search by default	—	Yes, until you switch it on
Account needed	Yes (the Claude account)	Not to try; free to keep

When Claude's built-in publishing is the better choice

Use Publish when the page is disposable and the audience is small — a quick look for a colleague, a prototype in a thread — and you are on a Free, Pro or Max plan. It is one click, it needs no other service, and if the artifact will be superseded tomorrow, a stable address is not worth a second tool. Move it out when the link has to last, has to be yours, or has to come from a Team or Enterprise account.