Download your website and share a preview

Downloading your website gives you a ZIP containing the saved page and its supporting files. It does not buy hosting, connect a domain or turn a preview into a live business website. You can keep the ZIP, give it to a developer or upload it to compatible hosting yourself.

If you only need someone to check the design, use the optional shareable preview instead. The two options serve different jobs: one hands over files; the other lets someone view a saved version without entering your editor.

Save the version you want to keep

Open your project and choose Edit website if anything needs changing. Save the finished edits before downloading. Check the business name, phone, email, logo, service descriptions and genuine reviews. The editing checklist explains the desktop and phone checks worth completing first.

Choose Download and complete the email and quick-feedback fields. Additional written feedback is optional. Finish the security check. Where available, tick Also create a shareable preview link if you want a review URL as well as the files. You will then reach the download confirmation page.

Ready-made template use, editing and downloading do not spend the five-request generation allowance. You can return to the roofing templates or HVAC templates without purchasing launch help.

Choose the right kind of preview

A shareable link uses a separate preview subdomain. Its usual duration is 30 days, but follow the duration and expiry shown in your download flow. This is temporary review hosting, not the permanent address to put on a van, invoice or Google Business Profile.

Anyone who has the link can view the saved business information. Search exclusion is not password protection. Share only information you are comfortable showing, and send the preview link rather than your editor URL.

The shared version is a snapshot. Saving more edits later does not rewrite a link already sent. Create or open the preview associated with the newer saved version and check it before sending another approval request. Preview forms are intentionally disabled: a successful visual review does not test enquiry delivery.

Understand the files before uploading

Keep one untouched copy of the downloaded ZIP. Extract a working copy, retaining the directory structure.

Moving index.html away from assets can break images and interactions. Sending just a screenshot cannot transfer an editable website. Send the ZIP when handing the job to a developer, together with the intended domain and enquiry recipient.

Read the privacy notice before publishing. Replace starter instructions with information about your actual business, hosting and enquiry handling. A generated file cannot know every service you use or your retention practices.

Upload to compatible hosting

The supplied enquiry handler needs PHP, mbstring, outbound HTTPS requests and working outgoing email. A static-only host may display the page while being unable to run that handler. Check compatibility before changing any live website.

For Hostinger, use the File Manager for the correct hosting site. Its archive upload guide explains upload and extraction into public_html; that facility differs from its visual website-builder product. After extraction, confirm your page and assets sit in the intended website directory, not an accidental extra nested folder.

If another website already uses that domain, back it up and agree a replacement plan first. Do not overwrite an existing homepage just to test the ZIP. A developer can use an appropriate staging location, then publish the approved files.

Connect the enquiry form properly

The exported package is not connected to Website Generator Hub's production mail account or private security credentials. Configure your own hosting environment with:

• WGH_TURNSTILE_SITE_KEY
• WGH_TURNSTILE_SECRET_KEY
• WGH_TURNSTILE_HOSTNAME

Use the hostname visitors will actually use. Keep the secret in server configuration, never in HTML or browser JavaScript. The handler checks the security response on the server; Cloudflare explains why the visible widget alone is insufficient.

The current exported handler uses PHP's mail() function. It does not become SMTP-enabled by typing mailbox credentials into quote-config.json. Ask your hosting provider how outgoing PHP mail is configured, or have a developer adapt delivery appropriately. Hostinger's email-delivery guidance recommends authenticated SMTP for reliability.

Submit a clearly labelled test enquiry on the final HTTPS address. Verify that it reaches the intended mailbox and that replying addresses the test sender. Also test an incomplete form: required-field messages should appear without losing the visitor's work. If a security check expires, refresh it before trying again.

Keep a simple handover record

Record the downloaded version, final domain, hosting account owner, enquiry recipient and date of the successful delivery test. Keep passwords out of the ZIP and public page content. Check the phone link on a real mobile device and confirm images load after a fresh browser visit.

If you would prefer help publishing the selected page, compare the packages in Launch your finished website. Downloading stays free; launch help is a separate choice.