Claude Artifacts: Sharing, Sign-In, and Expiring Links
A Claude artifact is a document, design, code output, or interactive tool created beside a conversation. A shared artifact is not always a public website. The first check is whether your reader needs a Claude account, an invitation, or a different permission.
Does a Claude artifact expire?
There is no general artifact-expiry period stated in Anthropic's sharing guide. Pending email invitations expire after 30 days. Accepted invitations do not expire. Access can still end if the artifact is deleted, access is removed, or organization settings change. An invitation deadline is not a promise that the underlying artifact will stay available indefinitely. Source: Claude sharing documentation.
For a broken link, check these in order:
- Ask the owner to open the artifact from their account.
- Check whether the link is an invitation that was never accepted.
- Confirm that the recipient signed in with the invited email address.
- Review the artifact's access settings and any organization restrictions.
- Test again as the intended recipient, not only as the owner.
Do not make confidential work public just to clear a permission error.
Can someone open it without a Claude account?
Current shared artifacts require a Claude account. A legacy artifact published from a chat is the documented exception. Link access does not mean anonymous access. Open Share to inspect permissions before sending a link. Features that depend on Claude or connected services have further sharing restrictions. Source: Claude sharing documentation.
If a reader needs only a finished browser report or prototype, a separately hosted HTML version may fit. That requires portable files you own or may publish. It does not bypass Claude's permissions. See the HTML workflow below.
What is a legacy artifact?
Anthropic calls artifacts made in a chat before September 16, 2026 legacy artifacts. Their publishing workflow differs from current artifacts. Check the artifact type before following an older tutorial. Source: Claude artifact documentation.
What can each plan do?
As checked on October 29, 2026, all Claude plans can create artifacts in chat and use Docs, Slides, and Design templates. Dashboards, connected apps, and persistent storage require paid plans. Motion is limited to Team and Enterprise. Features can also depend on organization settings. The current feature table is the source for plan changes.
Stored data is a separate concern from visible code. Claude supports personal or shared artifact storage, with a 20 MB text-only limit. A code copy does not by itself copy that stored data. Check who can see shared information before adding it. Source: Claude artifact documentation.
Can I share an HTML version without reader accounts?
Use this route for a self-contained report, calculator, or prototype whose approved behavior can run in a browser. Keep native Claude sharing for collaboration or functions that still depend on its services.
Ask for a portable version of your approved work:
Return this approved report or prototype as finished browser files.
Include index.html, CSS, JavaScript, and permitted local assets.
Keep the facts and behavior unchanged. List anything that cannot transfer.
Do not use external CDN scripts, private keys, or Claude-only services.
Do not publish anything. Give me the files and a test checklist.
This prompt does not guarantee that every artifact can be exported. A React source file needs a build before it becomes a finished website. Connectors, stored data, and AI calls need separate replacements. Check hidden data and attachments as well as the visible page.
For compatible files, open Figment's HTML upload. Sign in, upload the files, check the preview, and approve publication. Readers of the public URL need no Figment or Claude account. Uploading does not require a Figment AI call; optional AI editing is paid. Limits are 100 files, 2 MiB per file, and 10 MiB total. Bundle scripts locally. ZIP uploads, server code, and secrets are not supported.
Figment app links are for sharing, not search-indexed websites. App pages use noindex, and custom domains are not supported on this path. Unlisted previews and public links are not confidential storage. For an indexable website, see the static website publishing guide.
Test the published link in a signed-out browser. Check every chart, filter, calculation, and navigation link. If the result still needs Claude, use native sharing or replace that dependency before you call it standalone.
