Nuxt on Vercel
Last updated September 24, 2025
Nuxt is an open-source framework that streamlines the process of creating modern Vue apps. It offers server-side rendering, SEO features, automatic code splitting, prerendering, and more out of the box. It also has an extensive catalog of community-built modules, which allow you to integrate popular tools with your projects.
You can deploy Nuxt static and server-side rendered sites on Vercel with no configuration required.
To get started with Nuxt on Vercel:
- If you already have a project with Nuxt, install Vercel CLI and run the
vercelcommand from your project's root directory - Clone one of our Nuxt example repos to your favorite git provider and deploy it on Vercel with the button below:
- Or, choose a template from Vercel's marketplace:
Vercel deployments can integrate with your git provider to generate preview URLs for each pull request you make to your Nuxt project.
The following table outlines the differences between and on Vercel:
| Feature | ||
|---|---|---|
| Default build command | Yes | No |
| Supports all Vercel features out of the box | Yes | Yes |
| Supports SSR | Yes | No |
| Supports SSG | Yes, with nuxt config | Yes |
| Supports ISR | Yes | No |
In general, is likely best for most use cases. Consider using to build fully static sites.
You can configure your Nuxt deployment by creating a Nuxt config file in your project's root directory. It can be a TypeScript, JavaScript, or MJS file, but the Nuxt team recommends using TypeScript. Using TypeScript will allow your editor to suggest the correct names for configuration options, which can help mitigate typos.
Your Nuxt config file should default export by default, which you can add an options object to.
The following is an example of a Nuxt config file with no options defined:
See the Nuxt Configuration Reference docs for a list of available options.
With the config option, you can:
- Create redirects
- Modify a route's response headers
- Enable ISR
- Deploy specific routes statically
- Deploy specific routes with SSR
- and more
At the moment, there is no way to configure route deployment options within your page components, but development of this feature is in progress.
The following is an example of a Nuxt config that:
- Creates a redirect
- Modifies a route's response headers
- Opts a set of routes into client-side rendering
To learn more about :
- Read Nuxt's reference docs to learn more about the available route options
- Read the Nitro Engine's Cache API docs to learn about cacheing individual routes
Vercel Functions enable developers to write functions that uses resources that scale up and down based on traffic demands. This prevents them from failing during peak hours, but keeps them from running up high costs during periods of low activity.
Nuxt deploys routes defined in , , and as one server-rendered Function by default. Nuxt Pages, APIs, and Middleware routes get bundled into a single Vercel Function.
The following is an example of a basic API Route in Nuxt:
You can test your API Routes with .
You can read and write server files with Nuxt on Vercel. One way to do this is by using Nitro with Vercel Functions and the Vercel KV driver. Use Nitro's server assets to include files in your project deployment. Assets within get included by default.
To access server assets, you can use Nitro's storage API:
To write files, mount KV storage with the Vercel KV driver:
Update your nuxt.config.ts file.
Use with the storage API.
See an example code repository.
Middleware is code that executes before a request gets processed. Because Middleware runs before the cache, it's an effective way of providing personalization to statically generated content.
Nuxt has two forms of Middleware:
In Nuxt, modules defined in will get deployed as server middleware. Server middleware should not have a return statement or send a response to the request.
Server middleware is best used to read data from or add data to a request's . Doing so allows you to handle authentication or check a request's params, headers, url, and more.
The following example demonstrates Middleware that:
- Checks for a cookie
- Tries to fetch user data from a database based on the request
- Adds the user's data and the cookie data to the request's context
You could then access that data in a page on the frontend with the hook. This hook is only available in routes deployed with SSR. If your page renders in the browser, will return .
The following example demonstrates a page fetching data with :
Nuxt's route middleware runs before navigating to a particular route. While server middleware runs in Nuxt's Nitro engine, route middleware runs in Vue.
Route middleware is best used when you want to do things that server middleware can't, such as redirecting users, or preventing them from navigating to a route.
The following example demonstrates route middleware that redirects users to a secret route:
By default, route middleware code will only run on pages that specify them. To do so, within the tag for a page, you must call the method, passing an object with set as an option.
The following example demonstrates a page that runs the above redirect middleware:
To make a middleware global, add the suffix before the file extension. The following is an example of a basic global middleware file:
See a detailed example of route middleware in Nuxt's Middleware example docs.
Middleware with Nuxt on Vercel enables you to:
- Redirect users, and prevent navigation to routes
- Run authentication checks on the server, and pass results to the frontend
- Scope middleware to specific routes, or run it on all routes
Server-Side Rendering (SSR) allows you to render pages dynamically on the server. This is useful for pages where the rendered data needs to be unique on every request. For example, checking authentication or looking at the location of an incoming request.
Nuxt allows you to deploy your projects with a strategy called Universal Rendering. In concrete terms, this allows you to deploy your routes with SSR by default and opt specific routes out in your Nuxt config.
When you deploy your app with Universal Rendering, it renders on the server once, then your client-side JavaScript code gets interpreted in the browser again once the page loads.
On Vercel, Nuxt apps are server-rendered by default
SSR with Nuxt on Vercel:
- Scales to zero when not in use
- Scales automatically with traffic increases
- Allows you to opt individual routes out of SSR with your Nuxt config
If you deploy with , you can opt nuxt routes into client-side rendering using by setting as demonstrated below:
To deploy a fully static site on Vercel, build your project with .
Alternatively, you can statically generate some Nuxt routes at build time using the route rule in your nuxt.config.ts:
To verify that a route is prerendered at build time, check
useNuxtApp().payload.prerenderedAt.
Incremental Static Regeneration (ISR) allows you to create or update content without redeploying your site. ISR has two main benefits for developers: better performance and faster build times.
To enable ISR in a Nuxt route, add a option to your nuxt.config.ts, as shown in the example below:
You should use the option rather than to enable ISR in a route. The option enables Nuxt to use Vercel's Cache.
using ISR with Nuxt on Vercel offers:
- Better performance with our global CDN
- Zero-downtime rollouts to previously statically generated pages
- Global content updates in 300ms
- Generated pages are both cached and persisted to durable storage
Learn more about ISR with Nuxt.
You can define redirects and response headers with Nuxt on Vercel in your nuxt.config.ts:
Image Optimization helps you achieve faster page loads by reducing the size of images and using modern image formats.
When deploying to Vercel, images are automatically optimized on demand, keeping your build times fast while improving your page load performance and Core Web Vitals.
To use Image Optimization with Nuxt on Vercel, follow the Image Optimization quickstart by selecting Nuxt from the dropdown.
Using Image Optimization with Nuxt on Vercel:
- Requires zero-configuration for Image Optimization when using
- Helps your team ensure great performance by default
- Keeps your builds fast by optimizing images on-demand
Learn more about Image Optimization
Dynamic social card images allow you to create a unique image for pages of your site. This is great for sharing links on the web through social platforms or text messages.
To generate dynamic social card images for Nuxt projects, you can use . It uses the main Nuxt/Nitro Server-side rendering(SSR) function.
The following example demonstrates using Open Graph (OG) image generation with :
- Create a new OG template
- Use that OG image in your pages. Props passed get used in your open graph images.
To see your generated image, run your project and use Nuxt DevTools. Or you can visit the image at its URL .
Learn more about OG Image Generation with Nuxt.
The Nuxt team does not recommend deploying legacy versions of Nuxt (such as Nuxt 2) on Vercel, except as static sites. If your project uses a legacy version of Nuxt, you should either:
- Implement Nuxt Bridge
- Or upgrade with the Nuxt team's migration guide
If you still want to use legacy Nuxt versions with Vercel, you should only do so by building a static site with . We do not recommend deploying legacy Nuxt projects with server-side rendering.
See our Frameworks documentation page to learn about the benefits available to all frameworks when you deploy on Vercel.
Learn more about deploying Nuxt projects on Vercel with the following resources:
Was this helpful?