Website builder export: code export, HTML export, and which builders lock your site in

OVERVIEW

Every website builder on the market tells you that you own your site. It is technically true almost everywhere and it settles nothing, because ownership and portability are different questions. You own the words on your about page in the same way you own a conversation you had. The question that costs money is what lands on your computer when you decide to leave, and how many hours somebody has to spend turning that into a working site somewhere else.

That gap is where lock-in lives, and it is deliberate rather than accidental. A builder that made leaving trivial would be competing on price every single month. A builder that makes leaving a rebuild gets to raise prices, and you will still probably stay, because the quote to redo a thirty page site is larger than the increase. Nobody writes this on a pricing page, so the only way to see it is to look at what the export button produces before you commit, not after.

Start with the term itself, because vendors use one word for at least five different things. Export can mean a full code bundle of HTML, CSS and JavaScript you can host anywhere. It can mean a structured content file such as WordPress XML that another platform can import. It can mean CSV dumps of a few collections. It can mean a PDF or a screenshot, which is not an export in any useful sense. And it can mean a code project in a Git repository, which is genuinely portable but hands you hosting, builds, dependencies and security patching along with it. Those five outcomes have wildly different switching costs, and the marketing word is identical in all five cases.

The Wix position is the most commonly misunderstood, so here it is straight from the source. Wix does not produce standard HTML and CSS you can lift out, and its own help center answers the export question directly: exporting blog posts to other platforms is not currently possible. What you can do is export CMS collections such as products or a blog feed as CSV files, and those files reference your images by URL rather than containing them, so pictures come down one right click at a time or through a scraper. Design and static pages do not come out at all. For a five page site that is an afternoon of copy and paste. For a business with two hundred blog posts and a product catalog, that is a real migration project with a real invoice attached.

Squarespace is better documented and more limited than most people expect. You get a .xml file shaped for WordPress import. It carries layout pages, text blocks, image blocks, and exactly one blog page including its posts and up to a thousand comments per post. Gallery pages come across on version 7.0 only. Everything else stays behind: store pages, portfolio pages, index, album, cover, calendar and info pages, anything in a page-specific header, footer or sidebar, dropdowns, audio blocks, video blocks, product blocks, drafts, style settings, and custom CSS. The images in the file are links to Squarespace servers rather than the files themselves, which matters the day the site comes down. If you run more than one blog on the site, the export takes one of them.

GoDaddy Website Builder is the simplest case to describe. There is no export tool. Moving to another platform means somebody opens both sites side by side and retypes. That is worth knowing at the point when you are choosing, not at the point when you are leaving.

Webflow is the interesting one, because Webflow is the builder everybody names when the topic is code export, and the export is genuinely real and genuinely partial. You get an HTML file per static page, the CSS, the JavaScript including the animation runtime, and your images and fonts, on a paid plan. What does not come with it: CMS collection content, ecommerce, user accounts, code components, and localized pages. On the exported site, collection lists render their empty state, collection pages show nothing bound to a collection field, forms stop working, site search stops working, file upload and reCAPTCHA stop working, and pages that were password protected are not protected anymore. So a marketing site exports cleanly and a content-driven or transactional site exports into something a developer has to finish. Anybody quoting Webflow as proof that code export solves lock-in has usually not exported a CMS site.

The AI code tools sit in their own category. Bolt, v0, Lovable and the rest hand you an actual code project, and you can push it to GitHub and host it anywhere, which is the strongest form of portability available. The bill arrives later and it is not financial. You now own a build pipeline, a dependency tree, a hosting account, and a security patching obligation, for a site whose purpose is to describe your plumbing company. Most small businesses that take that deal end up paying a developer a retainer to hold it, which is a subscription with extra steps. Portability is real there, and it is not free.

So what is the honest position here. AgentSite is a hosted product, and pretending otherwise would put us in the same paragraph as the vendors above. Two things are true and both are written into our terms rather than a marketing page. Your domain is registered in your name and stays yours, which is the single most valuable thing you can hold, because your rankings, your backlinks, your email and every business card you ever printed attach to the domain rather than to the platform. And your site and content are exportable, so what you would be moving is content into another system, not a site you have to conceive again from a blank page. Nothing sits inside a proprietary code project you cannot open. If a downloadable production code bundle you self-host is a hard requirement for you, say so before you buy, and understand that Webflow and the open source builders such as Webstudio are the category built for that specific need. We would rather lose the sale than have you discover the shape of it in month four.

There is a second, quieter form of lock-in that nobody puts in a comparison table, and it is usually the expensive one. It is not the export format. It is that rebuilding the site is a project you have to staff. If a redesign means eight weeks of somebody writing twelve pages of copy, you will not leave a vendor you dislike, because the alternative costs more than the annoyance. That calculation changes when a complete site can be generated from a description in minutes. When rebuilding is cheap, no vendor has leverage over you, including this one. That is a strange thing to advertise and it is the actual answer to lock-in.

The practical advice is the same whoever you buy from. Register your domain somewhere that is not your website builder, or at minimum confirm it is registered in your name and that you can move it. Keep the source text of every important page in a document you control, because copy is the part that took months and the part no export preserves properly. Export your Search Console Pages report before any move so you know which URLs actually earn traffic, and map every one of them with a 301 redirect when the structure changes, since rankings attach to URLs and to your domain rather than to your CMS. Keep original image files off the platform. Do those four things on day one and no builder can hold you, regardless of what its export button does. If you want the specific Wix version of this, we wrote the step by step in how to export a Wix website. And if what you are really weighing is whether to migrate or rebuild, the arithmetic is worked through on the website redesign with AI page.

Website builder export, compared honestly.

Common questions.