The fastest way to publish a Claude artifact is to let Claude do it. Connect Yetty over MCP and ask it to put the page online: it sends the HTML, converts it byte-for-byte, wires any contact form into a real leads inbox and takes it live on a real address - no downloading, no file-wrangling. Prefer to do it by hand? You can still save the artifact’s HTML and upload it yourself. Either way, conversion is free and the design stays exactly as Claude drew it.

Artifacts are Claude’s preview window: perfect for iterating on a design, but the page only exists inside your chat. Here’s how to get it out and onto a domain people can visit - the easy way first.

The easy way: your AI publishes it for you (MCP)

Yetty is run end to end over MCP, so the same Claude that built the artifact can publish it - no exporting, no zip, no hosting dashboard. Connect Claude to Yetty once (add the MCP server, sign in), then just ask in the chat:

  • “Put this artifact online.” Claude sends the artifact’s HTML to Yetty over MCP, which converts it and publishes it live on a yourname.yetty.site address with SSL - served exactly as Claude wrote it.
  • No account yet? Claude can still send the files - Yetty parks the converted site and emails you a link to approve and claim it. You go live by clicking one link, not by learning a new tool.
  • It keeps the keys. Because the connection stays open, Claude can then edit any word, add pages, read new leads and roll back a change - all from the same chat, over MCP’s 62 tools.

That’s the whole flow: build in the artifact, say “publish it,” done. If you’d rather move the file yourself, the manual path is below.

Prefer to do it by hand? Save the HTML and upload

Open the artifact and use the download or copy option, or switch to the code view and copy everything. Save it as index.html in an empty folder. If Claude built several pages across several artifacts, save each under the filename the links expect (about.html, contact.html and so on) in the same folder. Don’t edit anything by hand - the exact code is the design. Then zip the folder (with index.html at the top) and upload it to Yetty; conversion is free and the site is live in minutes, with the same leads inbox and editing you’d get the MCP way.

What breaks on naive hosts (and why Yetty doesn’t)

Dropping that file onto a random free host, or opening it from your desktop, usually disappoints in one of two ways:

  • Missing pieces. Artifacts often reference images by URL, fonts from Google, or icons from a CDN. Some hosts serve your HTML but choke on paths, so images 404 and the page loads half-styled. And anything the artifact loaded from Claude’s own preview environment simply isn’t there anymore.
  • Forms that go nowhere. Claude loves to include a lovely contact form - but a form needs a server to receive the message. On a static host the visitor clicks “Send” and the message evaporates. You’d never know a customer tried to reach you.

Neither is your fault, and neither means the artifact was bad. It means a page needs a platform, not just a parking spot. Yetty’s conversion checks your files as a whole site, and wires the form into a leads inbox automatically - so “Send” actually sends, whichever way you published.

Keep building past the artifact

A single artifact page is usually the start, not the site. The natural next step is to go back to Claude and grow it - more pages, a menu, real copy - and since Claude connects to Yetty over MCP, it can edit the live site directly from the same chat. If you’re starting that bigger build, read how to build a website with Claude for the prompts (and the one tool call) that make the whole site cleanly editable, let your AI run your website over MCP for what it can do once it’s live, and how to host an AI-generated website if you want the full lay of the land.

Two minutes of setup makes it permanent: connect Claude to Yetty, and publishing the next artifact is a single sentence in chat. For the full hosting picture, read how to host an AI-built website - it’s free to go live, and $13 for your own domain.

FAQ

Can I publish a Claude artifact directly to the web?

Yes, in effect: connect Claude to Yetty over MCP and ask it to publish - it sends the artifact’s HTML and Yetty puts it live on a real address in minutes. You can also save the HTML as index.html and upload it yourself if you prefer.

Do I have to download the artifact’s HTML?

No. If Claude is connected to Yetty over MCP it sends the files for you - no download, no zip, no upload. Downloading is only the manual fallback if you’d rather move the file by hand.

Why does my Claude artifact look broken when I host it?

Usually missing assets: the artifact referenced images or fonts that aren’t in your uploaded folder, or paths the host serves differently. Yetty’s conversion checks your files as a whole site, so what worked in the preview works live.

Do contact forms from Claude artifacts work after publishing?

On plain static hosting, no - there’s no server to receive the message. On Yetty the same form is wired into a leads inbox, so submissions reach you without any extra setup.