Webflow Hosting: What the Platform Covers and What You Handle Yourself

Webflow hosting is the managed hosting included in every paid site plan: Webflow delivers your website via a global CDN and takes care of SSL certificates and backups. You don't need your own server. Domain and email still stay with you, as do consent and tracking.

We've been working with Webflow for six years and have delivered more than 50 Webflow projects. Here we first explain how hosting works and what it means for security and performance. Then we show how far it carries during traffic spikes and what you need to handle yourself before launch. Finally, we clarify when an export or a different hosting option is the better choice.

How Webflow hosting works

You build the website in Webflow and publish it directly from the platform; Webflow then serves it on its own infrastructure. According to Webflow, hosting runs on AWS, with delivery through Cloudflare's CDN. For your own domain, you need a paid site plan; for testing, the free webflow.io address is enough.

In practice, the process looks like this:

1. Build the website in the Designer and test it on the webflow.io address.
2. Book a suitable site plan for the website.
3. Connect your own domain to Webflow via DNS records.
4. Publish. From then on, Webflow serves the site via the CDN.

If you're completely new to Webflow, you'll find the platform basics in the article What is Webflow? If you're coming from WordPress, the system comparison Webflow vs. WordPress will help.

Staging and production

Every Webflow website has a free address on webflow.io that serves as a staging environment. There, your team reviews changes before they go live on your own domain. According to Webflow, a custom or private staging domain is only available with Enterprise. From Basic upward, however, you can password-protect the website or individual pages.

The staging version shouldn't also end up in Google's index. In the site settings under SEO and Indexing, you can disable indexing of the webflow.io subdomain. Then save the change and publish the website. Webflow then creates a robots.txt only on the staging address, telling search engines to ignore that domain. According to Webflow's help center, this requires a site plan or a paid workspace.

Site plan instead of your own server

At Webflow, hosting is tied to the site plan, and every website with its own domain needs its own plan. According to Webflow, Basic is meant for websites without a CMS and is listed on the Webflow pricing page at USD 15 per month billed annually, or USD 25 billed monthly. Premium is aimed at websites with CMS content such as a blog or customer testimonials and costs USD 25 per month billed annually, or USD 39 billed monthly (as of 9 Nov 2026, source: webflow.com/pricing). For a B2B SaaS website, Premium is therefore usually the realistic plan. We compare the full overview and other differences between the plans in our Webflow pricing article. Prices can change, so check them on the pricing page before you book.

Connect the domain, keep email separate

Webflow is not a domain registrar. You can buy a domain through Webflow via IONOS, but usually you connect an existing domain via DNS records. Webflow doesn't host email inboxes, so your MX records stay with your email provider. Document them before you change DNS settings, so no emails get lost after launch.

Security: what Webflow handles and what stays with you

Webflow handles SSL and protection against DDoS attacks, as well as platform maintenance. What stays with you is mainly whatever you add or grant access to yourself. The table shows where the line runs.

A restore point resets the website in Webflow to a saved state, including design, CMS and files. Anything outside Webflow, such as entries in your CRM or data in a connected form service, won't come back that way. After restoring, check forms separately: Webflow turns off form-level bot protection (Cloudflare Turnstile), and you need to re-enter any stored reCAPTCHA keys. DDoS protection via the Cloudflare network is unaffected.

For privacy, storage location and contract matter most. According to its Privacy FAQs, Webflow stores customer data in the US and is certified under the EU-U.S. Data Privacy Framework. Webflow provides a data processing agreement to all customers regardless of plan. Still, align its use with your data protection officer, since these are Webflow's own statements and not legal advice.

Performance: what the CDN does and what's up to you

Webflow delivers your pages via a global CDN, so visitors load them from a server near them. Responsive images are included in every plan, and images can be converted to WebP or AVIF. Heavy videos and lots of third-party scripts still make a page slow, because the CDN only delivers them faster; it doesn't make them smaller.

Your team has the biggest lever with media and scripts. Check these points regularly:

• Compress images before uploading and convert them to WebP or AVIF.
• Embed videos via a video service instead of uploading them directly.
• Remove tracking and chat scripts whose data nobody analyzes anymore.
• Test new landing pages on a smartphone and with a slow connection before launch.

Scaling: what "scales automatically" means

Webflow promises that its hosting absorbs traffic spikes automatically. The limit marketing teams actually hit in practice is usually the site plan, with its bandwidth and CMS limits. The three questions below help you put it in context.

What "scales automatically" means

According to Webflow, the hosting infrastructure scales automatically and absorbs traffic spikes. That's a vendor statement about the platform, not a guaranteed quota for your individual site plan. How much bandwidth and how many CMS items your website may use is still set by the plan. For the launches of typical B2B SaaS marketing teams, standard hosting is enough in our view.

Bandwidth and add-ons

Bandwidth is the amount of data your website delivers to visitors per month. According to the Webflow pricing page, Basic includes 10 GB, while Premium starts at 50 GB and can be expanded up to 2.5 TB via add-on (as of 9 Nov 2026). You can see your current usage under Site settings, then Site usage. If you exceed the limit, Webflow notifies you by email and with a banner in the dashboard, according to its help center.

Short-term spikes are covered by surge protection: in the first month over the limit, there are no extra costs. If the website stays over the limit two months in a row, Webflow automatically upgrades the plan or the bandwidth add-on. So keep images and videos lean before buying more bandwidth.

When Team or Enterprise becomes relevant

Webflow only specifies an SLA with a percentage for hosting availability from the Team plan upward. According to the pricing page, Team guarantees 99.00 percent availability of the published website, Enterprise 99.99 percent (as of 9 Nov 2026). The SLA describes contractually guaranteed availability, not the availability of the Designer. Site plans come with a standard agreement without a percentage.

Team costs USD 2,500 per month and requires an annual contract, so it's in a different price range from Basic or Premium. Enterprise adds, among other things, custom SSL certificates. Most B2B SaaS marketing websites need neither Team nor Enterprise. So don't book a bigger plan as long as nobody uses its features.

Checklist: what you need to handle yourself before launch

The platform takes a lot off your plate, but a few points stay with you before every launch. Go through this list before go-live:

1. Domain and registrar: Sort out access to your domain provider before launch day.
2. DNS including MX: Document existing email records and only switch the website records to Webflow.
3. Site plan: Book Premium if your blog or use cases come from the CMS. Basic is only enough for websites without a CMS.
4. Staging test: Click through all pages, including forms, on the webflow.io address. You can also check target pages and the redirect plan there. After the domain switch, you also need to verify the redirects of your old URLs on the live domain, because staging doesn't fully reflect live conditions.
5. Consent tool: Add a consent banner, because Webflow doesn't come with one.
6. Tracking and CRM forms: Check that analytics events and form data arrive from the new site.
7. Access and 2FA: Assign workspace roles and turn on two-factor authentication for all accounts.
8. Backup before major changes: Create a backup point manually before a rebuild, because Webflow doesn't offer scheduled backups. Only Site Managers can restore.
9. Redirects: In a relaunch, point old URLs to the new pages with 301 redirects and check them on the live domain after go-live.

When switching systems, content and URLs from the old system come on top. We describe how to approach this in our article on Webflow migration. What to watch out for regarding rankings is covered in our guide to SEO during a website relaunch.

When external hosting or an export makes sense

A code export is mainly worthwhile for websites that consist only of static pages. As soon as CMS content or forms are involved, Webflow hosting is almost always the simpler solution. The reason lies in what gets lost in the export.

With a paid workspace plan, you can export your website's HTML and CSS and host it elsewhere. According to Webflow, CMS content isn't part of the code export; you export it separately per collection as CSV, and forms no longer work outside Webflow. You also can't import exported code back into Webflow.

Besides classic Webflow hosting and the code export, there's a third option for Enterprise. According to the pricing page, Webflow can set up dedicated hosting clusters for very high traffic (Custom Hosting Clusters). The website then stays in Webflow, so you don't have to export the code and run it yourself. Most B2B SaaS marketing websites don't need this.

An export makes sense if your website has to run on servers in a specific country or depends on your own backend logic on existing servers. If content should live as data in several systems, such as on the website and in the help center, an export is the wrong path. Then a setup with Astro and Sanity can make sense, where you own the code and content is available in structured form.