# How to share Claude artifacts: every option, and when you need more

> Share a Claude artifact privately, with your org or by public link, plan by plan. Plus what Claude can't do (password, expiry, who opened it) and how to add it.

To share a Claude artifact, open it, click Share and pick an audience: only you, people in your organization (Team and Enterprise), or anyone with the link. That covers most internal sharing. What Claude doesn't offer is a password, a link that expires, a separate link per person or an alert when someone opens it. If you're sending the artifact to a client, publish its HTML to a tool that does, such as Outbox, straight from Claude with the MCP server or the skill.

## The native options, plan by plan

Every new artifact starts private: only you can see it. From there, who you can share with depends on your plan and on how the artifact was made. Anthropic's Help Center and the Claude Code docs describe these options as of October 2026:

## Step by step: share from Claude

The Share control lives in the artifact's header on claude.ai or Claude Desktop. Sharing settings can't be changed from the iOS or Android apps, so do this from a browser or the desktop app.

## The fine print that trips people up

Account requirement. Anthropic's Help Center says everyone who opens an artifact shared from the Share dialog needs a Claude account, even with External sharing on; the exception is a chat artifact published with the older Publish button. The Claude Code docs describe public links that open without signing in. Before you send a link to someone outside your company, open it in a private browser window to see exactly what they will see.

External sharing is off by default on Team and Enterprise. An Owner turns it on in Organization settings → Artifacts. If it's turned off later, existing public links stop working until it's turned back on.

Live data and AI features belong to the viewer. An artifact that calls connected apps uses each viewer's own connections, and AI features count against the viewer's plan. Someone who opens a public link without signing in sees the page without those live sections.

Comments stay internal. People whose only access is the public link of a Claude Code artifact can't see or add comments.

Unpublishing is final. Once you unpublish a chat artifact you can't publish that same artifact again, and its stored data is deleted.

## When the native share isn't enough

Claude's sharing is designed for teams that live inside Claude. You need something else when the reader is outside your organization and you care about control: a proposal for a prospect, an audit for a client, a report for an investor.

Anthropic's docs don't describe password protection, link expiry, view analytics or open notifications for artifacts. A public link is one URL for everyone: if it gets forwarded, anyone can open it, and you never learn whether the person you sent it to read it. If any of those matter, publish the artifact's HTML somewhere that gives you those controls.

## How to share a Claude artifact with Outbox

Outbox publishes the HTML your agent made to a private page in your library, then lets you send it as one link per person, each with an optional passphrase and an expiry. Every open is recorded under the recipient's name, and whoever created the link gets an email when it's opened. This works on every Outbox plan, Free included.

The quickest path from Claude Code is the local MCP server. Create an API key in Outbox under Settings → Keys that can create share links (the Personal preset can; the agent presets can't by default) and add the server:

```
claude mcp add outbox --env OUTBOX_API_KEY=outbox_xxxxxxxx -- npx -y @out-box/mcp
```

## Prefer plain HTTP? The same flow with the API

Any agent or script can do the same with two calls. The recipient field is what turns a share link into a per-person link.

```
# 1. Publish the artifact's HTML (it starts private)
curl -X POST https://api.out-box.dev/publish \
  -H "Authorization: Bearer $OUTBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"slug":"clients/acme/proposal","title":"Acme proposal","html":"<!doctype html>...","model":"claude"}'

# 2. One link per person, with an expiry and an optional passphrase
curl -X POST https://api.out-box.dev/api/share \
  -H "Authorization: Bearer $OUTBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resource":"clients/acme/proposal","resourceType":"post","recipient":"Laura · Acme","expiresInDays":14,"passphrase":"pick-a-long-phrase"}'
```

## Other workarounds and their trade-offs

Download the HTML and email it as an attachment. It works offline, but you can't update it after sending, mail clients often block or strip HTML files, and you'll never know if it was opened.

Upload it to a generic static host. You get a URL quickly, but it's usually public to anyone with the address, there's no per-person link, and no record of who read it.

Export to PDF. Easy to send, but you lose the interactivity that made it an artifact in the first place.

## Comparisons

- [Outbox vs Claude Artifacts](https://out-box.dev/en/guides/vs/claude-artifacts)
- [Outbox vs Derive](https://out-box.dev/en/guides/vs/derive)
- [Outbox vs Display.dev](https://out-box.dev/en/guides/vs/display-dev)

---

Updated 2026-10-11. HTML version: https://out-box.dev/en/guides/how-to-share-claude-artifacts