Claude Artifact
Hand someone a working interactive thing behind one link — they click and it runs in their browser, no install, no account, ~5 sec. On a personal plan (Free/Pro/Max) you hit Publish and anyone can open it; on a work plan (Team/Enterprise) the button is Share and it stays inside your org.
Reach for it when you're handing a finished, clickable thing — a calculator, a quiz, an AI widget — to people who'll never open a code tool. Skip it when people need to build on it together: a viewer's copy never sends changes back (repo for that).
Last verified: 2026-06-07 · Confidence: high on plans, access, and billing; link durability is unclear.
It allows you to
- Hand over a running thing, not a file. They click and it works in the browser — no download, no setup, no account.
[confirmed] - Reach anyone with one link. From Free/Pro/Max, hit Publish and the link opens for anyone, logged out.
[confirmed] - Put the AI bill on the viewer. If it calls Claude, it runs against the viewer's subscription — no API key, no cost to you, whether 10 people use it or 10,000.
[confirmed] - Let them spin off their own. A signed-in user clicks Customize for a private copy; your original never moves, their changes never come back.
[confirmed] - Pull it back. One Unpublish kills the public version — a one-way door (fine print).
[confirmed]
Ideal for
- A clickable demo for a non-technical room — a cost-effectiveness calculator opened on a phone mid-pitch. They click in ~5 sec; a repo loses them at "run the code."
- A self-serve tool others reshape — a programme-planning template each chapter lead clicks Customize to tailor, yours untouched. Few present-to-use tools let a recipient remix the live thing.
- An AI widget you can't afford to run for everyone — a "draft a donor thank-you" helper that calls Claude on each viewer's account, so it spreads across a 200-person network with no per-use bill on you.
- A one-link send to someone with zero patience — a board member or journalist who won't sign up or install.
- Browse real ones for ideas: Anthropic's collection of artifacts (Artifacts → Inspiration).
[confirmed]
Who can get in
- Private until you act. A fresh artifact lives only in your chat — nobody else can reach it.
[confirmed] - Publish → anyone (Free/Pro/Max). Any visitor opens and uses it, no account. Sign-in is asked only for the extras — customizing, or running an AI-powered one.
[confirmed] - Share → org-only (Team/Enterprise). A work plan has no public Publish — the Share link opens only for signed-in org members, no logged-out view. To reach an outsider you'd rebuild it on a personal account and Publish, or use a website.
[confirmed]
Which rungs it can hold. Of the five rungs, an artifact holds just you, org-only (Share), and the whole internet (Publish) — no named-people rung, and Publish is open to anyone who clicks. Right for finished, non-confidential things; never for PII or secrets. → Who can see it? [confirmed]
Handing data to the host. A published artifact is something you meant to hand out, so the training question barely touches it; the hygiene that matters is your private chats. → Can you trust the company?
What you do to set it up
Ask Claude in a claude.ai chat for something self-contained — "build me a cost-effectiveness calculator I can share as an artifact by link" — and it appears in a side panel. Then you press Publish yourself and copy the link.
- Publish is the one click you can't delegate. The button lives in the web app; an agent can't reach it. Every share after: ~1–2 min (land on the right version, Publish, copy the link).
[estimate] - One-time: a Claude account (Free, Pro, or Max) — signup + email confirm, ~3 min once.
[estimate] - The catch that decides reach: only Free/Pro/Max get a public Publish — see Who can get in.
Full walkthrough (build, land on the right version, Publish, copy the link, optional embed) → Publish and share a Claude Artifact.
What the other person does
- Just open and use it. Click the link, it runs in the browser — no account, ~5 sec.
[confirmed] - AI-powered one? Sign in first. Anything that calls Claude needs the viewer logged in — one free signup, ~3 min once — then it runs on their limits. A plain artifact skips this.
[confirmed] - Want to change it? They click Customize for a private copy (free account needed) — see It allows you to.
[confirmed] - Cost to them: nothing to view; a free account only to customize or use AI features.
Other ways to share
- Want a URL you own, a custom domain, or no org wall? → Deploy a website. Same "click a link, it just runs," and a work account can publish publicly — but if it calls AI, that bill lands on you.
- Already working in Google's chat, not Claude's? → a Gemini Gem or Canvas is the cross-provider equivalent — chat-built, shareable by link. Outgrown a single file — several pages, logins, saved data? → Lovable builds a multi-page app with a real backend.
- Need exactly named people in, not anyone-who-clicks? → a Gated website. Publish is all-or-nothing public; a login wall holds the named-people rung an artifact can't.
- Want people to build on it together, not just remix a private copy? → a GitHub repo. A repo lets several people change one shared thing and send edits back.
Sources
- Publishing and sharing artifacts — Publish vs Share; logged-out view; Customize; one-way unpublish
- What are artifacts and how do I use them? — plans; AI-powered artifacts bill the viewer; 20 MB text-only storage
- Discovering, publishing, customizing, and sharing artifacts — browsable collection; Team/Enterprise share internally
- Disable public projects for your organization — org admins can switch off public sharing
Good to know
- All five plans build artifacts — Free, Pro, Max, Team, Enterprise.
[confirmed](what are artifacts) - The fine print — 20 MB text-only storage, the org-admin off-switch, why a published link is a snapshot, and what the docs leave unstated about link durability → Claude Artifact fine print.
[confirmed]/[unclear]