Sourcemap Explorer
Detect Web framework

How to detect Nuxt on any website

The Vue framework — SSR, file-based routing and module ecosystem on top of Vue 3.

Official site

What is Nuxt?

Nuxt is to Vue what Next.js is to React: a meta-framework with server rendering, file-based routing, auto-imports and a conventions-heavy build toolchain. Nuxt 3+ is fully Vue 3 based.

Nuxt's defining feature is its module ecosystem: `@nuxt/image`, `@nuxt/content`, `@nuxt/i18n`, `@nuxt/devtools` and hundreds of community modules plug in with minimal config and handle common concerns (SEO, images, CMS integration, auth) through shared conventions. This gives Nuxt a distinctive feel — fewer manual integration decisions, more 'install module X and done'. Nuxt 3 is built on Nitro, a Unjs-based server runtime that compiles to multiple deployment targets (Node, Cloudflare Workers, Vercel Edge, Deno Deploy, static). Detecting Nuxt tells you about the deployment flexibility and the module-first architecture style.

Why it matters to identify

Nuxt sites are common in European and Asian markets and are sometimes mistaken for 'vanilla Vue SPAs' by naive detectors. Identifying Nuxt specifically matters because it implies SSR, a specific hydration pattern, specific data layers (`useFetch`, `useAsyncData`), and a module-extension model distinct from Next.js's plugin approach.

A brief history of Nuxt

Nuxt launched in 2016 as a Vue-equivalent of Next.js. Nuxt 2 (2018) was the long-running stable version built on Vue 2. Nuxt 3 (2022) was a ground-up rewrite on Vue 3 with the Nitro server engine. Nuxt 3.x releases have incrementally added server components, Vercel Partial Prerendering equivalent, and improved edge-runtime support.

Ecosystem and common pairings

Common pairing: Nuxt + Vue 3 + Pinia + Nuxt UI (or Nuxt UI Pro) + TailwindCSS + Nitro-based deployment. `@nuxtjs/supabase`, `@sidebase/nuxt-auth`, `@vueuse/nuxt` are frequently seen.

Detection signals we look at

Each signal alone is rarely conclusive; the detector cross-references all of them and weights by confidence. You can reproduce any of these checks yourself in Chrome DevTools.

DOM selector
#__nuxt|#__layout

Nuxt injects `<div id="__nuxt">` and, in some layouts, `#__layout`.

Script src URL
/_nuxt/

Nuxt serves generated chunks from `/_nuxt/`, analogous to Next's `/_next/static/`.

JavaScript global
window.__NUXT__

Hydration payload global, on every SSR Nuxt page.

HTML source
data-n-head|data-nuxt-render

Nuxt head/render attributes on hydrated elements.

Sourcemap path
node_modules/nuxt/

Nuxt package bundled — exact version in the embedded package.json.

Versioning

Sites commonly running Nuxt

  • nuxt.com
  • openai.com (some docs)
  • ecosia.org

Often confused with

Nuxt vs Vue

Nuxt always implies Vue. Look for `/_nuxt/` paths and `__NUXT__` globals to confirm the meta-framework rather than vanilla Vue.

Related

See Nuxt — with the exact version — on every site you visit.

Sourcemap Explorer runs these checks passively in the background. When the target library is bundled, you get the precise package.json-level version.

Install free on Chrome