How to Share a Claude Artifact (Public or Private)

To share a Claude artifact, open it, use the share settings to make it available, and send the link. What changes is who can open it and what they see: a Claude Code artifact publishes as a public web page anyone with the link can view, while a Cowork artifact is shared inside your organisation. Whether the data stays live also depends on how it was built. This guide explains how to share a Claude artifact, the difference between public and private sharing, and why some artifacts update for viewers and others don't.

Sharing used to be the most frustrating part of artifacts. You would build something really useful and then have no clean way to get it in front of your team. That's now fixed, but "sharing" means slightly different things depending on where the artifact lives, so it's worth getting the model right.

The one thing to understand first

How you share an artifact, and what the other person sees, depends on two things: which Claude surface it was built in, and whether it runs on live data or a snapshot.

By surface: a Chat artifact and a Cowork artifact are shared within Claude, while a Claude Code artifact publishes as a standalone web page. By data: an artifact built on live connectors refreshes each time it loads, whereas one built from a file on your computer shares as a fixed snapshot. Get those two axes and the rest follows.

How to share, step by step

The mechanics are simple. Open the artifact you want to share, and by default it's private, so only you can see it. From the share settings you then choose who can open it: invite specific people, or open it to everyone in your organisation. You get a link to send, and that's the share.

There's also a version control worth knowing about. An "always share the latest version" option is on by default, so the moment you change the artifact, everyone with the link sees the current version. Turn it off and you can pin one fixed version to share, which is what you want when you're asking for feedback on a single draft rather than a moving target. Anthropic's guide to publishing and sharing artifacts covers the exact buttons.

Public vs private: who can actually see it

This is the question people really ask, and the honest answer is that it depends on the surface and your plan.

A Claude Code artifact publishes like a web page: anyone with the link can open it in a browser, no Claude account needed. That's public in the practical sense, so treat the link as you would any unlisted URL.

A Cowork artifact is built for organisations. You share it inside your company, either with everyone in the organisation (where it shows up in their Artifacts area) or with one specific person. It isn't designed to be handed to someone outside your company.

A Chat artifact sits in the middle: you can share it, but it's the original, simpler version of the feature.

In every case the default is private, so nothing is exposed until you choose to share it. And a detail that reassures people: the live artifacts you build and share inside Cowork are not published to the open web or indexed by Google. Sharing a link with your team is not the same as putting it online.

Are Claude artifacts private? And do they update?

Two things get conflated here, so to separate them: privacy is about who can open the artifact, and live-versus-snapshot is about what they see when they do.

An artifact built on live connectors is a "live artifact": every time someone opens it, it pulls fresh data, so they see the current picture. An artifact built from local files on your computer is shared as a static snapshot, because the viewer can't reach your files. If the underlying data changes, they won't see it until you rebuild and reshare. So if you need a dashboard that stays current for the whole team, build it on connectors, not local files. If a fixed snapshot is fine, local files are faster to work with.

"If you want something updated on a constant basis and shared with others, you'll prefer connectors."

— Alex Kantjas, 9x co-founder

What can you do with a published artifact?

More than you'd expect. A shared artifact isn't a screenshot: it's interactive, so the person you share with can use it, filter it, click through it and fill in forms. If it's a live artifact built on connectors, it shows them current data. And in Cowork, artifacts can now write back to your tools, so a shared planner or scheduler can actually create the task or book the meeting, rather than only display it. That turns a shared artifact from a report into a small internal tool the team can use together.

The short version

Sharing a Claude artifact is: open it, set who can see it, send the link. A Claude Code artifact becomes a public web page anyone with the link can open; a Cowork artifact is shared inside your organisation. Everything is private by default, live artifacts stay current for viewers while snapshot ones don't, and Cowork's shared artifacts stay off the open web. Build on connectors when the data needs to stay live, and keep the "always share latest" toggle on unless you're pinning a draft for review.

If you want your team building and sharing artifacts like this properly, our hands-on Claude Cowork training takes people from their first build to shared, live tools the whole team uses.

Common questions

How do I share a Claude artifact? Open the artifact, choose who can see it in the share settings (a specific person, or everyone in your organisation), and send the link. A Claude Code artifact publishes as a web page with its own URL; a Cowork artifact is shared within your company.

Are Claude artifacts private or public? Private by default. A Claude Code artifact, once published, is a web page anyone with the link can open. A Cowork artifact is shared only inside your organisation and is not published to the open web or indexed by Google.

Do the people I share with need a Claude account? For a published web-page artifact, no. For an AI-powered artifact, any Claude usage counts against each viewer's own limits, not yours, so sharing doesn't cost you.

Why doesn't my shared artifact update for other people? It was probably built from local files, which share as a fixed snapshot. Rebuild it on live connectors and it becomes a live artifact that refreshes each time someone opens it.

Can I share one fixed version instead of the latest? Yes. Turn off "always share the latest version" and pin a specific version, which is useful for getting feedback on a single draft.