Download websites that use Vue.js

About Vue.js

Counting a modern JavaScript frameworks honestly means starting with what the count leaves out. Vue.js can be loaded from a public CDN as a plain script tag, in which case detection is trivial. The framework can equally be compiled into an application bundle, renamed by a minifier, tree-shaken and served as an anonymous blob of JavaScript, in which case a crawler sees a framework-shaped application and no framework at all. As of September 2026 we detect it on 2,088,043 sites, and the honest description of that figure is a floor rather than a measurement.

The bias runs in a known direction, and knowing the direction is what makes the data usable. Detectable installs skew toward the progressive end of the framework's own design, where it is dropped into an existing server-rendered page to make one part of it interactive. Build-tool installs, which is how most greenfield single-page applications are written, are systematically underrepresented. The list is closer to a census of sprinkled-in interactivity than to a census of engineering teams that have standardised on the framework.

Version data carries the same fingerprint. We record 1,071 distinct version strings, and the one that recurs most often is 2.7.14, which belongs to the older major line rather than the current one. The reason is the same as before. A pinned CDN URL is readable and rarely revisited, while a bundled install is unreadable and quietly current. Anyone using our version breakdown to argue about migration progress across the ecosystem would be reading the artefacts of detection rather than the state of the ecosystem, and we would rather say so than let the chart speak for itself.

United States accounts for 746,044 of the sites where we find it, and .com carries the bulk of the domain mix. The framework has been available under MIT since 2014, so it costs nothing to adopt and presence implies no purchase whatsoever. What presence does imply is a development style. Somebody wrote components, somebody set up reactive state, and somebody on that project is comfortable maintaining JavaScript beyond a plugin settings screen.

A capability signal of that kind narrows the audience for the list considerably. Component and interface kit vendors, headless content and commerce platforms, error monitoring and performance tooling, and recruiters mapping which employers actually run the stack they advertise all want the same underlying thing, which is a population of sites with in-house front-end capability. Agencies use the list in reverse, to find sites that have outgrown a page builder and are ready for a rebuild conversation. Security researchers use it to study how client-rendered pages behave under content policies.

A per-domain lookup settles a single question, which is whether one site loads the framework today. The downloadable list is what the work needs when the question is shaped the other way round. Which sites pair it with a particular backend or commerce platform, how the detectable population splits across countries and suffixes, which hosting networks concentrate it, and whether it is being displaced on the same domains from one snapshot to the next. Attach the caveat about bundled installs to every one of those answers and the analysis stays honest while remaining genuinely useful, which is a better outcome than a confident number nobody can defend.