How to share a Claude Artifact with other people

Publish and share an artifact, step by step

1. 1

   Open the artifact and pick the version

   Open the artifact in your conversation and confirm the version selector shows the version you actually want other people to see. Publishing shares the selected version, not the newest one you happen to be looking at.

2. 2

   Click Publish

   Use the Publish control on the artifact. On Team and Enterprise accounts this shares within your organisation rather than to the open web, which is a policy your admin controls, not a setting on the artifact.

3. 3

   Copy the public link

   Copy the link the publish step gives you. This is the address you send people, and it stays the same when you publish updates later.

4. 4

   Send it, and keep publishing updates to the same link

   Share the link however you normally would. When you change the artifact and publish again, everyone holding the link sees the new version at the same address, so you never have to redistribute it.

What each kind of viewer can and cannot do

This is where most confusion lives, because the answer is different for three groups of people. Anthropic's own wording for the first two:

View and interact with any published artifact without signing up. Try all basic functionality without a Claude account.

Publish and share artifacts, Claude Help Center

Full access to view, interact with, and copy any published artifact. Can use AI-powered features within their usage limits.

Publish and share artifacts, Claude Help Center

That third row is the one that stops people mid-task, so it is worth quoting directly:

Artifacts created on Team or Enterprise accounts can only be shared within your organization

Publish and share artifacts, Claude Help Center

If you are on a work account and you need to send something to a client, a supplier or a friend, this is a hard stop rather than a setting to find. A personal Pro or Max account can publish publicly; the work one cannot.

What happens when someone copies your artifact

A signed-in viewer can take your artifact into their own conversation and change it. Worth understanding before you share something you consider yours:

Your version is separate from the original, so nothing you do affects the artifact you started from.

Publish and share artifacts, Claude Help Center

• Their copy is a fork. Your artifact is untouched by anything they do.
• It is also a fork in the other direction: your later updates never reach their copy.
• They get the source. Publishing an artifact publishes its code, so treat anything in it as readable.
• There is no attribution, no notification and no list of who has copied it.

Three things that surprise people after they share it

• Unpublishing is permanent. Once you unpublish an artifact, you cannot publish that same artifact again. And if the artifact stored anything, unpublishing deletes it. See what happens when you unpublish before you touch that button.
• Shared data is anonymous. If several people write into the artifact's shared storage, everyone sees everything and nothing records who wrote what. There is no author on a record.
• You cannot see who opened it. There is no view count, no visitor list and no analytics on a published artifact. Sharing is genuinely fire and forget.

When a shared artifact is exactly the right tool

For a large share of what people want to send someone, an artifact is not a compromise, it is the best available answer, and nothing on this site should suggest otherwise.

• Something to look at. A chart, a report, a diff walkthrough, a set of design options side by side. Anthropic's own framing is that an artifact is a capture of work, and for that it is excellent.
• Something to try. A calculator, a quiz, a colour picker, an interactive explainer. Each visitor gets their own state and none of them needs an account.
• Something for strangers. Anyone on the internet can open the link and use it immediately. Every account-based platform, this one included, is heavier than that.
• Something disposable. Nothing to host, nothing to bill, nothing to remember to shut down.

The rule of thumb: an artifact is superb at sharing a thing to look at or try, and weak at sharing a thing to use together.

When you are sharing a thing people will use together

The moment more than one person is meant to put data in and get their own view back out, the shape of the problem changes. You need people to be people: named, distinguishable, allowed to do some things and not others.

Homespun is where the same agent that built the thing can host it. People sign in with their email, so the app can tell who is who and every row remembers who created it; permissions are set per collection, so some people can approve and others can only submit; and the agent keeps read and write access to the collections it is allowed, so it can keep working on the data instead of handing you a page and walking away. It is free today, and there is no paid plan to buy.

Questions people ask next

Primary sources

Every claim about Claude on this page comes from Anthropic's own documentation, quoted rather than summarised so you can check it yourself.

• Publish and share artifacts, Claude Help Center
• Persistent storage for artifacts, Claude Help Center
• Share session output as artifacts, Claude Code documentation