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
- Edit your site in Webflow, re-export the code, and redeploy it to your server for updates.
- Use third-party services or a custom backend to handle forms, since Webflow’s form handling is disabled after export.
- Build a backend/editor using custom code or a headless CMS to manage content, as Webflow CMS won’t function when self-hosted.
- Exported code remains fully functional and yours even if your Webflow subscription ends, but you can't edit or re-export without an active plan.
If you're exporting your Webflow site and hosting it on your own server, you lose some integrated Webflow functionality, especially with CMS and forms. Here's what you need to know about updates, form handling, backend creation, and subscription impacts.
1. Updating a Webflow Site on a Self-Hosted Server
- Exporting Code: First, export your site’s HTML, CSS, JavaScript, and assets via the Export Code button in the Webflow Designer (only available on a paid plan).
- Deploy to Server: Upload the exported files to your own hosting server using FTP, cPanel, or cloud hosting solutions (like AWS, DigitalOcean, etc.).
- Update Process: To make changes, you must return to Webflow, update your site in the Designer, re-export the code, and re-upload it to your server. This is a repeated manual process.
2. Handling Form Submissions on a Self-Hosted Webflow Site
- Webflow’s Native Form Handling Won’t Work: Once the site is exported, Webflow’s form backend is disabled, and form submissions will not be processed.
- Alternative Options:
- Use a Third-Party Form Service like Formspree, Basin, or Getform. These services provide an endpoint URL to replace Webflow’s default form action.
- Custom Server Script: Create a back-end script (in PHP, Node.js, etc.) to capture submissions, send emails, and/or store data.
- Zapier or Make (Integromat): Connect form submission to automation tools via a webhook. Replace the form’s action URL with Zapier’s webhook endpoint.
3. Creating a Back-End Page for Employee Content Updates
- Self-Hosted Means No Webflow CMS: Webflow’s built-in CMS does not function after export.
- Options for Adding Back-End Functionality:
- Use an External CMS like WordPress or Ghost and embed the content into your static Webflow HTML via Ajax or server-side rendering.
- Build a Custom CMS: Use languages like PHP or frameworks like Django/Laravel to build your own admin dashboard. Store data in a database (e.g., MySQL) and render it into the site’s structure.
- Headless CMS like Contentful, Sanity, or Strapi connected via APIs. Editors use a back-end interface, and developers fetch content with JavaScript or a server-side script.
4. What Happens to Designs if the Webflow Subscription Ends?
- Exported Code Is Yours: After the export, the static HTML/CSS/JS files are permanently yours, and the website will continue functioning independently on your server.
- Designer and Project Access:
- If your Webflow subscription ends, you lose access to project editing and exports in the Designer unless you renew or downgrade to support static-only access.
- If the original project is in a free plan and exceeds limits (e.g., over 2 pages), you won’t be able to edit until you upgrade again.
- You cannot re-import exported code back into Webflow—editing must happen within the Webflow project file.
Summary
To update a self-hosted Webflow site, edit in Webflow, re-export, and redeploy. For forms, use third-party services or a custom backend. A backend for content editing can be built using headless CMSs or custom admin panels. If your subscription ends, your exported code still works, but you lose access to edit or re-export the project in Webflow.