How can you share a Claude artifact with a client who doesn’t use Claude?

Claude’s apps ask viewers to sign in; a Claude Code public link does not. Five ways to send an artifact to a client, ranked on privacy, effort and what you learn.

On this page

By Kaz Kato · Published 12 October 2026 · Updated 12 October 2026

From Claude’s apps, a client needs a Claude account to open a shared artifact. Claude Code can publish one to a public link that needs no sign-in, but its page describes no record of who opened it. A room gives each client a link of their own, and shows you what each did.

This guide compares five ways to send a Claude artifact to someone outside Claude: Claude’s own Share, a Claude Code public link, a static host, a recording and a room. It ranks them for a named client you want to follow up, and says what has to change in the artifact first. Deploying from Claude covers the connector, and sharing a private link covers the links. What a Claude artifact is explains the kinds, and who can open each.

Five ways to share a Claude artifact, compared

Way Does your client need an account? Can they click through it? Private to one person? What you learn afterwards
A room on Roomi No Yes, with a guided tour Yes: a link each, on Pro Each person’s visits, time on each screen, comments and answers
A static host, such as Vercel or Netlify No, at a public address Yes On Vercel, by shareable link or email invitation On Vercel, traffic in total, not people
A Loom recording Only if you share it with specific people No: they watch Yes, if they sign in to Loom Who watched, if they were signed in
Claude’s Share, from Claude’s apps Yes: a Claude account, signed in Yes Yes, by email invitation No record of who opened it is described
A public link from Claude Code No Yes No: anyone with the link can open it No record of who opened it is described

Ranked for a client who does not use Claude, and whom you want to follow up:

  1. Roomi — deployed from the same chat, with a link for each client, a tour and a record of what each did. Nothing for them to sign up to.
  2. A static host — no account for the client, and a public address. You learn nothing about the one person you sent it to.
  3. A public link from Claude Code — no account for the client, if Claude Code made the artifact. Its page describes no record of who opened it, and no link in their name.
  4. A Loom recording — easy to watch, but nobody can click it, and viewers who are not signed in to Loom are anonymous.
  5. Claude’s Share, from Claude’s apps — the simplest for a colleague who uses Claude, and the wrong one for a client who does not.

How does Claude’s own sharing work?

On Claude’s Pro and Max plans, an artifact made in Claude’s apps can be shared with “Anyone with the link”, or with people you invite by email. One that connects to your apps or uses Claude cannot be shared by link. Either way, your client signs in to Claude before they see your work.

Sharing an artifact with “Anyone with the link” is on Claude’s Pro, Max, Team and Enterprise plans, not on Free. From Claude’s apps, whoever opens the link must still be signed in to Claude. Claude calls artifacts made in a chat before 16 September 2026 legacy artifacts. They still work and can still be published, but no new ones can be made. So for anything you make in Claude’s apps now, your client needs a Claude account to open it.

Claude’s help page on sharing artifacts describes no way to see who has opened one. So once it is sent, you wait to hear back. Sharing from Claude’s apps suits a colleague who already uses it, and anyone happy to make an account. Making a Claude artifact private goes through every setting, plan by plan.

Claude Code is the exception. Claude Code can publish an artifact to a public link that anyone can open, with no claude.ai sign-in. On Team and Enterprise plans, public sharing is off until an owner turns it on. Someone who opens a Claude Code artifact’s public link without signing in, or from outside your organisation, sees the label “Content is user-generated and unverified” instead of your name.

Claude Code’s artifacts page describes no record of who opened an artifact, no expiry date and no guided tour. For anyone outside your organisation, it describes a public link, not one for a named person. People who reach a Claude Code artifact only by its public link do not see its comments, and cannot add any. So it reaches a client with no account, and then you wait, as with Claude’s Share. A room’s link carries one person’s name, can expire or be revoked, and shows you who they passed it to.

The other ways

A static host

Ask Claude for the artifact’s code, and put it on a host such as Vercel or Netlify. It needs someone comfortable with a host’s dashboard.

Vercel’s Hobby plan is free, and Vercel says it is for personal, non-commercial use. On Vercel’s Hobby plan you can create one shareable link to a protected deployment, in total, per account. Netlify sets site-wide password protection in its dashboard, and it is not available on its credit-based Free and Personal plans.

Vercel’s Web Analytics tells visitors apart by a hash that resets every day, without cookies. It reports pages, referrers, countries, operating systems and browsers across all visitors. A static host is a good home for a public page. For one client, it tells you nothing about what they did.

A recording

Loom names a viewer only when they watch while logged in to a Loom account. Anyone else shows as “Anonymous”, with no way to see who they were. A Loom video can be shared with specific people by email, and each must be logged in to Loom with that address to watch it. A recording shows the artifact working, but your client cannot try it, and it goes out of date with your next change.

A room

Add the Roomi connector to Claude, then say “deploy it to roomi” in the chat where you made the artifact. Claude writes the files, checks them and shows you what would go live. Nothing is published until you say yes. On Pro, ask Claude for a link for your client, named for them.

When you send the link, tell your client who you are and how to reach you. Say that Roomi records what they do in the room, and shows it to you. The terms ask every publisher to say so.

Which one tells you who looked?

A room tells you the most. Claude’s help page on sharing artifacts describes no way to see who has opened one. Claude Code’s artifacts page describes none either. A static host counts traffic in total. A Loom recording names only viewers signed in to Loom. A room on a paid plan shows what each person did, screen by screen.

On Pro and above, Roomi records every visit, click and minute, by person. You see when they opened it, how far through the tour they got, which screen held them and what they said. At the top of the app, one sentence says who to call first, and why. Ask Claude, in the same chat, who has opened it. Then ask it to draft the follow-up: Roomi hands it exactly what that person did, and nothing is sent until you send it. What the room records lists every measure.

What has to change in the artifact first?

Two things, and Claude does both when you ask it to deploy. The artifact becomes plain files a browser runs, with an index.html at the root. And any part that calls Claude or your connectors becomes sample answers, because nobody outside your Claude account can use them.

  • Plain files. An artifact made with React is source code, which a browser cannot run as it is. The connector refuses a demo with no index.html, and warns that a .jsx file is served as it is, never built. So Claude writes it out as HTML and JavaScript first. React and Tailwind can still come from a public CDN, which your client’s browser loads.
  • Sample answers for anything that used Claude. For people invited from outside your organisation, the parts of a Claude artifact that use Claude or your connectors do not work. On a host or in a room there is no Claude behind it at all, so ask Claude to swap those parts for canned replies.
  • Nothing real in it. A demo runs on mock data, and the deploy stops on anything that looks like a live key.
  • Small enough for a chat. The connector takes a demo of the size a chat holds: at most 200 files and 3 MB. A bigger build, or one with its own server, deploys from your machine with the CLI, and Claude tells you when.

Which should you pick?

Pick by who it is for. For a colleague who uses Claude, share it from Claude. For a page anyone may open, use a Claude Code public link or a static host. For a named client you want to follow up, deploy it to a room, give them their own link, and call when they return to it.

Pricing has what each plan includes. If you built a whole app rather than one artifact, the prototyping use case shows the same room around a bigger build. Sharing a Claude prototype with a client takes the room route step by step.

Questions people ask

Does my client need a Claude account?

From Claude’s apps, yes, for anything made now. Claude Code can publish an artifact to a public link that anyone can open, with no claude.ai sign-in. On Team and Enterprise plans, public sharing is off until an owner turns it on. A room on Roomi needs no account either, and the link is that one client’s own.

Can I see if my client opened it?

Claude’s help page and Claude Code’s artifacts page both describe no record of who opened an artifact. On the paid plans of Roomi, you see each person’s visits, how far through the tour they got and what they said.

Will the parts that use Claude still work?

Not for a client outside your Claude account. Ask Claude to replace them with sample answers before you deploy, so the demo behaves the same for everyone who opens it.

Can I do it from Claude’s Free plan?

Custom connectors work on every Claude plan, Free included; Free is limited to one. The Roomi connector is one. On Free, a room is a draft only you open, or a public listing on the community; private links come with Pro.

Can I change it after I have sent it?

Yes. Deploy again from the same chat, and every link you sent shows the new version the next time it loads. Nothing goes live until you say yes to the rehearsal.

Sources

About the author

Kaz Kato, Co-founder & CTO, Roomi. Kaz co-founded Roomi with Tesh, whom he has built with since 2017: two startups that failed, one venture studio that didn’t, and an exit.

Send the artifact, not a sign-up form.

Add Roomi to Claude and say “deploy it to roomi” in the chat you made it in. It starts free.

Get started freeSee pricing