# Nuxt on Vercel

Canonical: https://inetgeek.com/stacks/nuxt-on-vercel/

Vercel publishes its own guide for deploying Nuxt.

Vue framework with file-based routing and a choice of static, server-rendered or hybrid output.

## What Nuxt needs

Every host claims to run Nuxt, so the claim on its own decides nothing. These are the things Nuxt requires from the platform underneath it, and what Vercel publishes about each. Vercel documents 4 of the 4.

| Requirement | Vercel | Why it matters |
| --- | --- | --- |
| Max request duration | Hobby: 300s default and maximum. Pro and Enterprise: 300s default, 800s maximum, and 1800s extended maximum | Nitro server routes and server-side rendering both run per request, bounded by this ceiling. |
| Edge network | Supported | Nuxt's route rules cache and revalidate at the edge. Without an edge network those rules degrade to origin rendering. |
| Build allowance | No monthly build-minute allowance. Build CPU minutes are billed from $0.0035 each on Pro, against the plan's usage credit, and any single build is capped at 45 minutes. | Nuxt prerenders routes at build time when asked to, which moves cost from request time into the build allowance. |
| Scales to zero | Supported | Nitro can deploy as functions. Scaling to zero removes the idle bill and adds a cold start to the first request instead. |

- Max request duration source: https://vercel.com/docs/functions/limitations
- Edge network source: https://vercel.com/docs/cdn
- Build allowance source: https://vercel.com/docs/limits
- Scales to zero source: https://vercel.com/docs/fundamentals/what-is-compute

## What Vercel documents

> Nuxt is an open-source framework that streamlines the process of creating modern Vue apps.

Source: https://vercel.com/docs/frameworks/full-stack/nuxt

### Nuxt features on Vercel

- **zero_config_deploy**: Supported — You can deploy Nuxt static and server-side rendered sites on Vercel with no configuration required. [...] On Vercel, Nuxt apps are server-rendered by default ([source](https://vercel.com/docs/frameworks/full-stack/nuxt))
- **nitro_server_routes**: Supported — Nuxt deploys routes defined in /server/api, /server/routes, and /server/middleware as one server-rendered Function by default. Nuxt Pages, APIs, and Middleware routes get bundled into a single Vercel Function. ([source](https://vercel.com/docs/frameworks/full-stack/nuxt))
- **route_rules_isr**: Supported — To enable ISR in a Nuxt route, add a routeRules option to your nuxt.config [...] You should use the isr option rather than swr to enable ISR in a route. [...] using ISR with Nuxt on Vercel offers: Better performance with our global CDN ([source](https://vercel.com/docs/frameworks/full-stack/nuxt))
- **image_optimization**: Supported — To use Image Optimization with Nuxt on Vercel, follow the Image Optimization quickstart by selecting Nuxt from the dropdown. [...] Requires zero-configuration for Image Optimization when using @nuxt/image ([source](https://vercel.com/docs/frameworks/full-stack/nuxt))

## What it costs to run there

|  | Vercel |
| --- | --- |
| Entry paid plan | $20 per developer seat / month (Pro) |
| Pricing model | Per-seat subscription plus metered resource usage; CDN charges cover requests, data transfer to visitors and Fast Origin Transfer, and vary by the region a request comes from. |
| When you exceed a cap | Billed automatically: extra usage beyond the included amount or Pro credit is charged, not throttled or suspended |
| Regions | 20 compute-capable regions, from Stockholm and Mumbai to Cleveland and Cape Town; functions default to iad1 (Washington, D.C.). |

- Entry paid plan source: https://vercel.com/docs/plans/hobby
- Pricing model source: https://vercel.com/docs/cdn
- When you exceed a cap source: https://vercel.com/docs/pricing
- Regions source: https://vercel.com/docs/regions

## Whether it suits you

Teams building on a framework the CDN understands natively, who want a predictable per-seat cost with metered usage on top. The Git integration covers GitHub, GitLab, Bitbucket and Azure DevOps, so it drops into an existing review workflow.

Consider something else if: The team is large enough that $20 per developer seat dominates the bill rather than the metered usage underneath it.

Written by Palash Bagchi on 2026-09-05. This is a recommendation, not a sourced fact — it carries no citation because it is an opinion.

## Related

- Best hosting for Nuxt: https://inetgeek.com/stacks/nuxt/
- Vercel: https://inetgeek.com/hosting/vercel/