To publish a Claude artifact as a website, save the artifact’s HTML to a file (download it, or copy the code into a file named index.html), then upload it to a hosting platform. Yetty converts it for free and puts it live on a real address in minutes, keeps the design byte-for-byte, and wires any contact form into a working leads inbox - the two things naive hosting gets wrong.

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.

Step 1: get the HTML out of the artifact

Open the artifact and look for 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 you several pages across several artifacts, save each one 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.

What breaks on naive hosts (and why)

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.

Step 2: upload to Yetty

Zip the folder (with index.html at the top) and upload it to Yetty - or, if your Claude is connected over MCP, just ask it to "put my site online" and it sends the files itself. Conversion is free and the site is live on a yourname.yetty.site address in minutes, with SSL, served exactly as Claude wrote it. Your form gets wired into a leads inbox automatically, so "Send" actually sends - every enquiry lands where you’ll see it.

From there the artifact stops being frozen: your text and images become editable cards, every change is versioned with one-click rollback, and the custom domain wizard connects yourname.com whenever you’re ready.

Step 3: 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, 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.

FAQ

Can I publish a Claude artifact directly to the web?

Not from inside the chat - an artifact lives in Claude’s preview. Save its HTML as index.html and upload it to a host like Yetty, and it’s a real website in minutes.

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.