# Next.js on Netlify

Canonical: https://inetgeek.com/stacks/nextjs-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 requires from the platform underneath it, and what Netlify publishes about each. Netlify documents 5 of the 6.

| Requirement | Netlify | Why it matters |
| --- | --- | --- |
| 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. |
| 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. |
| Edge network | Supported | Middleware runs on every matched request before the cache is consulted. Where it executes decides how much latency it adds. |
| 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. |
| 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. |

- Max request duration source: https://docs.netlify.com/build/functions/configuration/
- Streaming response limit source: https://docs.netlify.com/build/functions/api/
- Edge network source: https://docs.netlify.com/build/edge-functions/overview/
- Git deployment source: https://docs.netlify.com/build/git-workflows/overview/
- Concurrent builds source: https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/

## What Netlify documents

> Netlify supports all major Next.js features with zero configuration, via our open-source OpenNext adapter.

Source: https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview/

### Next.js features on Netlify

- **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. ([source](https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview/))
- **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. ([source](https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview/))
- **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. ([source](https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview/))
- **isr**: 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. ([source](https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview/))
- **streaming_ssr**: Supported — Next.js feature support table row: Response Streaming — Full Support. ([source](https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview/))

## What it costs to run there

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

- Entry paid plan source: https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/
- Pricing model source: https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/
- When you exceed a cap source: https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/

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

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/
- Netlify: https://inetgeek.com/hosting/netlify/