Updated 8 min readBy The VibeDeploy team

Claude Artifact Custom Domain: Download, Host, and Launch

Download or copy your Claude artifact code, host it outside Claude, and connect a custom domain with EU hosting and automatic Let's Encrypt SSL included.

Short answer

You cannot attach a custom domain to a Claude artifact or its claude.ai link. Save the artifact as index.html or let Claude deploy it through the VibeDeploy connector (https://mcp.vibedeploy.be/mcp), then add your domain and two DNS records: a CNAME such as www.example.com pointing at the host and a TXT record proving ownership. The deploy takes about a minute, SSL follows automatically after verification, and plans start at EUR 4 a month after a 14-day free trial.

Skip the download: let Claude deploy it

Connect Claude opens Claude's connector settings with VibeDeploy filled in. Click Continue and Add, then Connect, and create your free account in the sign-in window (14 days, no card). Back in your chat, say "deploy this" and get a live URL. Or paste the artifact's code into VibeDeploy yourself.

https://mcp.vibedeploy.be/mcp

Claude saved your site to /mnt/user-data/outputs/index.html? That path is inside Claude's sandbox, not on your computer; the linked guide shows how to get the file out.

You asked Claude for a landing page, a calculator, or an interactive chart, and it produced an artifact: a working page rendered right next to the conversation. It looks finished. It is not online. This guide walks through the whole path from that artifact to a real website on a domain you own, including the parts Claude's own Publish or Share button cannot do.

What a Claude artifact actually is

An artifact is Claude's container for substantial, self-contained output. For websites, that means one of three formats:

  • A single HTML file. Markup, CSS, and JavaScript in one document. This is the most common web artifact and the easiest to host anywhere.
  • A single-file React component. Claude renders it in the chat with its own runtime. Outside Claude it needs a small wrapper page or a build step, or you can ask Claude to rebuild it as one self-contained HTML file.
  • SVG and other visual documents. Diagrams and graphics that can be embedded in a page.

The important property is "single file". A single HTML file can be served as-is by any static host: no bundler, no CI pipeline, no node_modules. A React component needs the wrapper or build step first.

Made the page in Claude Design rather than in a chat? Claude Design exports HTML or a ZIP, which can be hosted outside Claude too; publishing a Claude Design website covers that route.

Where the format hits its limits

Before you deploy, know what you are working with:

  • In-chat rendering helpers do not travel. An artifact that relies on Claude's chat-side renderer, the Mermaid diagram renderer for example, needs the equivalent library loaded in the file itself. For Mermaid, add Mermaid.js via a CDN script tag and the diagrams render standalone.
  • Real build steps are a different animal. If Claude gave you TSX with imports across multiple files, that is a project, not a single-file artifact. Run npm run build locally and deploy the dist folder instead.
  • Publish or Share keeps ownership at Anthropic. The built-in Publish or Share button puts your artifact on a claude.ai URL with a fixed Created-with-Claude header. There is no custom domain, no control over the OG image, favicon, or meta tags, no analytics, and Anthropic can unpublish the page. Fine for showing a prototype to people who have a Claude account (Anthropic's help center says every viewer needs one, except for a legacy artifact published from a chat), wrong for anything you want to look like yours. If the button fails or you want a page taken down, see why a Claude artifact won't publish or share.

That last point is the reason this guide exists. The fix is to move the file to hosting you control.

How to download or copy a Claude artifact

Open the artifact's code view in Claude and copy the complete source into a local file. Save a plain HTML artifact as index.html. If Claude produced a React component or a multi-file project, copy every file into a local project folder and keep the paths and filenames Claude supplied.

If the client you use offers a file download for the artifact, download it and inspect the result before deploying. The same rule applies: a standalone HTML file can go directly to a static host, while a project with package.json must be built first. The Claude artifacts deployment guide covers both formats.

One trap worth naming: if Claude told you it saved the site to a path like /mnt/user-data/outputs/index.html, do not go looking for that file on your computer. That path lives inside Claude's own sandbox and disappears with the session; the linked guide explains what it means and how to get the file out.

Step 1: let Claude deploy it

You do not have to move the file by hand. Claude can publish it from the conversation in two ways.

With the VibeDeploy connector (fastest). In claude.ai, open Customize > Connectors, click + Add and choose Add custom connector. Name it VibeDeploy and paste https://mcp.vibedeploy.be/mcp as the server URL, or open the form with both fields filled in. If Claude asks for an OAuth client, choose Register automatically. Connect, sign in with your VibeDeploy account (or start the 14-day trial, no card) and allow access. Then say "deploy this as my-site" in the chat that holds the artifact. Claude's help center says the Free plan includes one custom connector.

The same connector works in Claude Desktop and the mobile app. In Claude Code, register it with claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp and sign in by running /mcp in a session. The full connector setup covers each client and the usual snags.

With the deploy guide. Prefer not to add a connector? The deploy guide is a single instruction file that teaches the AI how to publish to VibeDeploy:

  1. Start a 14-day free trial. No credit card is needed.
  2. In the dashboard, export your deploy guide. It contains a private deploy key and the exact API instructions, so keep it out of public files.
  3. Paste the guide into the same conversation where the artifact lives and say "deploy this".

Claude reads the instructions and either sends the artifact's files to the VibeDeploy API itself or, when its sandbox has no network access, gives you a deploy page to open in your browser that finishes the upload. Either way you end up with a live URL of the form https://yourname.subsite.site. Open it in a normal browser tab: same page, but now it exists outside the chat, served over HTTPS from Belgian infrastructure. Both routes are summarised on the Claude artifacts page.

Skip the download: let Claude deploy it

Connect Claude opens Claude's connector settings with VibeDeploy filled in. Click Continue and Add, then Connect, and create your free account in the sign-in window (14 days, no card). Back in your chat, say "deploy this" and get a live URL. Or paste the artifact's code into VibeDeploy yourself.

https://mcp.vibedeploy.be/mcp

Step 2: check the deployed page

Almost every single-file HTML artifact works identically once hosted. Run through this quick list anyway:

  • Console errors. Open the browser dev tools. A missing CDN script shows up here first.
  • External resources. If the artifact loads fonts, images, or libraries over http://, switch them to https:// to avoid mixed-content warnings.
  • The title tag. Claude often leaves a generic title. Ask Claude to set a proper <title> and meta description, then redeploy. On your own hosting you control all of this, which is exactly what claude.ai publishing denies you.

Redeploying is the same sentence again: "update the site with these changes". Every deploy is kept as a version, so if a revision goes wrong you can restore an earlier one in one click from the dashboard, within your plan's restore window.

Step 3: put it on your own domain

A *.subsite.site subdomain is fine for testing. For anything public-facing, attach your own domain:

  1. In the dashboard, open Web Addresses (the site's Settings tab links there too). Under "Use your own domain", type the domain, pick the site and connect it.
  2. Add the DNS records shown at your registrar: an A record for the apex (example.com) pointing at VibeDeploy's edge IP (or an ALIAS to proxy.vibedeploy.be if your DNS offers one), a CNAME for www pointing at proxy.vibedeploy.be, and a TXT record whose name begins with _vibedeploy to prove you own the domain.
  3. Wait for DNS to propagate (most registrars take a few minutes), then click Verify.

With the connector added you can also ask Claude: Connect www.example.com to my-site. It adds the domain and replies with the ownership TXT record. Set that record and the CNAME at your registrar, then ask Claude to verify the domain.

Once the domain is verified, VibeDeploy issues a Let's Encrypt certificate automatically, usually within 60 seconds, and the artifact is live on https://example.com. No Created-with-Claude header, your favicon, your meta tags, and analytics if you want them: the dashboard tracks traffic per site, and because you own the HTML you can drop in any analytics snippet.

The iteration loop

The real payoff shows up on the second deploy. Your workflow becomes: describe a change to Claude, Claude edits the artifact, Claude redeploys it, the custom domain serves the new version. The chat that built the site also maintains it. Compare that with the old loop of copying code into an editor, committing, and waiting for a pipeline.

What it costs

The 14-day trial covers a full site with a custom domain, so the entire flow above costs nothing to try. After the trial, plans start at EUR 4 a month for one site with one custom domain, and custom domains and SSL are included on every plan. Prices include VAT where it applies. Details on the pricing page.

Summary

A Claude HTML artifact is a single self-contained file, which makes it the easiest class of website to host. Claude's own Publish or Share button parks it on claude.ai with Anthropic's branding and no domain of your own. Moving it takes one connector (or one pasted deploy guide), one sentence, and a few DNS records. Fifteen minutes from chat window to https://yourdomain.com, most of which is DNS propagation.

Full tool page with FAQ and comparison table: Deploy Claude artifacts.

Sources

  • Anthropic Help Center, Getting started with custom connectors using remote MCP: the Customize > Connectors steps and "Free users are limited to one custom connector". Checked 13 October 2026.
  • Claude Code docs, Connect Claude Code to tools via MCP: claude mcp add --transport http, the --scope option and signing in with /mcp. Checked 13 October 2026.
  • Anthropic Help Center, Share artifacts: "Everyone needs a Claude account. People without one can't open a shared artifact, even with the link. The only exception is a legacy artifact published from a chat." Checked 13 October 2026.
  • Anthropic Help Center, What are artifacts and how do I use them?: "Legacy artifacts are artifacts made in a chat before September 16, 2026", and you can't make new ones. Checked 13 October 2026.
From the VibeDeploy team

Ship your AI-built site in minutes

VibeDeploy hosts your AI-built websites in the EU with custom domains, automatic SSL, and a 14-day free trial that gets you online today.

Deploy guides for this topic

Questions people ask

Can I put a Claude artifact on my own domain?

Not on claude.ai: a published artifact keeps its claude.ai address and there is no setting for your own domain. Host the artifact's HTML yourself instead. On VibeDeploy you deploy it with the connector, the deploy guide or an upload, then add the domain in the dashboard and set the DNS records it shows.

How do I get my Claude artifact off claude.ai?

Copy the code view into a file called index.html or use the download control, then upload that file. Or skip the file: add VibeDeploy as a custom connector in Claude with the URL https://mcp.vibedeploy.be/mcp and say "deploy this as my-site". Claude's help center says the Free plan includes one custom connector.

Which DNS records does a custom domain need?

One that routes traffic and one that proves ownership. For a subdomain such as www.example.com the routing record is a CNAME pointing at proxy.vibedeploy.be; for the bare domain example.com use an ALIAS to the same name, or an A record with the IP address the dashboard shows. For ownership, add the TXT record the dashboard shows (its name begins with _vibedeploy). Then click Verify: VibeDeploy issues a Let's Encrypt certificate automatically, usually within a minute.

What does hosting a Claude artifact on VibeDeploy cost?

Nothing for the first 14 days: the trial needs no card and includes one custom domain. After that, plans start at EUR 4 a month for one site with one custom domain. Prices include VAT where it applies.

Related reading