Guide

How to save HTML from ChatGPT, open it and share it

Updated 30 October 2026

Paste the code ChatGPT wrote into a file that ends in .html and open it in any browser: that is your preview and your copy. To show it to other people, ChatGPT’s own share link opens for anyone who has it, or only inside your workspace, and ChatGPT Sites shares with ChatGPT accounts, your workspace or the whole internet. Connect the ashare.net MCP server and ChatGPT publishes the page itself, open only to your company, specific emails or anyone with a password.

Save the code as an HTML file

Ask for one file: “Put the HTML, CSS and JavaScript in a single file.” A page split across several code blocks is harder to save.
Copy the whole code block.
Paste it into a code editor, VS Code for one, and save it as page.html. A word processor adds its own formatting and breaks the file.
Double-click the file. It opens in your default browser, scripts and all.

If the page pulls a library or a font from a CDN, it needs the internet to look right. Everything written inside the file works offline.

What ChatGPT shows in the chat

For a while, canvas rendered React and HTML code inside ChatGPT, and a canvas could be shared from its toolbar like a conversation. On 28 May 2026 OpenAI took canvas out of GPT-5.5 Instant and GPT-5.5 Thinking: writing and code now come as writing blocks and code blocks in the reply. Paid users could keep canvas on legacy models only until those models are retired. So if the preview you used to see is gone, the file in your browser is the preview that works with any model.

Who opens ChatGPT’s own links

Option	Who opens it	Limits
Shared conversation, personal account	Anyone who has the link	No access per person, no expiry. A snapshot as of sharing; delete the link to close it.
Shared conversation, Business, Enterprise or Edu	Members of the same workspace only	People outside the workspace cannot view it.
ChatGPT Sites	At first the owner and workspace admins. Then chosen people or groups, named external viewers, the whole workspace, or anyone on the internet where public publishing is on.	Plus, Pro, Business and Enterprise. An external viewer signs in with the ChatGPT account that got access. Building a Site counts toward Codex usage.

OpenAI notes that a shared link is not meant for search engines, but that this does not make it private: whoever has it can forward it. If everyone who should read the page is in your ChatGPT workspace, a workspace link or a Site is the shortest path, and you need nothing else.

Publish from ChatGPT with access

ashare.net is an MCP server. Add it to ChatGPT once:

Settings

chatgpt.com/plugins → + → Add custom MCP server
Name: ashare
Connection: https://ashare.net/mcp
Authentication: OAuth

Then “I understand and want to continue”, Create as a plugin, sign in to ashare with the 6-digit code from your email and Allow. ChatGPT sends no API keys, so it is sign-in only. Custom MCP servers connect on ChatGPT on the web, not on mobile. Your plan and workspace policy decide whether they are available; in a Business or Enterprise workspace an admin may have to allow it. More clients: Connect your agent.

Now ask in the chat, in plain words:

Your company. “Publish this page to ashare for the company” opens it to everyone who signs in with an email on your company domain.
Specific people. “Publish it and share it with marta@client.com” adds up to 100 emails; each one gets a letter with the link.
A password. “Make it public with a password, expiring in 7 days” lets in anyone who has both the link and the password, until that date.

A new document is private until you say otherwise. Readers sign in with a code sent to their email: no account to create, and no ChatGPT account either. Someone not on the list sees “You don’t have access” and can ask you in; you approve from the email. For private and company documents you see who opened the page and when.

Fix it from the comments

Readers select text on the page and comment. Back in ChatGPT, say “Read the comments on that ashare document and fix them.” It lists the open threads, publishes a corrected version at the same link, replies and resolves each thread. Readers pick a version in the header and compare it with an older one, so they see what changed. If you would rather they saw only the latest version, hide the history.

Without the connector

If custom MCP servers are off on your plan or in your workspace, save the file as above and publish it yourself:

Upload the .html file on My documents, then press Share on the document page.
Or from a terminal, with a key from ashare.net/me/api:

Terminal

$ npx ashare-cli login
$ npx ashare-cli publish page.html --visibility company
$ npx ashare-cli share <id> marta@client.com

The access rules are the same whichever way the page arrives. See Sharing and access and Expiry and passwords.

ashare.net: your agent publishes HTML or Markdown and you choose who opens it: your company, specific emails or a password. Readers comment, the agent fixes the document.

Connect your agent