Webflow
Design a responsive site, manage its content and host it from the same workspace.
Webflow Funding History
Webflow develops a visual web design platform. The company was founded in 2012 and is based in San Francisco.
Company Overview
Webflow
San Francisco, California, US
Official WebsiteWebflow Funding Timeline
Series C
US$120 million
Webflow set aside $10 million for community grants alongside the round.
Led by Y Combinator Continuity. Participation included CapitalG, Silversmith Capital Partners, Accel, Draper Associates.
Source · prnewswire.com ↗Series B
$140 million
CapitalG joined the round, and its general partner Laela Sturdy joined Webflow’s board.
Led by Accel, Silversmith Capital Partners. Participation included CapitalG.
Source · prnewswire.com ↗Series A
US$72 million
Webflow had operated on seed funding for years and grown from a landing-page builder into a visual platform for building more complex websites.
Led by Accel.
Source · webflow.com ↗Seed
$1.5 million
Webflow disclosed the seed funding after participating in Y Combinator, as it developed tools to design and host responsive websites.
Participation included Y Combinator, Khosla Ventures, Draper Associates.
Source · techcrunch.com ↗
Webflow Founding Team
Vlad Magdalin, Sergie Magdalin, and Bryant Chou started Webflow to give designers more control over building websites. The three joined Y Combinator after launching the beta and seeing early interest from designers.
Webflow Products
Webflow Company Development
Campaign Production Extends the Website Builder
Webflow expanded beyond its visual site builder with the 2026 acquisition of Vidoso. The acquisition brought brand-aligned content generation into the wider marketing workflow, alongside the tools teams already use to manage and publish their sites.
Webflow Competitive Landscape
Visual Site Operations and Code Deployment
Webflow and Vercel meet at the point of publishing to the web. Webflow is organized around a visual editor and site content, while Vercel's platform is organized around application deployments. The distinction matters to teams that expect marketers to make routine site changes themselves.
