Open Source Tools

6 Best Open Source Alternatives to Webflow

Updated July 2026

Webflow won designers over by letting them build production sites visually and still ship clean, semantic HTML and CSS, with a CMS attached for content. The pinch is ownership and cost: the work lives inside Webflow's editor and hosting, the exported code is something you look at more than genuinely take with you, and the moment a project needs more CMS items, pages, or scale, the plan tiers and per-site fees start defining what you can build. The open source alternatives below keep the visual canvas but treat the output as yours from the start. You export or self-host clean code, deploy it on any host you like, and run the builder itself on infrastructure you control rather than a subscription that gates pages and publishing.

GrapesJS logo

1.GrapesJS

25.9kOtherTypeScript Self-host
GrapesJS screenshot

GrapesJS is a free and open source web builder framework for building HTML templates for sites, newsletters, and mobile apps. It is designed mainly to be used inside a CMS, where users need to create dynamic templates made from HTML structure, CSS style, and variables rendered later by the application.

  • Build HTML templates for sites, newsletters, and mobile apps
  • Local and remote storage options
  • Built-in commands for creating and managing components
  • Webpage, newsletter, and MJML newsletter presets
More about GrapesJSVisit website
WordPress logo

2.WordPress

21.2kOtherPHP Self-host
WordPress screenshot

WordPress is open source software for creating a website, blog, or app. It is a semantic personal publishing platform and CMS that you install on a web host, then manage through wp-admin in a browser. The installer creates the configuration file with database connection details and sets up the tables needed for the site.

  • Browser-based installer for wp-config.php and database tables
  • Automatic updater in wp-admin/update-core.php
  • Manual upgrade path through wp-admin/upgrade.php
  • Import tools for migrating from other systems
More about WordPressVisit website
Webstudio logo

3.Webstudio

8.6kAGPL-3.0TypeScript Self-host
Webstudio screenshot

Webstudio is an open source visual development platform for developers, designers, and cross-functional teams. It is built for creating websites while keeping the data, components, and infrastructure under your control, with a hosted version available or the option to roll out your own.

  • Visual editor with access to every CSS property and value
  • Reusable styles and design tokens without writing classes
  • Connects to any headless CMS
  • You own the data, components, and infrastructure
More about WebstudioVisit website
Webiny logo

4.Webiny

8kOtherTypeScript Self-host
Webiny screenshot

Webiny is a self-hosted content platform that deploys into your own AWS account on serverless services. It is a TypeScript framework you extend with code rather than a closed product configured through a UI, which fits teams that need data ownership, compliance control, or a CMS embedded inside their own product.

  • Custom content models with a GraphQL API
  • Field-level permissions, localization, and versioning
  • Drag-and-drop page editor with a Next.js SDK
  • File manager with folders, tags, search, and CDN delivery
More about WebinyVisit website
Microweber logo

5.Microweber

3.4kMITHTML Self-host
Microweber screenshot

Microweber is a drag-and-drop website builder and content management system based on PHP and the Laravel framework. It is built to create websites, online stores, and blogs without technical expertise, with a focus on visual editing and content management.

  • Drag-and-drop editing for images, text, videos, modules, and layouts
  • Real-time text editing in Live Edit view
  • Pages, posts, and products with custom categories
  • Built-in e-commerce features for online shops
More about MicroweberVisit website
Silex logo

6.Silex

2.8kAGPL-3.0JavaScript Self-host
Silex screenshot

Silex is a free/libre visual website builder for creating static sites. It solves the lock-in problem common in no-code tools by letting you design visually, export clean HTML and CSS, and host the result anywhere. It is built for people who want a website they can keep, move, and edit without a proprietary format.

  • Drag-and-drop editor with HTML, CSS, and JS editing
  • Static HTML output for hosting anywhere
  • CMS integration with WordPress, Strapi, Squidex, or GraphQL APIs
  • 11ty-compatible templates for static site generation
More about SilexVisit website

Our picks

These three sit at different distances from Webflow: one mirrors the canvas, one prioritizes static ownership, and one is a framework for developers building their own editor.

Closest to Webflow's visual canvas: Webstudio Webstudio is the nearest analog to Webflow's designer, giving visual access to every CSS property and value plus reusable styles and design tokens without hand-writing classes. It connects to any headless CMS and can run on its hosted service or on infrastructure you control. For teams that want Webflow's precision with real ownership of data and components, it is the natural starting point.

Best for clean static output and no lock-in: Silex Silex is built to solve the lock-in problem directly: design visually, export clean HTML and CSS, and host the result anywhere. It binds components to WordPress, Strapi, or any GraphQL API, supports 11ty-compatible templates, and is maintained by the Silex Labs non-profit with open finances and no premium tier. It fits people who want a site they can keep, move, and self-host with Docker or Node.js.

Best for embedding a builder in your own app: GrapesJS GrapesJS is a web builder framework rather than a finished site tool, designed to be dropped inside a CMS or app where users assemble HTML templates from components. With presets for webpages and newsletters and a broad plugin ecosystem, it suits developers building their own editing experience, not teams looking to publish a marketing site out of the box.

Switching from Webflow to open source

Replacing Webflow is not swapping one page builder for another, because Webflow bundles a visual designer, CMS, hosting, CDN, form handling, and client editing into a single workflow. The first decision is whether you want a similar integrated builder or a split stack where the editor, static build, and hosting are separate. That choice matters more than any feature checklist: a split setup gives you more control but moves previews, deployments, image handling, and cache invalidation onto your team.

The alternatives here sit at different points on that spectrum. Webstudio is the closest to Webflow's designer-centric canvas, exposing every CSS property and value and connecting to any headless CMS, with the option to self-host or use its hosted service. Silex leans toward ownership and static output: it exports clean HTML and CSS you can host anywhere, integrates with WordPress, Strapi, or a GraphQL API for content, and is run by a non-profit with no premium tier. GrapesJS is different again - a builder framework meant to be embedded inside your own CMS or app rather than a turnkey site tool, so it fits developers building an editor rather than teams publishing a marketing site. On the content-first end sit WordPress, Microweber, and Webiny, which put a CMS at the center rather than the design canvas - WordPress extended through plugins and themes, Microweber pairing drag-and-drop editing with built-in ecommerce, and Webiny a headless CMS with a page builder that deploys into your own AWS account.

Whatever you choose, migration runs through Webflow's export and a full inventory of pages, templates, redirects, assets, and forms. Static HTML and a CMS CSV give you a visual reference and a short-term bridge, but they rarely become a clean codebase without refactoring, and CMS collections need field mapping, slug checks, and rich-text cleanup. Anything tied to Webflow hosting - forms, search, and password-protected pages - has to be rebuilt before launch, and 301 redirects should go live with the site, not after traffic drops.

Related alternatives

Shopify14WordPress17Buffer6

Frequently asked questions

Will I still get a visual designer after leaving Webflow?+

Usually yes, but expect a different editing model. Webstudio comes closest to Webflow's canvas, giving access to every CSS property, reusable styles, and design tokens. Silex offers a drag-and-drop editor focused on static output. Others, including block-based tools, trade pixel precision for content-team friendliness. If designer-level control matters, test breakpoints, nested layouts, and custom CSS access before committing to any one of them.

What actually breaks when a Webflow site is moved?+

The failures are usually not the visible pages but the services around them. Forms stop submitting until you wire a new handler, search disappears unless rebuilt, CMS references can lose relationships, and redirects get missed. Custom code embeds may depend on Webflow-specific DOM structure. Test every template, form, redirect, tracking script, and breakpoint before you change DNS, because these break quietly.

How do Webflow CMS collections migrate to an open source CMS?+

Export each collection as CSV, then map its fields to the new content model. Simple text, numbers, dates, slugs, and plain images are manageable; rich text, multi-reference fields, and media galleries need cleanup. Silex and Webstudio both connect to headless CMSes, so part of the decision is which CMS holds the content afterward. Preserve original slugs where you can, and review imported content because automated migration rarely captures editorial intent.

What happens to my Webflow forms in an open source setup?+

Webflow form submissions run on Webflow's hosted handling, so after export the form markup may survive but submissions do not. You need a new backend, email service, CRM integration, or serverless endpoint, plus spam protection, validation, and notification routing. A form that looks migrated is not necessarily operational, so test a real submission end to end before launch.

How do I protect SEO when moving off Webflow?+

Keep URL paths stable wherever possible. Document every page, CMS slug pattern, canonical URL, title, description, and redirect before you move, then recreate 301 redirects before launch rather than after traffic drops. Compare old and new HTML for headings, structured data, and alt text. After launch, crawl the new site and watch indexing so a rebuild does not quietly cost you rankings.

Do I have to self-host, or can someone else run it?+

No self-hosting is required. Webstudio and Silex can run on your own servers or containers, and Webstudio also offers a hosted service, while Silex has a free hosted version plus static output you can put on any host. The real question is who owns updates, backups, SSL, and uptime. If nobody on the team wants that work, use managed hosting even with open source software.