Your uploads encrypted in your browser Open source
Use case

Share a Claude artifact privately

Claude built you an HTML artifact — a report, a dashboard, a little app. Drop it on html.cloud and get a private link you can send to anyone. It's encrypted in your browser before upload, with no account and no public URL.

Using Claude Desktop? Skip the download entirely — connect html.cloud to Claude once, then just ask it to share what it made. Let Claude share for you →

Why not just send the file?

A Claude artifact is a self-contained HTML file, which is awkward to pass around. Emailing it as an attachment often gets the file blocked or flagged; dropping it on a public host like Netlify Drop puts it at a public URL anyone could stumble onto. html.cloud is built for exactly this: a private link that opens the page, encrypted so that only the people you send it to can read it.

From Claude to a private link

  1. 1

    Get the artifact out of Claude. Open the artifact and download it as an HTML file — or copy the code and save it into a file ending in .html. Any Claude plan works; there's nothing to configure.

  2. 2

    Drop it on html.cloud. Your browser encrypts the file with AES-256-GCM before anything is uploaded, then hands you a private link. The decryption key sits after the # in that link and never reaches our servers.

  3. 3

    Send the link. The recipient sees the artifact as a working page in any browser — no account, no download, no Claude access needed. Set the link to expire, or replace the file later without changing the link.

What about Claude's Publish button?

Claude can publish an artifact to a public URL, and for something meant to be public that's the right tool. The difference is exposure: a published artifact is viewable by anyone the link reaches — forwarded, pasted into a chat, or found later — and the file sits on the host's servers in readable form. html.cloud is the opposite default: the file is encrypted before it leaves your machine, we store only ciphertext, and the link can expire or be deleted when the conversation is over. For a client deliverable, an internal dashboard, or anything with real data in it, private-by-default is the safer starting point.

Private by design

The encryption happens in your browser before anything is uploaded, so we only ever store ciphertext — never the file, the filename, or the key. The decryption key lives in the link, which browsers never send to a server. Not even we can read your files. Read how the encryption works →

FAQ

How do I share a Claude artifact privately?

Download the artifact as an HTML file, then drop it on html.cloud. Your browser encrypts it and gives you a private link — send it to anyone, and they open the page with no account and no public URL.

Can the person I share with see my Claude account or conversation?

No. html.cloud only has the single encrypted file you upload — no link to your Claude account or chats. The recipient sees just the page.

Do I or the recipient need an account?

Neither — there's no sign-up. You drop the file and share the link; anyone with the link can open it.

Why not just use Claude's Publish button?

Publishing puts the artifact at a public URL — right for things meant to be public, but anyone the link reaches can view it and it isn't encrypted. html.cloud encrypts the file in your browser before upload, so only people with your link can read it, and the link can expire or be deleted.