Next Netlify Starter is a boilerplate project that combines a minimal Next.js v12 application with one-click deployment to Netlify. The project was originally hosted at this repository and has been moved to the netlify-templates organization; the current canonical repository is https://github.com/netlify-templates/next-netlify-starter.
What is Next Netlify Starter?
Next Netlify Starter is a minimal Next.js project bootstrapped with create-next-app and preconfigured for instant deployment to Netlify. It includes two sample components, a global stylesheet, a netlify.toml deployment configuration, and a jsconfig.json file that sets up absolute imports and path aliases. The project also integrates the Essential Next.js Build Plugin, which adds support for Preview Mode, server-side rendering and incremental static regeneration through Netlify Functions, and internationalized routing.
Key Features
- One-click deployment — The repository includes a "Deploy to Netlify" button that lets you clone and deploy the starter through Netlify's app without local setup.
- Next.js v12 — Built with create-next-app on Next.js v12, providing React-based pages and the standard Next.js development workflow.
- Minimal structure — Ships with just two sample components and a single global stylesheet, making it easy to inspect and replace with your own code.
- netlify.toml — A configuration file that defines build settings and deployment behavior for Netlify.
- Absolute imports — jsconfig.json enables custom import aliases so you can reference project paths without long relative segments.
- Essential Next.js Build Plugin — This Netlify plugin unlocks Preview Mode, server-side rendering, incremental static regeneration (ISR) via Netlify Functions, and internationalized routing on the platform.
- Moved repository — All future updates live at https://github.com/netlify-templates/next-netlify-starter; the old location still redirects for reference.
Who is it for?
- Next.js developers who want a known-good starting point for deploying to Netlify without configuring CDN, functions, and build rules themselves.
- Netlify users evaluating how Next.js performs on the platform, including SSR, ISR, and preview deployments.
- Teams prototyping a Next.js site quickly — the starter's minimal content lets you add pages and components without deleting scaffolding.
What can you do with Next Netlify Starter?
- Deploy a Next.js site in one click: Use the Deploy to Netlify button to spin up a live site from GitHub in seconds.
- Add dynamic rendering: The Essential Next.js Build Plugin lets you opt into server-side rendering and incremental static regeneration using Netlify Functions.
- Set up internationalized routing: The plugin's i18n routing features work without additional configuration.
- Preview content before publishing: Preview Mode is supported through the plugin, allowing draft content to be viewed on deployed URLs.
How does Next Netlify Starter work?
Click the Deploy to Netlify button, which triggers Netlify to clone the repository, run the build defined in netlify.toml, and host the output. Locally, you run the standard create-next-app development server. The Essential Next.js Build Plugin runs during the Netlify build and adapts the Next.js output for Netlify's platform, wiring up functions and routing.
FAQ
Is Next Netlify Starter free?
The starter repository is open source and free to use. You can clone it, modify it, and deploy it on Netlify using whatever Netlify plan fits your needs.
What Next.js version does it use?
The project was bootstrapped with Next.js v12. The repository is minimal and does not pin a specific patch version in the visible content.
Where is the latest version of the starter?
The project has moved to the netlify-templates organization. The canonical repository is https://github.com/netlify-templates/next-netlify-starter.
Does this starter support server-side rendering?
Yes, through the Essential Next.js Build Plugin. It enables server-side rendering and incremental static regeneration using Netlify Functions, along with Preview Mode and internationalized routing.
What does jsconfig.json do here?
It sets up absolute imports and custom aliases, so you can import components or utilities using path shortcuts instead of long relative paths.
