# Next.js on Cloudflare Pages

Canonical: https://inetgeek.com/stacks/nextjs-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.

## 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 requires from the platform underneath it, and what Cloudflare Pages publishes about each. Cloudflare Pages documents 6 of the 6.

| Requirement | Cloudflare Pages | Why it matters |
| --- | --- | --- |
| 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. | 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 | No enforced ceiling. Cloudflare documents no response body size limit; CDN cache limits apply at 512 MB on Free, Pro and Business and 5 GB on Enterprise. | 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 — Cloudflare's network page advertises deploying to 330+ cities. | Middleware runs on every matched request before the cache is consulted. Where it executes decides how much latency it adds. |
| Build allowance | 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. |
| Git deployment | Supported | The Next.js workflow assumes a push builds and ships. A host without git-triggered deploys means wiring CI yourself before the first deploy, which is most of the setup cost. |
| Concurrent builds | 5 concurrent builds on Pro (1 on Free, 20 on Business), with 5,000 builds per month on Pro | Next.js builds are slow enough that queueing is felt. One build at a time is workable alone and becomes the bottleneck the moment two people merge in the same hour. |

- Max request duration source: https://developers.cloudflare.com/workers/platform/limits/
- Streaming response limit source: https://developers.cloudflare.com/workers/platform/limits/
- Edge network source: https://www.cloudflare.com/network/
- Build allowance source: https://developers.cloudflare.com/pages/platform/limits/
- Git deployment source: https://developers.cloudflare.com/pages/configuration/git-integration/
- Concurrent builds source: https://developers.cloudflare.com/pages/platform/limits/

## What Cloudflare Pages documents

> 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.

Source: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-static-nextjs-site/

## What it costs to run there

|  | Cloudflare Pages |
| --- | --- |
| 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. |

- Entry paid plan source: https://developers.cloudflare.com/workers/platform/pricing/
- Pricing model source: https://developers.cloudflare.com/workers/platform/pricing/
- Regions source: https://developers.cloudflare.com/workers/configuration/smart-placement/

## 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.

## Related

- Best hosting for Next.js: https://inetgeek.com/stacks/nextjs/
- Cloudflare Pages: https://inetgeek.com/hosting/cloudflare-pages/