You built something in Claude, came back weeks later, and it's gone. Usually it isn't deleted — it's sitting inside a conversation you can no longer find. Here's how to get it back, and the one case where it really is unrecoverable.
You made something in Claude. A dashboard, a proposal page, a small tool for a client. It worked, you showed someone, you moved on. Weeks later you go back for it and it isn't there.
The panic is reasonable and the diagnosis is usually wrong. In most cases the artifact was never deleted, was never corrupted, and is sitting exactly where you left it. What's missing is the conversation, not the work.
The mental model most people carry is that an artifact is a document — something Claude created and filed somewhere, the way a word processor writes to a folder. That model is what makes the disappearance feel like data loss.
The real arrangement is closer to this: an artifact is a rendered thing attached to a moment in a conversation. It updates in place as you iterate, it's re-rendered when you scroll back to it, and unless you take an action to promote it, that conversation is the only place it exists.
Claude's documentation states it plainly — artifacts you create in a conversation don't appear in your sidebar automatically, and the Artifacts section shows what you have explicitly published. That single sentence explains almost every "it disappeared" story. Nothing broke. The artifact was never in the place you went looking.
Search for something only that build would contain. Not the project name you'd give it now, not what you think you titled the chat — a string from inside the artifact. A section heading. The label on a button. A column name. The client's surname if it appeared in the copy.
This matters more than it sounds. Chat titles are generated from the opening message, so a conversation that ended up producing a client dashboard might be titled after whatever you asked first. Searching titles is searching the wrong field.
If you know roughly when, scroll to then. History around a date is a coarse tool but a reliable one, and it beats trying more search terms once the obvious ones have failed.
Check whether you're looking at an old turn. Artifacts update in place, so the version you remember may have been replaced by a later iteration in the same conversation. If the conversation is there but the artifact looks wrong rather than absent, scroll the conversation and check the artifact's own version selector before concluding anything is lost.
If it was published, check the Artifacts section. That's the collection that survives independently of where the conversation sits in your history — which is exactly the property the unpublished ones lack.
If you unpublished it, the link is gone permanently. Claude's documentation says you cannot publish that same artifact again, and that unpublishing also deletes any storage data the artifact was using. We wrote about that trap separately — what unpublishing a Claude artifact permanently takes with it — because it's the one action in this area that is genuinely irreversible.
Worth separating two things that get conflated here. The link is unrecoverable. The content often isn't: if the original conversation still exists, the artifact is usually still rendered in it, and you can copy the work out and rebuild. What you'll have is a new artifact at a new address. Anyone holding the old link has a dead one, and no amount of republishing changes that.
Everything above is recovery. This is prevention, and it's one step.
Ask for the artifact as a single self-contained HTML file, and download it. One file, styles and scripts inlined, no external dependencies. That file opens by double-clicking it, on any machine, with no account and no conversation involved. The export checklist covers what "self-contained" usually fails to include — CDN scripts, fonts, images referenced rather than embedded — because an artifact that looks self-contained and isn't will fail in a quieter way later.
Once the file is on your disk, the disappearance problem is over. The conversation can vanish, the platform can change, you can unpublish whatever you like: you hold the thing.
If you want to check what the file actually renders as before you file it away, you can drop it into a viewer — it renders in your browser without uploading anywhere.
There's a second half to this for anyone who sent that artifact to a client.
A downloaded file solves your copy. It doesn't solve their link. If you shared a published artifact URL and later unpublish it, or the artifact goes away for any of the reasons above, the person you sent it to has a broken link and no idea why. That's the part that costs you something.
Putting the exported file on a link you hold changes what the recipient's link depends on. It points at a file you can replace, re-upload, and keep working — and on miinideck specifically, replacing the file keeps the same URL, so the link in an email you sent in June still opens the current version in December. Free accounts hold one always-on document; the paid tiers drop the forced expiry entirely.
Being straight about the boundary: this is only worth doing for work that someone else needs to keep opening. A scratch artifact you built to think something through doesn't need a hosting decision. And if what you built genuinely needs a server — a database, real accounts, an API key that has to stay secret — no static link solves that, and a platform like Vercel or Netlify is the honest answer. Claude's own documentation is clear that artifacts can't reach backend infrastructure or external networks either, so if you hit that wall inside the artifact, you were always going to need somewhere else to run it.
Claude's behaviour described here was checked against Anthropic's own support documentation on 11 August 2026. Platform behaviour changes; confirm on their side before relying on it.
An artifact that disappeared is usually a conversation you can't find. Search for the content rather than the title, check the Artifacts section if you published it, and accept that an unpublished artifact has exactly one home.
Then take the thirty seconds that makes this the last time: get the file out.
The message is about Anthropic's side, not yours, and it usually clears on its own. The risk isn't the outage — it's what people press while waiting. Here's the safe order of operations, and how to get the work out of the artifact while you wait.
Artifacts stop appearing and every guide says the same four generic fixes. Here's the order that actually separates a setting on your side from an outage on theirs — starting with the one documented cause that produces total failure.
The artifact works in the chat, publishing succeeds, and the link opens to nothing. Three different failures produce that same white screen, and one thirty-second check tells you which one you have.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.