Nuxt: Application framework

Explore Nuxt’s Vue application framework, universal and hybrid rendering, and the Nitro server engine used to build and deploy full-stack sites.

Updated 8 September 2026

What Nuxt provides for Vue applications

Nuxt builds an application framework around Vue. It supports server-rendered, client-rendered and pre-rendered output, with options to choose behaviour for different routes. Its Nitro server engine supplies server endpoints and deployment output.

For a content site with a member area, public articles and private account pages do not have to follow the same rendering strategy. The architecture should reflect how often the data changes and who is allowed to see it.

Universal rendering and hydration

With universal rendering, the server produces HTML for the initial request and Vue adds browser interactivity through hydration. Pre-rendering produces HTML ahead of time, while client-side rendering makes the browser responsible for generating the interface.

Those choices affect the first page load and when data is fetched. A page that needs browser-only APIs requires care when some code also runs on the server.

Choosing a deployment model

Nitro supports deployment to several kinds of JavaScript environments. Match the chosen target to the application’s server code and dependencies rather than assuming all runtime environments provide identical APIs.

Test content refresh behaviour explicitly. An editor saving a change in a CMS does not necessarily refresh a pre-rendered page until the project’s publishing workflow runs.

How DNSTrace.dev detects Nuxt

Detection reads the final HTTPS response and the first bytes of its markup. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed.

/_nuxt/ in markup — The fixed build output directory for compiled assets.
window.__NUXT__ in markup — The hydration payload the client uses to resume server-rendered state.
x-powered-by naming Nuxt — Emitted by some deployments.

What a detection proves

The page was produced by Nuxt.

What it does not prove

The major version, the rendering mode of other routes, or where the application is hosted.

Common questions about Nuxt

Does every Nuxt page have to use the same rendering mode?

No. Nuxt supports hybrid rendering through route rules, allowing different routes to use different rendering or caching behaviour. The deployment must support the selected features.

Does a Nuxt detection imply Vue?

Nuxt is built on Vue, but DNSTrace.dev reports Vue separately and only when Vue's own scoped-style attributes appear in the markup.

Can a fully static Nuxt site still be detected?

Yes. Prerendered output keeps the /_nuxt/ asset paths and, for hydrated pages, the payload block.

Frontend framework