What happens when you unpublish a Claude Artifact
Two things happen, and both are permanent. The public link stops working, and if the artifact used persistent storage, every stored record is deleted, personal and shared alike, with no export. You also cannot publish that same artifact again, ever. Unpublishing is a one-way door, not a pause button. If you want the artifact offline for a while, or you want the data first, do that work before you click Unpublish, because there is no undo and no support path back.
Last checked against Anthropic's documentation on . Claude changes often. If something here no longer matches the help centre, the help centre is right.
What unpublishing does, exactly
Anthropic's help centre is unusually blunt about this, which is to its credit. Both sentences below are worth reading twice.
Unpublishing also permanently deletes all associated storage data (both personal and shared) if the artifact used persistent storage.
Publish and share artifacts, Claude Help Center
Once you unpublish an artifact, you cannot publish that same artifact again.
Publish and share artifacts, Claude Help Center
Read together, those two lines mean the following:
- The link 404s for everyone who has it, immediately.
- Stored data is deleted, not archived. Personal storage and shared storage both go.
- There is no export step in the flow, and no prompt warning you that data is about to be destroyed beyond the confirmation itself.
- That artifact can never be published again. Not tomorrow, not after support intervenes.
- Anything that linked to the URL, a message, a doc, a bookmark, a QR code on a printed sheet, is now broken and cannot be repaired by republishing.
Before you unpublish: how to get your data out
There is no export button, so you have to build one, and you have to do it while the artifact is still published. Storage only answers on the published page, so an export control added and tested in the preview pane will read back nothing and convince you the data is already gone.
- Ask Claude to add an export control. In the same conversation, ask for a button that reads every key out of both personal and shared storage and dumps the result as JSON into a textarea on the page.
- Republish the artifact. The new version has to be live for the storage calls to work.
- Open the published link, not the preview. Click the button and copy the JSON out.
- Do it once per person, if you used personal storage. Personal storage is per viewer, so your own copy of the export sees only your own rows. Other people's personal data is genuinely not reachable from your account, which is the point of it.
- Save the artifact's source too. It is in the conversation. Once the artifact is gone, rebuilding from a description is much worse than rebuilding from the code.
That last point about personal storage is the honest limitation of any export you can do: you can recover the shared pool in full, and your own personal pool, and nothing else. If other people have private data in that artifact, unpublishing destroys it and no one, including you, can get it back.
What people actually want, and what to do instead
Most people who search for how to unpublish do not want the outcome unpublishing produces. Find your row.
| What you want | Does unpublishing do it | Do this instead |
|---|---|---|
| Take it down temporarily | No. It is permanent, and you can never republish it | Leave it published and stop sharing the link, or publish a replacement version that shows a short notice |
| It has private information in it | Yes, and this is the right tool. The data is destroyed with it | Unpublish now, then rebuild elsewhere. Assume anyone who had the link may already have a copy |
| Stop people editing the shared data | Yes, but it also deletes the data and kills the link | Publish a new read-only version of the artifact instead |
| Fix a mistake in it | No, and it costs you the URL forever | Publish an updated version. Publishing again updates the same link |
| Hand it over to someone else | No. Nobody can use it after you unpublish | Ask them to open it and copy it into their own conversation while it is still live |
| Move it somewhere with real accounts | No, and doing it first destroys the data you were migrating | Export the data, rebuild it as a hosted app, and only then decide whether to unpublish |
The republish trap, and the only workaround
The rule is per artifact, not per URL: that particular artifact is finished. What still works is creating a new artifact from the same code.
- Copy the artifact's source out of the conversation before you unpublish, or from a version you still have.
- Ask Claude to create a fresh artifact from that source.
- Publish the new one. It works normally, including storage.
- It gets a new URL. Every existing link, bookmark and printed QR code still points at the dead one, and there is no redirect.
- Its storage starts empty. The old data is gone and cannot be restored into it.
So the workaround recovers the software and not the data or the address. If the address matters, which it usually does the moment more than three people have it, that is the strongest argument in this whole guide for not putting anything durable behind a link you can permanently destroy with one click.
Why the destructive behaviour is partly a feature
It is worth being fair here, because the design has a real virtue that hosted platforms, ours included, do not match.
- Nothing outlives your decision. When you unpublish, the data is actually gone. There is no forgotten copy sitting on a host you stopped paying attention to, no orphaned database, no export in a bucket somewhere.
- There is nothing to clean up. No account to close, no bill to cancel, no retention policy to read.
- It is a genuinely fast privacy lever. If you published something you should not have, one click destroys the page and its data together. Most hosting platforms make that harder, not easier.
If you are unpublishing because something private got out, that behaviour is exactly what you want and you should use it now rather than reading the rest of this page.
If the thing turned out to matter
The recurring shape of this problem is that an artifact built as a throwaway became load bearing. Fifteen people use it every week, the link is in a group chat, and it now lives one confirmation dialog away from permanent deletion with no backup.
Homespun is where the same agent that built the thing can host it. People sign in with their email, so the app can tell who is who and every row remembers who created it; permissions are set per collection, so some people can approve and others can only submit; and the agent keeps read and write access to the collections it is allowed, so it can keep working on the data instead of handing you a page and walking away. It is free today, and there is no paid plan to buy.
| Published artifact | Homespun app | |
|---|---|---|
| Taking it offline | Permanent, deletes the data | Reversible, the data stays |
| Getting the data out | Only if you build an export first | Export the collections whenever you like |
| Republishing at the same address | Impossible | Normal, the URL is stable |
| Who can delete everything | Anyone who can reach the Unpublish button | The owner, deliberately |
| Restoring after a mistake | No path at all | The data was never deleted |
None of that makes an artifact the wrong choice for what an artifact is for. It makes it the wrong place to leave something fifteen people depend on.
Questions people ask next
Can you republish a Claude Artifact after unpublishing it?
No. Anthropic states that once you unpublish an artifact, you cannot publish that same artifact again. The workaround is to create a new artifact from the same source code and publish that, which gives you a new URL and empty storage.
Does unpublishing delete the artifact itself?
The artifact stays in your conversation, so you keep the code and can still view it yourself. What goes is the public link and, if it used persistent storage, all of the stored data for every viewer.
Can you recover data after unpublishing an artifact?
No. The deletion is permanent and there is no export or restore path, so anything you did not copy out before unpublishing is gone. This applies to both the shared pool and every viewer's personal pool.
How do you take an artifact offline temporarily?
You cannot, at least not with unpublish, which is permanent. The practical substitute is to publish an updated version of the artifact that shows a short notice instead of the content, then publish the real version again later.
Does anyone else get warned before I unpublish?
No. There is no notice to viewers, no grace period and no way for someone holding the link to be told in advance. The link simply stops working the moment you confirm.
Is there a way to see who used the artifact before I unpublish?
No. A published artifact has no viewer identity, so there is no list of people to warn and no record of who wrote which stored record. If you need that, you need an app with real accounts rather than an artifact.
Primary sources
Every claim about Claude on this page comes from Anthropic's own documentation, quoted rather than summarised so you can check it yourself.