MakeItRun blog

How to Share a Claude Artifact So It Doesn't Disappear When You Delete the Chat

2026-07-06 · MakeItRun team

TL;DR. Copy the HTML out of your Claude artifact, then either paste it at app.makeitrun.ai or ask Claude to publish it straight from the chat through the MakeItRun connector. Either way, you get a live URL in about ten seconds — and unlike Claude's native Publish button, the link doesn't come with a one-way door built in. Claude's own Publish is fine for something disposable. It's the wrong tool the moment you want the link to still work in six months.

Claude already has a button for this. Open the artifact, click the caret next to Copy, click Publish, copy the link — nobody who opens it needs a Claude account. For a one-off share, that's the right tool. Use it.

Read Anthropic's own Help Center article on it, though, and four things stand out that don't matter until the moment they do:

The link is Anthropic's, not yours. Every published artifact lives at a claude.ai/public/… URL. No custom domain, no subdomain, nothing you control.
Unpublishing is one-way. The article states it directly: "Once you unpublish an artifact, you cannot publish that same artifact again." Change your mind and you don't get the link back — you build a new artifact from scratch. If the artifact used Claude's persistent storage, unpublishing deletes that data for good, too.
Team and Enterprise accounts can't publish publicly at all. Same article: "Artifacts created on Team or Enterprise accounts can only be shared within your organization — they cannot be published publicly." Pay for Claude Team, and the Publish button quietly stops doing the one thing you'd want it to do.
No QR code, no custom URL, no version history. The whole flow is three steps — navigate, publish, copy link. Nothing about updating the page later, nothing about rolling back a version.

None of that makes Claude's Publish button bad. It makes it a one-way, Anthropic-hosted, single-use link — and most people don't find that out until they've already unpublished something they needed back.

The fix is the same either way: get the artifact's HTML out of Claude and onto a URL you actually control.

The fast path

Copy the artifact's HTML. In the artifact pane, click the caret next to Copy and choose "Copy code" — or ask Claude to show you the raw HTML if it's hidden behind a rendered preview.
Publish it. Paste the HTML at app.makeitrun.ai, or — if you've added the MakeItRun connector — tell Claude to publish it and it happens without leaving the chat. The same steps work for ChatGPT's canvas output. New to this? /connect walks through all three ways to get a live link.
Get your link. It's live immediately. Pick your own slug and later re-publishes land on the same URL, so there's no new link to redistribute and no unpublish trapdoor. Need a QR for a menu or flyer? Point any QR generator at your URL — that's exactly how we made the one further down this page.

Claude's Publish button, compared honestly

Claude's native Publish button

Zero setup, no account required for whoever opens the link, and it's already sitting inside the product you're using. Genuinely the fastest way to share something you'll never touch again. Weak for anything you want to last — see the four points above.

ShareDuo

Purpose-built for exactly this problem, and it goes further than Claude's own button on features — password protection, view analytics, and an MCP integration that lets Claude push an artifact to it directly from the chat. The catch is by design: links expire, capped at 30 days. That's a real advantage for something meant to disappear (a client review, a one-time demo) and a real limitation for anything you'd want to bookmark or print.

send.co

The strongest permanence story of the group, on paper. Revise the artifact and, per their own copy, "the same link serves the new version" — no republish step required. It also works on Team and Enterprise Claude plans, where native Publish is blocked outright, and it supports custom domains. What their public materials don't spell out: pricing, free-tier limits, or a QR code. You'll also need to install their connector first.

static.app

Not built specifically for Claude, but a legitimate general-purpose static host that happens to accept Claude and ChatGPT output alongside React, Vue, and plain ZIP uploads. It has a real free tier with a custom domain, a one-click QR code, analytics, and password protection — a fuller feature set than most single-purpose tools on this list. Because it's general-purpose, it also comes with a built-in code editor and webhook/Airtable integrations — more surface than most people sharing one artifact actually need.

MakeItRun

Built for one workflow: you have HTML from Claude or ChatGPT and you want a link. Paste it or publish through the chat connector, and re-publishing to your slug updates the same URL for as long as you want it — no 30-day clock, no unpublish lock. The honest gaps: no custom domain yet, no built-in analytics, and QR export is still on the roadmap too (we made the QR below with a standard generator — thirty seconds). If a custom domain or Team-plan compatibility is a hard requirement right now, send.co covers that ground better than we do. A real example, also built in one Claude prompt: a startup dilution calculator, live since the day it was published.

A real artifact, published — not just described

Here's the whole thing end to end. We asked Claude for a small recipe card with a servings scaler and a checkable method — one prompt — then published it exactly the way this post recommends: copy the HTML, paste it in, done.

Nonna's Sunday Sugo — a slow tomato-sauce recipe card. Adjust the servings and every ingredient recalculates; check off what you've gathered and what you've cooked. Interactive, not a screenshot.

See it live: https://rvnqr33buo.clientview.page

Open it, move the servings from 6 to 10, and watch the quantities recalculate. That's what "published" should mean — a link that still works, that you still control, the next time someone asks for it.

FAQ

Does my Claude plan affect whether I can publish an artifact publicly?

Yes. Free, Pro, and Max plans can publish artifacts publicly. Team and Enterprise accounts can only share within the organization — Anthropic's Help Center is explicit that Team/Enterprise artifacts "cannot be published publicly."

What actually happens when I unpublish a Claude artifact?

The link stops resolving, and you can't publish that same artifact again — Anthropic's own guidance says you'd need to create a new artifact from scratch. If it used persistent storage, unpublishing deletes that data permanently as well.

Can I put a Claude artifact on my own domain?

Not through Claude's native Publish button — it's always a claude.ai link. static.app and send.co both support custom domains if that's a hard requirement today; MakeItRun doesn't yet.

Can I publish an artifact without leaving the Claude chat?

Yes, two ways: Claude's own Publish button (with the caveats above), or the MakeItRun connector, which lets you ask Claude to publish directly and get a live URL back in the same conversation.

Built something in Claude or ChatGPT?
Get a permanent URL you control — no unpublish trapdoor.
Get your link →