How to share a ChatGPT Canvas (or Sites page) with a client — without a ChatGPT seat

You asked ChatGPT for a landing page, a pricing table, or a mini-site in Canvas. It built useful HTML in minutes. Now a client needs to open it, leave feedback, and come back after you change it. The client is outside your chat — they should not need a ChatGPT seat or any AI tool. Feedback should happen on the live page, not in email. Docklet is built for that handoff: a universal link anyone can open, comments in place, and publish from any MCP-connected assistant.

When ChatGPT's native share is the right choice

ChatGPT Canvas and Sites are strong fits when the recipient is already in the conversation, when you want a quick look inside ChatGPT with no review loop, or for a one-off share you will not revise. Native sharing keeps everything in the ChatGPT workspace and works well for those jobs.

Paste-and-host tools such as Netlify Drop, NudgeHost, PreviewShip, and Static.app turn HTML into a URL quickly — a complementary path when you need public hosting without a review workflow. For a deeper comparison of hosting paths, see publish without Netlify Drop (the same paste-host pattern applies to Canvas HTML).

When a client is outside the chat

As of September 2026, OpenAI's documentation describes ChatGPT Canvas and Sites as workspace features inside a ChatGPT session. Sharing a conversation or Canvas view typically ties the recipient to ChatGPT — they open inside the product or need an account to participate. That default is built for collaborators in the chat, not for a client who should simply open a page in their browser, leave comments, and return when you ship v2.

When your recipient is a teammate already in the ChatGPT thread, native share may be all you need. When the recipient is a client outside the chat, Docklet adds what that handoff needs: they open without your AI tool, comment on the page, and you publish from any MCP client — with email allowlist and the same URL when you ship a revision.

What a client-ready link needs

Three things matter for a client outside the chat:

1. Open without the tool — a normal browser URL; no ChatGPT, Claude, or Cursor seat required.
2. Feedback on the page — inline comments on the live artifact, not a side channel.
3. Any AI tool — you publish via MCP from whatever generated the HTML; the link is not locked to one vendor's share dialog.

Supporting details: email allowlist (not public by default), analytics on opens, and the same URL when you publish a revision.

Your AI made something useful. Docklet makes it usable. Publish AI-generated pages, guides, demos, and mini-sites as live links with comments, analytics, permissions, and version history — in-place right from your AI tool.

How to publish with Docklet

Three paths — all land on the same live URL:

1. From ChatGPT (MCP) — Connect the Docklet connector (endpoint https://app.docklet.io/mcp) and ask ChatGPT to publish the Canvas HTML. ChatGPT calls publish_website and returns the link. See also the Claude setup guide — the MCP endpoint and flow are the same across tools.
2. Copy from Canvas, paste in console — Open the Canvas code view, copy the HTML, and paste it in the Docklet console. No MCP required for a first publish.
3. From the Docklet API — Upload files or use a personal access token for programmatic publish.

Set visibility to public, any signed-in user, or selected users (email allowlist — the usual default for client work). The Free plan includes the email allowlist and covers your first five Docklets. Pro is $4 per user per month and adds private visibility, a custom domain, and up to five versions with rollback.

A concrete client loop:

1. Publish the Canvas HTML to Docklet.
2. Allowlist two client email addresses.
3. They open the link, read the page, and leave comments.
4. You revise in ChatGPT and republish — same URL, new version.

See a live example: ashley.docklets.io/q3-pricing/ (opens without login).

FAQ

How do I share ChatGPT Canvas HTML with a client who does not use ChatGPT?

Publish to Docklet and set visibility to selected users with your client's email addresses on the allowlist. They get a normal browser link — no ChatGPT account, not indexed, not open to the world.

Does my client need a ChatGPT account?

No. Docklet links open in any browser. Only the emails you allow can access a restricted Docklet.

Can I share a ChatGPT Sites page the same way?

Yes. Export or copy the HTML from Sites (or Canvas), publish to Docklet, and send the link. The recipient experience is the same: open without ChatGPT, comment on the page.

Does the link change after I edit the Canvas?

No. Ask your AI tool to update the existing Docklet (via update_website) or republish from the console. The URL stays the same; version history keeps prior revisions.

What if I just need a quick look, not a review loop?

ChatGPT's native share works well for a fast snapshot inside the product. A paste-and-host tool works when you only need a public URL. Add Docklet when recipients should open without your AI tool, leave comments on the page, or you may publish from a different MCP client next week.

Does this work from Claude or Perplexity?

Yes. Any MCP-connected tool can publish to Docklet the same way. You can also paste HTML in the Docklet console without MCP.

What does it cost?

Free ($0) covers five Docklets with public and selected-user visibility. Pro is $4 per user per month (private visibility, custom domain, five versions). Team is $9 per user per month. Enterprise is custom. Yearly billing saves 20%. See pricing for full details.

ChatGPT, Canvas, and Sites are trademarks of OpenAI. Claude, Claude.ai, and Anthropic are trademarks of Anthropic, PBC. Perplexity, Netlify, Slack, and other product names are trademarks of their respective owners. Docklet is not affiliated with, endorsed by, or sponsored by those companies. Product behavior cited here is based on public documentation as of September 2026 and may change.

← Back to the homepage