What happens to my website if I cancel my builder subscription?

Start with the honest answer, because the marketing version of this question is "it stays yours", which can mean several very different things.

Your domain name is never the builder's. A domain registration is a separate legal relationship with an accredited registrar; a website builder that sells you a domain is acting as a reseller. If you cancel, the registration continues until its prepaid expiry date, and you can point its DNS records anywhere — at another host, another builder, or your own server.

Your content survives if the platform gives you a way out. This is the part that differs between products, and the part to check before you sign up rather than after you want to leave.

The three things a builder can do with your site

The third row is the only one where the question has no scary answer, and it is the only one where the export is not an emergency.

What "exportable" has to mean

A download is not portability. Three properties make an export a real answer:

1. Complete. Every page, with its copy, its images and its structure — not

a front page and a contact form.

1. Self-contained. No PHP, no database, no runtime server, and no call

back to the platform that produced it. The bundle has to run somewhere that knows nothing about you.

1. Reachable. A static bundle on Cloudflare Pages, GitHub Pages, Vercel,

Netlify, or an ordinary Nginx server. If the export only runs on the vendor's infrastructure, it is a subscription with extra steps.

How long the answer is good for

Three shelf lives, and they are usually confused with each other.

The domain is the longest. A registration continues to its prepaid expiry whatever you do with the website, and moving it is a registrar-side action, not a builder-side one.

The export terms are the shortest. They are a property of the plan you are on, they change with the plan, and a page that says "export" today may say something else after the next pricing change. Read them the day you sign up; on the day you want to leave, they are written for the person who has already decided.

And what you took is a snapshot. An export is the site as it was on the day you took it. Whether that matters is the difference between the second model and the third: a bundle is a rendering you now have to keep, while a document is the thing that renders, so moving it is a build rather than a rescue.

How to tell, before you commit

Three questions, answerable on a pricing page without logging in:

• Does the product's own terms mention export, and does the price page say

what is included in the export?

• Can you produce the export today, before you ever need it? A capability

you have never exercised is a capability you do not have.

• Is the underlying format a document you can read, or is it a database behind

a login?

And a platform that does not publish its export terms is not promising you one. Across the platforms we profiled, just under half of what we could read says nothing at all about export — not a denial, not a promise, nothing. That is a fact about what we could read rather than a claim about what those platforms offer, and it is still the most useful thing to take from it: ask for the terms, in writing, before you sign.

The part that is ours

On Zeso the site is stored as a JSON document, and rendering is a service on top of it. The studio and the tenant worker are two readers of that one format, and your content is readable as JSON over an open API — so leaving is a read rather than a purchase, and it does not need a good week to run. We ship no export button and no CLI, and the portability guide says exactly what that means and what to do instead; the comparison pages record what each platform we profiled publishes about export, and where its own pages did not say, they say so.