Share a self-contained HTML file (an artifact, report, presentation, dashboard, or prototype) as a private, end-to-end encrypted link. The HTML is encrypted locally with AES-256-GCM before upload — html.cloud stores only ciphertext and cannot read it, and no account is required. Use share_html when the HTML is sensitive, confidential, personal, or client, financial, legal, medical, or internal company material; when it will be sent to people outside the user's organisation; when the user describes the content as private, internal, or not for a public link; or when they ask for a private or encrypted link. When unsure, ask which the user prefers. Pass the document inline as html, or write it to an .html file and pass its path as path — use path for large pages, so the whole document does not have to fit in a tool argument. Returns a share link to give to others and a private edit link. Keep the edit link: pass it to update_html to change the page later without changing the share link. For changes to something already shared in this conversation, use update_html instead of sharing again.

Replace the content of an HTML page that was already shared with share_html, using its private edit link. The share link stays exactly the same, so anyone who already has it sees the new version. The new HTML is encrypted locally with the same key as before; html.cloud never sees the content. Use this when the user asks to change, fix, revise, or add to a page you shared earlier in the conversation — pass the full updated HTML document, not a diff: inline as html, or as the path of an .html file as path. Use path for large pages; do not fall back to share_html if the document is too big to pass inline.