Next.js is a React-based open source framework that provides a hybrid static / server-side rendered model for enterprise-grade sites and applications.
# Key features
These Next.js features provide important benefits for sites and apps, including those built and deployed with Netlify.
Page routing. Next.js boasts a file system-based routing structure. Organizing files and subdirectories within a
pagesdirectory automatically results in corresponding routes.
Automatic API endpoints. For simpler API management, any file added to the
pages/apidirectory is treated as an API endpoint with a corresponding API route.
Preview mode. Netlify supports rendering a draft page from any data-fetching solution instead of building a statically-generated page to preview. This preview mode functionality eliminates waiting for a build to run before previewing new content.
Hybrid or static. You can use a hybrid approach to generate content, choosing between server-side rendering or static generation on a per-page basis, or you can use
next exportto generate a completely static site.
Image optimization. The
next/imagecomponent allows you to automatically optimize images for your site on-demand, as they’re requested by users. On Netlify,
next/imageuses ipx and On-demand Builders.
Incremental Static Regeneration (ISR). ISR on Netlify works with On-demand Builders to revalidate pages as needed without rebuilding your entire site. This enables faster builds, especially for very large projects.
Internationalization. Netlify supports Next.js internationalized routing functionality for locale-specific options.
# Next.js Runtime
Netlify’s Next.js Runtime configures your site on Netlify to enable key Next.js functionality. It automatically generates serverless functions that handle server-side rendered (SSR) pages, incremental static regeneration (ISR), images, and Next.js features.
# Redirects and rewrites
We recommend using Netlify redirects when possible because they are faster to evaluate. Rewrites are a little different. Generally with Next.js Runtime, you should use Next.js rewrites instead of Netlify rewrites.
Avoid root-level rewrite
Do not add a rewrite from the site root (such as
from = "/") in
_redirects. Your root-level rewrite would take precedence over Next.js Runtime’s own rewrites and break routing on your site.
Learn more on the Next.js redirects and rewrites on Netlify page.
Next.js Runtime supports Middleware, a feature in which functions run before a request has finished processing. Regular Next.js Middleware can be used to modify the request or replace the response. For example, it can change headers, rewrite the request path, or return a different response entirely.
Beyond regular Middleware, Netlify’s Next.js Advanced Middleware, available in the
@netlify/next library, gives improved access to requests and responses. This is similar to Netlify Edge Functions, but with some additional Next.js-specific helpers.
Learn more on the Next.js Middleware on Netlify page.
# Custom Headers
Next.js Runtime supports Next.js custom headers. Custom headers work for SSR, static site generation (SSG), ISR pages, and IPX images. There’s no need to add custom headers in the Netlify configuration.
next/image and Edge Functions
next/image automatically optimizes your images’ size and format. Next.js Runtime uses a Netlify Edge Function to deliver the correct format to a visitor’s browser.
If you don’t want to use Edge Functions to handle image processing on your site, you can disable this feature by setting the environment variable
true. With this environment variable update, Next.js Runtime defaults to delivering the original file format.
Large functions. During deployment, a function is packaged into a ZIP file, which AWS limits to 50 MB in size. Some functions generated by Next.js Runtime may exceed that limit and throw an error. This can happen for a few reasons. The troubleshooting page has more information.
Asset optimization. Don’t enable asset optimization on Netlify. Next.js automatically bundles your project and further optimization through Netlify can result in build issues for projects that use server-side rendering.
Cache control for SSR pages isn’t supported. As an alternative, you can use incremental static regeneration (ISR) pages instead and leverage the caching functionality that comes with On-demand Builders on Netlify.
# Suggested configuration values
When you link a repository for a Next.js project, Netlify provides a suggested build command and publish directory:
next build and
If you’re using the CLI to run Netlify Dev for a local development environment, Netlify suggests a dev command and port:
You can override suggested values or set them in a configuration file instead, but suggested values from automatic framework detection may help simplify the process of setting up a Next.js site on Netlify.
For manual configuration, check out the typical build settings for Next.js.
serverless target deprecated
experimental-serverless-trace targets are deprecated in Next 12, and all builds with Next.js Runtime use the default
server target. If you previously set the target in your
next.config.js, you should remove it.
# Edge Functions
This feature is in
Edge Functions connect the Netlify platform and workflow with an open runtime standard at the network edge. This enables you to build fast, personalized web experiences with an ecosystem of development tools.
# NextAuth.js support
NextAuth.js is a complete open source authentication solution for Next.js applications. When Next.js Runtime detects the
next-auth package in your build, it automatically sets the
NEXTAUTH_URL environment variable to your site’s canonical URL. If a custom base path is specified as part of your site configuration, this is included as part of the
# More resources
Did you find this doc useful?
Your feedback helps us improve our docs.