Shareable vs sending an HTML file

Sending an HTML file directly works only when the page is a single self-contained file and the recipient is comfortable opening raw HTML. The moment the artifact has separate assets, needs to stay private, or should look like a finished deliverable, a share link wins — it keeps the page intact, hides the source, and updates in place.

Both options start from the same place: an index.html your agent produced. The difference is everything that happens after you hit send.

The catch with a raw attachment

• Assets break.If the page references a separate CSS file, a chart script, fonts, or images, those don't travel with a single .html attachment — the recipient sees an unstyled or broken page.
• It opens as code. Depending on their mail client or browser settings, a .html file may download as source or render with security warnings rather than just showing the page.
• It's editable and losable.The file lives in someone's Downloads folder. It can be changed, renamed, or lost, and there's no way to update it once it's sent.
• It looks like a dev artifact. A loose HTML file reads as something technical, not a polished report.

What Shareable changes

Shareable takes the same HTML — plus its assets or a zip — and serves it at a stable link that renders in a sandboxed viewer. Local asset references are rewritten to private render URLs, so nothing breaks. The recipient gets a clean page, not files; the link is unlisted and noindex; and you can add a password. Update the artifact and the same link shows the new version.