How to Password Protect a Claude Artifact
Table of Contents
The short answer
Claude has no password setting for artifacts. What you can do depends on how you share the artifact today:
- Artifacts start private. You can share one with people that you invite by email, with your organization or with anyone who has the link. Every viewer must sign in to Claude.
- An older artifact published from a chat is different. Anyone with its link can open it without a Claude account. The only way to close that link is to unpublish the artifact.
- If you want to give people a password or an email code instead of Claude sign-in, download the artifact. Host the copy behind Cloudflare Access, Netlify or Vercel.
| How it is shared | Who can open it | Password |
|---|---|---|
| Only you (the default) | You | Not needed |
| Invited by email (beta on Pro, Max, Team and Enterprise) | People signed in to Claude with an invited address | No, Claude sign-in instead |
| Anyone at your organization (Team and Enterprise) | Signed-in members of your organization | No |
| Anyone with the link | Anyone signed in to Claude who has the link | No |
| Older artifact published from a chat | Anyone with the link, no account needed | No |
| Downloaded copy behind Cloudflare Access | People whose email address your policy allows | No, a one-time code by email |
| Downloaded copy on Netlify or Vercel | Anyone who knows the password | Yes, on paid plans |
Step 1: Check who can open it now
- Open the artifact. Click Share. The Who has access setting shows the current audience.
- For an older artifact made in a chat, look at the publishing control. If it shows Unpublish, the artifact is published. Then anyone with the link can open it. Claude lists published artifacts under Artifacts in the sidebar. Look in that list for artifacts that you forgot.
- Copy the link. Open it in a private browser window where you are not signed in. If the artifact loads there, it is public.
Step 2: Restrict it inside Claude
If your viewers have Claude accounts, you can keep the artifact in Claude and limit who can open it.
To make the artifact private again, open it. Click Share. Choose Only you (Pro and Max) or Only people invited (Team and Enterprise). To remove one person, open the access level of that person. Select Remove.
You can also invite named people. Email invitations are in beta on Pro, Max, Team and Enterprise plans. The invited person needs a Claude account under the exact address that you invited. On Team plans, invitations to people outside the organization are on by default. On Enterprise plans, an Owner must turn on Email invitations outside your organization in Organization settings > Artifacts. Invitations are not available for artifacts that connect to other websites or for documents made with Claude Docs.
Viewers can also see more than the artifact. On Team and Enterprise plans, when you share an artifact made in a chat, viewers also get the attachments and files from that chat. Some artifacts keep shared data that every viewer can see, such as items in a shared tracker. Look at both before you add anyone.
To unpublish an older chat artifact, first copy or download its code. Then click Unpublish. The Claude help center gives two warnings. You cannot publish the same artifact again afterward. Unpublishing also permanently deletes the personal and shared storage data that the artifact used. To find out if search engines indexed your old artifacts, see how to find public Claude artifacts in Google.
Step 3: Host a copy behind a password or an email code
Use this method if reviewers do not have Claude accounts, or if you want a password instead of Claude sign-in. The protection covers the copy at its new address only. It does not protect the original Claude link. Restrict or unpublish that link too.
Get the files out of Claude
- For an artifact made in a chat, use the controls at the top of the artifact panel. They let you view, copy or download the code. For a published artifact, Copy copies its code.
- Artifacts made from a template use Export. A design exports as a .zip or as standalone HTML. A document exports to PDF, Word or Markdown (artifact help).
- If you have a single HTML page, save it as
index.htmlin an empty folder. - A React component starts with
importlines and has anexport default. If the code is a React component, it will not run as a plain file. Ask Claude to rewrite it as one self-contained HTML file. You can also put it in a small Vite project. Then runnpm run buildto get static files.
Then find out what will stop working. Features that call Claude, persistent storage and connected apps run through Claude. They use the Claude account of each viewer. Expect them to fail in a copy on another host. Before you send the link, click every control. Remove API keys, personal data and anything else that must stay in Claude.
Option A: an email code with Cloudflare Access
- Upload the folder in the Cloudflare dashboard: Workers & Pages > Create application > Get started > Drag and drop your files.
- In the project, go to Settings > General. Select Enable access policy. This setting alone covers only preview deployments. Extend the policy to the main
pages.devaddress with Cloudflare’s steps. - Add an Allow policy that includes the addresses of the reviewers (Emails) or their company domain (Emails ending in).
- Turn on the one-time PIN login method. Reviewers then get a code by email and do not need an account anywhere.
The Cloudflare Pages password protection guide shows each screen.
Option B: a shared password on Netlify or Vercel
- Netlify password protection needs a Pro plan or higher. Set it under Project configuration > General > Visitor access (Netlify docs).
- On Vercel, Password Protection is under Settings > Deployment Protection. It is a paid option on the Pro plan. It is not available on Hobby (Vercel docs).
Test before you share
Open the new link in a private window. Make sure that the gate (the password or code screen) appears before any content. Make sure that the artifact works after you pass the gate. Also make sure that a direct link to a file inside the folder is protected. Send the password through a different channel from the link.
Which option fits
Choose the option for your audience:
- For a public demo, share it with anyone who has the link, or publish it.
- For colleagues, share it with your organization.
- For a few outside reviewers who use Claude, invite them by email.
- For clients without Claude accounts, or for confidential work, keep the artifact private in Claude. Send a protected copy.
Do not use a long URL that is hard to guess as protection. People forward links and paste them into chats. Link-preview services also fetch them.
Free email addresses
for your AI agents
Each agent gets an address like myagent.x7k2@revdokumail.com. It can receive emails, send replies and store files.
- 3 free mailboxes, each with its own address
- 3,000 incoming and 500 sent emails a month
- 3 GB of storage for attachments and files
- Virus, malware, spam and prompt-injection filter
- Read and reply through API, MCP or CLI
You do not need a card.
Frequently Asked Questions
If I invite someone by email, can they pass the link to a colleague?
They cannot if the access setting of the artifact is Only you or Only people invited. Claude opens the artifact only for a person who signs in with an invited address. The colleague needs a separate invitation. If the access setting is Anyone with the link, each signed-in Claude user with the link can open it.
Can I embed a published artifact on a password-protected page instead?
You can, but it does not protect the artifact. The Claude embed code comes from an older artifact published from a chat. That published link stays open to anyone who has it. A password on your own page hides the embed. But anyone who gets past the password can copy the URL of the artifact from the page source and share it.
Will unpublishing remove the artifact from Google right away?
No. Unpublishing closes the link in Claude. But a search engine can show the old title or snippet until it visits the URL again. Unpublishing also cannot remove copies, screenshots or downloads that other people already made.
History
- August 3, 2026 — Published by Revdoku Content Team
- August 1, 2026 — Reviewed by Eugene Mi
- October 22, 2026 — Last updated by Revdoku Content Team.
Related Articles

Move Exported Grok Website Files to Another Host
Export a Grok Build site to GitHub, deploy it on Cloudflare Pages, Netlify, Vercel or GitHub Pages, test it, then retire the grok.me copy.

Move Exported Claude Artifacts to Another Host
Move a Claude Artifact to Cloudflare Pages, Netlify or GitHub Pages: get the code, build React artifacts, replace Claude-only features, then unpublish.

Move a ChatGPT Site to Another Host
ChatGPT Sites has no documented export. Get the source, and replace storage and sign-in. Test a copy on Cloudflare Pages or Netlify before you switch.