Is website builder lock-in something to actually worry about?

Only if you have not registered your own domain and kept your source text somewhere outside the platform. With both of those in place, lock-in costs you a rebuild, not your name or your writing — which is a manageable trade for most single-person sites.

What does a website builder actually let you take with you if you cancel?

Almost never the finished site. Some hand back raw text and image files, a few generate real exportable code, and at least one keeps everything with no export path at all. The terms are usually on the pricing or FAQ page, not hidden, just unread.

Does owning my domain protect me from lock-in?

It protects the one thing that is hardest to rebuild — your name having a fixed address — but not the site itself. A domain you own can be pointed anywhere; the layout and copy sitting on a platform's servers are a separate question with a separate answer per vendor.

Is it worth paying more for a builder specifically because it exports code?

If the site needs to survive a decade, or survive the vendor, yes — that is what the premium buys. If the site is disposable by design, a fast, non-exporting tool is a reasonable trade for the time it saves, as long as you know that is the deal you made.

Lock-in is not a conspiracy, it is a design decision

Every article about website builder lock-in wants to be a scandal. Vendor traps you, vendor profits, vendor bad. It is a satisfying shape for a piece of writing and it is also mostly wrong, because it treats lock-in as something that happened to you rather than something you bought. A builder that renders your site cannot hand you a portable copy of it, by construction, and the convenience you are paying for — drag a block, click publish, no server to think about — is the same mechanism that makes the output non-portable. The honest question is not whether lock-in exists. It obviously does. It is whether the trade is worth it, and which two things you should refuse to let the platform hold, regardless of which one you pick.

A rendered site cannot be portable, and that is the deal

Start with what "the site" actually is on a modern builder. It is not a folder of HTML files sitting somewhere waiting to be copied. It is a set of structured data — this block, this order, this style, this breakpoint — interpreted at request time by code that belongs to the vendor. Wix's editor does not produce a webpage the way a person writing HTML by hand produces one; it produces a description of a webpage that only Wix's renderer knows how to read. Squarespace, Framer and Webflow's Basic tier work the same way underneath their different interfaces. That indirection is not an oversight. It is the entire product. It is what lets a person with no code experience drag a section into place and see it work immediately, on every device, without touching a stylesheet.

The price of that convenience is that the description cannot leave, because the renderer that understands it does not leave either. You are not being denied your own work out of spite. "Your work," in this context, was always half yours and half the platform's interpretation of it, and only the platform can run that interpretation. That is why the picture is consistent across the whole category, not one company's bad behavior.

Where reach sits on this, stated plainly

For a single-person page — a CV turned into a site, a portfolio, a freelancer's one-pager — reach is the strongest answer available, and that is worth saying before getting to its limits, not after. Give it a résumé and a photo and it generates a complete page in about twenty seconds, live on a free yourname.joinreach.app subdomain in under two minutes total. That number removes the step where most personal sites actually die — not the design, the blank template staring back at you on a Saturday. The honest cost sits right next to that speed: the same architecture that makes reach fast makes it a closed system. It has no HTML export and no custom code field, on Premium or off it, at $4.99 a month or $49 a year. What you build there stays there, the way a Wix or Squarespace site stays where it was built. For a page you plan to replace within a year or two anyway, that is a fair price for skipping a weekend of template-picking. For a page you want to still control in five years without depending on one vendor's pricing or survival, know that before you start.

Three layers, and only two of them travel

The useful way to think about a site is as three separate layers stacked on top of each other, because they do not share a portability story.

The domain is the layer that travels cleanly, always, on every platform. A domain registration is a record you control at a registrar, independent of what it points to. Move the DNS, and the same address serves a completely different site the next day. This is the one piece of the stack that was never platform-specific to begin with, and it is worth understanding what markup vendors add to registering one through the builder itself rather than a standalone registrar — the comparison is laid out in why your builder sells domains at a markup.

The content — the actual words and images — travels with effort on some platforms and not at all on others. This is the layer where "export" means something real on a few tools and almost nothing on most. Ghost, since a July 2026 update, generates a Markdown version of every public post reachable simply by appending .md to its URL — an unusually clean way to get writing out. WordPress content already lives in a database you control, so leaving means a hosting decision more than a content-recovery project. At the other end, Butternut AI's own product pages document no code export, no WordPress export and no static export of any kind, on any tier — leaving means copying text off the rendered page by hand, one field at a time, because there is no file the platform will hand you. That sits alongside the rest of Butternut's picture worth knowing before treating its "20 seconds" flow as an unqualified win: a seven-person team with no disclosed funding round since 2023, and a $5 entry tier that exists specifically to keep the vendor's badge visible on the page rather than to give you a real presence off it.

The presentation — the layout, the component code, the styling — is the layer that almost never travels, because it is the layer the platform is actually selling. Webstudio is the clean exception among newer tools: it is AGPL-licensed and produces a standard Remix/React codebase you can self-host, so its presentation layer is portable by design rather than by favor. That is rare enough to be worth naming as the exception, not the rule, and the full account of what each platform's export button does and does not hand back is in what you can actually export from each website builder.

What the terms actually say when you stop paying

Cancellation terms are usually not hidden, they are just never read until the moment they matter, and they say more than the marketing pages do about who actually holds the content once the invoice stops. Squarespace states outright that content on an expired trial is "marked for permanent deletion" — not archived, not frozen, deleted. Wix's own support documentation confirms a smaller but sharper version of the same problem while you are still paying: "it's not possible to switch to a different template for a site you already created," which means the lock-in on Wix is not only about leaving the platform, it is about changing your mind while still on it. Notion Sites ties the removal of its badge to a paid custom domain on every tier including Plus, so cancel the domain add-on and the platform's branding returns to your page even though the content is still technically live. reach's own comparable moment is milder by contrast: cancelling Premium takes a custom domain offline and the site falls back to the free reach subdomain rather than disappearing, which is a real difference worth naming alongside the export limitation above, not instead of it.

None of these are secrets. They are sentences on pricing and FAQ pages that nobody reads until the subscription lapses and the content is already gone or the badge is already back. Reading them before signing up costs five minutes. Reading them after cancelling costs the content.

The comparison that actually matters

Platform	What survives cancellation	Real code export
reach	Falls back to free subdomain, content stays live there	None — no HTML export, no code field
Wix	Site typically goes offline; template cannot be swapped even while active	Not offered
Squarespace	Trial content "marked for permanent deletion" after expiry	Not offered
Webflow (Basic)	Site goes offline without an active plan	Not offered
Butternut AI	Hosting is Butternut-only	None of any kind, on any tier
Webstudio	Self-hostable regardless of subscription status	Yes — standard Remix/React, AGPL
WordPress (self-hosted)	Content lives in your own database independent of any vendor	Yes — you already hold it

Prices checked August 2026.

The pattern in that table is not "some vendors are good and some are bad." It is that portability correlates with how much of the actual rendering engine the vendor is willing to give up, and almost none of them are, because the rendering engine is the product. Webstudio and self-hosted WordPress are outliers for the same reason: in both cases the thing you are running is not proprietary to begin with.

The two things to keep outside the platform, regardless of which one you pick

Given all of that, the sensible response is not to avoid builders that lock you in — that would rule out nearly the entire category, including some genuinely good tools — it is to keep exactly two things outside whichever platform you choose, so that lock-in costs you a rebuild rather than your identity.

Keep the domain registered in your own name, at a registrar, not bundled into the builder's account in a way that makes it hard to separate later. And keep a copy of the source content — the sentences describing what you do, the photos, the project list — in a plain document the platform cannot touch: a folder, a repository, a note file, anything not itself rendered by the vendor's engine. Neither costs anything to maintain, and together they turn "the platform shut down" or "the price tripled" from a crisis into an afternoon of pasting content into a new tool. The layout will not survive the move on most platforms; accepting that in advance is what makes the rest of the decision calm instead of reactive, which is also the moment to work out whether the subscription is still earning its keep, addressed directly in when a website builder subscription stops making sense, and, if the answer is no, in moving a site from one builder to another without losing the search traffic.

Convenience now, a rebuild later if it comes to that — stated as plainly as the trade actually is, because every builder in this category is selling some version of it, and the only mistake is not knowing which version you agreed to.