Base Frameworks vs. Meta-Frameworks

React and Vue are base frameworks — libraries for building user interfaces, without an opinionated structure for routing, server rendering, or build configuration. Next.js and Nuxt are meta-frameworks built on top of them, adding routing, server-side rendering, and a standardized project structure. A site can use React directly or use Next.js (which uses React internally) — detection distinguishes between these because the meta-framework introduces its own additional, more specific signature.

Next.js sites show a distinctive __next root container in their HTML and load assets from a _next/static/ path. Nuxt sites show a __nuxt root container and load assets from _nuxt/. When these meta-framework signatures are present, they're reported instead of just the underlying base framework, since they're more informative about the site's actual technical setup.

Identify the JavaScript framework instantly
Free, no sign-up, results in seconds
Open the Tool →

Static Site Generators and Newer Frameworks

Astro, Gatsby, and similar static site generators produce their own distinctive output even though some are built on React or other base frameworks internally. Astro sites are identifiable by astro-island custom HTML elements used for selective hydration. Gatsby sites show distinctive ___gatsby root containers and a characteristic webpack-generated asset structure. Svelte compiles away the framework itself at build time, but produces a distinctive class naming convention (svelte-[hash]) in its compiled CSS output that remains detectable.

Detecting these accurately matters because each represents a meaningfully different technical and performance profile — a statically generated Astro or Gatsby site behaves very differently in terms of load performance and hosting requirements than a fully client-rendered React single-page application, even though both might appear similar at a glance.