Nuxt on Cloudflare Pages
Cloudflare Pages 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 Cloudflare Pages publishes about each. Cloudflare Pages documents 3 of the 4.
Max request duration
No limit for HTTP requests. A Worker keeps running as long as the client stays connected; Cron Triggers, Durable Object alarms and Queue consumers are capped at 15 minutes.
Nitro server routes and server-side rendering both run per request, bounded by this ceiling.
Sources (1) →Sources ↓
- Workers limits — Cloudflare Docs ↗
“Duration measures wall-clock time from start to end of a Worker invocation. Trigger type Duration limit HTTP request No limit Cron Trigger 15 min Durable Object Alarm 15 min Queue Consumer 15 min”
Read 2026-09-13 · official docs
Edge network
Supported — Cloudflare's network page advertises deploying to 330+ cities.
Nuxt's route rules cache and revalidate at the edge. Without an edge network those rules degrade to origin rendering.
Sources (1) →Sources ↓
- Cloudflare Global Network ↗
“Cloudflare Global Network One of the world's largest networks - running every service in every data center for unmatched performance, security, and reliability. [...] Deploy to 330+ cities instantly”
Read 2026-09-14 · official site
Build allowance
500 builds per month on the Free plan
Nuxt prerenders routes at build time when asked to, which moves cost from request time into the build allowance.
Sources (1) →Sources ↓
- Limits — Cloudflare Pages Docs ↗
“Build limits depend on your plan: Free Pro Business Builds 1 build at a time 5 concurrent builds 20 concurrent builds Builds per month 500 5,000 20,000 Builds will timeout after 20 minutes.”
Read 2026-09-14 · official docs
Scales to zero
Not documented
Nitro can deploy as functions. Scaling to zero removes the idle bill and adds a cold start to the first request instead.
What Cloudflare Pages documents.
Cloudflare Pages publishes its own guide for deploying Nuxt.
In this guide, you will create a new Nuxt application and deploy it using Cloudflare Pages.
Sources (1) →Sources ↓
- Nuxt · Cloudflare Pages docs ↗
“In this guide, you will create a new Nuxt application and deploy it using Cloudflare Pages.”
Read 2026-09-05 · official docs
Nuxt features on Cloudflare Pages
Capabilities Cloudflare Pages documents specifically for Nuxt, with the constraint it documents alongside each.
zero_config_deploy
Supported
The create-cloudflare CLI (C3) will configure your Nuxt site for Cloudflare Pages. [...] C3 will also install the necessary adapters along with the Wrangler CLI.
nitro_server_routes
Supported
In Nuxt, add server-side code via Server Routes and Middleware [...] The defineEventHandler() method is used to define your API endpoints in which you can access Cloudflare's context via the provided context field.
Sources (1) →Sources ↓
- Nuxt · Cloudflare Pages docs ↗
“The create-cloudflare CLI (C3) will configure your Nuxt site for Cloudflare Pages. [...] C3 will also install the necessary adapters along with the Wrangler CLI.”
Read 2026-09-13 · official docs
What it costs to run there.
- Entry paid plan
- $5 / month account minimum
- Pricing model
- Metered usage with a $5 monthly account minimum
- Regions
- No region selection. Pages Functions run in the data centre closest to the request; Smart Placement can instead pin a Worker near a named cloud region, host or hostname.
Sources (2) →Sources ↓
- Cloudflare Workers and Pages pricing ↗
“The Workers Paid plan includes Workers, Pages Functions, Workers KV, Hyperdrive, and Durable Objects usage for a minimum charge of $5 USD per month for an account.”
Read 2026-09-05 · official docs
- Smart Placement · Cloudflare Workers docs ↗
“By default, Workers and Pages Functions run in a data center closest to where the request was received. If your Worker makes requests to back-end infrastructure such as databases or APIs, it may be more performant to run that Worker closer to your back-end than the end user.”
Read 2026-09-14 · official docs
Whether it suits you.
Projects where the entire fixed cost should be a $5 monthly account minimum rather than a per-seat fee, and teams already running on the wider Workers platform. Billing is metered, so cost tracks traffic rather than headcount.
Consider something else if…
Your repository is hosted somewhere other than GitHub or GitLab, or the free plan's 500 builds a month is not enough headroom.
Visit Cloudflare Pages documentation