Can Claude Host A Website? What A Chat Can And Cannot Do

You asked Claude for a page, it built one in the artifact panel, and there's a Publish button sitting right there. So you're wondering whether that's it. Can Claude host a website, or is that button something else?

Short answer: it's something else, and it's useful as long as you know what it isn't.

Publishing an artifact gives you a public link that anyone can open, with no Claude account. That's genuinely handy for showing someone a draft. But the page lives on Claude's site, under Claude's address, as part of your Claude account. It isn't your website. Claude's docs offer no way to put your own domain on it, and some of what you'd expect from a site isn't there.

A Claude chat can put a real page online, though. It needs one extra piece first: a connector that gives it a way to send files to a host. Or you take the code and publish the Claude HTML file yourself, which takes about a minute.

Here's what each option gets you, and which one I'd pick for what.

Can Claude Host A Website?

No. Claude can write a website and show it to you, and it can publish an artifact to a shareable link, but it doesn't host websites. Hosting means serving your pages at your own address, on your terms, for as long as you want. An artifact link is a view of something inside your Claude account.

That's not a criticism. Claude is built to make things, not to run a web server.

The confusion comes from the Publish button, so let's look at exactly what it does.

What Does Publishing An Artifact Actually Do?

It turns the artifact into a public link. Anthropic's help article on publishing and sharing artifacts, which I read in November 2026, says a few things worth knowing:

• Who gets the button. Artifacts made in a chat show Publish on Free, Pro, Max and Ultra plans. Team and Enterprise show "Share & copy link" instead, and the link stays inside your organisation unless an owner has turned on external sharing. Newer artifacts use a Share button, where Pro, Max and Ultra can pick "Anyone with the link".
• Who can see it. Anyone with a published link can view and use the artifact without a Claude account.
• What breaks for viewers. If the artifact connects to other websites or calls Claude, those parts don't work for people who aren't signed in or are outside your organisation. They see an error where your data would be.
• What viewers get on work plans. On Team and Enterprise, people you share a chat artifact with also get access to the attachments and files in that chat.
• Unpublishing is final. You can unpublish to revoke access, but you can't publish that artifact again afterwards, and unpublishing deletes its stored data.

That fourth point is the one I'd read twice. If you dropped a spreadsheet of client details into the chat to build a dashboard, sharing the artifact on a work plan shares that file too.

And the last one catches people who unpublish to fix a typo. There's no republish. You make a new one, with a new link.

Artifact Link Or Real Website?

An artifact link is right for showing a draft to someone today, and a real website is right for anything with your name on it. Here's the difference side by side:

For a quick "is this what you meant?" to a colleague, I'd use the artifact link without a second thought. It's one click and the person on the other end needs nothing.

For a landing page, a portfolio or anything a customer sees, I wouldn't. The address is the first thing people judge, and a link without your domain is a link you'll have to replace later, which breaks everything you've already shared.

A Walkthrough: A Quote Calculator For A Cleaning Business

Here's how the decision plays out. Say you run a small cleaning business and ask Claude for a page where customers pick the number of rooms and see a price. Claude builds it as an artifact: a few sliders, a total, and a WhatsApp button.

Step one is the artifact link. Press Publish and send it to your business partner, who can open it on a phone with no Claude account. That's exactly the job the button is for.

Step two is the real page. You want it at your own domain and linked from your Google profile. The calculator only does maths in the browser, so it's a static page with nothing to build. Copy the code, paste it into a static host, and you have a live link in about a minute. Nothing about it needs a build, a repository or a terminal. Because it's a business page, budget for a paid hosting plan that allows a custom domain.

Keep the artifact link for drafts and the hosted page for customers. Two links, two jobs.

How Can A Claude Chat Publish A Real Page?

With a connector. On its own, a Claude chat can read web pages but can't send a file anywhere, so it has no way to put a page on a host. A custom connector is an MCP server, a small tool service, that you add to Claude once. After that the chat can call it, and a publishing connector's job is to send the page to a host.

There are two kinds of publishing connector:

1. No sign-in. The chat publishes the page and replies with a temporary live link plus a claim link. Claim it into a free account inside the window and it stays. This is the same no-account pattern coding agents use, explained in how to deploy without an account.
2. Signed in to your account. You approve the connection once on the host's site, and the chat can then publish new versions of your real sites.

Anthropic's connector docs, read in November 2026, say custom connectors work on every plan, Free included, with Free limited to one custom connector. Anthropic's guide to custom connectors using remote MCP You add one under Customize, then Connectors, and switch it on for a chat from the + menu. Adding a Claude custom connector step by step covers the sign-in choices.

When I checked in November 2026, the official MCP servers from Vercel, Netlify, Cloudflare and Render all needed a sign-in or a token before they'd publish anything. Ours doesn't, which is what makes a one-reply publish from a chat possible. The result is still temporary until you claim it, and a busy hour can mean a refused publish, because anonymous publishing is rate limited.

When The Chat Should Not Publish For You

If the page needs a login, a database or a payment flow, a chat publishing static files won't help. That's an application, not a page, and it needs a host that runs code. OxyPages only serves static files, so it's the wrong home for that kind of project too.

What If You're Using Claude Code Instead?

Then you're not limited by any of this. Claude Code runs on your own machine and can run commands, so it can build a project and deploy it with one request, no connector needed. Putting a Claude Code website online walks through it.

What To Do Next

Decide what the link is for, then pick the route.

1. Showing a draft to one person? Press Publish on the artifact. Done.
2. Need it at a real address? Copy the HTML and publish it to a static host.
3. Want the chat to do it? Add a publishing connector, then ask Claude to publish the page.
4. Anything private in the chat? Check what's attached before you share on a work plan.

If you'd like a real address without the connector step, paste the page into OxyPages and you'll have a live link in about a minute. To keep a personal page online, start a free account, no card needed. A business page needs a paid plan.