How do I share something I built in Gemini Canvas?

Gemini's own share button publishes a public link to the canvas, which is fine for showing it off. For review, copy the HTML out of the canvas code view, paste it into Comma, and send that URL — readers see the rendered page and can pin comments to any paragraph or table cell without an account.

Why not send the Gemini share link?

It is public to anyone who has it, it has no comment layer, and it points at a conversation that keeps changing as you keep prompting. A published report is a fixed version you chose, with access you control, and later versions arrive as revisions at the same URL.

Will the page still work outside Gemini?

If it is plain HTML, CSS and JavaScript, yes. Comma runs scripts in a sandboxed iframe and allows jsDelivr, unpkg, cdnjs and esm.sh for libraries like Chart.js, D3 or Tailwind's CDN build. If Canvas produced a React component, ask Gemini for a single self-contained HTML file first.

What about pages Gemini CLI produces?

The terminal agent can publish directly: attach Comma as an MCP server in ~/.gemini/settings.json and the agent returns a URL instead of pasting output. See the Gemini CLI guide.

Yes. Unlimited reports and unlimited commenters on the free plan.

Share what Gemini Canvas built

Canvas is good at the thing that used to take an afternoon: "turn this spreadsheet into a dashboard", "make an explainer page for the new pricing", "lay out these survey results with charts". The page renders beside the chat, it looks finished, and now it needs to go to someone who has an opinion about it.

The three ways it usually goes

Share the chat. Gemini's share button makes a public link. Anyone who gets it can open it — including anyone it gets forwarded to — and there is nowhere for the reader to say this number is wrong except in a separate message that doesn't point at anything.

Screenshot it. The charts become pixels, the table stops being selectable, and anything below the fold is gone.

Download the file and attach it. The recipient's mail client blocks or strips it (why), or they open it and see source code instead of a page (why).

Take the page out of the conversation

Open the canvas and switch to the code view.
If the result is a React component rather than an HTML document, ask: "Rewrite this as one self-contained HTML file with inline CSS and JavaScript."
Copy the code and paste it into Comma, or check it first in the free HTML viewer.
Send the link.

The markup is stored as-is and rendered in a sandbox with scripts on, so charts and filters behave the way they did in Canvas. Chart.js, D3, Plotly and similar libraries load from the CDNs Comma allows (jsDelivr, unpkg, cdnjs, esm.sh). What won't work is anything that called a private API from the browser — it never had credentials outside Gemini either.

What the reviewer can do that they couldn't before

Comment on the exact line. Select the paragraph, the table cell, the chart caption, and pin a thread there. No account needed — commenting on HTML.
See only what you meant to send. Not the eleven drafts above it in the chat.
Open it anywhere. Same rendering on a phone as on a laptop, and the link unfurls with a title in Slack and Teams.

And you can choose who that is: public, password-protected, invite-only, or limited to your team or email domain — sharing options.

When you revise it

Take the comments back to Gemini, get the new version, and update the same report. The link you already sent now shows the fix; the old version is still in the revision history, and any two versions diff. Open threads carry across, so reviewers can check their point was addressed and resolve it.

If Gemini is running as an agent

Gemini CLI can skip the copy step entirely: attach Comma's MCP server, put the rule in GEMINI.md, and the agent publishes finished work and replies with a URL. On the next run it can read the comments and respond to them.

Try it

Publish your Canvas page →