Next.js on Netlify
Netlify publishes its own guide for deploying Next.js.
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 actually requires from the platform underneath it, and what Netlify publishes about each. Netlify documents 5 of the 6.
Max request duration
60 seconds (synchronous); 30 seconds (scheduled); 15 minutes (background)
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.
Sources (1) →Sources ↓
- Functions configuration — Netlify Docs ↗
“Synchronous execution limit 60 seconds No Scheduled execution limit 30 seconds No Background execution limit 15 minutes No”
Read 2026-09-14 · official docs
Streaming response limit
Streaming (non-edge) Functions: 60-second execution limit and 20 MB response size limit. Stated without plan differentiation (applies on the cheapest paid plan).
The App Router streams the dynamic parts of a page as they resolve. A host that buffers the whole response first removes the benefit.
Sources (1) →Sources ↓
- Functions API reference ↗
“A function can stream data to clients as it becomes available, instead of returning a buffered payload after the function finishes. To stream a response, return a ReadableStream as the body of the Response. Streaming functions have a 60-second execution limit and a 20 MB response size limit.”
Read 2026-09-05 · official docs
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) →Sources ↓
- Edge Functions overview | Netlify Docs ↗
“All this dynamic processing happens in a secure runtime based on Deno directly from the worldwide network edge location closest to each user for fast response times.”
Read 2026-09-05 · official docs
Build allowance
Not documented
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.
Sources (1) →Sources ↓
- Git workflows overview | Netlify Docs ↗
“When you push changes to your site's Git repository, Netlify detects your changes and triggers automated deploys, functions, and more across our global CDN.”
Read 2026-09-05 · official docs
Concurrent builds
Personal: 1 concurrent build included, purchasable up to a maximum of 3, at $40/month per additional build
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.
Sources (1) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“1 concurrent build included in plan with option to purchase more. Limited to 3 concurrent builds, meaning up to 3 builds can run at the same time. Ideal for using multiple agents and running projects that depend on each other. Add 1 additional concurrent build as an add-on at $40/month”
Read 2026-09-05 · official docs
What Netlify documents.
Netlify publishes its own guide for deploying Next.js.
Netlify supports all major Next.js features with zero configuration, via our open-source OpenNext adapter.
Sources (1) →Sources ↓
- Next.js on Netlify | Netlify Docs ↗
“Netlify supports all major Next.js features with zero configuration, via our open-source OpenNext adapter.”
Read 2026-09-05 · official docs
Next.js features on Netlify
Capabilities Netlify documents specifically for Next.js, with the constraint it documents alongside each.
Image optimization
Supported
Image optimization: the next/image component uses Netlify Image CDN by default, to ensure your images are optimized and served in the most efficient format.
Middleware
Limited
Full support. Implemented automatically via Edge Functions. Note there are some limitations, including a Node.js Middleware specific limitation. — Limitations: Middleware Execution Order: Headers and redirects are evaluated after middleware, differing from stand-alone Next.js behavior. Node.js Middleware: C++ Addons are not supported, Filesystem is not supported.
Server Actions
Supported
Provisions a serverless Netlify Function for handling: Server-Side Rendering (SSR), Incremental Static Regeneration (ISR), Partial Prerendering (PPR), Route handlers or API routes, and Server Actions.
ISR / revalidation
Supported
On-demand and time-based revalidation: both the App Router and Pages Router support on-demand and time-based revalidation, allowing you to revalidate and regenerate content at any time after a deploy.
Streaming SSR
Supported
Next.js feature support table row: Response Streaming — Full Support.
Sources (1) →Sources ↓
- Next.js on Netlify ↗
“Image optimization: the next/image component uses Netlify Image CDN by default, to ensure your images are optimized and served in the most efficient format.”
Read 2026-09-05 · official docs
What it costs to run there.
- Entry paid plan
- $9/month for 1,000 credits/month
- Pricing model
- Monthly plan credits are included with your plan each billing cycle and reset at the start of each cycle.
- When you exceed a cap
- Suspended: when credits run out every project is paused and visitors see a Site not available page, unless auto recharge is configured.
Sources (2) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“$9/month for 1,000 credits/month, with an auto recharge option (500 credits for $5) if you go over your monthly credits.”
Read 2026-09-05 · official docs
- How credits work — Netlify Docs ↗
“Once your credit balance is completely used up, all of your web projects (sites/apps) are paused and visitors to your web projects will find a Site not available page at each of your web project's URLs.”
Read 2026-09-14 · official docs
Whether it suits you.
Teams that want Git-driven deploys onto a global CDN with a managed Postgres database built into the same platform. The free tier is 300 credits a month with a hard limit, so spend cannot surprise you.
Consider something else if…
You need to run containers or long-lived processes — Netlify does not document either.
Visit Netlify documentation