How to export and host your AI website

The builder preview and the downloadable source are separate. Free previews let you inspect the result, while unlocking releases that project's source files. Buy a one-time $4.99 unlock or use an unlock included in your plan. An unlocked project remains unlocked, including after a subscription ends.

Choose the saved version you intend to publish and review it before downloading. If you restore a previous version, verify that the preview shows the right content and imagery. A saved version retains its asset references, so removing an image from the project library does not change that historical preview.

Your ZIP includes generated source and the uploaded image and bundled font assets referenced by that version, together with font licenses. Read the included deployment instructions. Exact filenames and folders depend on the generated project; the entry page is typically index.html.

Extract the complete archive into a folder. Do not move individual images or rename folders without updating the paths in the HTML and CSS. A relative reference such as assets/photo.webp expects the same relationship between files on your host.

Externally referenced media can still depend on third-party availability and usage terms. Review those dependencies and any required attribution. An export containing your uploaded photograph does not grant rights to a photograph you did not have permission to upload.

A Uvilno export is a static website. It does not need a Next.js build, a Node server, or Uvilno to run once exported. Choose a host that serves HTML, CSS, JavaScript, images, and fonts. Hosting plans and limits are separate from your Uvilno subscription.

For a manual deployment, upload the extracted site's contents using your host's static upload workflow. The published root should contain the entry HTML file, rather than an extra parent folder. Open the host's temporary URL and check that every asset loads before connecting a domain.

Cloudflare Pages and Netlify document workflows for deploying prebuilt files. Follow the provider's current instructions and limits. Choose a repository-connected workflow if you want your own future file edits to trigger deployments automatically.

Check the live URL on a phone and desktop. Open the browser's developer tools if images or fonts are missing: a 404 often means a path, filename, or nested folder changed during upload. File paths can be case-sensitive on hosting platforms even when they worked on your computer.

Test internal links from the live root. Check anchor links, email destinations, and any third-party booking or payment links. A contact form needs a configured form service or backend before it can deliver messages. Never publish secret keys in an exported script.

If you rebuild or revise the project in Uvilno, download and deploy the new version. Editing in the builder does not automatically replace files on an external host.

Add the domain in your host's dashboard and apply the DNS records it specifies. Domain registration, DNS, and hosting are managed with those providers. Wait for the provider to confirm the domain and HTTPS certificate before promoting the site.

Choose one canonical public URL. Ask Uvilno to use that domain in your website's canonical metadata, and check the exported title and description. Redirect alternate hostnames to your preferred address where your host supports it. Ensure the published website is not carrying a preview-only noindex directive.

When the site is live, verify your own domain in Google Search Console or Bing Webmaster Tools. Submit the site's sitemap if it has one. Helpful, accurate content and a reliable site give search engines something useful to index; submitting a URL does not guarantee a ranking.

Keep a copy of the exported version and record where you deployed it. That makes future updates and a move to a different host easier.