Share Claude Artifacts on Teams Plan: A Workaround
Claude Teams plan users cannot generate public artifact links or embed codes. Free, Pro, and Max plan users can. Anthropic's August 2025 release notes state: "Claude users with free, Pro, or Max plans can generate an embed code for any published artifacts." Teams is absent from that list. If you bought Teams seats and expected to share artifacts with clients or stakeholders outside your organization, you hit a wall that Anthropic has not formally explained. This post covers what the restriction actually is, what Teams plan can still do, and a step-by-step workaround to share any Claude artifact publicly without switching plans.
Claude Teams plan artifact sharing is scoped to your organization
Claude Teams plan artifact sharing is limited to internal org sharing. The plan does not include the public artifact link and embed-code feature that Free, Pro, and Max users received in August 2025.
The clearest documentation is the August 21, 2025 entry in Anthropic's release notes: "Claude users with free, Pro, or Max plans can generate an embed code for any published artifacts." Teams is not listed. The Claude Teams marketing page describes artifact sharing as "secure sharing across your organization." The scope is internal by design.
What Teams plan can do with artifacts:
- Create artifacts (code, documents, HTML, SVG, React components)
- Edit and iterate on artifacts inside Claude
- Share artifacts within the org via Project sharing and collaboration
- Use admin controls to manage sharing permissions across the organization
What it cannot do:
- Generate a public link that anyone with the URL can view
- Generate an embed code for an artifact
- Share an artifact with someone who is not in your Claude org
What changed for Teams plan users
Teams plan users effectively lost access to public artifact sharing when Anthropic launched the public embedding feature in August 2025. That feature shipped for Free, Pro, and Max plans; Teams was excluded at launch with no public explanation.
Anthropic has not published a formal announcement about this exclusion. The r/ClaudeAI thread 1klzl01 documents the user reaction, with Teams plan subscribers reporting the inability to share artifacts outside their organization. The thread is worth reading if you want a sense of the scope of the frustration.
If you are evaluating Claude plans for an organization and artifact sharing with external recipients is a requirement, the current documented answer is: Free, Pro, and Max support it; Teams and Enterprise do not (Enterprise shares the same scope as Teams on this feature).
Which Claude plans can share artifacts publicly
The table below maps each plan to its artifact sharing capabilities, based on the August 2025 release notes and the current pricing page.
| Feature | Free | Pro | Max | Teams | Enterprise |
|---|---|---|---|---|---|
| Create artifacts | Yes | Yes | Yes | Yes | Yes |
| Share within org/project | No | Yes | Yes | Yes | Yes |
| Public artifact link | Yes | Yes | Yes | No | No |
| Embed code for artifact | Yes | Yes | Yes | No | No |
| Admin sharing controls | No | No | No | Yes | Yes |
Source: claude.com/pricing, claude.com/teams, Anthropic release notes.
The counterintuitive result: a Free plan user can share artifacts publicly; a Teams plan user paying $30/month per seat cannot. The Teams plan trades that capability for org-scoped controls, admin tooling, and higher usage limits.
How to share a Claude artifact publicly from a Teams account
Teams plan users can share any Claude artifact publicly by copying the artifact content, saving it as a local file, and publishing it to a stable URL. Here is the step-by-step using Anchorify.
Step 1: Generate the artifact in Claude as normal. Nothing changes here.
Step 2: Copy the artifact content. Click inside the artifact panel, select all (Cmd+A or Ctrl+A), and copy (Cmd+C or Ctrl+C).
Step 3: Save it to a local file. The file extension determines how it renders:
- Markdown document:
my-report.md - HTML artifact:
my-dashboard.html - React component:
my-component.jsx - SVG:
my-chart.svg - Code block:
script.py,analysis.ts, etc.
Step 4: Install Anchorify if you haven't. Full setup is in the getting started guide.
Step 5: Publish with one command.
# Markdown artifact
anchorify my-report.md
# HTML artifact
anchorify my-dashboard.html
# Code file
anchorify script.py
The command returns a URL. That URL is public by default. Anyone with it can view the rendered content, no login required.
Step 6: Share the URL. Paste it in an email, a Slack message, a client deck, anywhere. The recipient sees a rendered document, not a file download prompt.
Step 7: Update when the artifact changes. Re-run the same command. The URL stays the same; the content updates. Useful for live reports or iterative deliverables.
The full CLI reference is at /docs/cli.
What recipients see compared to other sharing options
A recipient who clicks an Anchorify URL sees a clean, rendered document: no login prompt, no permission request, no "request access" dialog.
| Sharing method | Recipient sees | Login required | Updates in place | Works for HTML artifacts |
|---|---|---|---|---|
| Anchorify URL | Rendered document or page | No | Yes, same URL | Yes |
| Google Doc paste | Formatted doc | Often yes | Manual re-paste | No |
| GitHub Gist | Raw code or markdown | No | New gist or edit | Limited |
| Email attachment | File download | No | No | No |
| Screenshot | Image | No | No | No |
For HTML artifacts specifically, Anchorify serves the HTML as a live page (useful for interactive charts, dashboards, or any Claude-generated app). For the full comparison with Google Docs, see the Anchorify vs Google Docs page.
The workaround is not seamless compared to a native public artifact link. You copy content, save a file, run a command. But the recipient experience is comparable: a stable URL, no login wall, readable on any device.
Frequently Asked Questions
The questions below cover the most common points of confusion about Claude Teams artifact sharing and the workaround.
Can I share a Claude artifact publicly on a Teams plan?
Claude Teams plan does not include public artifact links or embed codes. You can share artifacts within your organization via Project sharing, but you cannot generate a public URL or embed code that someone outside your org can access. The workaround is to copy the artifact content, save it as a file, and publish it to a service that generates public URLs.
Why can't Teams plan users share artifacts publicly?
Anthropic has not published a formal explanation. The August 2025 release notes launched public artifact embedding for Free, Pro, and Max plans without including Teams. The Teams plan marketing page describes artifact sharing as "secure sharing across your organization," which suggests the public-sharing scope is intentionally excluded from the Teams tier. One reasonable inference: Teams plan is designed for orgs that want admin control over what leaves the organization, so public sharing is off by default and not individually overridable.
Does the workaround work for all Claude artifact types?
Yes, with one caveat for React artifacts. Markdown, HTML, SVG, and plain code artifacts can be copied and published as-is. HTML artifacts render as live pages. Markdown renders as a document. For React artifacts, the JSX copies cleanly and renders as a code file with syntax highlighting. It will not run as a live React app unless you build it first. If your React artifact is a self-contained HTML file with inlined JavaScript, use .html as the extension and it will run.
Will Anthropic add public sharing back for Teams?
There is no public roadmap entry for this. Teams plan features are controlled by Anthropic. If public artifact sharing is a firm requirement, a Pro individual plan currently includes it. Pro does not include admin controls, org management, or the higher usage limits that Teams provides, so the trade-off depends on your use case.
Is downgrading from Teams to Pro worth it just for artifact sharing?
Only if public artifact sharing is your primary use case and you do not need Teams' admin controls or org-level collaboration. The workaround in this post lets you keep the Teams plan while sharing artifacts externally with a few extra steps. For organizations with multiple users who all need to share externally, the workaround scales: each user copies their artifact, and anyone with the Anchorify CLI can publish in under a minute.
Sources
- Anthropic release notes, August 21 2025: "Claude users with free, Pro, or Max plans can generate an embed code for any published artifacts"
- Claude Teams plan page: "secure sharing across your organization" language for artifact collaboration
- Claude pricing page: plan feature comparison table
- r/ClaudeAI thread 1klzl01: community documentation of Teams plan artifact sharing frustration
If you are a Teams plan user who needs to share artifacts externally, Anchorify converts any file into a stable public URL with one command. Free during beta. No permission dialogs, no login walls for recipients. Sign in at anchorify.io to get started, or read the /for/claude-artifacts page for the Claude-specific workflow.
Last updated: 2026-05-24