Share HTML that an AI chat wrote for you
You asked for a summary and got something genuinely good: a styled page with a table, a couple of charts, headings that make sense. Then you tried to send it to someone.
The options are all bad. A screenshot loses the table. A copy-paste into email loses the styling. Downloading the file and attaching it produces the message "your browser has blocked this download". Sharing the conversation link shows the recipient your seven earlier attempts, and often asks them to sign up.
Paste it, get a link
- Copy the HTML out of the canvas, artifact, or code block.
- Paste it into Comma.
- Send the URL.
The markup is stored verbatim and rendered in an isolated sandbox, so the page your reader opens is the page you saw — not a reflowed, restyled approximation. Comma does not rewrite AI-generated HTML into its own design system; the document is the document.
If the page was generated by an agent rather than a chat window, the same thing happens over the API or the MCP server — see where should my agent post.
Then the useful part
Sending output is where most people stop. The reason to publish rather than attach is what happens next:
- Comments anchor to the content. "This number is from last quarter" pins to that number. See commenting on HTML.
- Regeneration keeps the URL. Prompt again, update the report, same link — with the old version still in the revision history.
- Readers need nothing. No account with your model vendor, no extension, no download.
- You control who sees it. Private by default; team, domain, or named reviewers per report. See the sharing model.
Limits worth knowing
- HTML body: 5 MB — plenty for a generated page, tight if the model inlined a large image as base64.
- Scripts run, sandboxed, with CDN scripts and styles limited to jsdelivr, unpkg, cdnjs and esm.sh.
- Nothing re-executes. A published page is a snapshot. To refresh it on a schedule, hand the job to a routine.
Try it
Comma is free — unlimited reports, unlimited commenters, unlimited revision history.