Download websites that use Visual Composer

About Visual Composer

Page builders occupy an odd position in a website. The site owner sees one every day and the developer, if there is one, may never open it. Visual Composer sits in that position on 5,554 sites as of October 2026, turning layout work into dragging blocks around instead of editing templates.

The plugin reaches further into a site than the name suggests. Beyond the content of a page it takes over headers, footers, sidebars and full page layouts through a theme builder, so a site running it has usually handed over the whole front end rather than one page at a time. Visual Composer offers theme integration to template authors who want to ship the builder with a design, which puts a copy on sites whose owner chose a theme rather than a tool. Our record files the plugin as Proprietary software, and free and paid tiers sit side by side in the vendor's own pricing, so an installation on its own says nothing about whether anybody ever paid for it.

Detecting the builder therefore says more about how a site was built than about who built it. Pages assembled this way are tied to the tool, because the layout is held in the builder's own elements rather than in the platform's plain editor. Removing the plugin leaves the pages without the thing that renders them. The practical result is a long tail of sites that keep the plugin active because migrating away means rebuilding every page by hand.

Geography follows the wider WordPress market rather than anything specific to the builder. United States accounts for 5,303 of the sites we see, and most of the domains sit on .com, which is what an English language product priced in dollars tends to produce. The sites underneath that pattern are largely small business and agency built brochure pages, the segment that buys a design tool once and treats the result as finished.

Since 2011 the builder has faced a crowded market of competing builders and a shift in the platform itself toward a native block editor that now does much of the same work at no cost. The move toward the block editor is what makes this list commercially interesting. Every site still running the builder is a site that has not migrated, and each one eventually faces the same decision: rebuild in blocks, move to a competing builder, or stay put. Agencies selling migration work, rival builder vendors and hosting companies planning their support load all want the same thing, which is a list of domains rather than a yes or no answer about one of them.

Detection depends on markup the plugin leaves in the rendered page, and only the browser facing half of a PHP plugin is visible to a crawler at all. A heavily cached or aggressively optimised site that rewrites class names can strip the traces we look for. The figure should be read as sites where the builder is visible in the delivered HTML, not as the number of licences in existence, and the gap between those two counts is real and cannot be measured from outside.