Share an internal HTML document securely
Share an internal document, dashboard, or runbook with your team through a zero-knowledge encrypted link. It's encrypted in your browser, can expire automatically, and is never readable by us.
Keep internal work off public URLs
Internal HTML — a status dashboard, an incident runbook, a draft spec — shouldn't sit on a public address where it could be found, and not every team wants it stored in a third party's plaintext. html.cloud encrypts the file on your device, so the server only ever holds ciphertext, and gives you a link that opens the page. Set it to expire so stale material doesn't linger.
Why not the company wiki or a Drive link?
The usual homes for internal HTML each have a catch. A wiki or intranet often can't render a self-contained HTML file with its own scripts and styles — it strips them, so your dashboard or runbook arrives broken. A Google Drive or SharePoint link keeps the file intact but pulls the reader into an account and a permissions dialog, and it stores your document in readable form on someone else's servers. html.cloud renders the real file exactly as built and holds only ciphertext, so it's a fit for the in-between case: something you need a colleague to see right now — not something that belongs in a permanent, access-controlled knowledge base.
Because the link is the credential, treat it like one: send it over a channel your team already trusts (not a public post), and set an expiry on anything sensitive so an old link can't be reused months later.
How it works
-
1
Drop your HTML file. Your browser encrypts it with AES-256-GCM before anything is uploaded.
-
2
Get a private link. The decryption key sits after the
#in the link and never reaches our servers. -
3
Share it. Anyone with the link sees the page. Set it to expire, replace it, or delete it anytime.
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
Is html.cloud safe for internal documents?
It's zero-knowledge — encrypted in your browser with AES-256-GCM before upload, with the key never reaching the server. Since anyone with the link can open it, share the link over a trusted channel and set an expiry for sensitive material.
Can I make an internal document expire automatically?
Yes — set it to expire after 7 or 30 days, keep it indefinitely, or delete it anytime.
Who can access the document?
Anyone with the full link, including the part after the #. The link is the credential,
so distribute it through trusted internal channels and lean on expiry rather than secrecy alone.