How it works
A Nuxt project maps files in a pages folder to URLs, auto-imports components and helpers, and renders each route on the server, at build time or in the browser, as configured. Its server engine, Nitro, runs API routes and deploys the same app to Node.js, serverless platforms or edge networks through presets.
A large module ecosystem adds content sites, images, authentication, SEO and UI kits such as Nuxt UI. NuxtLabs, the company behind it, joined Vercel in 2025; Nuxt and Nitro stayed MIT-licensed and host-neutral, and several previously paid add-ons became free.
Nuxt pros and cons
Pros
- Vue's official answer for server rendering and full apps
- Sensible defaults: auto-imports, file routing and layouts
- Nitro deploys to almost any host, from Node.js to the edge
- Rich module ecosystem for content, images and SEO
Cons
- Smaller community than Next.js
- Auto-imports and conventions can feel like magic when debugging
- After a major upgrade, some modules take time to catch up
When to use Nuxt
Pick it when
- Vue teams building SEO-friendly sites, stores or apps
- Content sites that also need server routes
Skip it when
- The team works in React (Next.js or React Router fits better)
Nuxt pricing
Related terms
More in Frontend
Meta-frameworks