How to Unpublish a Claude Artifact — and Why You Only Get One Shot

Unpublishing is quick: open the artifact, find the publish control you used to create the link, and turn it off. The link stops resolving.

The reason this deserves a page rather than a sentence is what happens next — or rather, what can't. Per Anthropic's documentation, unpublishing an artifact is permanent. That specific artifact cannot be published again, and the data stored with the published version is deleted. There is no re-publish button waiting for you to change your mind.

That makes unpublishing less like toggling a setting and more like deleting a file. Worth two minutes of thought before you click.

Before you unpublish, do these three things

1. Save the code. Use Copy or Download on the artifact panel first. The conversation usually still holds the artifact, but "usually" is doing work there — chats get deleted, projects get archived, and if you lose both the published version and the source you're asking Claude to rebuild something from memory. Thirty seconds now.

2. Find out where the link is. Search your sent mail, Slack, and any ticket system for the URL. Anyone who saved or bookmarked it is about to hit a dead link with no explanation. That's fine if the point was to cut off access; it's an unpleasant surprise if the page was a shared reference and you just wanted to move it.

3. Decide whether you need a replacement link. This is the one people skip, and it's the one that hurts — because after unpublishing, the same artifact can't go back up. If a live page still needs to exist somewhere, set that up first.

If you're unpublishing to move the page somewhere else

Do it in this order, and there's no gap where the page is unreachable:

1. Copy the artifact's code from the panel.
2. Paste it onto a new link and confirm it works — JavaScript runs, so interactive artifacts stay interactive.
3. Send the new link to anyone still using the old one.
4. Then unpublish the Claude version.

The reason to move rather than just take it down is usually that you want the lifecycle in your own hands: a link you can update in place, take down and put back up, put a password on, or point at a custom slug. Claude's publish is deliberately simple, and one-way unpublish is the price of that simplicity.

If you're unpublishing because it shouldn't have been public

Then unpublish immediately — the permanence is working in your favour here, and nothing above should slow you down.

But be clear-eyed about what unpublishing does and doesn't achieve. It stops the URL resolving from now on. It does not retract anything already read, copied, screenshotted, or remixed while the link was live. Claude users who opened a published artifact could take a copy into their own conversation, and those copies are theirs.

So treat unpublishing as stopping further exposure, not as undoing it. If the content was genuinely sensitive, the follow-up work — rotating anything that leaked, telling whoever needs telling — isn't optional just because the link is dead.

Why this catches people out

Every other "publish" button most of us use is a toggle. Google Docs sharing, Notion's public pages, a WordPress draft — all of them flip back and forth freely. Claude's doesn't, and nothing in the interface at the moment of clicking makes that obvious.

The practical rule: treat Claude's Publish as a one-time decision per artifact. If you expect a page's visibility to change over its life — public for a launch, private afterwards, public again for a retrospective — that page wants a host with a reversible switch. A password is one version of that switch; a link you can take down and restore is another.

Related

• Are Claude artifacts public? — what a published link exposes, and to whom
• How to publish a Claude artifact — the two routes and when each fits
• How to download a Claude artifact — getting the code out before you unpublish

Bottom line: unpublishing takes one click and can't be undone — the artifact can't go back up and its published data is gone. Copy the code first, and if the page still needs to exist, put it on a link you control before you switch the old one off.