Share a Claude Code artifact outside your org

To share a Claude Code artifact, open it in your browser and use the Share control in the page header. Every artifact starts private to you. From Share you can give access to people in your organization (Team and Enterprise) or create a public link that anyone can open without signing in to Claude. On Team and Enterprise, public links stay off until an Owner turns on External sharing. On Pro, Max and Ultra, a public link is the only way to share a Claude Code artifact.

This guide covers each option, what the person on the other end sees, and what to do when the client can't open a claude.ai link or the page doesn't fit Claude's limits.

What a Claude Code artifact is

An artifact is a web page Claude Code builds from your session and publishes to claude.ai/code/artifact/<id>. Ask for "an artifact that walks through this PR" or "a dashboard of last week's deploy failures", and Claude writes an HTML or Markdown file, publishes it, prints the URL and opens it in your browser. When Claude republishes, the page updates in place, so a status page can fill in while a long task runs.

Artifacts work in the Claude Code CLI and the Claude desktop app. You need a session signed in with /login to a Pro, Max, Ultra, Team or Enterprise account. Sessions using an API key, a gateway token, or Bedrock, Vertex or Foundry credentials can't publish. Organizations with customer-managed keys, HIPAA or Zero Data Retention don't get the feature.

Two commands are useful once you have a few:

/artifacts lists the artifacts you own and the ones shared with you. Press c to copy a link or o to open one.
Ctrl+] reopens the session's most recent artifact.

Who you can share a Claude Code artifact with, by plan

	Pro, Max, Ultra	Team	Enterprise
Starts as	Private to you	Private to you	Private to you
Specific people in your org	No org	Yes	Yes
Everyone in your org	No org	Yes	Yes
Public link, no sign-in	Yes	Only if an Owner enables External sharing	Only if an Owner enables External sharing
Editors	No	Yes	Yes
Comments	No	In-org shares	In-org shares
Admin can turn artifacts off	No	Yes	Yes, and by role

Source: Share session output as artifacts, Claude Code Docs.

People in your organization sign in to claude.ai as members to see an org-shared page. A public link is different. Anthropic describes it as "a link that anyone on the internet can open, with no claude.ai sign-in required." That makes Claude Code artifacts easier to send to a client than newer claude.ai chat artifacts, whose "Anyone with the link" option still requires a Claude account. The difference is explained in are Claude artifacts public.

How to share a Claude Code artifact

Step 1: Open it. Press Ctrl+] in the session, or run /artifacts and press o.

Step 2: Open Share in the page header. Choose the audience: specific people, everyone at your organization, or a public link if your plan and workspace allow it.

Step 3: Choose the version. Each publish is a version. The Share menu has a version picker and an "Always share latest version" toggle. Turn the toggle on if viewers should see each update. Leave it off to pin the version you've checked.

Step 4: Copy the link. Viewers in your organization see your name on the page. Someone who opens a public link signed out, or from outside your organization, sees "Content is user-generated and unverified." in its place.

To link to one tab or section of a page, ask Claude: "Give me a link to each tab of this dashboard." Each link is the artifact URL with an anchor such as #overview.

Letting a colleague edit, and collecting comments

On Team and Enterprise you can switch a person from viewer to editor in the share dialog. An editor updates the page by giving their own Claude Code session the artifact's URL. Claude pulls the current version and republishes with their changes. If two people publish from stale copies, Claude Code refuses the older one and merges onto the newer version.

People you share with inside the organization can comment on the page. With Claude Code v2.1.221 or later, Claude can read those comments when you give it the URL. From v2.1.228, if an editor sends a comment to Claude or mentions @claude, your session can reply on its own, depending on your permission mode. Public links don't get comments: "people whose only access is the public link don't see its comments and can't add any."

Turning on public sharing for a Team or Enterprise workspace

An Owner goes to Organization settings > Artifacts and turns on External sharing. If it's switched off again, every existing public link stops working until it's turned back on, though each artifact keeps its audience setting. Owners can also:

turn artifacts off for the whole organization,
turn off connector calls from artifacts separately, under Capabilities > Enable artifact connectors,
set retention periods that automatically delete private and shared artifacts after a time,
list and delete artifacts through the Compliance API.

If you need one page public and the Owner won't open the whole workspace, ask about allowing that single artifact. The claude.ai admin guide describes per-artifact exceptions while External sharing is off.

Limits that decide whether the page works for the viewer

Claude Code serves each artifact under a strict Content Security Policy, which shapes what you can share:

One page. The source must be a single .html, .htm or .md file. Relative links don't resolve, so a multi-page report becomes one page with in-page anchors.
16 MiB rendered. Embedded images are the usual reason a publish fails for size.
No external images. Images must be embedded as data URIs. Scripts load only from cdnjs, unpkg, jsDelivr and the Tailwind and jQuery CDNs, and fonts only from Google Fonts.
No backend. It's a static page and can't authenticate viewers itself.
No direct downloads. A plain download link or blob: URL is blocked. File downloads need Claude to declare the downloads capability.
Live data uses the viewer's account. A page that calls MCP connectors runs those calls through the viewer's own connections. Someone opening the public link signed out sees the page without its live sections.

So a public Claude Code link works well for a static report, an annotated diff or a chart. It works less well for a client who needs the live numbers, the underlying CSV or a password.

Sharing a Claude Code artifact with a client

A public link is the native answer, and for many clients it's enough. Reasons to send something else:

Your Team or Enterprise Owner hasn't enabled External sharing.
The page will say "Content is user-generated and unverified." on a claude.ai URL, which may not be how you want a client deliverable to look.
You need a password, or comments from the client. Public links take neither.
The deliverable includes a CSV, a PDF or several files, not one page.
The page depends on connector data the client can't load.

In those cases, publish the file Claude already wrote. Claude Code writes every artifact to a local file before publishing it, by default in a temporary directory outside your project. Ask Claude for the path, or ask it to write the page somewhere you choose. Then:

anchorify /path/to/q3-funnel-review.html --password 'client-password'
# → https://anchorify.io/your-org/your-project/q3-funnel-review

The client opens it without an account. Re-running the command after Claude updates the file keeps the same URL, and --access comment lets the client leave comments you can read back with anchorify comments. Ask Claude to write the current data into the page before you publish it, so it doesn't depend on anyone's connectors.

With the Anchorify skill for Claude Code installed, you can skip the copying. Say "publish this to Anchorify" in the same session and Claude runs the command. Anchorify also takes Markdown, CSV, code and PDF files, so a report and its data can go out as separate links. Check your company's policy on publishing outside Claude before doing this with work content.

Frequently Asked Questions

Can you share a Claude Code artifact publicly?

Yes. Use the Share control in the artifact's page header and choose the public option. On Pro, Max and Ultra, that's the only way to share. On Team and Enterprise, public sharing is off until an Owner turns on External sharing under Organization settings > Artifacts. Public links open without a claude.ai sign-in.

Do viewers need a Claude account to open a Claude Code artifact?

Not for a public link. Anthropic documents that anyone can open one with no claude.ai sign-in. For a page shared inside an organization, viewers sign in as members of that organization. Live connector data only loads for viewers who are signed in and have connected the same apps.

Are Claude Code artifacts available on the Pro plan?

Yes. Artifacts work on Pro, Max, Ultra, Team and Enterprise, in the Claude Code CLI and desktop app, as long as the session is signed in with a claude.ai account. On Pro and Max the artifact is private to you until you share it with a public link. There's no org sharing or editor role.

Can I password-protect or expire a Claude Code artifact link?

No. Claude Code artifacts have no password or per-link expiry setting. You can switch a page back to private, delete it with /artifacts (press d), or, on Team and Enterprise, rely on the Owner's retention policy. For a password, publish the underlying file somewhere that supports one.

How do I update a Claude Code artifact from a new session?

Give Claude the artifact's URL, or attach it with /artifacts, and ask for the change. Without either, a new session creates a new artifact instead of updating the old one. Each publish becomes a version, and the Share menu decides which version viewers see.

How is a Claude Code artifact different from a Claude chat artifact?

Claude Code artifacts live at claude.ai/code/artifact/..., are built from your coding session, and can be shared to a public link that needs no sign-in. Newer chat artifacts are shared from a Share menu with people, your organization or "Anyone with the link", and their viewers need a Claude account. Legacy chat artifacts, made before 16 September 2026, use a Publish button instead.

Sources

Share session output as artifacts, Claude Code Docs: sharing by plan, public links "with no claude.ai sign-in required," versions, editors, comments, page constraints, availability and admin controls.
Artifacts admin guide for Team and Enterprise plans, Claude Help Center: External sharing and per-artifact exceptions.
Publish and share artifacts, Claude Help Center: how chat artifact sharing differs.

When a Claude Code page needs to reach a client on a link with a password, comments, or no claude.ai branding, Anchorify publishes the file Claude wrote with one command. Free during beta. See the Claude Code setup.