Are Claude Artifacts Public? Privacy and Sharing Explained
Claude artifacts are not public by default. A new artifact is private to the person who created it, and it only becomes viewable by anyone else when you deliberately publish it (on Free, Pro, or Max plans) or share it inside your organization (on Team and Enterprise plans). Once you do publish, the result is genuinely public: Anthropic's help center states that publishing "makes your artifact publicly available. Anyone with the link can view and interact with it." This post explains who can access a Claude artifact at each step, what plan you are on changes, and how to share one at a stable public URL that you control instead of Anthropic's.
Are Claude artifacts public?
Claude artifacts are private by default and become public only when you click Publish. Until you publish, an artifact is visible only to you inside the conversation that created it. There is no automatic public directory, and nothing you generate is exposed to the internet unless you take an explicit action.
Anthropic uses two different words depending on your plan, and the distinction matters for whether "public" is even possible:
- Publishing (Free, Pro, Max plans): "Makes your artifact publicly available. Anyone with the link can view and interact with it," per the Publish and share artifacts help article.
- Sharing (Team, Enterprise plans): scoped to your organization. Viewers have to sign in as members of your Team or Enterprise workspace, and public publishing stays off until an Owner enables it for the whole organization.
So the honest answer to "are Claude artifacts public" is: only if you are on a Free, Pro, or Max plan and you press Publish. On Team and Enterprise, the default is the opposite, and an individual user cannot make an artifact public on their own.
Claude public artifact access, by plan
Claude public artifact access depends entirely on your plan tier, because publishing and org-only sharing are two separate features. The table below maps what each plan can do, based on Anthropic's current help center articles.
| Plan | Default visibility | Can create public link | Who views without a Claude account |
|---|---|---|---|
| Free | Private to you | Yes, via Publish | Anyone with the link |
| Pro | Private to you | Yes, via Publish | Anyone with the link |
| Max | Private to you | Yes, via Publish | Anyone with the link |
| Team | Private to you | Only if an Owner enables it | No, org members must sign in |
| Enterprise | Private to you | Only if an Owner enables it | No, org members must sign in |
Source: Publish and share artifacts and What are artifacts.
The counterintuitive part: a Free plan user can make an artifact public, and a Team plan user paying per seat cannot, unless an admin flips a workspace setting. On Pro and Max, a public link is the only sharing option, so there is no "share with three specific people" mode. It is either private to you or open to anyone with the URL. We cover the Team-plan side in more depth in the Claude Teams artifact workaround post.
What someone sees when they open a published Claude artifact
Someone who opens a published Claude artifact link sees the rendered artifact and can interact with it without signing up for anything. Anthropic's help center confirms non-users get to "view and interact with any published artifact without signing up," and are "prompted to sign up only for advanced features like using AI-powered capabilities."
For a static artifact (a document, a chart, an HTML page, a React component that runs in the sandbox), the recipient sees the finished thing. The one place a login prompt appears is when the artifact calls Claude itself, for example an app that runs a model behind a button. That interaction asks the viewer to sign in. The base content does not.
Two properties of a published Claude artifact catch people out:
- Unpublishing is one-way. Per Anthropic: "Once you unpublish an artifact, you cannot publish that same artifact again." Unpublishing also "permanently deletes all associated storage data" if the artifact used persistent storage. You cannot toggle public on and off casually.
- The URL lives on claude.ai. The link points at Anthropic's domain, carries Claude branding, and the content is tied to Claude's version of the artifact rather than a file you keep.
When a claude.ai public link is not what you want
A claude.ai public link is not ideal when you need a plain, on-brand deliverable, when you are on a Team plan that blocks public links, or when you want the URL to update in place as you revise. Claude's Publish button solves the "let anyone see it" problem, but the artifact still reads as a Claude page, and the one-way unpublish rule makes iteration awkward.
Common situations where people move the content off claude.ai:
- You are on Team or Enterprise and your admin has not enabled public publishing, so the native link only works for org members.
- You want to hand a client a document that does not carry another product's branding or a "made with Claude" frame.
- You expect to revise the deliverable several times and want one stable link, not a publish-unpublish-republish cycle that can strand the original.
- You want the same URL to hold a mix of formats over time: a markdown report this week, a data table next week.
For those cases, the fix is to copy the artifact content out of Claude and publish it yourself. If your artifact is a data table or a code file, the format-specific steps in the Claude Teams artifact workaround apply here too.
How to share a Claude artifact at a public URL you control
You can share any Claude artifact at a stable public URL you own by copying the artifact content, saving it as a file, and publishing it with one command. This keeps the artifact public without depending on Anthropic's Publish button or an admin's workspace setting.
Step 1: Copy the artifact. Use the copy icon in the artifact pane. Markdown copies as markdown, HTML as HTML, code as code.
Step 2: Save it to a file. The extension decides how it renders:
pbpaste > report.md # markdown document
pbpaste > dashboard.html # HTML artifact
pbpaste > analysis.py # code artifact
Step 3: Publish it.
anchorify report.md
# → returns a public URL, no login required for viewers
The command returns a URL that anyone can open with no account, no "request access" step, and no Claude branding. Re-run the same command after you edit the file and the URL stays the same while the content updates, which is the iteration loop the native unpublish rule does not give you. Full command shapes are in the docs. This is the same publish-a-file pattern we describe for sharing Cursor output as a link and sharing a ChatGPT deep research report.
How Claude sharing compares to publishing a file yourself
The two approaches solve overlapping problems, but the trade-offs differ on branding, iteration, and Team-plan availability. The table sums up the difference.
| Property | Claude Publish button | Publish the file yourself |
|---|---|---|
| Works on Free/Pro/Max | Yes | Yes |
| Works on Team without admin | No | Yes |
| Viewer needs account | No (public link) | No |
| Same URL after edits | No, unpublish is one-way | Yes, re-run the command |
| Branding on the page | claude.ai | Your own deliverable |
| Best for | Quick one-off shares | Client-facing, iterated work |
Neither is strictly better. If you are on Pro and want to fire a link at a colleague, the native Publish button is the fewest clicks. If you are on Team, or the deliverable is client-facing and will change, publishing the file yourself is the cleaner path. For the broader case against handing over portal or product links, see why you can share a deliverable without a portal.
Frequently Asked Questions
Are Claude artifacts public by default?
No. A Claude artifact is private to the person who created it until that person publishes it. On Free, Pro, and Max plans, clicking Publish makes it public so anyone with the link can view it. On Team and Enterprise plans, sharing is scoped to your organization by default, and public publishing is disabled until an Owner turns it on for the workspace. Nothing you generate is exposed to the internet automatically.
Can anyone with the link see a published Claude artifact?
Yes, on Free, Pro, and Max plans. Anthropic's help center states that a published artifact is "publicly available" and "anyone with the link can view and interact with it," without signing up. A viewer is only prompted to sign in when the artifact uses an advanced AI-powered feature that calls Claude. On Team and Enterprise, the shared link only works for people signed into your organization unless an admin has enabled public publishing.
Can I unpublish a Claude artifact to make it private again?
You can unpublish, but it is a one-way action. Anthropic states that "once you unpublish an artifact, you cannot publish that same artifact again," and unpublishing permanently deletes any persistent storage data tied to it. This is why people who expect to revise a deliverable often copy the content out and publish the file themselves, where re-running the publish command keeps the same URL without any destructive step.
Do Claude artifacts have an expiry date?
No. Published Claude artifact links stay live on claude.ai until you unpublish them, and there is no expiry setting. That is convenient for a permanent share but means an old link stays public until you remember to take it down, and taking it down is the irreversible unpublish action described above.
How do I share a Claude artifact if I am on a Team plan?
Copy the artifact content, save it as a file, and publish that file to a public URL yourself. On a Team plan you cannot generate a native public link unless a workspace Owner has enabled public publishing. Copying the content into a .md, .html, or code file and running one publish command produces a link anyone can open, no admin change required. The step-by-step is in the Claude Teams artifact workaround.
Sources
- Publish and share artifacts, Claude Help Center: "Makes your artifact publicly available. Anyone with the link can view and interact with it," plus the one-way unpublish rule.
- What are artifacts and how do I use them, Claude Help Center: default privacy and the Publish step.
- Manage project visibility and sharing, Claude Help Center: org-scoped sharing behavior on Team and Enterprise.
If you want a Claude artifact live at a public URL you own, without the one-way unpublish rule or a Team-plan admin gate, Anchorify turns any copied artifact into a shareable link with one command. Free during beta, no account needed on the reader side. Sign in at anchorify.io, or read the Claude artifacts workflow page.