How to share an AI-generated HTML page

Updated 2026-10-24 · 5 min read

Your AI assistant has produced a page that works in the chat preview or on your computer. Now you want a client, teammate or friend to open it. Sending the .html attachment often shows source code, breaks the assets, or asks the recipient to download something first.

The short answer

If the page is only HTML, CSS and client-side JavaScript, put those files on a URL and send the URL. You can upload them below without configuring a repository, a build command or a hosting project. If the page needs a server or database, finish the boundary check below first.

1. Spend a minute checking the page

Make index.html the entry point

A single HTML file is enough when its CSS and JavaScript are inline or loaded from public URLs. If it uses local images, stylesheets or scripts, upload the whole folder and keep index.html at the top level. Preserving the relative paths is what keeps the page looking the same after publication.

Remove secrets before you publish

Anything inside the HTML, CSS or browser JavaScript can be read by other people. Remove private API keys, service-role tokens, passwords and personal data. A key that an AI assistant put in the page is not protected just because it looks like code.

Check whether the page needs a backend

• A static page can render content, respond to controls and calculate in the browser.
• Saving shared data, authenticating users and hiding privileged operations require a server.
• localhost in the published page points to the visitor's computer, not yours.
• An external API must allow the page's origin through CORS and work over HTTPS.

Plopino serves the static page; it does not turn browser code into a backend. Keep the API on an appropriate service and publish only the static front end here.

2. Try a working example before uploading yours

The official Gradient Studio is a complete, single-file interactive page. Change its colors and angle, inspect the HTML, or edit a copy. Previewing and downloading do not publish anything. It is a safe way to see the full edit → preview → publish flow before using your own work.

3. Publish your page and send the link

1. Choose the HTML file, a zip, or the entire project folder in the uploader above.
2. Wait for the upload to finish, then open the returned link and test it on a phone.
3. Copy that link into your email, chat or document. The recipient opens the page in a browser.

If images or styles are missing, go back to the folder check rather than uploading the same HTML file repeatedly. If the controls depend on a local server, finish the backend setup before sharing the page with other people.

Keep the same link when the page changes

Anonymous uploads are public and kept for 30 days. Save the page to an account after publishing if you want to keep it and manage it. Once it belongs to your account, open My Boards and upload the next version there: the URL stays the same while the content changes. This is useful for an AI page you are still iterating on, a portfolio, or a proposal that needs corrections.

Do not put confidential work in an anonymous public upload. Use content you are comfortable sharing, and remove secrets before either kind of upload.

Common problems

The recipient sees code instead of a page

The file is being served as text rather than text/html. Publish it as a web page and send the resulting URL instead of forwarding the attachment.

The page works locally but loses images after publication

The HTML probably refers to files that were not uploaded. Include the whole folder, preserve its directory structure, and avoid absolute paths that only exist on your computer.

The page loads but cannot save or fetch data

Check the browser console for localhost, failed API requests, CORS and mixed HTTP/HTTPS content. Publishing the front end does not publish a local API.