Share Multiple Pages as a Bundle

Who it's for

• Students submitting multi-page HTML assignments who need a single share link for grading or feedback.
• Freelancers and agencies sharing project bundles with clients, ensuring all assets, subpages, and navigation open correctly without broken references.
• Designers and developers sending linked portfolios or landing pages where a single organized URL is preferred over multiple file downloads.

Steps

1. Gather every HTML file, stylesheet, script, and associated asset (images, fonts, etc.) into one folder on your computer; keeping relative paths intact prevents 404s when the bundle is hosted.
2. Create an account and host your first HTML page if you're new to HTMLPUT; this introduces the upload flow and shows how share links are generated.
3. In the HTMLPUT interface, click Upload and select the folder or create a zip archive; the platform will parse the index file and map all linked pages automatically.
4. After upload, use the host toolbar to set the page title, choose between public access or password protection, and generate your share link; password-protected links require a password before any page content loads.
5. Copy the generated share link; it serves as one organized entry point that opens the site's index page and navigates to every subpage and asset, preserving navigation and relative paths.
6. To update the project, open More → Re-upload in Uploads—the share link stays the same and all references remain valid.
7. For client hand-offs, compare this method to cloud-drive sharing by reading share a static HTML demo vs cloud drive, which outlines the trade-offs in asset integrity and access control.

Gotchas

• Loose file paths or missing assets can cause 404 errors when recipients open subpages from the shared link, so test the bundle locally before sharing.
• Password-protected bundles require the recipient to re-enter the password each time they navigate to a different page, which can feel repetitive if the site has many subpages.
• Re-upload replaces all files in the bundle; keep a local backup if you may need to revert to an earlier build.

vs Cloud Drive