How to Share Claude Artifacts Outside Your Organization (2026)
By Marcin, founder of Markloop · Last verified October 2026 against the official Claude Code docs and Anthropic's help center
Short answer: open the artifact and click Share. In the Claude app (chat and Cowork), even "Anyone with the link" means anyone signed in to Claude. A Claude Code artifact can get a public link that, per the Claude Code docs, opens without a sign-in: on Pro and Max it's the only way to share, and on Team and Enterprise it stays inside your claude.ai organization until an Owner turns on External sharing. A public link can't take comments. If a client needs to comment, save the artifact as an HTML file and share it through one of the four channels below.
How to share a Claude artifact, step by step
There are two kinds of Claude artifacts, and they share differently: artifacts in the Claude app, and pages Claude Code publishes from a coding session.
In the Claude app (chat and Cowork)
- Open the artifact and click Share. Every artifact starts private.
- Pick who can open it: people you invite or anyone at your organization (Team and Enterprise), Anyone with the link (paid plans), or people outside your organization by email (beta, paid plans, up to 50 people per artifact).
- Pick what they can do: Can view, Commenter or Can edit.
- Copy the link and send it.
Everyone who opens it has to sign in: in Anthropic's words, "Anyone signed in to Claude who has the link can open it." On Team and Enterprise, Anyone with the link works only after an Owner turns on External sharing or allows that artifact (Claude help center). Older chat artifacts still show Publish on Free, Pro and Max, which makes a public link anyone can open. The access rules for each plan are in who can comment on a Claude artifact.
In Claude Code (claude.ai/code/artifact links)
- Open the artifact in your browser. Its URL looks like
claude.ai/code/artifact/…. Every artifact you made is listed atclaude.ai/code/artifacts, or run/artifactsin Claude Code. - Click Share in the page header.
- Pick the audience: specific people or everyone in your organization (Team and Enterprise), or a public link.
- 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. What each plan allows is in the table further down.
Which one should you pick?
Sharing the artifact link works for a quick look. When the reader is outside your organization, has no Claude account, or needs to comment, share the HTML file instead. The four ways to do that, side by side; each one is explained below.
| Email the file | Static hosting | Send / ShareDuo / Anchorify | Markloop | |
|---|---|---|---|---|
| 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 Code | manual | manual | manual (Anchorify: CLI/API) | ✓ MCP pull |
| Versions with "addressed" tracking | — | — | — | ✓ |
| Viewer analytics | — | — | ✓ | — |
| Reviewer sees source file | yes | yes | varies | no - 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.
What Claude Code allows on each plan
Claude Code artifacts follow their own rules, set in the Claude Code docs:
| Plan | Who can see your Claude Code artifact | Public link? | Comments? |
|---|---|---|---|
| Pro / Max | Only you, until you make a public link | Yes (the only way to share) | Not on a public link |
| Team | People in your org you share with | Only if an Owner turns on External sharing | Yes, in-org (not on a public link) |
| Enterprise | People in your org you share with | Only if an Owner turns on External sharing | Yes, in-org (not on a public link) |
An artifact that pulls live data through connectors can now get a public 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, and people whose only access is the public link can't see or add comments; who can comment on a Claude artifact keeps the full, up-to-date rules.
First, get the HTML file out
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, embedded images, 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.
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, marking 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. Solo is $19/mo, Team $49/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.
FAQ
Can someone without a Claude account open a shared Claude artifact?
Only through a public link: a Claude Code artifact shared publicly (the Claude Code docs say it opens with no claude.ai sign-in), or an older chat artifact made public with Publish. Artifacts in the Claude app need the viewer to be signed in to Claude, even with "Anyone with the link". People who only have a public link can't comment, so if you need comments from someone without a Claude account, share the HTML file on Markloop instead.
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, invite them to the project by email instead, which needs a free Markloop account. 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
Related: How Claude artifacts work · Claude live artifacts are legacy · Claude artifact sharing options compared · HTML is the new Markdown - reviewing it is the missing half · How to get comments on a Cursor canvas