A pricing proposal for one client — rates and margins included.
Only the client can open it, and it can expire when the deal closes.
Share an HTML file in seconds. Private by design.
AI now hands you reports, proposals and dashboards as HTML — often full of numbers you’d never post publicly. HTML Cloud sends them as an encrypted link, not a public page.
Drop an HTML file here
or
or from your terminal: npx html-cloud ./file.html
Real situations
AI makes the page. Sending it shouldn’t make it public.
The monthly investor update, with burn and runway in it.
One private link for every investor. Fix a typo and it updates in place.
A landing page the client wants to click through before launch.
Opens like the real site — for nobody but the client.
A dashboard of company numbers for a partner outside your workspace.
No account needed to open it. Delete it when the project ends.
The 3 a.m. incident report a customer is waiting for.
A clean, readable report that expires in 7 days.
Works inside Claude
Made it with Claude? Ask Claude to share it.
Claude encrypts the page on your computer and hands you a private link. Ask for a change later and the same link shows the new version — nothing to re-send.
- Make it with Claude
- Ask Claude to share it
- They open the link
- Update, same link
Claude Desktop and Claude Code · free · no account
Why not just publish the artifact?
Publishing is right for pages meant for everyone. For the ones that aren’t:
- Encrypted, not just private A shared artifact lives on Anthropic’s servers as a normal page. html.cloud only ever holds ciphertext — not even we can read it.
- No Claude account to open it Outside your organisation, an artifact needs a public link (an admin setting on Team and Enterprise) or a Claude account for each reader. An html.cloud link opens in any browser.
- Gone when you say so Artifact links stay up until you unshare them. html.cloud links can expire after 7 or 30 days — or never — and you can delete one anytime.
// under the hood
The key lives in the link. Never on our server.
Your browser encrypts the file before upload, and the only key goes after the
# — the one part of a URL browsers never send to a server.
- Your browser shreds the file with a fresh 256-bit key
- Only the scrambled bytes are uploaded
- The key travels in the link you send — never through us
- Their browser fetches the bytes and unlocks them with the key
https://html.cloud/v/kT4eN7xQ/q3-report#b3FvXy9Lm2…Qe2k
- /v/kT4eN7xQ which file — all we can look up is its ciphertext
- /q3-report optional readable name, purely cosmetic
- #b3Fv… the 256-bit key — stays in the browser, never reaches us
// in your browser — nothing below leaves it unencrypted
const key = crypto.getRandomValues(new Uint8Array(32)) // 256-bit
const blob = AES_256_GCM.encrypt(file, key) // Web Crypto, no libraries
POST /api/documents { blob, editHash } // nothing readable
return `html.cloud/v/${id}#${key}` // the key rides after #Private HTML file sharing, in plain terms
HTML Cloud (html.cloud) shares a single HTML file through a private link. The person you send it to just sees the page in their browser: no download, no sign-up, nothing to install on either side. And because the file is encrypted before it leaves your machine, not even we can read it.
- AES-256-GCM
- encrypted in your browser, before anything is uploaded
- Key after #
- the decryption key rides in the link — browsers never send it to a server
- 0 accounts
- no sign-up for you, none for the person you share with
- 7 / 30 days
- optional expiry — or replace and delete the file without changing its link
When to use it over the usual routes
- Netlify Drop & CodePen put your file at a public URL anyone can stumble onto
- Google Drive & Dropbox make an HTML file download instead of open as a page
- Email attachments .html files are often blocked or flagged outright
- html.cloud a private, encrypted link that renders as the page