Download websites that use Nuxt.js

About Nuxt.js

Frameworks get chosen in a room with developers in it, which makes them a different class of signal from anything a marketing team can install on its own. Nuxt.js sits firmly in that class.

Nuxt.js is a JavaScript frameworks in JavaScript, first released in 2016 under the MIT licence, that wraps a component library with conventions for routing, rendering, and data loading so a team can ship server rendered pages without assembling the pieces themselves.

As of September 2026 we detect Nuxt.js on 580,627 sites, 321,479 of them in United States, with .com common across the set. The spread is broader than the country figure alone suggests, because the detections outside the leading country are scattered across many others rather than gathered in a second market, with European and Asian zones prominent among them.

What a meta framework implies is a team, a build step, and a deliberate rendering strategy. A site built this way has developers, a repository, a deployment pipeline, and almost always a headless content source behind it rather than a monolithic content management system. Nobody pushes a framework into production casually, so the buying committee for anything sold onto these domains includes engineering, and the pitch has to survive a technical reading. Sites in the group also tend to carry component libraries, edge hosting, and interface driven commerce, which makes the row an entry point into a whole modern stack rather than an isolated fact.

The list is worth most to vendors whose product lands inside a build pipeline. Headless content platforms, design system and component tools, monitoring and error tracking, edge hosting, and interface first payment and search providers all sell to the same team, and a framework population is a direct proxy for finding it. Recruiters and market researchers use the same view to measure where a framework is actually deployed rather than where it is merely discussed, which are two very different numbers.

Two limits should be stated. We hold no version data for Nuxt.js, so the split between framework generations, which is often the exact question a team weighing a migration wants answered, cannot be resolved from this dataset. And a fully static export can shed the runtime markers that detection depends on, so the published figure is a floor rather than a total. Reading the trend across snapshots is safer than treating any single count as complete.