← Blog

How to Share Claude Artifacts With Others, Including Outside Your Organization

Short answer: open the artifact, click Share and choose who has access.

  • Anyone, even without a Claude account: choose Anyone with the link. Most artifacts shared this way open without a sign-in, in the Claude app and in Claude Code. It's on Pro, Max and Ultra, and on Team and Enterprise once an Owner turns on External sharing.
  • Specific people: invite them by email (beta), or on Team and Enterprise add people from your organization. They sign in to Claude to open it.
  • Comments from people outside Claude: people who only have the link can't see or add comments. Save the artifact as an HTML file and share it where comments work. The four ways are below.

Need a client to comment on it?

  • Your client comments without an account
  • Every comment sits on its sentence
  • Claude Code pulls them in for v2, same link

14-day free trial · No credit card · Reviewers never pay

A reader selects a sentence in a Markloop document and types a comment on it.

How to share a Claude artifact, step by step

Claude artifacts come from two places: the Claude app (a chat, a template or Cowork) and Claude Code, which publishes pages from a coding session. Both start private, and both share from a Share menu.

In the Claude app

  1. Open the artifact and click Share.
  2. On Team and Enterprise, add people from your organization and pick each person's access. Enterprise can also add groups.
  3. Under Who has access, choose who else can open it. Pro, Max and Ultra: Only you or Anyone with the link. Team and Enterprise: Only people invited, Anyone at your organization, or Anyone with the link.
  4. Pick what people can do: Can view, Commenter or Can edit. Some artifacts offer only Can view and Can edit.
  5. Copy the link and send it.

To give access to one person, type their email in the Share menu and click Invite. Invitations are in beta on Pro, Max, Ultra, Team and Enterprise, work for up to 50 people outside your organization per artifact, and the person needs a Claude account with that email address (Claude help center).

Older artifacts show Publish (Free, Pro, Max and Ultra) or Share & copy link (Team and Enterprise) instead of Share. Publish makes a public link anyone can open without a Claude account. Share & copy link still needs a Claude account.

In Claude Code (claude.ai/code/artifact links)

  1. Open the artifact in your browser. Its URL looks like claude.ai/code/artifact/…. Every artifact you made is listed at claude.ai/code/artifacts, or run /artifacts in Claude Code.
  2. Click Share in the page header.
  3. Pick the audience: specific people or everyone in your organization (Team and Enterprise), or a public link.
  4. Choose which version viewers see, or keep sharing the latest one.
  5. Copy the link and send it.

According to the Claude Code docs, a public link opens for anyone on the internet, with no claude.ai sign-in. Viewers who aren't signed in to your organization see "Content is user-generated and unverified." instead of your name. On Team and Enterprise you can also make someone an editor, so their Claude Code session can publish new versions.

How to make a Claude artifact public

A public artifact is one shared with Anyone with the link (in the Claude app) or with a public link (in Claude Code).

  • Pro, Max and Ultra: open Share and choose Anyone with the link, or the public link in Claude Code. It works right away.
  • Team and Enterprise: the option is grayed out until an Owner turns on External sharing in Organization settings > Artifacts, or allows that one artifact. Ask an Owner or Primary Owner.
  • Free: new artifacts can't be made public. Only older chat artifacts can, with Publish.

What people with only the link get:

  • Most artifacts open without a Claude account. Docs are the exception: they open only for people signed in to Claude, and only to view. Some dashboards show part or all of their content only after the visitor signs in.
  • Parts that use Claude or connected apps don't work for them, and they can't see or add comments.
  • On Team and Enterprise, if an Owner turns External sharing off, public links stop working until it's back on.

Why you can't see Share or "Anyone with the link"

  • You're on your phone. Sharing settings can't be changed in Claude for iOS or Android. Use Claude on the web or Claude Desktop.
  • It's an older artifact. It shows Publish or Share & copy link instead of Share.
  • You're on Team or Enterprise. Anyone with the link stays grayed out until an Owner turns on External sharing. Email invitations outside the organization have their own setting: on by default on Team, off on Enterprise.
  • You're on Free. There's no Anyone with the link for new artifacts.
  • The artifact connects to other websites, or has an uploaded file that's still being checked or failed the check. Those can't use Anyone with the link or email invitations.
  • Claude Code doesn't give you a link at all. Artifacts need Pro or higher, a session signed in with /login (not an API key), and the Anthropic API rather than Bedrock or Vertex. On Team and Enterprise an Owner can also turn artifacts off.

Need comments from outside Claude? Which option to pick

A Claude link works for a quick look. People who only have the link can't comment, and people you invite by email need a Claude account. When the reader is outside your organization and needs to comment, share the HTML file instead. The four ways to do that, side by side; each one is explained below.

Email the fileStatic hostingSend / ShareDuo / AnchorifyMarkloop
Works outside your org✓✓✓✓
Viewer needs no account✓✓✓ to view (Anchorify: sign in to comment)✓ (types a name to comment)
Anchored comments on the doc✗✗Anchorify only✓ (invite, or link with comments on)
Feedback flows back into Claude Codemanualmanualmanual (Anchorify: CLI/API)✓ MCP pull
Versions with "addressed" tracking✗✗✗✓
Viewer analytics✗✗✓✗
Reviewer sees source fileyesyesvariesno (rendered view only)

If someone only needs to look once, email the file or put it on a static host. If you want to know who opened it, use an artifact-hosting tool. If you want comments that go back into Claude Code for the next version, use Markloop.

Markloop is the column with comments. Your client comments without an account, and Claude Code pulls the comments in.

Try it free

What each plan allows

From the Claude help center and the Claude Code docs, November 2026:

PlanPublic link (no Claude account)Invite by emailShare inside your orgComments
Free✗ (older chat artifacts: Publish)✗n/a (no organization)✗
Pro / Max / Ultra✓ Claude app and Claude Code✓ betan/a (no organization)People you invite as Commenter (Claude app); not on a public link
TeamOnly once an Owner turns on External sharing✓ beta, on by default✓Inside your org and invited Commenters; not on a public link
EnterpriseOnly once an Owner turns on External sharing✓ beta, off by default✓ also groupsInside your org and invited Commenters; not on a public link

An artifact that pulls live data through connectors can get a public Claude Code link, but anyone who opens it without signing in to claude.ai, or from outside your organization, sees the page without its live sections. An admin retention policy or switching off External sharing can make an existing link stop working (Claude Code docs). Comments on a Claude Code artifact need sharing within your organization and Claude Code v2.1.221 or later. People you invite by email can't comment on an artifact that's also shared with Anyone with the link. Who can comment on a Claude artifact has the full rules.

Claude Code public links can't take comments The HTML file can go where comments work. your claude.ai organization claude.ai/code/artifact/… Deploy-failures dashboard public link (Pro/Max) · in-org unless an Owner allows (Team/Ent.) public link: people can look, not comment C client E domain expert T contractor view only the HTML file → Markloop → comments back ask Claude for the HTML file, then share it where comments work
A public Claude Code link lets people look, not comment. The HTML file can go where comments work.

How to use a Claude artifact outside Claude

Every option below starts the same way. An artifact starts as an HTML or Markdown file. Unless you name a location, Claude writes it to a temporary directory outside your project before publishing, and the page shell is added at publish time. The simplest move is to ask in your session:

Save the artifact as a standalone HTML file in the project root.

Because the published page is self-contained by design (the artifact CSP forces inline CSS, images embedded as data URIs, and scripts only from a few public CDNs), the exported HTML renders the same anywhere. The one exception is a page that pulls live data through Claude connectors. Those sections stay empty outside claude.ai.

Option 1: Email the file

Attach the HTML file and send it. That's enough for a one-time look. Some mail clients block or mangle HTML attachments, the reviewer gets your source file, and feedback comes back as prose in a reply thread that you re-type into Claude Code by hand.

Option 2: Static hosting (GitHub Pages, Netlify, Vercel, S3)

Drop the file on any static host and share the URL. It's free, it stays up, and it can sit on your own domain. Anyone who finds the URL can open the page, every update is a redeploy, and the reviewer still has nowhere to comment on the page itself.

Option 3: Artifact-hosting tools (Send, ShareDuo, Anchorify)

A handful of tools host Claude artifacts on an external link: Send, ShareDuo and Anchorify. Some add viewer analytics (who opened it, when) or custom domains, which helps if you're tracking a sales deck.

Most of them handle distribution, not review. With Send and ShareDuo the viewer can't comment on the page, and nothing flows back into Claude Code. Anchorify is the exception: it has added comments, suggested edits and a CLI your agent can use to read them. If you need feedback, check how the comments get back to your agent before you pick one. The full comparison is in Claude artifact sharing options compared.

Option 4: Markloop (when the comments need to reach Claude Code)

Markloop hosts the exported HTML file at one link where people comment on the page, and Claude Code reads those comments back over MCP. With Markloop connected, publish from the same session:

Publish order-sync.html to Markloop as a new document.

A spec opened from a Markloop share link: the reader selected the sentence 'The integration is asynchronous.' and is typing a comment on it, with no account.
What your client sees: they select a sentence and comment on it. No account, no Claude.

Turn on commenting for the share link and send it. When the comments are in, Claude Code pulls the open threads with markloop_pull, makes the edits on your machine and publishes v2 at the same link. It also marks which comments it addressed.

No setup needed to try it: upload the HTML file to Markloop in the browser. Or connect Claude Code once (setup is a one-time step, shown in the app after signup) and ask it to publish. Watch the 2-minute walkthrough.

Markloop fits self-contained HTML documents, not live multi-page apps. Pro is $19/mo, Team $99/mo, reviewers never pay, and the 14-day trial needs no card. For the same loop without a terminal, see how to write a client proposal with AI and get comments on one link. Who can see your link and where your data lives is in the FAQ.

Get a link people can comment on See a sample doc

14-day free trial · No credit card · Reviewers never pay

The Markloop loop from Claude Code publish → comment → pull → next version at the same link claude code 1 · writes order-sync.html → markloop_put_version() ← markloop_pull() 5 · edits → publishes v2 ✓ order-sync.html v1 → v2 3 · People comment 1 “What if the reservation times out?” replied ✓ 1 open → next round 2 · publish 4 · pull Each comment comes back with its target, quote and version, and the loop repeats. Markloop hosts the doc and the comments. No AI runs on Markloop's servers: Claude Code makes the edits on your machine.
Claude Code publishes the file, people comment at the link, and Claude Code pulls the comments back for v2.

FAQ

Can someone without a Claude account open a shared Claude artifact?

Yes, for most artifacts. Share it with "Anyone with the link" (Pro, Max, Ultra, or Team and Enterprise once an Owner allows it) and most artifacts open without a Claude account or sign-in, in the Claude app and in Claude Code. Docs are the exception: they open only for people signed in to Claude. People who open a link this way can't see or add comments, so if you need comments from someone without a Claude account, share the HTML file on Markloop instead.

Can you share Claude artifacts on the Free plan?

Not new ones. "Anyone with the link" and email invitations start at Pro, and Claude Code artifacts need Pro or higher. On Free, only older chat artifacts can be shared, with Publish, which makes a public link anyone can open.

How do I stop sharing a Claude artifact?

Open it, click Share, and under Who has access choose "Only you" (Pro, Max and Ultra) or "Only people invited" (Team and Enterprise). On Pro, Max and Ultra, people you invited by email keep their access, so remove them one by one. For an older chat artifact, click Unpublish; you can't publish that artifact again afterwards.

Where do I find the link to a Claude Code artifact?

Claude Code prints the URL after the first publish, and it looks like claude.ai/code/artifact/…. All your Claude Code artifacts are listed in the gallery at claude.ai/code/artifacts, and /artifacts in Claude Code lists them too: press c to copy a link.

Does my client need a Claude account to comment in Markloop?

No. With commenting on, anyone who has the share link types a name and comments in the browser. That name is self-reported, so if you need to know exactly who commented, share the document with them by email instead; they sign in with a link Markloop emails them. Reviewers never need a Claude account and never pay.

What happens to the comments when Claude Code publishes v2?

Each version keeps its own comments. When Claude Code uploads v2, it marks which comments it addressed, and the rest stay open for the next round. All versions are kept, and the comments panel shows which version each comment was raised in and addressed in. The share link opens the latest version on the next refresh. Markloop doesn't email reviewers about a new version, so tell them yourself.

Who can see the link, and where is the document stored?

Anyone who has the link can open it, including anyone it gets forwarded to. A link can get an expiry date when you create it and can be revoked at any time; there are no link passwords. Markloop is hosted in Europe, and no AI runs on its servers: Claude Code makes the edits on your machine.

Can I send the client a PDF instead?

Yes. "Print / save as PDF" on the share link or in the app uses the browser's print dialog and gives a clean PDF of the document, without comments. The comments export separately as a ZIP with comments.md and comments.json.

Get outside comments on a Claude artifact

Publish the HTML from your Claude Code session, send one link with commenting on, and pull the comments back in for the next version.

14-day free trial · No credit card required · Reviewers always free