Can I host a Claude artifact outside Claude?

Yes. Claude renders an artifact inside the chat, but to put it on a permanent link of your own you need somewhere to host it. Repage hosts the artifact's HTML at a shareable URL, so anyone can open it in a browser without signing in to Claude.

How do I host a Claude artifact on Repage?

Two ways. Copy the HTML from your artifact and paste it into Repage to get a link instantly, or connect Claude to Repage's MCP server and ask Claude to publish the artifact directly — it returns the hosted URL without any copying.

Do people need a Claude account to view a hosted artifact?

No. A hosted artifact is standard HTML served by Repage. Anyone with the link can open it — and the password, if you set one. Viewers never need a Claude subscription.

Doesn't Claude already let you publish artifacts?

It does — Claude can publish an artifact to a public link. But Claude's published artifacts have no password, no comments, and no version history, and once you unpublish one you can't republish that same artifact. Repage adds those: a revisable link with passwords, inline comments, and version history.

Which Claude plans can publish or share artifacts?

Publishing an artifact to a public link is available on Claude's Free, Pro, and Max plans; restricting an artifact to your organization is a Team and Enterprise feature. Repage hosts the artifact's HTML regardless of your Claude plan.

Can Repage host interactive or AI-powered artifacts?

Repage hosts the artifact's HTML, so self-contained interactive pages — dashboards with charts, SVG, client-side widgets — work exactly as designed. Artifacts that call Claude at runtime can't run outside Claude; for those, host the rendered HTML output and link people to it.

Host Claude Artifacts on a Shareable Link

What is a Claude artifact?

An artifact is a standalone piece of content Claude generates in its own panel beside the conversation — a single-page website, an interactive dashboard, an SVG graphic, a flowchart, a document, or a small app. It is meant to be self-contained, which is exactly what makes it easy to host elsewhere as a real, shareable page.

Why host a Claude artifact on Repage

A link you own. The artifact lives at a stable URL instead of inside a chat thread you have to share access to.
No Claude account to view. Teammates, clients, or stakeholders just open the link — the page is plain hosted HTML.
Comments in context. Reviewers leave inline comments on the live page.
Every version kept. Republish a revised artifact and Repage keeps the history so you can compare or roll back.
Password protection. Gate sensitive artifacts behind a password while keeping the same link.

Claude can publish artifacts — when host on Repage instead?

Claude has built-in publishing: on Free, Pro, and Max you can publish an artifact to a public link, and on Team and Enterprise you can restrict it to your organization. That is great for a quick public demo. Host on Repage when you need what Claude's publishing leaves out:

Password protection. Claude's published artifacts are public; Repage can gate an artifact behind a password.
Inline comments. Claude publishing has no review layer — Repage lets people annotate the live page.
Version history. Claude publishing keeps no versions; Repage saves every revision so you can compare or roll back.
A link you can revise. If you unpublish a Claude artifact you can't republish that same one — on Repage the link is stable and you just publish a new version.
No viewer usage limits. A hosted page is plain HTML anyone can open, rather than running against each viewer's Claude usage.

How to host a Claude artifact

1. Paste the HTML

Open your artifact, copy its HTML, and paste it into Repage. You get a hosted link instantly — best for a quick one-off.

2. Publish via MCP

Connect Claude to the Repage MCP server and ask Claude to publish the artifact. It returns the hosted URL — no copying, and revisions become new versions automatically.

3. Share the link

Send the URL to anyone. They open the live artifact, leave comments, and you keep control of versions and access.

What you can host

Interactive dashboards with live charts and tables
Single-page HTML sites and landing pages
SVG graphics, diagrams, and flowcharts
Reports, briefs, and documents people can annotate
Rendered prototypes and design mockups

Host your first Claude artifact

Publish HTML from any AI assistant, collect comments, keep every version.

Publish a document

Frequently asked questions

Can I host a Claude artifact outside Claude?: Yes. Claude renders an artifact inside the chat, but to put it on a permanent link of your own you need somewhere to host it. Repage hosts the artifact's HTML at a shareable URL, so anyone can open it in a browser without signing in to Claude.
How do I host a Claude artifact on Repage?: Two ways. Copy the HTML from your artifact and paste it into Repage to get a link instantly, or connect Claude to Repage's MCP server and ask Claude to publish the artifact directly — it returns the hosted URL without any copying.
Do people need a Claude account to view a hosted artifact?: No. A hosted artifact is standard HTML served by Repage. Anyone with the link can open it — and the password, if you set one. Viewers never need a Claude subscription.
Doesn't Claude already let you publish artifacts?: It does — Claude can publish an artifact to a public link. But Claude's published artifacts have no password, no comments, and no version history, and once you unpublish one you can't republish that same artifact. Repage adds those: a revisable link with passwords, inline comments, and version history.
Which Claude plans can publish or share artifacts?: Publishing an artifact to a public link is available on Claude's Free, Pro, and Max plans; restricting an artifact to your organization is a Team and Enterprise feature. Repage hosts the artifact's HTML regardless of your Claude plan.
Can Repage host interactive or AI-powered artifacts?: Repage hosts the artifact's HTML, so self-contained interactive pages — dashboards with charts, SVG, client-side widgets — work exactly as designed. Artifacts that call Claude at runtime can't run outside Claude; for those, host the rendered HTML output and link people to it.

Host Claude artifacts on a shareable link