Are Claude Artifacts Private?

The short answer

An artifact you create in Claude is private to you while it lives in your conversation. Nobody else can see it until you take an action to share it.

The question people actually mean, though, is: what happens when I share it? And there the honest answer is narrower than most people expect. Claude's sharing surfaces give you two settings, and neither one is "everyone at my company, and only my company."

• Publish (public). Claude's publish button turns the artifact into a page anyone on the internet can open with the link. No sign-in. No company check. If the link leaks, forwards, or gets indexed, the content is out.
• Share inside a Claude organization. On Claude Team and Enterprise you can share an artifact with your workspace, but viewing it requires a Claude seat in that organization. Your PM, your legal reviewer, and your exec each need a paid Claude account to open the page.

So the practical shapes are "fully public" or "only people who pay for Claude." For anything internal, competitive analyses, financial summaries, client work, the first is too open and the second is too narrow.

What "private" actually means for a shared artifact

There are three different privacy questions hiding inside "are Claude artifacts private," and they have different answers.

1. Is it private before I share it? Yes. It sits in your conversation, tied to your account.

2. Is a published artifact private? No. A published Claude artifact is served at a public URL. Anyone with that URL can view it, whether you sent it to them or not. This is the setting most people click when they want to "send it to a colleague," and it is the one that surprises them: they have not shared it with a person, they have posted it to the open web and handed one person the address.

3. Is an org-shared artifact private to my company? Only in the sense that viewers must be logged into a Claude seat in your organization. That gates by Claude subscription, not by company identity. The colleague who does not use Claude cannot get in. The setup requires Claude Team or Enterprise, which is a per-seat cost for every viewer.

The gap is the middle: a page only your company can open, where viewers use the Google or Microsoft account they already have and do not need to buy a Claude seat. Claude does not offer that. It is exactly the shape internal work needs, and it is the reason a separate publishing step exists.

Claude sharing options, side by side

For how the underlying access model works and where it fits, see what is gated publishing.

Why this matters more every month

AI tools now produce rich internal content by default. Claude Code, Cursor, and Codex write self-contained HTML, reports, dashboards, and analyses in minutes. More than half of developers use AI coding tools daily (Stack Overflow 2025), and Claude Code alone reached roughly $2.5B annualized revenue by early 2026. The volume of agent-made artifacts inside companies is now large, and most of it is exactly the kind of material that should not sit at a public URL.

The instinct is to hit publish and paste the link in Slack. That instinct quietly makes internal work public. The correct move is to keep the artifact off the open web and put it behind the identity your company already runs.

The middle option: publish behind company SSO

display.dev publishes a Claude artifact to a URL that is gated by your company's Google or Microsoft login, not by a Claude subscription.

A viewer clicks the link, signs in once with their work Google or Microsoft account, the same one they use for email, and sees the full interactive page. If their email is on your company's domain, they are in. If it is not, they are not. Nobody buys a Claude seat to read the page, and the content never lived at a public address.

Two ways to get an artifact from Claude to display.dev:

• From Claude Desktop or Claude.ai: add display.dev as an MCP connector and ask, "publish this to my team." Your agent returns a company-gated URL in the conversation. Setup takes about five minutes, or IT can push it once. See the non-technical guide.
• From Claude Code: the artifact is a file on disk, so run dsp publish ./report.html and get the URL back in about 15 seconds.

Either way you land on the option Claude does not offer: private to your company, open to every colleague, no extra seat to buy. Full walkthrough on the share a Claude artifact page.

The per-seat point is the one that keeps mattering. Viewers outnumber creators roughly ten to one: one person makes the artifact, ten need to read it. Gating on Claude seats charges for every one of those ten. Gating on company SSO charges for none of them. display.dev has no per-seat fee at any tier, and viewers are unlimited.