How to Share a Claude Artifact (5 Ways Compared, 2026)

The fastest way to share a Claude artifact depends on who you're sending it to: if they have a Claude account, the native Share button (Pro/Max) works in two clicks; if they don't, you need to host the HTML somewhere else. This guide covers all five realistic options, with a comparison table and a per-scenario recommendation at the end. Source: Anthropic's share artifacts help article (updated September 23, 2026).

Last updated: October 6, 2026. Tested on a Pro plan the same day.

How to share a Claude artifact with others

The method depends on whether you're sharing a new artifact or a legacy chat artifact, and which plan you're on. Here are the two native paths.

New artifacts — Share button (Pro and Max)

New artifacts use the Share button, which generates a link that requires a Claude account to open.

1. Open the artifact. Click into the artifact panel on the right side of the conversation.
2. Click Share. The Share button appears in the artifact toolbar at the top right.
3. Choose access level. Select Anyone with the link (anyone signed into Claude can open it) or Specific people (enter up to 50 email addresses, each gets an invitation).
4. Set permissions. Choose Can view, Can comment, or Can edit.
5. Click Copy link. Paste it wherever you want to share.

The recipient opens the link in their browser and sees a Claude sign-in prompt if they're not already signed in. There is no guest-access option for new artifacts.

Legacy chat artifacts — Publish button (Free, Pro, and Max)

Artifacts created inside a chat conversation show a Publish button instead of Share. Published artifacts are publicly viewable — the link works in any browser without a Claude account.

1. Open the chat artifact. Locate the artifact in the right panel of your conversation.
2. Click Publish. The Publish button appears in the artifact toolbar.
3. Copy the public link. Claude generates a claude.ai/public/... URL immediately.
4. Share the link. Anyone who receives it can open it — no account needed.

Note: published artifacts may be indexed by search engines if other pages link to them. If you want to remove a published artifact, click Unpublish — the link stops working immediately. You cannot republish the same artifact at the same URL after unpublishing.

How to share Claude artifacts outside your organization

Team and Enterprise plans have different defaults that affect external sharing.

Team: new artifacts are organization-only by default. To share with someone outside your organization, an Owner must first enable External sharing in Organization settings. Once enabled, you can use Share → Anyone with the link and the recipient still needs a Claude account to open it.

Enterprise: external sharing is off by default and controlled by your admin. If Share is grayed out or you can only see org-level options, ask your admin whether External sharing is permitted under your organization's policy.

For both plans, the practical limit is the same: the link only works for people with Claude accounts, and the free tier sign-up is available. If you need to share with someone who won't create a Claude account, the only path is to host the artifact HTML outside Claude — see the comparison below.

For the full plan-by-plan breakdown of who can open what, see sharing a Claude artifact without an account.

Quick comparison

	Claude Share / Publish	ShareDuo	tiiny.host	Netlify Drop	GitHub Pages
Viewer needs Claude account	Share: Yes. Legacy Publish: No	No	No	No	No
No signup to upload	—	✅	❌	✅	❌
View analytics	❌	✅	❌	❌	❌
Password protection	❌	✅	Paid only	❌	❌
Expiry control	❌	✅ (up to 30d)	❌	❌	❌
Permanent URL	✅	Up to 30d	✅	✅	✅
Custom domain	❌	❌	Paid	Paid	✅ (free)
MCP integration	—	✅	❌	❌	❌
Setup time	~0s	~10s	~60s	~30s	10–15 min
Free tier	✅	✅	Limited	✅	✅

1. Claude's native Share and legacy Publish

Best for: sharing with recipients who already have Claude accounts, or quick public sharing of legacy chat artifacts.

Claude's native sharing is free and built in — no extra steps. If your recipients are all on Claude Pro, Max, Team, or Enterprise, the Share button is all you need. They click the link, sign in if they aren't already, and see the artifact immediately.

Where it falls short: no expiry control, no password, no view analytics, and new Share artifacts won't open for anyone without a Claude account — including free-tier users unless they create an account. If recipients keep hitting a sign-in wall, that's the issue. The legacy Publish path (chat artifacts, any paid plan) sidesteps this because those links are genuinely public.

When Claude's native Share is enough: your recipients are colleagues or collaborators already on Claude. You don't need to know when or how often they opened it. You're not sharing sensitive content that needs to expire or be password-gated.

Verdict: the right default for internal sharing among Claude users. Not suitable when recipients aren't on Claude or when you need access controls.

2. ShareDuo

Best for: sharing with anyone outside Claude, with expiry, password, or view-count needs.

ShareDuo is built specifically for Claude artifact sharing. Paste or upload the HTML, get a public link in under 10 seconds. No signup required to upload or view. The link works in any browser — no Claude account, no subscription.

The differentiating features: view analytics (see how many times your link was opened), password protection, expiry windows (1 hour to 30 days), and an MCP integration that lets Claude push an artifact and return a public link without leaving the conversation.

The one real limitation: links max out at 30 days. If you need a URL that lives indefinitely, use Netlify Drop or GitHub Pages instead. For client deliverables, stakeholder previews, and time-limited shares, the expiry window is usually an advantage, not a limitation.

Verdict: best when recipients don't have Claude accounts, or when you need expiry, password, or view counts. More friction than Claude's native Share for internal teams already on Claude.

3. tiiny.host

Best for: permanent public hosting with a simple drag-and-drop interface.

tiiny.host is a dedicated HTML hosting service with a clean upload flow. Drag your .html file onto the upload area, pick a subdomain, and get a permanent URL at yourname.tiiny.host. The process takes about a minute. Links are permanent and the free tier allows a handful of active sites.

To use tiiny.host you need to create an account — there's no anonymous upload path like Netlify Drop. Free-tier sites are publicly viewable by anyone. Password protection and custom domains are available on paid plans.

Where tiiny.host fits: you want a permanent URL and don't mind creating an account. You're hosting a tool or resource you'll reference repeatedly, not a one-time share. The interface is clean enough for non-developers.

Where it doesn't: there are no view analytics on the free tier, no expiry control, and no MCP integration. If you need those, you're looking at a different option. And while tiiny.host is a solid general-purpose HTML host, it has no specific features for Claude artifact use cases — it just happens to work fine for them.

Verdict: good for permanent hosting when you want a clean interface and don't need analytics or access controls. More friction than no-signup alternatives for quick one-off shares.

4. Netlify Drop

Best for: permanent hosting with no account required, for users comfortable handling a file folder.

Netlify Drop (app.netlify.com/drop) is the fastest way to get a permanent, no-account URL for a static HTML file. Drag your folder onto the drop zone and Netlify generates a URL like random-name.netlify.app within seconds. No sign-in, no configuration.

The one friction point: Netlify Drop expects a folder, not a standalone file. For a single .html artifact, you need to put it inside a folder first — a minor extra step on Mac (right-click → New Folder With Selection) but worth noting. If you then want to claim and manage the deploy (rename the URL, update the files), you'll need a free Netlify account.

Free-tier deploys are permanent as long as you don't delete them. There are no view analytics, no passwords, no expiry. The URL is random and not particularly memorable without a custom domain (paid).

Netlify Drop is also a strong option for developers who already use Netlify for other projects — the deploy fits naturally into an existing workflow and can be connected to a git repo for continuous deployment later.

Verdict: the best no-account path to a permanent URL. Slightly more friction for quick one-off shares, but the URL doesn't expire.

5. GitHub Pages

Best for: developers who want permanent hosting, version control, and a custom domain at no cost.

GitHub Pages turns a repository into a static website at username.github.io/repo-name — or your own domain if you configure it. Setup the first time takes 10–15 minutes: create a repository, add the .html file, commit and push, then enable Pages in repository Settings → Pages. After that, every commit to the main branch deploys automatically.

For a one-off Claude artifact share, this is genuine overkill. GitHub Pages is worth the setup when the artifact is something you'll keep updating (a portfolio piece, a recurring report, a tool you're iterating on), when you want the full history of every version via git, or when a custom domain matters and you want it free.

There's no built-in analytics, but GitHub Pages works with any client-side analytics script (Google Analytics, Plausible, Fathom). You can add it directly to the HTML Claude generated.

Non-developers should not attempt GitHub Pages unless they're comfortable with git basics. The other options on this list are far faster for people who just want to share something.

Verdict: best for version-controlled, permanently hosted artifacts that you'll keep maintaining. Not the right choice for quick one-off shares.

Which should you use?

• Recipients all have Claude accounts → Claude's native Share. Two clicks, no extra tools, zero friction. This is the right answer for most internal team sharing.
• Recipients don't have Claude accounts → download the HTML, host externally. ShareDuo for quick shares with expiry, password, and view analytics; Netlify Drop for a permanent URL without signup; tiiny.host or GitHub Pages for permanent hosting with more setup.
• Need a permanent URL → tiiny.host, Netlify Drop, or GitHub Pages. All three give you a URL that doesn't expire.
• Developer workflow, want version control → GitHub Pages. Free custom domain support and git history are strong advantages once you're past the initial setup.
• Want Claude to generate and share the link automatically → the MCP integration. Set it up once and Claude returns a public URL mid-conversation without you touching a browser.

If your recipients keep hitting a sign-in wall, see share Claude artifacts so they actually work — that guide covers the diagnostic flow for every error type.

Frequently asked questions

Can a Claude artifact be shared?

Yes. Legacy published artifacts (chat artifacts, Publish button on Free/Pro/Max) create a public link anyone can open without a Claude account. New artifacts (Share button, Pro/Max) require a Claude account to view. For sharing with people who won't create a Claude account, download the HTML and host it with any of the four external options above.

Can you export an artifact from Claude?

Yes. Click the download icon in the artifact panel to save a standalone .html file. Alternatively, ask Claude to output the full HTML source in the conversation and copy it. Either way, the exported file is a self-contained webpage that runs in any browser — no Claude, no dependencies, no internet connection required for self-contained artifacts.

Can other people see Claude artifacts?

Only if you share them. Artifacts are private by default. Legacy published artifacts are visible to anyone with the link. New shared artifacts (Share, Pro/Max) are visible only to signed-in Claude users you've given access. Team and Enterprise artifacts default to org-only unless External sharing is enabled by an Owner.

Does my artifact link update when I edit it?

For new Share links and legacy Publish links — yes, the same URL reflects the latest version when you save or republish. For externally hosted files (tiiny.host, Netlify Drop, GitHub Pages, or any upload-based service), you need to re-upload the updated HTML; those URLs point to the file you uploaded, not to Claude's live version.

Can I see who viewed my Claude artifact?

Claude's native Share and Publish don't offer viewer analytics. You can see a view count on ShareDuo's manage page. tiiny.host and Netlify Drop don't include analytics on free tiers. GitHub Pages has no built-in analytics but accepts any client-side analytics script added to the HTML.

What is the safe way to share Claude artifacts?

For sensitive content shared internally, use Claude's native Share (Pro/Max) with org-only access — the link can't be forwarded outside your organization. For external sharing with controlled access, host the HTML with password protection enabled. Don't put credentials, personal data, or confidential business information in an artifact you intend to make publicly accessible.