How To Host A Webflow Export Without Webflow

You've decided to leave Webflow, or at least to stop paying for its hosting. The site's finished, it rarely changes, and the plan renews every year whether anyone touches it or not.

Webflow has an export button, so this should be easy. Then you find out two things.

The first is that your site plan doesn't include it. Code export is a feature of Webflow's paid Workspace plans, not its Site plans, so the plan you pay for hosting doesn't let you take the files.

The second is that a Webflow export only carries the parts of the site that are plain files. Your CMS content, your forms, your site search and any password protection stay behind.

You can still move, and plenty of sites should. Just know exactly what's in the ZIP before you cancel anything, because the plan you cancel is also the only way back to your CMS content. The worked example below follows a boutique hotel through the whole move without losing a single page address.

Which Webflow Plan Lets You Export Code?

Only a paid Workspace plan. Webflow's help article on code export says it directly: Site plans do not include the ability to export your site's code. The free Starter workspace doesn't include it either.

At the time of writing, Webflow's pricing page lists code export from the Core workspace plan up, at $19 a month billed yearly. If you only need the files once, check the monthly price before you commit to a year.

You don't need to keep any Webflow plan after you've downloaded the ZIP. Webflow says an exported site needs no attribution and no ongoing plan to work on your own server.

What you're left with is an ordinary static site, and the general method for hosting a static website works the same whatever tool built it.

What Is In A Webflow Export?

The export is a ZIP with every static page and the files they need. You get it from the main menu under Code export, or with Shift and E, then Prepare ZIP.

Inside, according to Webflow's documentation:

• One HTML file per page, including empty Collection template pages
• A CSS folder with three files: your site's styles, webflow.css and normalize.css
• A JS folder that forms, navbars, sliders, tabs and interactions depend on
• An images folder with everything from your Assets panel

Keep the JS folder. Webflow's own warning is that without it a page might look correct but won't work as expected, which is the worst kind of broken because nobody notices until a menu won't open on a phone.

Interactions come along as long as those scripts do. Lottie animations are the exception when testing: they won't play from a file opened on your own computer and need a real web server, so judge them on the live upload, not locally.

If you've never uploaded a ZIP of site files, uploading a ZIP and getting a live site covers the mechanics and the wrapper folder mistake.

What Stays Behind When You Leave Webflow?

Everything that relies on Webflow's servers rather than files. Here's the full list from Webflow's documentation, with what to do about each.

Two rows deserve a second look.

Password protection disappears silently. A page that was protected on Webflow is a normal public page in the export. If you had a private page for staff or trade partners, delete it from the folder before uploading or protect it on the new host.

Forms still look perfect. The exported form renders exactly as it did. It just doesn't send anything, because the processing happened on Webflow's servers. Webflow says forms won't work on exported sites, and you'll need a third-party tool. A form service such as Formspree, Web3Forms or Basin gives you an address to point the form's action at, and it emails you each entry.

Worked Example: A Boutique Hotel Moves Off Webflow

Take a twelve-room boutique hotel. Its Webflow site has a homepage, a gallery, a Rooms collection with six room types, a Journal collection of about twenty posts, an enquiry form, a "Book now" button that opens an external booking engine, and one password-protected page of trade rates for travel agents.

The site changes perhaps four times a year. It still pays for a Webflow site plan with the CMS every year, and the owners would rather spend that money on breakfast.

Here's the move, in the order that avoids losing anything.

1. Get export access first. Upgrade the workspace to a plan with code export. Don't cancel the site plan yet.
2. Export the CMS as CSV. Webflow lets you export Collections as CSV files. Download Rooms and Journal. This is the content the ZIP won't have.
3. Download the ZIP. Prepare it, download it, unzip it, and open index.html locally to see the static pages.
4. Rebuild the room pages. The ZIP includes the empty room template. Make one copy per room, named to match the old address, and fill each from the CSV. An AI assistant will do this well if you give it the template and the CSV together.
5. Decide on the Journal. Twenty posts can be rebuilt the same way. If a few get no traffic, it's fine to let them go, but note their addresses for the check further down.
6. Remove the trade rates page. It's public in the export. The hotel emails the rates sheet to agents as a PDF instead.
7. Replace the enquiry form. Point it at a form service and send a test enquiry.
8. Leave the booking engine alone. The "Book now" button links to the booking provider's own site, so it works exactly as before.
9. Upload, test, then switch the domain. Only cancel the Webflow site plan once the live site checks out.

Step four is where the time goes, and for six rooms it's an afternoon. Any static host takes the finished folder: Netlify, Cloudflare Pages and an ordinary cPanel host all will. how to connect a domain to your website covers the DNS change.

Will Your Old Page Addresses Still Work?

Mostly, but check every one. Webflow serves a page at /rooms, while the export names the file rooms.html, and whether /rooms still works depends on the new host.

On OxyPages, a request for /rooms finds rooms.html automatically, and /rooms.html is sent to /rooms, so the old Webflow addresses keep working unchanged. Other hosts vary, so test yours. Webflow's FAQ suggests an .htaccess file to drop the extension, but that only works on Apache servers, and most modern static hosts ignore it.

Collection pages need the most care. A room that lived at /rooms/garden-suite should be rebuilt as rooms/garden-suite.html or rooms/garden-suite/index.html so the address doesn't change. Google's guidance is that keeping URLs the same is the simplest kind of site move, and anything that does change needs a redirect. Google Search Central on site moves with URL changes

Redirects are the one gap to plan for. OxyPages can't set per-page redirects, so for a retired Journal post you'd keep a short page at the old address that links to the new one. If you're retiring dozens of pages, a host that reads a _redirects file, as Netlify and Cloudflare Pages do, is the better fit.

Before you switch the domain, paste your ten most visited old URLs onto the new address one at a time. Any 404 is a page you forgot to rebuild.

When You Should Stay On Webflow

Stay if the site is a product rather than a brochure. Webflow is the better home in these cases:

• You sell online. Ecommerce doesn't export at all.
• You have member logins. User accounts stay on Webflow.
• Someone edits the CMS every week. A static folder means editing files or asking for help each time.
• You run several languages. Only the primary language comes out.
• A marketing team designs new pages often. Webflow's designer is the reason they chose it.

A static host serves files. It doesn't run a CMS, a store or logins. If your site needs those, OxyPages is the wrong tool, and so is every other static host. The best fit for a static move is a site like the hotel's: finished, steady, and paying for features it no longer uses.

What To Do Next

Make a list of what your site uses before you touch any plan. If it's CMS content, a form and nothing else, you're a good candidate to move.

Then work through it in order: get export access, download the CSVs and the ZIP, rebuild the Collection pages, fix the forms, check your old addresses, and only then cancel.

When the folder's ready, drop the exported folder in and get a live link. Test it on its new address before the domain moves, and keep the Webflow ZIP somewhere safe as a backup.