Does my client need an account to open the prototype?

No. An unprotected link opens in their browser. If you enable password protection, they use the shared site password rather than a Pagelet account.

Can I share a prototype with several HTML pages?

Yes. Upload the folder or ZIP with index.html at its root, include the supporting files and use relative links between pages. The downloadable Little Studio example demonstrates this structure.

Can I upload a new ZIP and keep the same URL?

No. A new ZIP upload creates a separate publication and a new URL. Saving a home-page change in the dashboard editor keeps the existing address, provided you do not rename the subdomain.

How long will the preview stay available?

Unclaimed guest sites are removed after 30 days. Sign in from the same browser to claim the prototype with a free account and keep it without a time limit while it follows the terms.

How to share an HTML prototype with a client

To share an HTML prototype with a client, upload the HTML file or its project folder to Pagelet, wait for the safety checks to pass, and send the resulting HTTPS link. Your client opens the page in a browser without downloading the project or creating an account.

A working preview lets them try the navigation, click buttons and check the layout on their phone. This guide uses a small example website so you can try the process before uploading your own work.

Try the prototype before uploading

The example below has two pages, a stylesheet, a JavaScript file and an illustration. Press Try the JavaScript, then follow Visit the second page to see how its files work together.

Little Studio · Open the example ↗

A public example with sample content. The ZIP below contains the same files as this preview.

Open the example in a new tab, or download the complete example project. You can upload the ZIP as it is. To change it first, unzip it, edit the files and upload the project folder or a new ZIP.

1. Choose a single file or the whole folder

Use the format that matches the prototype you already have:

One HTML fileUpload the .html file when its CSS and JavaScript are inline, or its supporting assets have publicly accessible URLs. Local files on your computer will not accompany it automatically.

A folder or ZIPInclude index.html at the root, plus the CSS, JavaScript, images and other pages. Keep relative paths such as styles.css and images/studio.svg.

Code from a chatUse Paste HTML & get a shareable link for a complete document. Pasting does not upload separate files from your computer. The ChatGPT publishing guide explains this route.

For folder structure and missing-file troubleshooting, follow the HTML hosting guide. Pagelet hosts static files and browser JavaScript; a contact form, login or payment flow needs its own working service behind it. Label unfinished controls so your client knows what is ready to test.

2. Upload, check and claim the prototype

Open the Pagelet upload area and drop your HTML file, folder or ZIP. You can also browse for a file or ZIP.
Wait until the publication passes its safety checks. An upload that is still being checked is not publicly available yet.
Open the returned link and check the page before sending it.
If you published as a guest, sign in with Google from the same browser to claim the site. Open your dashboard and check that it appears under Your sites.

A free account can keep up to 10 sites of 5 MB each. Claimed sites have no time limit while they follow the terms; unclaimed guest sites are removed after 30 days. Claim a prototype you want to keep available for future feedback.

An unprotected publication is public to anyone with its link. For a site you own, you can enable password protection before sending it. The upload is public before protection is enabled, so use sample content for a prototype and avoid this flow for material that must remain private from the moment it is uploaded.

3. Check the preview before sending it

Open the link on a computer and a phone. The responsive design tester can help check common widths too.
Visit every page and check that images, styles and fonts load.
Try the buttons and navigation. Say which controls are demonstrations and which actually submit information.
Remove API keys, personal records and client details that should not be public.
If you enabled a password, test the link in a private window and follow the visitor sign-in instructions.
Choose the subdomain name before sharing. Renaming it changes the address.

Keep your original project files locally. The hosted preview is the version you are asking the client to review.

4. Ask for feedback on specific decisions

Send the link with a short explanation of what is ready and what you want reviewed. Copy this message and replace the bracketed details:

Hi [name],

Here is the [project] prototype: [link]

For this round, please focus on [layout, wording or another decision].
[List any buttons or forms that are only demonstrations.]

Could you check it on your phone as well as your computer?
Please send me:
- Any text or sections you would change.
- Anything that was hard to find or use.
- The page and button involved if something did not work.

Screenshots help if you spot a layout problem.
Please reply by [date] so I can prepare the next version.

Thanks,
[your name]

If the site is password protected, include the access instructions from the password guide. Your client does not need a Pagelet account, and the prototype itself does not include a commenting system; collect their feedback through your usual email, chat or project tool.

5. Know when an update changes the link

For a small correction, open the site's Edit control in your dashboard, change its home page and press Save. The address stays the same while the subdomain name stays the same. Public pages can be cached briefly, so allow a few minutes for an older copy to refresh.

The visual editor edits the home page. It does not replace a whole project folder, its other HTML pages or its separate CSS and JavaScript files.

Save a home-page editThe existing publication keeps its URL. Ask the client to refresh the page to review the saved changes.

Upload revised filesA new upload creates a separate publication with a new URL. Send the new link and identify the revision; uploading the same filename does not replace the old publication.

Rename the subdomainThe address changes. Update the links and QR codes you have already shared.

For larger changes, update your local project and publish a new revision. Keep the previous claimed publication if the client needs to compare both versions, and make clear which link is the current one.