Download websites that use Webflow

About Webflow

Behind every website sits a quiet question about who actually holds the keys. Webflow answers it more cleanly than most entries in this dataset.

Webflow is a Page builders platform from Webflow Inc., launched in 2013, that produces JavaScript driven sites through a visual canvas and hosts them on its own infrastructure. Nothing about a Webflow site requires a server administrator, a deployment pipeline, or a plugin update, and that absence is the entire proposition.

As of September 2026 we detect Webflow on 583,784 sites. United States accounts for 529,168 of those, and .com is the suffix running through the set. A distribution weighted that heavily toward one market means the install base works as a proxy for a particular slice of the American commercial web rather than as a global sample, and anyone extrapolating from it to another region should do so carefully.

Webflow presence tells you who was allowed to build the site. Marketing and design own the page, engineering was not in the room, and the money came out of a brand or growth budget rather than a product roadmap. Sites in the group tend to belong to venture backed startups, agencies, consultancies, and business software companies that needed a fast, well designed public face without spending developer time on it. Integrations arrive as embedded scripts rather than as committed code, which has a useful side effect: the rest of the stack on those domains is unusually legible from the outside.

The commercial value follows directly from the ownership question. Vendors whose buyer is a marketing team get a population whose marketing team demonstrably controls the website and can adopt a tool without filing an engineering ticket, which shortens a sales cycle more than any amount of firmographic filtering. Agencies get prospects already committed to a platform they build on. Competing builders and headless content vendors get a defined displacement target with a known switching cost. A per-domain check confirms one site. A list segmented by country, by suffix, and by the analytics, payment, and support tools running alongside turns an install base into a territory somebody can work.

There is a second, less obvious use for the population. Because these sites are assembled rather than coded, the tools bolted onto them are a fair record of what a non engineering team will actually adopt without help, which makes the group a useful test bed for anyone trying to understand self serve adoption in general rather than adoption of this platform in particular.

One structural limit deserves a mention. Webflow permits exporting a site's code and hosting it elsewhere, and an exported site sheds much of what identifies the platform, so builds that left the nest are undercounted. Detection otherwise rests on hosting and markup fingerprints that the vendor can change whenever it likes, which is another reason to trust movement between snapshots more than an exact figure on any single day.