What is the process for updating a website built with Webflow after exporting the code and hosting it on your own servers? What are the options for handling form submissions on a self-hosted Webflow website? How can a back-end page be created for employees to make changes to the website? What happens to website designs if the Webflow subscription ends?
TL;DR
- Re-export and manually replace code via FTP to update a self-hosted Webflow site.
- Use third-party form services or custom backend code to handle form submissions.
- Build a backend or integrate an external CMS to allow employee content edits.
- Exported sites remain functional if your Webflow subscription ends, but editing and CMS access are lost.
When you export a Webflow website and host it on your own servers, you lose access to some Webflow features. Here’s how to update it, handle forms, create a backend, and what happens if your subscription ends.
1. Updating a Self-Hosted Webflow Site
- Webflow does not sync changes to exported code. When you edit your site in Webflow Designer, you must re-export the code and replace the old files on your server.
- Steps to update:
- Open Webflow Designer, make your changes.
- Click Export Code (top-right arrow icon).
- Download the ZIP file, extract the contents.
- Upload/replace the files on your web host manually or via FTP.
- There’s no automatic deployment—exported files are static HTML, CSS, JS.
2. Handling Form Submissions on a Self-Hosted Site
- Webflow’s built-in form handling only works when hosted on Webflow.
- For self-hosted forms, you must use your own form backend. Options:
- Form backend services: Use services like Formspree, Formbucket, Basin, or Getform. These allow you to connect static HTML forms via form action URLs.
- Server-side processing: Develop a PHP, Node.js, or Python script on your server to collect form data and send emails or store in a database.
- Zapier or Make (Integromat): Use Webhooks to send submitted data to automation platforms.
3. Creating a Back-End Page for Employee Edits
- Webflow exports static files, so there’s no built-in CMS or admin portal on self-hosted sites.
- To allow updates without re-exporting:
- Build a custom CMS/backend: Use frameworks like WordPress (headless or hybrid), Strapi, or a traditional database+admin panel to manage content.
- Integrate a third-party CMS: Platforms like Netlify CMS or Sanity can be embedded into static sites to manage dynamic content.
- Use Webflow CMS API: If you host the editor page elsewhere and still have a Webflow CMS plan, your employees can update content through Webflow, and you can use the CMS API to sync changes.
- These setups typically require developer involvement.
4. What Happens If Your Webflow Subscription Ends
- If your subscription ends:
- You keep any exported code—you can continue to host and use it on your own server.
- You lose access to the Webflow Designer, CMS, Editor, and hosting features.
- You can’t make further changes or re-export unless you reactivate your account.
- Projects may become locked/read-only depending on the plan and account status.
Summary
To update a self-hosted Webflow site, re-export and replace the code manually. For forms, use a third-party service or custom backend. To enable employee edits, you’ll need to build a custom backend or use an external CMS. If your Webflow subscription ends, your exported site keeps working, but you lose access to editing and CMS features.