How we read Anthropic’s page
That is worth saying carefully, because “it does not expire” is a claim about what Anthropic documents, nothing more. Anthropic's help centre page on sharing artifacts is the page that lists every sharing setting, and it describes several ways access can end. None of them is a date. Read on 25 September 2026.
What does end access, according to Anthropic
| What happens | What Anthropic documents |
|---|---|
| You unpublish a chat artifact | An Unpublish button appears after publishing and revokes access. It is one-way: Anthropic says you cannot publish that same artifact again, and that persistent storage it used is permanently deleted. |
| You stop sharing from the Share menu | Set who has access to Only you (Pro and Max) or Only people invited (Team and Enterprise). |
| A Team or Enterprise owner turns off External sharing | Anthropic states that existing public links stop working until it is turned back on. |
| You delete the artifact | Everyone you invited loses access. |
| An Enterprise chat retention period ends | Standalone chats and any artifacts inside them are deleted. The shortest period an owner can set is 30 days, and the default is to keep data indefinitely. |
| A Team or Enterprise artifact retention period ends | Owners can set how long artifacts are kept before automatic deletion, with separate periods for private and shared ones. |
Which plans have a retention setting
Both retention rules are owner settings: chat retention on Enterprise plans and artifact retention on Team and Enterprise. On Free, Pro and Max there is no equivalent setting in the documentation, so nothing removes an artifact on a schedule.
The one thing that really does expire in 30 days
If you invited someone to an artifact by e-mail rather than sending them a link, Anthropic documents that pending invitations expire after 30 days, while accepted invitations do not expire. So the invitation has a clock on it and the access it grants does not. That is the opposite of what most people want when they ask whether an artifact expires.
Why a link that never expires is a problem
A link you sent last year is most likely still open today.
Why that matters
A permanent link is fine for a demo you want the world to keep. It is less fine for a proposal, a pricing sheet or a board update. The version you sent in March is still the version someone can open in November. Claude lets you switch the link off by hand, but nothing lets you put a date on a single link.
For your company
On HTMLRadar’s Team plan, an admin sees every colleague’s links, can switch off a leaver’s links, and colleagues on Microsoft 365 open company-only pages by signing in with their work account.
Set the end date once and the link closes for every colleague on that day; until then, replace the file and the same link shows everyone the new version. See how to share an artifact with colleagues.
$59 a month for up to 3 senders, or $590 a year. Each extra sender is $15 a month, however you pay, up to 20 senders. Readers are always free.
Where HTMLRadar helps, and where it does not
How HTMLRadar helps
HTMLRadar does not change anything inside Claude. It gives you a second route for the cases above: download the artifact as an HTML file, upload it, and send an HTMLRadar link instead. That link carries an expiry date you choose, and switching it off is reversible: switch it back on, or make another link for the same document. You can also replace the file behind a link you have already sent, so the recipient gets the current version rather than March's.
Where it does not help: if the artifact needs Claude to run (an app that asks Claude questions, reads your connected tools, or keeps stored data), Anthropic runs it on its own infrastructure and an exported HTML file will not carry that behaviour with it. HTMLRadar is for the self-contained page.