How to Share a Claude Artifact as a Password-Protected Website

Claude can build a complete HTML page inside a chat: a landing page, a small tool, or an interactive demo. For Free, Pro, and Max users, the Publish button creates a link that anyone can open. Team and Enterprise artifacts stay within the organization. Neither option gives you a shared project password, so a self-contained HTML artifact may need a different home before you send it to a client.

What you'll need

• A self-contained HTML artifact. React components, AI-powered artifacts, persistent storage, and MCP-backed artifacts need a different export or runtime.
• A way to zip a single file. Every OS has one built in.
• Two minutes.

Step 1: Get the HTML out of Claude

In the artifact panel, use the download option if it gives you a standalone .html file. If it does not, the artifact is not automatically portable through this workflow. You can ask Claude to make a self-contained HTML version, but treat that as a new static implementation and test it before sharing.

Step 2: Name it index.html

Rename the downloaded file to index.html. PreviewSend looks for an index.html at the root of your upload to know what to serve.

Step 3: Zip it

A single file still has to go inside a ZIP:

zip site.zip index.html

(On Mac or Windows, right-click the file and use "Compress" or "Send to → Compressed folder.")

Step 4: Upload and lock it down

1. Sign up for PreviewSend. Eligible first-time owners get a one-time 14-day Pro trial on their first workspace without entering a card. Afterward, Free limits apply: the most recently updated site stays live and excess sites are archived.
2. Create a project and upload site.zip (up to 100 MB compressed). You get a live link immediately.
3. Open the project settings and add a password. Passwords are available on the Free plan. This is a server-side gate, not a prompt written into the page. If you've tried the JavaScript version of a password, why that distinction matters for any static site is worth two minutes.
4. Send the same link for review. New projects enable account-free pinned comments by default, so feedback stays attached to the artifact version the client saw.

Every PreviewSend project is unlisted by default, separate from the password. It gets a globally unique PreviewSend URL and an X-Robots-Tag: noindex header that asks supporting search engines not to index the response. Anyone with the link can still open it. Add a password when you need to limit who may open the page.

Updating the artifact later

If you keep iterating in Claude, download the updated self-contained HTML, re-zip it, and upload it as a new version on the same project. The link your client already has keeps working. Earlier versions remain in version history within your plan's retention, and the file-level version diff is available on Pro, Agency, or an active Pro trial. To put one back, re-upload that saved build as a new version.

A multi-file project can use the same upload flow only after its build produces static files with an index.html entry point. Hosting a compatible Lovable build without Lovable's hosting shows that version of the workflow. If a hosted page loads without its styling, the guide to hosting a static ZIP explains the usual path problem.