-
How to check it before you commit.
Five steps, and the useful one is the last.
Build one throwaway test page.
Download the HTML on Pro.
Open the files on your machine.
Put them on any static host.
Check what survived, then decide.
-
The list to run through
Build the test page with the things your real site uses, not a blank rectangle. One image, one uploaded font, one form, one link to a second page. Then download it and answer these, in this order.
Does it open? Open whatever you get in a browser, straight from your own disk. A page that renders offline with its styling intact is a very different asset from one that needs the platform to look right.
Are the images in it, or pointed at? Cut your internet connection and reload. Anything that vanishes is being fetched from a server rather than sitting in the folder, which is a dependency you would be carrying with you.
Did the fonts come? Uploaded font files are yours, but a licence covering one platform does not automatically cover self-hosting the file elsewhere. Check the folder, then check your licence.
What happens to the form? Submit it from the copy you are hosting and see whether anything arrives. Assume it does not until proven otherwise.
One page or the whole site? Follow the link to your second page and see whether it is in the download at all.
Where this page and the app disagree, the app is right. Nothing above describes a file we have opened for you, and an afternoon of your own testing beats our word on something Siter.io has not put in writing.
Download your website as HTML
Siter.io can hand you a page as HTML to host somewhere else. It is on the Pro plan only, and what the download contains is not documented anywhere, so this page tells you how to find out for yourself instead of guessing on your behalf.
Start for free -> See the plans
The short answer.
HTML download on Pro only; the contents of the export are not documented. The download exists and it is real. Whether the files open as a working site, and what comes with them, is not written down anywhere we can point you at. If the export is your reason for paying, test it on a throwaway page before you commit to a year.
-
What is confirmed
The pricing table lists Download HTML, described as taking a page from Siter.io and hosting it somewhere else. It sits on Pro, $24/mo billed yearly or $28 monthly. The three cheaper plans do not have it.
-
What is not
The contents. Nobody has published what arrives when you press the button, so we are not going to describe it, and you should distrust any page that does without having opened one. Fifteen minutes on a test page settles it.
Which plans include it.
One row, four plan columns, three of them no. The pricing table lists no cut-down version of it further down, and no add-on for it either, so the Pro row is the whole answer.
| Feature | Start (free) | Solo $7 | Plus $12 | Pro $24 |
|---|---|---|---|---|
| Download HTML | No | No | No | Yes |
Read off the “View all features and options” table on siter.io/pricing on 2026-09-03.
Pro is $24/mo billed yearly and $28 month to month, and carries 5 published websites and 6 editor seats alongside the download. Publishing at all starts lower down, from $7/mo billed yearly, but the download is not on that tier. The free plan sits further out still: no - the free plan builds and previews privately; publishing needs a paid plan.
A copy is not the same as a portable site.
This is the part people get wrong, and it is not specific to Siter.io. It is true of every builder that offers an export.
Why anyone wants the file
Four reasons, wanting quite different things. Client handover: the invoice is paid and the client would rather own a folder than inherit a subscription. Archiving: nobody plans to touch the site again, but the company wants a copy of what it published. Leaving: usually asked before signing up rather than after. A developer taking it further: a designed page becomes the front end of something with a backend behind it.
Only the first two are really about files. The other two are about whether what you get is workable, which is exactly the part nobody has published.
What actually has to be reconnected
Assume the markup arrives intact and you still have a list. Assets have to be in the folder rather than fetched from the old platform, or the archive quietly rots the day the account lapses. Fonts have to be present and licensed for wherever you put them. Forms have nowhere to post on a plain static host, so they need a form service or a small endpoint before the contact page means anything. Analytics is a setting inside the builder, so check the tag is really in the markup. Hosting and the certificate become your problem the moment you take the files, and the domain has to be repointed at wherever you moved.
What "you can leave" actually requires of a platform
Three things, and only one of them is an export button. You need a copy of the output that you have verified with your own eyes, not one you have been told about. You need to own the pieces the output depends on, which mostly means the domain registration and the font licences. And you need the destination to be somewhere ordinary, because a static folder can go almost anywhere while a proprietary bundle cannot.
The domain is the piece most people forget and the one most within your control. Siter.io connects a name you registered yourself, and that registration stays in your account, which is the single biggest reason leaving is cheap. It is written up on connecting a custom domain.
How this compares with a real code export
Honestly: it does not, and we are not going to pretend. Webflow's code export is the more serious feature, built and documented as a way of taking a site off the platform, with its own conditions attached. If leaving with your code is the deciding factor rather than a nice-to-have, that is a reason to choose Webflow and we say so on the Webflow comparison. Siter.io's HTML download is a smaller thing, and until its contents are documented the sensible way to treat it is as an unknown you test rather than a promise you buy.
-
Not documented means not documented
Siter.io publishes that Pro can download HTML. It does not publish what the download contains. We are not going to fill that gap with a confident guess, so treat the archive as unknown until you have opened one yourself.
-
A copy is not a portable site
Even a perfect export lands somewhere with no host, no certificate and no form handler. Reconnecting that is the real work of moving, and it is the same work whichever builder you are leaving.
-
Forms stop at the door
A form sitting on a plain static host has nowhere to post. Whatever collects your submissions today belongs to the platform you are leaving, so budget for a form service or a small endpoint wherever the files land.
-
One page, or the whole site
The pricing table describes downloading a page. Whether a multi-page site comes down in one go or one page at a time is not stated anywhere we can cite, which makes it the first thing to establish in your own test.
Frequently asked.
Can you export a website as HTML?
From Siter.io, yes, on Pro. The pricing table lists a Download HTML row, described as taking a page and hosting it elsewhere. What it does not list is what the download contains. Treat the existence of the feature and the usefulness of its output as two separate questions.
Which plan do I need to download HTML?
Pro, at $24/mo billed yearly or $28 month to month. Start, Solo and Plus do not include it. If the download is the only reason you would move up two tiers, test one before you pay for a year, because the yearly commitment is the part you cannot undo cheaply.
Can I host my Siter.io site somewhere else?
That is what the download is for, and also the claim we can least stand behind, because the contents are undocumented. A folder of HTML will run on any static host. Whether what you get is that folder, and whether images, fonts and forms come with it, is for you to establish first.
Is the exported HTML still editable?
Not documented. Realistically, markup generated by a visual builder is editable in the sense that a developer can change it, and unpleasant in the sense that nobody wants to maintain it by hand. If a developer is taking the page further, have them look at a download before you promise them anything.
Will my forms still work after I export?
Assume not. A form needs something on a server to receive the submission, and a plain static host has nothing there. Whatever collects your entries inside Siter.io belongs to Siter.io. Moving the files means a form service or a small endpoint at the new address, whichever builder you leave.
Can I download my website for free?
Not from Siter.io. The download is on Pro only, and the free plan sits further back than that: no - the free plan builds and previews privately; publishing needs a paid plan. Publishing starts from $7/mo billed yearly, and the download is two plans above that.
Does an export mean I own my website?
Partly, and the parts that travel best are not the export. The domain registration sits at your own registrar, in your own name. If the page started in Figma, the source is still in your Figma file, because the import runs one way and never syncs back. A download adds a copy of the published output on top of those. What it does not add is hosting, a certificate, a form handler or anywhere to edit, so treat it as one item on the moving list rather than the whole move.
More of what the editor does
-
Custom domains
Point a domain you own at the site, included in every paid plan at no extra cost.
-
Hosting and SSL
No separate host to buy, no certificate to renew. It is part of the plan.
-
Forms
Design a form on the canvas and get the answers in your inbox.
-
Custom fonts
Upload the font files the design was made with, on every plan including free.
-
Responsive design
Three fixed breakpoints, laid out by you rather than guessed by the tool.
-
SEO settings
Per-page title, description and slug, plus custom meta tags in the head.
-
Teams and roles
Editor and viewer roles on every plan, with seats included rather than billed per head.
Also useful: Siter.io pricing in full, how this compares with Webflow and the Figma to HTML plugin.
-
Test the export before you trust it.
Build one page, download it, and open the files yourself while cancelling is still cheap. The free plan builds and previews privately, publishing starts at $7/mo billed yearly, and the HTML download sits on Pro at $24/mo billed yearly.
Get the plugin -> -
Start for free with Siter.io
Start for free ->