Hostinger Website Builder export: code, WordPress or rebuild

It depends on the mode. A Hostinger Website Builder site is now a manual-mode site in Hostinger AI Builder, and manual mode has no code or backup download: its built-in content export sends pages, text, images and files to a WordPress site, without styles, layout, store, forms or SEO settings, and getting code means copying the site into agentic mode first. Agentic mode, the former Horizons, exports a ZIP of a React + Vite project you can host anywhere, but your backend data stays at Hostinger and the code can't be imported back.

One builder, three former names

• Zyro. Hostinger owned Zyro and moved its customers over. Hostinger's Zyro migration notice says sites, hosting, domains and email moved automatically, Zyro plans became Hostinger plans, and Zyro accounts with no active subscription were deleted on February 6, 2024. The notice now calls AI Builder the improved version of Zyro.
• Hostinger Website Builder. Hostinger's drag-and-drop editor. zyro.com now redirects to its product page.
• Hostinger Horizons. Hostinger's prompt-to-app tool, where an AI chat writes the code.

In August 2026 Hostinger combined the last two. Its week 34 product update reported the merged product, and the AI Builder page describes it as the website builder and Horizons merged into one builder with two modes. hostinger.com/horizons now redirects there, and the old "Horizons: how to export code" help page now opens the agentic-mode export article. Hostinger's launch post says existing projects keep working as before.

So an old Website Builder site is a manual mode site (drag and drop, no code access), and an old Horizons project is an agentic mode project (built through chat, with a code editor). Hostinger's comparison of the two modes spells out the trade: manual mode gives up file manager, FTP, SSH and database access in exchange for speed and ease of use. Agentic mode lacks file manager, FTP and SSH too, per its technical specifications, but adds a code editor and export.

What you can take, and what stays behind

Everything here was checked against Hostinger's help center in October 2026.

What	How to get it out	What stays behind
Agentic-mode code	Code tab > Export code > Export, then download the ZIP	Integrated backend data; edits can't be imported back
Agentic-mode backend data (users, form entries, uploads)	No export tool	All of it
Manual-mode pages, text, images, files	Settings (⋯) > Export content to WordPress	Styles, layout, store, integrations, forms, submissions, SEO settings
Manual-mode contact form entries	Form submissions > View, then export to CSV	The form itself
Manual-mode backups	Not downloadable	Backups only restore inside the editor, for 30 days
Manual-mode site as code	Switch to agentic mode first (see below)	Sites using Ecommerce, the Instagram element or search can't switch
Domain	Change nameservers, or transfer out with an EPP code	Nothing, if you move it before the registration lapses

Hostinger Ecommerce, which runs the store in both modes, is a separate subscription. Its help center documents a spreadsheet import for products but, as of October 2026, no product export, and the manual-mode content guide states that store data isn't included.

Agentic mode: exporting the code

Hostinger's code export article gives the steps:

1. In the Hostinger dashboard, open the project from the Websites list.
2. Click the Code tab at the top of the editor.
3. Choose Export code under the files sidebar, then click Export.
4. Download the ZIP when it's ready.

The download is a Node.js project built with React and Vite, the only format offered. It covers frontend and logic files only; integrated backend data stays inside AI Builder. An edited copy can't be imported back to keep prompting, so from then on you edit by hand or start a new project.

Plans. As of October 2026, the AI Builder page's comparison table ticks "Code editor and export" for all three plans it lists: Premium, Unlimited and Cloud Startup. The hosting requirements article says creating, publishing or exporting a project needs an active Web, Cloud or Agency hosting plan, and VPS hosting doesn't qualify. The 7-day trial doesn't include export.

Running the export somewhere else

As static files. With Node.js installed, open a terminal in the unzipped folder, then install the dependencies and build:

npm install
npm run build

Vite writes the result to a dist folder by default, and its static deploy guide covers putting that folder on Netlify, Vercel, Cloudflare, GitHub Pages and others. If the app handles routes like /about in the browser, the host must answer unknown paths with the app's index page. Cloudflare Pages does that automatically when there's no top-level 404.html; elsewhere, look for a single-page app or rewrite setting (on Hostinger's PHP/HTML websites, an .htaccess rewrite rule). On a Hostinger plan without Node.js support, such as Premium, create a PHP/HTML website and upload the built files with File Manager, as the export article describes. Uploading the raw project instead of the build doesn't work there.

As a Node.js app. Hostinger runs Node.js web apps on Business (Unlimited) and Cloud plans, deployed from GitHub or a ZIP upload, per its Node.js web app guide. A VPS or any other Node host works too.

Check one thing before choosing. Hostinger's agentic SEO article says new AI Builder sites use server-side rendering on its servers, and the export article doesn't say how that carries over to a static build. After npm run build, open a built page and confirm your headings and copy are in the HTML. If they aren't, search engines and link previews get an empty shell until JavaScript runs, and a Node host helps only if package.json has a script that starts a server (often start).

The backend data problem

Logins, form storage, file uploads and automated emails run on Hostinger's integrated backend. Hostinger says there's currently no export tool for it, so user records, form submissions and uploaded files can't be downloaded. Support can't recover that data either, because Hostinger doesn't hold the encryption keys.

For a brochure site, that changes little. For a client portal or membership site, the exported frontend needs a new backend, and with no export tool for user records, plan on your users signing up again. Some older projects use Supabase instead, and Hostinger notes that its backend article doesn't apply to them, so check where your data lives first.

Manual mode: content to WordPress

This is the only built-in content export for a manual-mode site. Hostinger's WordPress export article lists what you need first:

• A WordPress site running version 6.5 or later, on a domain that has finished propagating.
• Permalinks set to "Post name".
• All plugins deactivated during the export.
• Application passwords enabled. The export fails with an error if they're switched off.

Then, in the builder, open settings with the ⋯ button, choose Export content to WordPress, enter the WordPress site's domain and click Start export. WordPress asks you to create an application password and approve the connection. When the export finishes, Hostinger recommends revoking that password.

What arrives is regular pages, text, images and other files. What doesn't is the part that made the site look like itself: styles and layout, the online store, integrations, forms, collected submissions and SEO settings. Hostinger's fix for pages or blog posts missing after the export is to copy them over by hand. Budget for a WordPress theme, re-entered meta titles and descriptions, and new forms, and export your form entries to CSV from the builder's Form submissions screen first.

Order matters. Hostinger's guide to switching platforms frees the domain by deleting the builder site, and warns that a deleted website can't be restored. Run the export into WordPress on a temporary or second domain, check every page, and only then delete the builder site and switch WordPress to your main domain with Hostinger's Change domain option.

For any platform other than WordPress, Hostinger's guide for other platforms is manual: copy the text page by page, save images (the Media Library helps), download PDFs and videos, then rebuild.

The detour: switch to agentic mode, then export code

A manual-mode site has one indirect way to become code. In the editor menu, Continue in Agentic mode creates an agentic copy of the site, per Hostinger's switching guide. The original stays unchanged, the copy counts as an additional website on your plan, and Hostinger says it looks identical. From there, the code export above applies.

The limits: sites using Ecommerce, the Instagram element or search can't switch, and there's no way back from agentic to manual. Hostinger describes the switch as an AI recreation, so compare the copy with the original page by page before exporting it.

Your domain and hosting when you cancel

Hostinger's cancellation article offers two paths. A refund, where eligible, ends the service at once and erases its data. Otherwise you turn off auto-renewal and the plan runs to its end date. The same article notes that manual-mode sites can't be backed up to your computer and points agentic users to the code export.

Once a plan expires, its sites stop loading. Hostinger's expired plan article gives 30 days to renew and restore them, and says the backup download offered in that window doesn't cover AI Builder websites, which come back only through reactivation. After that, the data is gone.

The domain is a separate service. Canceling hosting cancels only that subscription, and Hostinger's refund policy says that if a refunded plan included a free domain, the domain's standard price may be deducted from the refund, and you keep the domain for the rest of its billing period. To point it elsewhere:

• Keep it at Hostinger and change the nameservers or DNS records. Hostinger says changing nameservers costs nothing and takes effect within 24 hours.
• Transfer it out. Per Hostinger's transfer-out guide, at least 60 days must have passed since registration or the last transfer. Switch off the transfer lock, WHOIS privacy and DNSSEC, then give the EPP code to the new registrar. It can take up to 7 days. A .uk domain moves by changing its IPS tag instead.

A safe sequence: export the code or content, export form entries, save images, set up the new host, move DNS, check the new site, and only then cancel. If page URLs change on the way, map each old URL to its new one and add 301 redirects; our redirect map guide walks through it.

Rebuilding instead

Rebuilding is often less work than it sounds, because the WordPress route drops the design anyway and the agentic route drops the backend. Either way you keep your text and images, and you can pick a stack that doesn't depend on Hostinger's editor.

For a marketing site (a business site, portfolio or landing page), FNJ's AI website builder is one option. You describe the site and give it references, such as screenshots or the link to your current Hostinger site, and it designs desktop, tablet and phone layouts together on a visual canvas that you edit by prompt or by hand. You get a Next.js App Router project or static HTML, downloaded or pushed to a branch of your own GitHub repository, with no FNJ runtime in the code. FNJ doesn't host it: static HTML goes on a host such as Cloudflare Pages, the Next.js project on Vercel, Netlify or a Node server.

Its limits matter here. It doesn't import or convert Hostinger sites, so you're rebuilding from your content, not migrating a file. It doesn't build forms, stores, log-ins, databases or a blog engine, so a Hostinger site with a shop or member area needs other services for those parts. The first build, one prompt producing version 1 of a site of up to 4 pages, costs nothing; editing after that and downloading the code need a plan. For a side-by-side with other options, see our Hostinger alternatives page.

Frequently asked questions

Can I download my Hostinger Website Builder site as HTML?

Not directly. Manual mode, which is what Website Builder became, has no code download, and Hostinger says its backups can't be downloaded. Your options are the WordPress content export, switching the site to agentic mode and exporting the code, or copying content by hand.

Does the Hostinger AI Builder code export include my data?

No. The ZIP holds the frontend and logic files of a React + Vite project. Data in the integrated backend, such as user accounts, form submissions and uploaded files, has no export tool as of October 2026, and Hostinger says support can't recover it.

Can I import an exported project back into Hostinger AI Builder?

No. Hostinger says an edited export can't go back into AI Builder to continue prompting. You keep editing the code yourself or start a new project in the builder.

Which Hostinger plans include code export?

As of October 2026, the AI Builder page ticks "Code editor and export" on all three plans it lists: Premium, Unlimited and Cloud Startup. It applies to agentic-mode projects, needs an active Web, Cloud or Agency hosting plan, and isn't part of the 7-day trial.

What happens to my Hostinger builder site if I cancel?

A refunded plan ends immediately and its data is erased. A plan you don't renew stays active to its end date, then the site goes offline, with 30 days to renew and restore it before deletion. Hostinger offers no downloadable backup of AI Builder sites, so export first.

What happened to Zyro and Hostinger Horizons?

Zyro accounts were migrated to Hostinger, and those without an active subscription were deleted on February 6, 2024. In August 2026, Hostinger merged its Website Builder and Horizons into AI Builder: Website Builder sites became manual mode, and Horizons projects became agentic mode.