# Next.js on Render

Canonical: https://inetgeek.com/stacks/nextjs-on-render/

Render 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 Render publishes about each. Render documents 4 of the 6.

| Requirement | Render | Why it matters |
| --- | --- | --- |
| 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. |
| Build allowance | 500 build-pipeline minutes a month on Hobby, 1,000 on Pro, 5,000 on Scale. Minutes, not builds. | 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 | One active build per service, platform-wide on all plans; a new build cancels the in-progress one for that service | 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. |

- Edge network source: https://render.com/docs/static-sites
- Build allowance source: https://render.com/docs/build-pipeline
- Git deployment source: https://render.com/docs/github
- Concurrent builds source: https://render.com/docs/build-pipeline

## What Render documents

> You can deploy a Next.js application on Render in just a few clicks.

Source: https://render.com/docs/deploy-nextjs-app

### Next.js features on Render

- **image_optimization**: Limited — Next.js Image Optimization requires server-side processing [...] The optimization process requires persistent disk for cache. Optimized images cache in .next/cache/images. [...] the default ephemeral filesystem means cached images are lost with each deploy or restart. ([source](https://render.com/articles/how-to-deploy-next-js-applications-with-ssr-and-api-routes))
- **isr**: Limited — Critical Requirement: Because Render Web Services have ephemeral filesystems, the ISR cache will be lost on every deploy or restart unless you configure a Persistent Disk. ([source](https://render.com/articles/how-to-deploy-next-js-applications-with-ssr-and-api-routes))
- **middleware**: Supported — Middleware Behavior: Next.js Middleware runs as a standard Node.js process on Render Web Services, not in a specialized "Edge Runtime" environment. This means you have access to the full Node.js API, but you should still keep middleware lightweight to avoid latency on every request. ([source](https://render.com/articles/how-to-deploy-next-js-applications-with-ssr-and-api-routes))

## What it costs to run there

|  | Render |
| --- | --- |
| Pricing model | The Hobby plan does not have a monthly fee, so you only pay for usage. |
| When you exceed a cap | Pipeline minutes: overage is auto-purchased, but with no payment method or once the monthly spend limit is reached Render stops running pipeline tasks, builds included. |
| Regions | Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore |

- Pricing model source: https://render.com/docs/new-workspace-plans
- When you exceed a cap source: https://render.com/docs/build-pipeline
- Regions source: https://render.com/docs/regions

## Whether it suits you

Workloads that need real background workers and persistent processes alongside web services, deployed from a repository or a Dockerfile. Managed Postgres and static sites run on the same platform.

Consider something else if: Free web services spin down after 15 minutes without traffic, which makes the free tier unsuitable for anything that must answer immediately.

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/
- Render: https://inetgeek.com/hosting/render/