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 actually requires from the platform underneath it, and what Vercel publishes about each. Vercel documents 4 of the 4.
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.
Sources (1) →Sources ↓
- Functions limitations — Vercel Docs ↗
“Default Maximum Extended maximum Hobby 300s (5 minutes) 300s (5 minutes) - Pro 300s (5 minutes) 800s 1800s (30 minutes) Beta Enterprise 300s (5 minutes) 800s 1800s (30 minutes) Beta”
Read 2026-09-13 · official docs
Edge network
Supported
Nuxt's route rules cache and revalidate at the edge. Without an edge network those rules degrade to origin rendering.
Sources (1) →Sources ↓
- Vercel CDN overview ↗
“Vercel operates 126 Points of Presence (PoPs) across 51 countries.”
Read 2026-09-05 · official docs
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.
Sources (1) →Sources ↓
- Limits — Vercel docs ↗
“Build Time per Deployment (Minutes) 45 45 45 [...] Build CPU Minutes Starting at $0.0035 per CPU Minute [...] The maximum duration of the Build Step is 45 minutes. When the limit is reached, the Build Step will be interrupted and the Deployment will fail.”
Read 2026-09-06 · official docs
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.
Sources (1) →Sources ↓
- What is Compute? - Vercel Docs ↗
“You never pay for idle CPU, and you pay nothing between requests.”
Read 2026-09-05 · official docs
What Vercel documents.
Vercel publishes its own guide for deploying Nuxt.
Nuxt is an open-source framework that streamlines the process of creating modern Vue apps.
Sources (1) →Sources ↓
- Nuxt on Vercel ↗
“Nuxt is an open-source framework that streamlines the process of creating modern Vue apps.”
Read 2026-09-05 · official docs
Nuxt features on Vercel
Capabilities Vercel documents specifically for Nuxt, with the constraint it documents alongside each.
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
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.
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
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
Sources (1) →Sources ↓
- Nuxt on Vercel ↗
“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”
Read 2026-09-13 · official docs
What it costs to run there.
- 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.).
Sources (4) →Sources ↓
- Vercel Hobby Plan ↗
“Developer seats cost $20 per user / month, while Viewer seats are free”
Read 2026-09-05 · official docs
- CDN — Vercel Docs ↗
“CDN pricing covers CDN requests, data transfer to visitors, and Fast Origin Transfer. Pricing can vary by the region where requests originate. CDN requests appear as Edge Requests in Billing and on the Usage page.”
Read 2026-09-14 · official docs
- Pricing on Vercel ↗
“Some resources include an amount of usage your projects can use within your billing cycle. Pro teams also receive a monthly usage credit and can use many resources on demand. If you exceed an included amount or credit, Vercel charges for the extra usage.”
Read 2026-09-05 · official docs
- Regions — Vercel Docs ↗
“Vercel regions: Behind these PoPs, we maintain 20 compute-capable regions where your code can run close to your data. [...] Vercel Functions default to running in the iad1 (Washington, D.C., USA) region.”
Read 2026-09-14 · official docs
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.
Visit Vercel documentation