Skip to content
inetGeek

Next.js on Cloudflare Pages

Cloudflare Pages documents a generic path that covers Next.js, rather than a dedicated guide.

React framework with file-based routing, server components and a build step that produces both static and server-rendered output.

01.

What Next.js needs.

Every host claims to run Next.js, so the claim on its own decides nothing. These are the things Next.js actually requires from the platform underneath it, and what Cloudflare Pages publishes about each. Cloudflare Pages documents 2 of the 4.

Max request duration

Not documented

Server components and route handlers run per request. The wall-clock ceiling decides whether a slow upstream API or a model response can finish at all.

Streaming response limit

Not documented

The App Router streams the dynamic parts of a page as they resolve. A host that buffers the whole response first removes the benefit.

Edge network

Supported

Middleware runs on every matched request before the cache is consulted. Where it executes decides how much latency it adds.

Sources (1) →

Build minutes

500 builds per month on the Free plan

A large Next.js app prerenders at build time, so the build allowance is a recurring cost rather than a one-off.

Sources (1) →

The requirement and the reason it matters are ours. Every value beside them was read from Cloudflare Pages's own pages — expand a source to see the sentence it came from.

02.

What Cloudflare Pages documents.

Cloudflare Pages documents a generic path that covers Next.js, rather than a dedicated guide.

Use this guide when you specifically want to deploy a Next.js static export to Cloudflare Pages. For Next.js on Workers, Cloudflare recommends vinext, which also supports static exports. Limited: the Pages guide covers static export only; full-stack Next.js is redirected to Cloudflare Workers.

Sources (1) →
  • Static site · Cloudflare Pages docs ↗

    “Use this guide when you specifically want to deploy a Next.js static export to Cloudflare Pages. For Next.js on Workers, Cloudflare recommends vinext, which also supports static exports. Limited: the Pages guide covers static export only; full-stack Next.js is redirected to Cloudflare Workers.”

    Read 2026-09-05 · official docs

03.

What it costs to run there.

Entry paid plan
$5 / month account minimum
Pricing model
Metered usage with a $5 monthly account minimum
Regions
348 cities across 100+ countries
Sources (2) →
04.

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.

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.

Visit Cloudflare Pages documentation

Other hosts for Next.js

Next.js on AWS AmplifyAWS service for hosting full-stack web applications with a Git-based continuous deployment workflow, server-side rendering support, and delivery via the AWS content delivery network.Next.js on Fly.ioRuns Docker images as lightweight VMs in chosen regions, billed on provisioned resources rather than plan tiers.Next.js on NetlifyPlatform for building and deploying web projects from Git to a global CDN, with serverless and edge functions.Next.js on RailwayApplication platform that builds services from a repository or Dockerfile and bills plan fees that include usage credits.Next.js on RenderManaged cloud platform that builds and runs web services, background workers, static sites and databases from Git repositories or Docker images.

Zoom out

Best hosting for Next.jsEvery provider that documents Next.js, ranked by how they document it.Cloudflare PagesStatic and full-stack site hosting on Cloudflare's network, billed together with Workers compute.