How to publish a Claude artifact, inside Claude or at your own URL

You asked Claude for a landing page, a calculator or a client report, and it looks right. Now you want to send it to someone. Publishing a Claude artifact can mean two different things: sharing it from Claude, which works for people who have a Claude account, or putting it on the web at your own URL, which works for everyone. This guide covers both, and the second one is the same flow as any AI website hosting: export the files, check them, upload them.

---

Two ways to publish a Claude artifact

The right method depends on who needs to open it.

• Share it from Claude when the viewers already use Claude: a teammate, a colleague in your organization, a friend with an account. Nothing leaves Claude, and AI features inside the artifact keep working.
• Publish it at your own URL when the viewers are clients, recruiters, customers or anyone who has never signed up for Claude. The artifact becomes an ordinary web page that opens in any browser.

If you are not sure what counts as an artifact, or which type you have, start with what a Claude artifact is. The type decides the export options.

Option 1: share the artifact from Claude

Every artifact has share controls in its panel. Depending on your plan, you can give access to anyone signed in to Claude who has the link, to people you invite by email, or to members of your organization on Team and Enterprise plans.

The rule for viewers is the same in every case. Anthropic’s help center, in its share artifacts article, puts it plainly: “Everyone needs a Claude account. People without one can’t open a shared artifact, even with the link.”

There is one exception. A legacy artifact, made in a chat before September 16, 2026, can still be published on Free, Pro and Max plans. A published legacy artifact can be viewed and used by anyone with the link, without an account. Two catches: Team and Enterprise plans use “Share & copy link” instead, and once you unpublish an artifact, you cannot publish it again.

Option 2: publish it at your own URL

When the audience does not have Claude, the artifact has to leave Claude. The four steps below turn it into a website with an address you choose.

Step 1: Export the artifact as HTML

The export depends on the kind of artifact.

• Designs (web pages, landing pages, mockups) have an Export button with a standalone HTML option, as well as a ZIP, PDF and PowerPoint. Pick standalone HTML for a single page. Pick the ZIP when the design comes with images or several files.
• Docs and decks export to Word, PDF, Markdown, Google Docs, PowerPoint or Google Slides. They are not web pages, but a PDF can be shared as a link too: see our page on turning a PDF into a link.
• Legacy chat artifacts have controls at the top of the panel to view the code, copy it or download it. Save the code in a file named index.html.

If a legacy artifact is written as a React component rather than plain HTML, ask Claude first: “convert this artifact into a single self-contained HTML file.” The result runs in any browser without a build step.

Step 2: Check the file before it goes public

An artifact contains whatever the conversation gave it, and some of it was never meant for the public. Before you upload, open the HTML in a text editor and search for:

1. Private data. Client names, real prices, email addresses, internal notes, sample rows pasted from a spreadsheet.
2. API keys. If you pasted a key so Claude could test a feature, it may sit in plain text in the JavaScript, readable by anyone who views the page source. Remove it, then revoke it in the service that issued it. Keys designed for the browser, such as a Supabase anon key protected by row-level security, are the exception, and the provider’s documentation says so explicitly.
3. Placeholder metadata. Set a real <title> and meta description in the <head>. That is what people see in their browser tab and in link previews.

Step 3: Upload it and pick an address

On Supadrop, drag the HTML file or the ZIP into the dashboard and choose a subdomain, such as pricing-tool. About thirty seconds later the artifact is live at pricing-tool.supadrop.site, over HTTPS, with no Claude interface around it and no sign-in for your visitors.

For a ZIP, make sure index.html sits at the root of the archive, not inside a subfolder. That file becomes the home page of the site, and every other file gets its own URL next to it.

Step 4: Share the link, the QR code or your domain

Send the link, or download the QR code that comes with every site, as PNG for screens and SVG for print. On a paid plan, connect your own domain (tools.yourcompany.com) and Supadrop handles the HTTPS certificate. Our guide to adding a custom domain to a static site covers the DNS records.

When Claude produces a better version, export it again and drop it on the same site. The URL and the QR code stay the same, so everything you already shared opens the new version.

What keeps working once the artifact leaves Claude

An exported artifact is a static web page: HTML, CSS and JavaScript that run in the visitor’s browser. Everything that lives in the page keeps working exactly as it did in Claude:

• layouts, animations and responsive design;
• calculators, quizzes, forms that compute a result, and games;
• charts drawn from data inside the file.

Two things do not travel with the export. Artifacts that call Claude (to answer a question, summarize text or generate content) run on the viewer’s own Claude account, and artifacts that store data keep it in Claude, with a 20 MB text-only limit. Outside Claude, those calls have nowhere to go. If your artifact depends on them, keep sharing that version inside Claude for people who have an account, and host a static version for everyone else.

Publish from Claude Code or another agent

If you work in Claude Code, Cursor or Codex, the project is already on your disk and the export step disappears. Build it if needed, then upload the HTML file or a ZIP of the build folder like any other site.

To skip the dashboard, Supadrop’s Pro and Large plans include an API and a ready-made skill file, skill.md, that teaches your assistant every endpoint. Store the API key in an environment variable, give the assistant the skill, and ask it to publish: it deploys the files and replies with the live link.

What you have achieved

You now have the artifact at a public address that opens in any browser, with a QR code, and a way to update it without breaking the link. The same steps work for anything an AI tool builds, from a ChatGPT page to an exported app build. Our comparison of the best vibe coding tools shows what each builder exports and how to host it.

Ready to put your artifact on a link anyone can open? Start free with Supadrop: 15 days, no credit card, then from $5/mo billed yearly ($7 month to month). Compare plans on the pricing section.

---

Frequently asked questions