Claude Artifact on Your Own Domain: What Works, What Doesn't

A Claude artifact cannot take a custom domain directly. Three ways to get your page onto your own address, with editing and contact forms compared.

Build your site free. No card needed.

Short answer: A Claude artifact cannot be given your own domain name. It lives at a link on Claude's side, and Anthropic's help pages do not describe a custom domain setting. You have three routes: keep the share link (or embed it in a site you already own), export the code and put it on a static web host where a domain can be attached, or have Claude make the site through a website builder connector so it is a hosted site from the start.

Which one is right depends on two things most people only notice later: how often you will change the page, and whether anyone needs to contact you through it.

What Claude's own publishing gives you

Sharing is good at one job: letting other people open what you made.

  • Who can view. A published or publicly shared artifact opens for anyone with the link, and the viewer does not need a Claude account. Artifacts start private until you share them.
  • Which plans. Anthropic's help article on sharing describes the link option for the Pro, Max, Ultra, Team and Enterprise plans. On Team and Enterprise an owner must switch on outside sharing first.
  • The address. The link is on Claude's domain. Nothing in the help pages lets you swap it for yours.
  • Editing later. For artifacts made with Claude Code, Claude republishes to the same link and each publish is kept as a version, so the address does not change when the page does.
  • Embedding. Older published chat artifacts offer an embed code, with a field where you list the websites allowed to show it.

What it does not give you

The limits come from what an artifact is. Anthropic's Claude Code documentation describes it as "one self-contained page with no backend", and most of the gaps follow from that sentence.

  • No separate pages. It cannot serve several addresses such as /about and /contact. Sections inside one page work; links between files do not.
  • No working contact form. With no server there is nothing to receive a message, and the page is blocked from sending requests to outside services.
  • No outside images. Pictures hosted elsewhere are blocked, so images have to be built into the page. The whole page must stay under 16 MiB.
  • Small, text-only storage. According to the artifacts overview, an artifact can store up to 20 MB of text on paid plans, with no images or files.
  • Some artifacts cannot be shared by link. One that connects to other websites cannot use the option that opens it to anyone.

Two housekeeping points if your artifact is an older one made inside a chat. The overview says artifacts of that kind made before September 16, 2026 keep working and can still be published, but new ones cannot be created. And unpublishing one is permanent: it cannot be published again, and any data it stored is deleted.

Route A: keep the share link

This is enough more often than people expect. If the page is a menu for one event, a calculator for a client, a resume or a prototype you want feedback on, nobody cares what the address looks like. Share the link and stop there.

If you already have a website, embedding gets you most of the way to "on my domain". Visitors go to your address and see the artifact inside one of your pages. Where the embed option is offered, copy the embed code, add your site to the allowed list and paste the code into a page. The artifact is still hosted by Claude, so its limits do not change: one page, no form delivery.

Choose this when the page is temporary, personal, or a small part of a site you already run.

Route B: export the code to a static host

A static host stores your files and serves them to visitors, with no program running behind them. Well-known examples are Netlify, GitHub Pages and Cloudflare Pages. All three document how to attach a domain you own.

The steps are the same wherever you go:

  1. Get the code out. Open the artifact, view its code and copy or download it. Save a plain HTML page as index.html.
  2. Check what kind of code it is. If Claude wrote the page as a React component, the file will not open in a browser as it stands. It has to be turned into ordinary web files first, which developers call a build step. The simplest fix for a non-developer is to ask Claude to rewrite the page as one plain HTML file with everything it needs inside it.
  3. Upload it. Cloudflare Pages, for example, accepts a folder or zip file dragged into its dashboard. GitHub Pages serves files from a repository.
  4. Connect the domain. Add your domain in the host's settings, then create the DNS records it asks for at the company where you bought the name. Usually that is a CNAME record for www and an A record for the bare domain. Our guide to A records and CNAME records explains the difference.

What you give up:

  • Every edit is a round trip. The host has a copy, not the artifact. To change a phone number you go back to Claude, change it, export again and upload again. Skip a step and the live site quietly stays out of date.
  • The form still needs somewhere to go. You have to connect it to a form service. Netlify has one built in, but its documentation notes that forms drawn by JavaScript need extra setup, and a page Claude wrote in React draws its form that way.
  • You are the maintainer. If something breaks in six months, you are the one opening the code.

Choose this when the page rarely changes, you are comfortable following a host's setup guide, and you want full control of the files.

Route C: a website builder connector inside Claude

The third route skips the artifact. A connector lets Claude work with another service during the chat, so instead of producing a page for you to move, Claude creates the site on a platform that already hosts it.

We make one of these, so here is exactly what the We.Inc connector does and where it stops.

What it does:

  • You describe the business in the chat and a site is created in your We.Inc account with your services and opening hours on it.
  • You can change the wording from the chat. Each change leaves an undo point.
  • When you say so and confirm, the site is published to a weinc.app address.
  • You can ask whether a domain name is available.
  • You can ask Claude to read the messages visitors sent through the site's contact form.

Where it stops:

  • It does not import your artifact. It makes a new site from your description. If you love the exact layout Claude already drew, Route B keeps it and this route does not.
  • Layout changes are not made in the chat. Asking for a new section, different photos or a different look opens the We.Inc editor.
  • You need a We.Inc account.
  • Your own domain is connected on We.Inc, not in the chat. The steps are in connecting a custom domain.

Setup is covered on the We.Inc connector for Claude page. If you already use a different website builder, check whether it has a Claude connector and ask the same three questions of it: does it host the site, can you edit from the chat, and where do form messages go?

Choose this when the site is for a real business, the details will change, and you want enquiries to reach you without wiring anything up.

The three routes compared

Route A: share linkRoute B: static hostRoute C: builder connector
Own domainNo, unless embedded in a site you already haveYes, through DNSYes, set up on the builder
Effort to set upLowest: click ShareHighest: export, upload and DNS recordsLow: describe the business, then add the domain on the builder
Editing laterAsk Claude, then check the linkChange, export and upload each timeWording from the chat, layout in the editor
Contact formDoes not deliver messagesNeeds a separate form serviceIncluded, messages readable from the chat
Keeps your exact artifactYesYesNo, a new site is made
Good forOne-off pages, prototypes, sharing with a few peoplePersonal projects and pages that rarely changeBusiness sites that change and take enquiries

Which route for which situation

A one-off page to share. A party invite, a pitch, a tool for one client. Use the share link. A domain adds cost and work that the page will not repay.

A personal project. A portfolio, a hobby page, something you built to learn. Export it to a static host. You keep the design Claude made, you learn how hosting and DNS work, and occasional edits are manageable.

A real business site. Opening hours change, services get added and customers need to reach you. Re-exporting a file for every small change gets old quickly, and a form that silently drops messages costs you work. Start on a hosted platform, through a connector or by signing up to a builder directly.

Whichever you pick, test it the way a stranger would: open the address on a phone, on mobile data, signed out of everything, and send yourself a message through the form. If the message arrives, you are done.

Sources

All three were checked on November 12, 2026. Anthropic changes these features often, so read the live pages before relying on a detail here.

Frequently asked questions

Can I connect a custom domain to a Claude artifact?

Not directly. Anthropic's help pages for sharing artifacts describe share links and embedding, and neither mentions a setting for your own domain. To use your own address you either embed the artifact in a site you already have, move the code to a web host, or build the site on a platform that hosts it.

How do I publish a Claude artifact?

Open the artifact and use the Share control, then pick the option that lets anyone with the link open it. Anthropic's help article describes that option for the Pro, Max, Ultra, Team and Enterprise plans, and on Team and Enterprise an owner has to allow outside sharing first. Older artifacts made inside a chat have a Publish button instead.

Can I edit a Claude artifact after it is published?

For artifacts made with Claude Code, yes: Anthropic's documentation says Claude publishes the change to the same link and keeps each publish as a version. The help article on sharing does not describe how edits to an older published chat artifact reach its link, so check the live link after any change rather than assuming it updated.

Will the contact form in my Claude artifact send me messages?

Not by itself. An artifact has no server behind it, so a form has nowhere to deliver a message. Once the page is on a web host you can point the form at a form service, or you can build the site on a platform that includes a working form and an inbox.

Claude built me a website. What do I do next?

Decide what the page is for. If people only need to see it, share the link. If it should sit on your own address and rarely change, export the code to a static host. If it is a business site you will keep updating and take enquiries through, build it on a hosted platform, which you can do from inside Claude with a website builder connector.

More in Blog

Related guides and tools

Start building

How we research, test and update this page: our editorial policy. We.Inc is our own product.

Product

Who It's For

Features

Resources

Company

View Sitemap