The steps take about ten seconds. The cost is less obvious: unpublishing permanently retires that artifact's ability to be published, and deletes its stored data. Here's how to do it, what it takes with it, and what to reach for when access only needs to end for now.
There's a button in Claude's artifact interface called Unpublish. It does what it says: the public link stops working. It is also, for that artifact, permanent.
Anthropic's documentation states it plainly — once you unpublish an artifact, you cannot publish that same artifact again; you'll need to create a new one. People who run into it describe the Publish button going inactive, with an explanation along the lines that the artifact was previously unpublished and a new artifact is required to publish again.
That's not a bug report. It's the design.
If you're here to press the button, this is where it lives.
On Team and Enterprise plans there's a second, separate action: opening the same Share control gives you an Unshare option in the artifact shared modal, which ends organisational sharing rather than public publishing. They look adjacent and they are not the same lever — see which Claude shares are public and what unsharing actually undoes for the difference in full.
Anthropic's own page on publishing and sharing artifacts is the authoritative source for the current interface, and it's worth a look before you press anything — because of what the next section covers.
Losing the link is the expected cost. Most people press Unpublish knowing the URL will die — that's the point.
The unexpected cost is the storage. Anthropic's documentation notes that unpublishing also permanently deletes all associated storage data, both personal and shared, for artifacts that used persistent storage.
Think about what that covers. An artifact that saved state between visits. A tool colleagues had been entering things into. Anything the artifact accumulated while it was live. Unpublish doesn't quietly park that data somewhere pending your return, because there is no return — the artifact can't be republished, so there's nothing for the data to belong to.
If the artifact holds anything worth keeping, get it out first. Once the button is pressed, that decision has been made for you.
Almost nobody unpublishes because they've decided a piece of work should cease to exist. The reasons are mundane and temporary:
Every one of those is a question about when and to whom access applies. None of them is a question about whether the artifact should permanently lose its capacity to be published.
The mismatch is that publishing offers one lever — on or off, and off is final — for a job that needs a dial. So people pull the lever, because it's the only one there.
If you know at delivery time that access will need to end, or narrow, or change, then the delivery method should carry those controls from the start:
None of that is exotic. It's the ordinary shape of access control — the same shape you'd expect from anything designed for delivering work rather than for showing work.
Export the artifact, host the file, and set the expiry when you send it — so ending access later is a setting, not a one-way door.
Publishing an artifact is a genuinely good feature and this isn't an argument against using it. For a public demo, a tool you want strangers to find, something you're linking from a post — publish it. Reach is the whole point, permanence of the publishing decision is irrelevant, and it costs you nothing.
The friction only appears when the same button is asked to do delivery: a named client, a fixed review window, work that shouldn't outlive the engagement. Then "on forever or off permanently" is the wrong shape, and no amount of care in pressing it makes it the right one.
The practical move is to notice which of the two you're doing before you send anything. If it's delivery, export the file — ask Claude for the full HTML as a single self-contained file if the download button isn't cooperating — and host it on a link that carries its own controls. Sharing a Claude or ChatGPT artifact privately covers that route end to end, and if you want to see who actually opened it, that's a property of the link too.
Unpublish will still be there. You just won't need it.
Claude refuses to share your artifact and suggests publishing a new version — which often doesn't clear it. Here's the diagnosis that actually separates the two failures behind that message, and the export route that doesn't depend on the toggle working.
Not to a public link — on any plan. On Pro and Max, a connector-backed artifact can't be shared at all. Here's the mechanism that makes that rule inevitable, and what to do once you know which page you're actually building.
ChatGPT Sites hosts what you build and gives you access controls — owner only, named workspace members, the whole workspace, or the public internet. There's no rung for one outside client. Here's the shape of that gap and the route round it.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.