How to share a Claude artifact as a live URL

Claude built you something good — a dashboard, a landing page, an interactive demo — and now you want to show it to someone who doesn't use Claude. The artifact lives inside a chat; your recipient needs a normal link. Here's how to get one in about a minute, and how to make Claude publish it for you so you never copy-paste again.

Get a URL for your artifact

Why the built-in share link isn't enough

Claude can share an artifact, but the link opens inside Claude. That's fine between Claude users; it breaks down the moment you send it to a client, your team's Slack, or anyone who hits a login wall instead of your page. Artifacts are also tied to the conversation that produced them — not something you'd put in an email signature or a proposal.

The artifact itself, though, is just an HTML file. Host that file at a real URL and it behaves like any other web page: opens for everyone, previews with a card when pasted into Slack or iMessage, works on phones, and stays up after the chat is long gone.

The one-minute way (no signup)

Copy the artifact's code. In the artifact panel, switch to the code view and copy everything — or use the download button to save it as an .html file.
Drop it on htmldrop.app. Drag the file onto the drop zone (up to 2 MB anonymously). If you copied instead of downloading, paste into a new file named anything.html first.
Send the URL. You get a live slug.htmldrop.app address immediately. Anyone can open it — no Claude account, no login, no download. Anonymous links stay live for 7 days.

The zero-copy way: let Claude publish it

If you're in Claude Code, Claude Desktop, Cursor, or Cline, skip the copy-paste entirely. Add htmldrop's MCP server and "publish this as a page" becomes a one-liner Claude handles itself:

claude mcp add --transport http htmldrop https://htmldrop.app/mcp

The remote server signs you in with OAuth in the browser — no API keys to copy. From then on, Claude can publish (htmldrop_publish), list, and delete your pages, handing back the live URL each time. It's the difference between "generate, download, upload, share" and just "ship it". Details on the agents hub and per-client setup on Claude Code and Claude Desktop pages.

What ports cleanly (and what doesn't)

Anything self-contained runs exactly as it did in the artifact panel: vanilla HTML/CSS/JS, canvas animations, p5.js sketches, Three.js scenes, and CDN-loaded libraries like Tailwind or React UMD builds. Artifacts built as Claude-powered apps — ones that call the window.claude API to talk to the model — depend on Claude's own runtime, so those stay in Claude. Everything else is just a web page.

Make it private, permanent, or yours

Unlisted by default: drop URLs are unguessable and user pages are not indexed by search engines unless you opt in.
Password protection: paid plans from $5/mo gate the page behind a password — right for client work and drafts.
Permanence: a free account keeps drops around (10 MB each); paid plans make them permanent with version history, so you can update the page without changing the link.
Your own domain: from $10/mo, serve the artifact at a URL on your brand instead of a htmldrop slug.

From artifact to URL in under a minute.

Free, anonymous, no signup — or wired straight into Claude via MCP so publishing is one sentence.

Try it free

FAQ

Can people view a Claude artifact without a Claude account?

Claude's built-in share link opens inside Claude, which is a problem when your recipient doesn't use it. Hosting the artifact's HTML on htmldrop gives you a normal web URL that opens for anyone, in any browser, with no Claude account or login.

Do interactive artifacts (React, Tailwind, charts) work?

Yes for anything self-contained in the HTML — JavaScript, canvas, p5.js, Three.js, and CDN-loaded libraries all run as-is. Artifacts that call the window.claude API (Claude-powered apps) depend on Claude's runtime and only work inside Claude — everything else ports cleanly.

Can Claude publish the artifact itself?

Yes. Add the remote MCP server (https://htmldrop.app/mcp, browser sign-in via OAuth) and asking Claude to "publish this page" returns a live URL in one tool call. Works in Claude Code, Claude Desktop, Cursor, and Cline.

How do I keep the shared artifact private?

Every drop gets an unguessable URL and user drops are not indexed by search engines by default. For an actual gate, paid plans from $5/mo add password protection — the page asks for the password before it renders.