How to publish HTML from ChatGPT canvas

Why the ChatGPT canvas has no publish button

A canvas renders inside a sandbox. It looks like a finished page on your screen, but there's no "publish" control and no public URL behind it — the canvas only exists inside your ChatGPT session. The one sharing option, a chatgpt.com share link, shares the whole conversation — every prompt, revision, and false start — not the standalone page you built. So the HTML that looked done has nowhere to live once you want to send just that to someone.

The fix is to lift the HTML out of the canvas into a single self-contained file, then publish that file. ilolink is the step that turns it into a URL served like any web page, with the reading captured on the other side.

How to publish ChatGPT HTML

The loop is short:

1. Ask ChatGPT for one self-contained HTML file — a single file with its CSS inline, not a project split across assets.
2. Copy the HTML out of the canvas — select all of it, or use the canvas copy control, so you have the full markup.
3. Paste it, or drop the .html file, into the composer at ilolink.com.
4. Pick a visibility mode — public, unlisted, private (teamspace members only), password, or expiring.
5. Get ilolink.com/<slug> and send it.

The branded link 302-redirects to an isolated render origin, view.ilolink.com, where the doc is served under a strict content-security policy (default-src 'none'). Untrusted AI HTML is sanitized on the way in: javascript:, data:, and vbscript: URLs are dropped, and by default no arbitrary JavaScript runs. A static landing-page mockup renders exactly as designed — the CSS is kept. By default an interactive JS app is shown frozen to its static state rather than executing; if you mark the doc trusted at publish time it runs as-is inside a sandboxed frame on that isolated origin. The cap is 15 MB per doc. For the wider view of getting AI output onto the web, see share AI output as a real link and the best way to share AI-generated HTML.

What you learn after sharing

This is the part ChatGPT doesn't give you. Once the link is out, ilolink shows you how the page was actually read — all cookieless, from a rotating visitor hash, with no fingerprint and no personal profile:

• Views — total, plus approximate unique views (uniques are approximate by design).
• Scroll funnel bucketed at 0 / 25 / 50 / 75 / 100%, so you see where people stop.
• Heatmaps — click and scroll, viewable by device class.
• Reactions and notes — readers can react or leave a short note, no account.
• Comments — threaded, anchored to the doc.

There's more — average time on page, top referrers, countries, device class, 30-day daily views. See analytics, heatmaps, and feedback for the full picture, or open your documents once you've published one.