This guide uses "self-host your website" for one job. You leave Wix, Squarespace, Webflow, Framer, or a similar hosted builder. Then you serve the public pages from a host you control.

The new host can be Netlify, Vercel, GitHub Pages, Cloudflare Pages, object storage with a CDN, or a VPS. You choose the host. You can change it later. You do not need a rack of hardware at home.

This is the general hub for that move. Builder-specific checklists live elsewhere. Use the Wix self-hosting guide, the Squarespace self-hosting guide, the Webflow export playbook, or the guide on leaving Framer when you already know the source platform.

Only move a site you own or are authorized to copy. A public URL is not permission to copy, republish, or host someone else's website.

Self-hosting a website versus self-hosted apps

People looking up "self host website" often mix two jobs.

One job is running software you operate for yourself. Examples are Nextcloud, Immich, a home dashboard, and other apps discussed on r/selfhosted. That path is about a Raspberry Pi, a NAS, Docker, and a private network.

The other job is taking a public marketing site off a hosted website builder and putting it on hosting you control. That is this article.

If you want to self-host apps at home, this page is the wrong guide. If you want to leave Wix, Squarespace, Webflow, Framer, or similar builder hosting and keep the public site online, keep reading.

Why people leave builder hosting

People leave builder hosting for concrete reasons, not slogans.

Monthly cost. A builder plan can be worth it while you are still designing. After the site is stable, you may be paying for an editor and hosted apps you no longer use. Static hosts and a cheap VPS often cost less for a brochure site.

Ownership of files. On a hosted builder, canceling the plan can take the live site with it. If you have the files, you can upload them to another host.

Portability. If the public pages are ordinary HTML, CSS, JavaScript, images, and fonts, you can change hosts without rebuilding the design from memory.

Lock-in you can name. Forms, CMS editing, memberships, and checkout often live only on the builder. Those features are the real lock-in. Leaving without a replacement for them is how a migration fails.

Leaving is not automatically an upgrade. Stay if the editor is still worth the monthly fee. Stay if the hosted features are the product. Stay if no one on the team can maintain files or a CMS.

What you need before you move

Do this inventory while the current site is still live.

Domain and DNS access. Confirm you can log into the registrar or DNS host. Save the current records. If you can lower TTL a day or two before the DNS change, do that. Some resolvers will still cache longer.

Page inventory. List the homepage, pricing, contact, legal, blog or CMS item templates, localized routes, and any deep URL that brings traffic or conversions. You will test those URLs on the new host.

Hosted feature inventory. Note every form, store, membership gate, booking tool, search box, comments widget, and login. A static copy can keep the visible page. It cannot keep the backend.

A working copy of the public pages. You need files you can open and click through before DNS moves. For many brochure sites that copy is a static ZIP of published pages. For sites that must keep a CMS, use a staging WordPress or similar install, plus a visual reference of the old public site.

Authorization. Export and republish only sites you own or are allowed to copy.

Path A. Static files on a host you control

This is the main path for most people leaving a website builder.

You capture the published public pages as static files. You deploy those files to a static host. You replace forms and other hosted services if you still need them. You point DNS at the new host only after the deploy passes checks.

A typical snapshot ZIP contains HTML, CSS, JavaScript, images, fonts, and other public assets. Exporters rewrite internal links so navigation works without the original builder. That is what a website-to-ZIP export is for. The broader crawl, verify, and deploy checklist is in how to download an entire website as HTML, CSS, JavaScript, and assets. If you are still choosing a tool category, start with best website downloaders.

Make a copy of the live published pages as files. Export Your Site is one way to create that copy. The copy is a published-page snapshot. It is not a CMS or database export, not a designer project file, not a forms backend, not ecommerce, not memberships, and not private pages.

Use Path A when:

the site is mostly a brochure, portfolio, landing page, or docs site;
you are fine without a CMS dashboard;
you can replace or drop builder-hosted forms and apps;
you want a host you can change later without a new builder subscription.

Skip Path A as the long-term home when you need a store, member logins, or a team CMS. Use the snapshot as a bridge, then follow Path B.

How to put the ZIP on Netlify

The same idea works on Vercel, Cloudflare Pages, GitHub Pages, and object storage with a CDN. Netlify is a typical static host, so the steps below are concrete. Translate the clicks to whichever host you picked.

Unzip the archive on your computer.
Find the folder that contains index.html. Some ZIPs nest the site one directory down. Upload that folder, not the outer wrapper.
Click through the files locally if you can. Missing images and broken menus are cheaper to see now.
Sign in to Netlify and create a new site. Drag the folder onto a manual deploy, or put the files in a Git repo and connect the repo.
Open the temporary hostname Netlify assigns, usually a *.netlify.app URL.
Test the homepage, a few deep pages, mobile navigation, images, fonts, and the contact path. Submit a form only if you have already pointed it at a new endpoint you control.
Check 404 behavior, HTTPS, and whether inner routes 404 because the files are about.html instead of about/index.html. Add a redirect rule on the host if clean URLs need it.
Keep this temporary URL as the source of truth until it passes. Do not change DNS yet.

GitHub Pages can host a small static site for free. Add a .nojekyll file at the site root so Pages does not run Jekyll on the files. Cloudflare Pages and a Netlify starter plan can also host a small site at no charge if you stay inside their free limits. "How to self-host a website for free" still usually includes a paid domain. The registrar bill is separate from hosting.

Path B. Rebuild on WordPress or another CMS

Choose Path B when someone still needs to edit pages, publish posts, or run a content model after you leave the builder.

On Path B you install a CMS you can host, such as WordPress. The old builder does not come with you. Ghost, a static-site generator with a Git workflow, or another CMS can fit the same need.

Do not treat a static ZIP as a WordPress import. The ZIP is a visual reference and a temporary public copy. Posts, pages, fields, users, plugins, and themes have to be created or imported in WordPress on purpose.

A realistic order:

Keep the current builder site live.
Capture a public snapshot so you have a clickable reference.
Stand up WordPress, or another CMS, on staging.
Rebuild templates and navigation to match the pages that matter.
Move structured content through official exports, CSV, APIs, or a manual copy. Then spot-check slugs, images, and metadata.
Replace forms, search, and other hosted features in the new CMS.
Verify staging, then change DNS last.

If Webflow is the source and WordPress is the destination, use the Webflow to WordPress guide. That post is the deep dive. This hub only points to that path.

The reverse job is different. If you already run WordPress and want files instead of PHP, see convert WordPress to static HTML.

Path C. A VPS or your own hardware

You can host a website on your own server. A VPS from a provider, a machine in a rack, or a Raspberry Pi at home can all serve index.html with nginx or Caddy.

For most people leaving a website builder, this should not be the first path.

A VPS adds operating system updates, TLS certificates, firewall rules, backups, uptime monitoring, and a plan for disk and traffic. That work is normal if you already run servers. It is extra risk if you only wanted to cancel a Wix or Squarespace plan.

A home Pi or NAS is a weak primary host for a public marketing site. Residential ISPs, power cuts, dynamic IPs, and upload bandwidth show up as downtime. Use home hardware for experiments. Use a static host or a maintained VPS for the domain customers type.

If you still want this path, put the static files or the CMS on the server. Serve them with a web server over HTTPS. Test on the server hostname. Point an A or AAAA record at that server after checks pass. Keep the builder live until that hostname stays up.

What a static ZIP includes, and what it does not

A published-page snapshot can include:

HTML for the homepage and captured public routes;
CSS and browser JavaScript used by those pages;
images, icons, fonts, and public downloads;
rewritten internal links between captured pages;
the look of forms, carts, and login screens, as HTML.

It does not include:

the builder editor or designer project;
a CMS or database you can keep publishing into;
form delivery, inboxes, or CRM pipelines;
ecommerce inventory, checkout, orders, or customer accounts;
memberships, gated pages, or private dashboards;
unpublished drafts, collaborator settings, or billing records.

The files are yours. An AI assistant such as ChatGPT, Claude, or Cursor can help you swap text or add a page. A store, member logins, or a team CMS still need their own tools.

Change DNS last

Keep the builder site live while you test.

Save current DNS records. Deploy the replacement on a temporary hostname. Click the page inventory on that hostname. Confirm HTTPS. Confirm redirects you care about. Confirm that forms post somewhere you control, or that you have removed them on purpose.

Only then point the domain at the new host. Watch the homepage, a deep URL, TLS, and the main conversion path. Leave the builder plan running during that window. Overlapping hosting for a few days is cheaper than an outage.

If canonical tags, sitemaps, or Open Graph URLs still name the old builder hostname, update them on the new host before you treat the cutover as done.

Cancel builder hosting after the new host passes checks

Do not start by canceling Wix, Squarespace, Webflow, Framer, or any similar plan.

Cancel after:

the domain resolves to the new host;
the page inventory loads without the old builder;
required forms and integrations work, or you accepted dropping them;
you have the ZIP, a Git copy, or another durable backup of the files;
you know how the next edit will be made.

Then cancel only the site plan, app, or domain connection you no longer need. If email, another site, or a store still uses the same account, leave that piece alone.

FAQ

What does it mean to self-host your website?

Here it means leaving hosted website-builder infrastructure and serving the public site from hosting you control. The files may be a static snapshot or a CMS you install. It does not mean running a homelab of self-hosted apps unless that is a separate project.

How do I self-host a website after leaving a builder?

Inventory pages and hosted features, get a working copy of the public site, deploy it to a temporary hostname, replace forms and other services you still need, change DNS last, and cancel the builder only after the new host passes those checks.

How do I host a website on my own server?

Put static files or a CMS on a VPS or machine you administer, serve them with a web server over HTTPS, test on the server hostname, then point DNS at that server. For a marketing site leaving a builder, a managed static host is usually less work than running the server yourself.

Can I self-host a website for free?

You can put a small static site on GitHub Pages, Cloudflare Pages, or a Netlify starter plan at no hosting charge if you stay inside the free limits. A custom domain from a registrar is usually not free.

What does self-hosting a website builder mean?

It can mean two things. This hub is about leaving a hosted builder and putting the public site on hosting you control. The other meaning is installing a CMS or builder, such as WordPress, on a server so you can keep editing. That is Path B, not Path A.

Does a static ZIP include forms, ecommerce, or memberships?

No. The ZIP can keep the public HTML for those screens. Submission handling, checkout, inventory, accounts, and gated content stay on the original platform unless you replace them.

Should I cancel the builder before I self-host?

No. Keep the live site up until the new host has been tested, the domain points at it, and the checks in this guide pass.

Is this the same as r/selfhosted or a Raspberry Pi setup?

No. Those communities are mostly about self-hosted apps and home servers. This page is about a public marketing site leaving Wix, Squarespace, Webflow, Framer, or similar builder hosting.

How do I self-host a Wix, Squarespace, Webflow, or Framer site?

Follow this hub for the hosting decision, then use the builder guide for platform traps: Wix, Squarespace, Webflow, and how to self-host a Framer site.

Can I edit the site after I deploy the ZIP?

Yes. The files are yours. An AI assistant can help you swap text or add a page if you do not want to hire a developer. A store, member area, or CMS dashboard still needs a separate tool if you use those.

A published-page copy can start from the homepage.