# How to Password Protect a Claude Artifact

> Learn how to unpublish a public Claude Artifact and securely share its export using password or verified-email access.

TL;DR: A publicly published Claude Artifact has no shared-password gate. If the Artifact should not be public, unpublish it. For controlled external sharing, publish permitted exports behind password or verified-email access.

## Claude Artifact password protection options

| Sharing method | Password protected? | Good for |
|---|---|---|
| Unpublished Artifact | Not publicly reachable | Private work in your Claude account |
| Team or organization sharing | Identity-based, where supported | Internal collaboration |
| Publicly published Artifact | No shared password | Open demos and tools |
| Exported Artifact on Revdoku | Yes, password or verified email | Client review and controlled delivery |

Claude’s Publish dialog warns that published Artifacts are available to anyone online and may appear in search results. Your chat remains private; the published Artifact does not.

Our [Google audit of public Claude Artifacts](https://revdoku.com/blog/find-public-claude-artifacts-in-google-and-unpublish-yours/) shows why a public link should not hold a confidential report, proposal, prototype, or customer data.

## Make a Claude Artifact private: check and unpublish

1. Open Claude and select **Artifacts**.
2. Open the Artifact.
3. Find the **Publish** or **Unpublish** control.
4. If it shows **Unpublish**, the Artifact is public.
5. Export or save permitted material.
6. Select **Unpublish**, read the confirmation carefully, and confirm.
7. Open the old public URL in a private browser window.

Claude’s [official publishing guide](https://support.claude.com/en/articles/9547008-publish-and-share-artifacts) documents the Publish and Unpublish flow. Current guidance warns that unpublishing may permanently remove associated persistent storage and prevent republishing the same Artifact. Read the confirmation before proceeding.

Unpublishing removes Claude access, making the Artifact private again. Google may show an old title or snippet until it recrawls the page; copies saved elsewhere remain outside your control.

## Secure a Claude Artifact behind a password

To secure a browser-ready Claude Artifact for external access:

1. Export the HTML, CSS, JavaScript, images, and other required files.
2. Remove secrets and data that should stay in Claude.
3. Upload the folder to Revdoku.
4. Choose **Password** for a shared secret or **Verified email** for identity-based access.
5. Optionally allow only named emails or approved domains.
6. Test the new link while signed out before sharing.

Revdoku password-protects exported Claude Artifact files. It does not lock the existing `claude.ai/public/artifacts` URL.

The protected link can also send visitor notifications and record page, click, and download activity. If the Artifact changes, replace its files at the same URL so the client keeps the link.

See [Claude Artifacts vs Revdoku](https://revdoku.com/compare/claude-artifacts/) for a feature comparison.

## Keep a Claude Artifact public, internal, or client-only?

Publish Artifacts meant for everyone. Use organization sharing for internal workflows. Use protected hosting when external reviewers must pass a password or verified-email check before receiving files.

Do not rely on an obscure URL. Anyone can forward public-by-link content; services may log or preview it, and others may later discover it.

## Bottom line: how to password protect a Claude Artifact

You cannot add a password to an existing public Claude Artifact URL. Unpublish sensitive Artifacts, then publish the export through Revdoku for password or verified-email access, an allowlist, visitor activity, and a stable, updatable link.

Start publishing for free

Connect this AI to Revdoku so it can store files, create, update, and publish websites for me. Read and follow https://revdoku.com/prompt.md. A Revdoku account is required. If I do not have one, send me https://app.revdoku.com/users/sign_up?utm_source=revdoku.com&utm_medium=ai-chat&utm_campaign=connect_ai_first and wait until I confirm signup is complete. For ChatGPT, Claude, or another cloud AI, connect https://app.revdoku.com/mcp and complete Revdoku OAuth. For a local agent, use Revdoku's browser device sign-in and complete the connection in Revdoku. Never ask me for a password or API key in chat, or for a verification code. When Revdoku tools are connected, verify the connection, tell me you’re ready, and ask what I want to publish.

Copy Prompt

or

Create Free Account

## Frequently asked questions

### Can I add a password to an existing public Claude Artifact URL?

No. A published Claude Artifact is accessible to anyone with the link and may also appear in search results. For password protection, unpublish it and host a permitted export behind an access gate.

### How can I tell whether my Claude Artifact is currently public?

Open the Artifact and check its publishing control. If the available action is **Unpublish**, the Artifact is currently published. Confirm by opening its public URL in a private browser window.

### What should I check before unpublishing an Artifact?

Save or export any material you are permitted to retain, then read the confirmation carefully. Unpublishing may permanently remove associated persistent storage and could prevent you from republishing the same Artifact.

### Will unpublishing immediately remove the Artifact from Google?

Unpublishing removes access through Claude, but search engines may continue displaying an outdated title or snippet until they recrawl the URL. It also cannot delete screenshots, downloads, or copies that others previously saved.

### Should I use password or verified-email access for an exported Artifact?

Use a password when a shared secret is sufficient for the intended audience. Choose verified email when you need identity-based access, such as restricting entry to named reviewers or approved company domains.

### Does protecting an exported Artifact also secure the original Claude link?

No. Protection applied by Revdoku covers only the exported files hosted at the new link. You must separately unpublish the original Claude Artifact if it contains material that should not remain public.

### When should an Artifact be public, internal, or client-only?

Keep general demos and tools public when they are safe for anyone to access. Use organization sharing for internal collaboration and protected hosting for clients or external reviewers who need controlled access.

---

[View the canonical page](https://revdoku.com/blog/how-to-password-protect-a-claude-artifact/) · [Browse llms.txt](https://revdoku.com/llms.txt)