Let Claude share your HTML for you
When you've made something with Claude — a report, a proposal, a page — you can just ask Claude to share it privately, and it hands you a link to send on. No saving files, no account, no setup files.
Claude encrypts the page on your computer before it's uploaded, so not even we can read it. See how that works →
Add it to Claude Desktop
One file, one click — Claude Desktop has everything it needs built in.
- 1
-
2
Double-click the downloaded file. Claude Desktop opens and offers to install it. (If it doesn't, open Claude's Settings → Extensions, click Advanced settings, and use Install Extension… under Extension Developer to pick the file — that works even when drag-and-drop doesn't.)
-
3
Click Install. That's it — no accounts, no terminal, no settings to edit. The first time Claude uses it, you'll be asked to allow it; click Allow.
About the red warning. Claude Desktop shows the same "access to everything on your computer" box for every extension installed from a file rather than from its built-in directory — it isn't about html.cloud specifically. This one is open source, about 250 lines you can read on GitHub, talks to one host (html.cloud), and sends only encrypted content. Extensions installed from Claude's directory don't show the warning; we're working on getting listed.
Try it
Make something with Claude, then ask:
Share this privately with html.cloud and give me the link.By default the link expires in 30 days. Want it shorter or permanent? Just say so — “with a 7-day expiry,” or “that never expires.” Claude also gives you a private edit link with each share, so you can replace, re-expire, or delete the page anytime.
Changed your mind about something? Keep talking:
Make the title bigger and add a section on next steps, then update the page.Claude revises the HTML and updates the page in place. The share link you already sent stays exactly the same — whoever opens it now sees the new version.
Artifacts or html.cloud?
Both, and Claude sorts it out. Artifacts stay the default for building pages and for anything meant to be public. html.cloud steps in when the page is sensitive or has to reach someone outside your organisation.
That switch is real — you'll see it when you install the extension (manual setups use
HTML_CLOUD_PREFER=always). More on when to use which →
Using Claude Code or another app?
If you use Claude Code, add it with one command (this path uses Node.js 20+):
claude mcp add html-cloud -- npx -y html-cloud-mcpManual setup for other MCP apps
Any app that supports the Model Context Protocol can run the server via npx.
Add this to its MCP config (requires Node.js 20+):
{
"mcpServers": {
"html-cloud": {
"command": "npx",
"args": ["-y", "html-cloud-mcp"]
}
}
}Questions
Is my HTML really private?
Yes. It's encrypted with AES-256-GCM on your own computer before anything is uploaded. The key to read it lives in the link after the # and is never sent to us, so html.cloud only ever stores scrambled bytes it can't read. The extension is open source, so anyone can verify that.
Do I need an account, or to pay?
No. There's no sign-up for html.cloud and nothing to pay. You just share links.
Do I need to install Node or anything else?
Not for Claude Desktop — it includes everything the extension needs. (The Claude Code and manual setups above use Node.js, which is a free one-time install.)
Who can see a page I shared?
Only people you send the link to — the link is the key. Treat it like a password: share it through a trusted channel, and set an expiry for anything sensitive.
Can I change or remove a page after sharing?
Yes. Just ask Claude to change the page — it updates it at the same share link, so nobody needs a new one. Every share also comes with a private edit link you can open yourself to replace the page, change when it expires, or delete it right away.
Why does Claude Desktop warn that it can access everything on my computer?
Because it's installed from a file, not from Claude's built-in extension directory — Claude Desktop shows that same box for every extension installed that way, whoever made it. It's an honest statement about how extensions run, not a finding about this one. What this extension actually does is public: about 250 lines of open-source code on GitHub, one outbound host (html.cloud), and the only thing it uploads is ciphertext (privacy policy). If you'd rather not install anything, the homepage does the same job in your browser.
Does it work in Cowork?
Yes, in Cowork sessions linked to the computer the extension is installed on — Claude Desktop passes the extension through to the session. It won't appear in cloud-only Cowork sessions that aren't linked to a computer; for those, ask for your share link in a regular chat, or paste the finished HTML into one and ask Claude to share it.
Prefer to do it yourself?
You can drop a file on the homepage or use the command line — same encryption, same private links.