Can I add a password to a Claude artifact?

Not with Claude's native Publish button — Claude has no password option. To password-protect a Claude artifact, download the HTML and upload it to ShareDuo, which lets you set a password at upload time. Only viewers who enter the password can see the artifact.

Does Claude's Publish button have password protection?

No. Claude's Publish creates a fully public link — anyone with it can view the artifact. There is no password, expiry, or access control option in Claude's native sharing. If you need those controls, you have to host the artifact somewhere else.

What does a viewer see when they open a password-protected ShareDuo link?

They see a simple password prompt before any content loads. The artifact itself is never sent to the browser until the correct password is entered. You send the password to your viewer separately — by email, DM, or however you prefer.

Can I remove or change the password on a ShareDuo link?

Password protection is set at upload time. To change the password, re-upload the artifact with the new password — you'll get a new link. The old link stops working when you delete it from your manage page.

How to Password-Protect a Claude Artifact

Claude's Publish button creates a public link. Anyone with it can open the artifact — there is no password, no access control, no way to limit who sees it. If you're sharing a client prototype, an internal tool, or a prerelease you don't want forwarded, that's a problem.

ShareDuo solves this with a password field at upload time. The artifact doesn't load until the correct password is entered. This page explains how it works and when to use it. For background on why Claude's native sharing is limited this way, see what "Publish Artifact" actually does in Claude.

Why Claude has no password option

Claude's sharing model is binary: public (anyone with the link) or team-only (behind a Claude login). There is no middle option. The Publish button generates a claude.ai URL — and claude.ai doesn't have a per-artifact password layer. The only access control available is Claude's own account authentication, which requires your viewer to have a Claude account.

That works fine for internal team sharing. It breaks down the moment you want to share with someone outside your Claude workspace — a client, a beta tester, a stakeholder — and you still want some control over who can actually see the content. For the full picture of what Claude's sharing can and can't do, see can I share a Claude artifact?

How ShareDuo password protection works

When you upload an artifact to ShareDuo, there's an optional password field. Set a password, and ShareDuo wraps the artifact behind a prompt — the HTML is never sent to the browser until the viewer enters the right password. You send the password to your viewer separately (email, Slack, whatever channel makes sense). If they don't have it, they see a blank prompt, not your work.

The flow:

Get the HTML from Claude. Click the download icon in the artifact panel, or ask Claude: "Show me the full HTML for this artifact."
Go to shareduo.com. Drop the file or paste the HTML into the text area.
Enter a password in the password field. Any string works — make it something you can share separately.
Click Upload & share. You get a preview URL and a private manage URL.
Send the preview link and the password separately. The link alone is useless without the password — that's the point.

When to use password protection

Client previews. You're sharing a dashboard or prototype before a formal handoff. You want the client to see it, but you don't want it indexed, forwarded to competitors, or discovered by accident. A password means only the people you brief can open it.

Prereleases and beta tools. You've built something — a calculator, a generator, an internal tool — and you're testing it with a limited group before wider release. Password protection keeps it within your test cohort without needing accounts or login infrastructure.

Sensitive demos. Sales demos, investor previews, confidential project mockups. Things that are meant for a specific audience and carry some consequence if they leak before you're ready.

Internal tools that shouldn't be Googled. ShareDuo serves artifacts with a noindex tag by default, so they won't show up in search results. Password protection adds a second layer for anything where obscurity alone isn't enough.

What the viewer sees

When someone opens a password-protected ShareDuo link, they see a simple password prompt — just a text field and a submit button. No ShareDuo branding beyond the minimal prompt, no indication of what's behind the password. The artifact HTML is never delivered to the browser until the correct password is entered, so there's nothing to inspect in the page source.

If they enter the wrong password, they see an error. If they enter the right one, the artifact loads normally — full interactivity, all external scripts (Chart.js, Google Fonts, CDN libraries), exactly as Claude built it.

The alternative: no password, but hidden from search engines

If your goal is privacy-by-obscurity — you don't mind if someone who has the link can open it, you just don't want it discoverable — you don't need a password. ShareDuo serves all artifacts with X-Robots-Tag: noindex by default, so search engines won't crawl or list them. The link is effectively secret as long as you only share it with people you trust not to forward it.

Password protection is for when you need a harder guarantee: even if the link leaks, the artifact doesn't.

Comparison: Claude Publish vs ShareDuo

Sharing feature	Claude Publish	ShareDuo
Password protection	No	Yes
Viewer needs a Claude account	Yes (for most artifact types)	No
Hidden from search engines	No (artifacts may be indexed)	Yes (noindex by default)
Link expiry	No	Yes (1h to 30d)
Update without breaking the link	No	Yes

For a full breakdown of all the differences, see how to share a Claude artifact so it actually works. And if you're deciding between all the sharing options available, see the best ways to share a Claude artifact.