How to Share Claude (and Codex) Artifacts Externally: 8 Tools Compared

Your agent just built something good — a Claude Code dashboard with live filters, a Codex-generated internal tool, a single-file HTML report with charts that actually work. Then you try to send it to a teammate, or worse a client, and hit the wall everyone hits: there's no clean way to share it. The hard part (generating a polished, interactive artifact) is now trivial. The easy part (putting it at a URL the right people can open) is where everything breaks. So people screenshot the output into Slack, zip the HTML and email it, or paste it onto a public link and hope nobody indexes it.

This guide compares the eight realistic ways to share Claude artifacts externally — plus Codex Sites and ChatGPT canvas output — and tells you which one fits which job. We're straight about where each tool wins and where it doesn't.

Why sharing Claude artifacts is harder than it should be

The constraints are specific, and most people don't discover them until they're already stuck:

• Claude Team and Enterprise plans cannot share artifacts publicly at all. Sharing stops at your organization — viewers have to be logged-in members of your paid Claude org. There is no option to make an artifact viewable to an outside client or partner.
• Free, Pro, and Max plans can only go fully public. You get a claude.ai/public/artifacts/... link anyone can open — but it's all-or-nothing. There's no middle setting that limits viewing to your company without exposing it to the whole internet. (We unpack why this matters in gated publishing vs. public hosting.)
• OpenAI Codex Sites are workspace-locked. They're hosted by OpenAI, restricted to ChatGPT Business and Enterprise, and offer no public mode or custom domain. OpenAI's own docs frame them as internal tools — "not suitable for customer-facing applications."

So the paying customers have the least flexibility, and the thing teams need most — "let the right people see this, gated by their own company login, without making it public" — is exactly the thing none of the first-party tools do. That gap is why Claude's own publish button doesn't solve internal sharing.

Note: Claude Code Artifacts, Codex Sites, and several SSO features below are in beta or shipped recently (mid-2026). These products move fast, and the external-sharing limits are the most likely thing to change. Re-check before you bet a workflow on any single behavior.

What to look for in an artifact-sharing tool

Six things actually matter when you're comparing options:

1. External + gated sharing. Can outsiders view it, gated by their company login — not fully public, not locked to your vendor's org?
2. No viewer accounts. Does the viewer have to create yet another account, or can they authenticate with credentials they already have (Google or Microsoft)?
3. Agent-neutral. Does it work with output from any agent — Claude Code, Claude.ai, Codex, ChatGPT, Cursor — or only one?
4. Pricing model. Flat org pricing vs. per-seat vs. per-viewer. Per-viewer pricing quietly punishes you for sharing widely.
5. Permanence and versioning. Does the URL survive updates, or do you mint a new link every time you change a line?
6. Collaboration. Can people comment on the artifact so the agent can iterate, or is it a dead end?

Here's how the eight options stack up.

1. display.dev — best for team and external sharing behind company SSO

One-liner: An agent-neutral host that publishes any artifact to a URL gated by the viewer's company login — no viewer accounts, flat org pricing.

Best for: Teams (and anyone sharing with clients) who need artifacts visible to specific people or whole companies without making them public — and without paying per viewer.

How sharing and auth works: One command — dsp publish report.html — returns a live URL. You set visibility to public, company (anyone with a verified company Google or Microsoft email), or private, or share with named email addresses. Viewers authenticate with credentials they already have; there are no accounts to create and nothing for IT to provision. It's agent-neutral by design, so output from Claude Code, Codex, Cursor, or a plain build script all publish the same way, and there's an MCP integration so an agent can publish on your behalf mid-conversation. Artifacts get version history, an audit log of who opened what, and inline comments an agent can read and act on to republish a new version. Anonymous publishes are claimable — ship a 30-day link first and sign in later to make it permanent.

Pricing: Free tier includes 10 gated artifacts (one-time-password auth; public artifacts unlimited). Solo is €15/month for unlimited gated artifacts. Pro is a flat €49/month for the whole organization — unlimited viewers, Google + Microsoft SSO, 90-day audit log. Enterprise from €499/month adds SAML, custom domains, RBAC, and 365-day audit retention.

Pros:

• The only option here that gates by the viewer's company login with no viewer accounts.
• Flat org pricing — sharing with 5 people or 5,000 costs the same.
• Agent-neutral; comments and versioning make artifacts living documents.

Cons:

• Overkill if all you need is a throwaway public link.
• Company-gated viewing assumes the viewer's org uses Google Workspace or Microsoft 365 (named-email shares cover the rest).

See display.dev for Claude Code for the agent-specific workflow.

2. Claude's native publish & share — best for quick public demos on Free/Pro

One-liner: Built into Claude, zero setup — but the gating model is all-or-nothing.

Best for: Free, Pro, or Max users sharing a public demo, or Team/Enterprise users sharing strictly inside their Claude org.

How sharing and auth works: On Free, Pro, and Max you publish to a public claude.ai/public/artifacts/... link anyone can open and interact with — no account required. On Team and Enterprise you instead get internal sharing: viewers must be logged-in members of your Claude organization, and organization artifacts cannot be published publicly. Artifacts are hosted on Anthropic's infrastructure (a sandboxed claudeusercontent.com origin), capped at 16 MiB, under a strict content security policy that blocks external scripts, fonts, and network requests.

Pricing: Included with your Claude plan (Pro and Team from roughly $20–30/user/month).

Pros:

• Zero friction — it's already in the product.
• Public links need no viewer account.

Cons:

• No middle ground: fully public or locked to your org.
• The paid Team and Enterprise tiers are the ones that can't share externally.
• Claude-only, and the CSP sandbox blocks anything that calls out to the network.

3. OpenAI Codex Sites — best for internal-only tools inside a ChatGPT workspace

One-liner: Deploy Codex-generated apps to an OpenAI-hosted URL — but only for your own workspace.

Best for: ChatGPT Business and Enterprise teams shipping internal tools to colleagues in the same workspace.

How sharing and auth works: Codex builds your app into Cloudflare Worker-compatible modules that OpenAI hosts. Access is workspace-bound, with three modes — admins only, the whole workspace, or custom users and groups — all requiring active membership in your ChatGPT workspace. There's no public-by-default mode and no custom domain. OpenAI's docs state Sites are "not suitable for customer-facing applications."

Pricing: Bundled with ChatGPT Business and Enterprise.

Pros:

• Tight loop from Codex generation to a hosted internal URL.
• Granular workspace access controls.

Cons:

• No external or public sharing, and no custom domain.
• Codex/ChatGPT-only; locked to OpenAI hosting.

4. ShareDuo — best for fast external Claude shares with expiry and analytics

One-liner: Paste a Claude artifact, get a shareable link in seconds, with password and expiry controls.

Best for: One-off external shares where you want a password, an expiry date, and view analytics — but don't need company-wide gating.

How sharing and auth works: Paste or upload your HTML and ShareDuo hosts it on a public link. You can add an optional password, set the link to expire (up to about 30 days), and see view analytics. An MCP integration lets Claude hand you a link mid-conversation.

Pricing: Free to use.

Pros:

• Genuinely fast; optional password, expiry, and analytics.
• No signup needed to view.

Cons:

• Public-first — no company-SSO gate.
• Links expire (about 30 days max), so it's not for permanent docs.

5. PreviewShip — best for instant public preview URLs

One-liner: Turn AI-generated HTML into a public HTTPS preview link with no deploy setup.

Best for: Developers who want a quick public preview of Claude or AI HTML without touching GitHub or a host.

How sharing and auth works: Paste or upload the HTML, or deploy via CLI or MCP, and PreviewShip serves it at a public preview URL. New versions can reuse the same link.

Pricing: Freemium (tiers not consistently published).

Pros:

• Frictionless; CLI and MCP deploy paths suit agent workflows.
• Good for the create → inspect → share → revise loop.

Cons:

• Public links only — no SSO or company gating.
• Preview-oriented, not a governed team workspace.

6. Handoff.host — best for permanent, versioned artifact links

One-liner: Permanent, versioned URLs for AI-generated artifacts, with optional password protection.

Best for: Sharing specs, reports, and prototypes that get updated over time, where a stable link matters.

How sharing and auth works: Upload via CLI or API (with a Claude Code integration) and get a stable URL that persists across versions. Password protection is available for basic gating.

Pricing: Free tier available; paid tiers not clearly published.

Pros:

• Stable URLs and version history.
• Password option for light access control.

Cons:

• A shared password is not company SSO; no per-company viewer gating.
• Public-first model.

7. Tiiny.host — best for the simplest possible public link

One-liner: Drag-and-drop an HTML file or zip and get a permanent public URL.

Best for: Non-technical users who just need a quick, permanent public link — the fastest way to share an HTML file with your team without GitHub.

How sharing and auth works: Drop a single HTML file or a zipped folder, pick a custom subdomain (or take an auto-generated one), and it's live. No account needed to view. You can edit in the browser after publishing and generate embed or QR codes.

Pricing: Free tier with a custom-name option; paid plans for custom domains and extras.

Pros:

• Dead simple, permanent, no signup to view.
• Handles multi-file sites via zip.

Cons:

• Public by default — no SSO or company gating.
• Not built for AI-agent workflows or collaboration.

8. Vercel (+ v0) — best for turning an artifact into a real production app

One-liner: Production-grade hosting for AI-generated apps — far more than artifact sharing, with the overhead to match.

Best for: When the "artifact" is really an app that needs a database, custom domain, and CI/CD — not a one-off page to share.

How sharing and auth works: Deploy generated code (for example from v0) to a Vercel URL. But gating it behind your company login is the catch: "Vercel Authentication" forces viewers into a Vercel account with access rights, gating behind your own identity provider ("Passport") is an Enterprise-only beta excluded from the standard protection add-on, and on the free Hobby tier production stays publicly accessible.

Pricing: Hobby (free, non-commercial); Pro from $20/user/month; Enterprise for advanced auth.

Pros:

• Real hosting: custom domains, build pipelines, scale.
• Deep integration with AI app builders like v0.

Cons:

• Company-SSO viewer gating is Enterprise-only beta.
• Requires a deploy pipeline — heavy for sharing a single artifact.

Comparison: 8 ways to share Claude and Codex artifacts

The pattern is clear: most tools solve public sharing well and gated, external, agent-neutral sharing not at all. If you only need a quick public link, Tiiny.host or PreviewShip will have you done in a minute. If the artifact is really an app, Vercel is the right home. But if you need the right people — your team, a client, a partner — to see it, gated by their own company login and not the open internet, that's the specific gap display.dev was built for.

How to pick

• Quick public demo, throwaway: Claude's native public link (Free/Pro) or Tiiny.host.
• External share with a password and expiry: ShareDuo.
• Permanent, versioned link: Handoff.host or display.dev.
• Internal-only tool inside your AI vendor's workspace: Claude org sharing or Codex Sites.
• A real production app: Vercel + v0.
• Team or external viewing gated by company login, any agent, flat pricing: display.dev.