
Next.js is an open-source framework, maintained by Vercel, for building websites and web applications with React. Choose it when the project behaves like an application: customers log in, pages are personalized, data comes from several systems, or a custom front end sits on top of a headless CMS. Do not choose it for a brochure site or blog that a client wants to edit without a developer. WordPress usually does that job with less cost and less upkeep.
This guide covers what Next.js adds to React, where the framework stands in November 2026, and how to decide whether it fits a project.
What Next.js Adds to React
React is a library for building user interfaces out of components. On its own it does not decide how pages are routed, where data is loaded or how the site is built and served. Next.js supplies those missing pieces. The Next.js documentation calls it a React framework for building full-stack web applications.
In practice a team gets:
- Routing from folders. A file at
app/pricing/page.tsxbecomes the page at/pricing. - Rendering on the server. Pages can be turned into HTML at build time or when a visitor requests them, so browsers and search engines receive real content and not an empty shell.
- Server and client code in one project. Server Components fetch data on the server. Route Handlers and Server Functions cover API endpoints and form submissions.
- Built-in caching. You mark which parts of a page can be stored and for how long.
- Image optimization through the
next/imagecomponent. - Tooling that is already configured. TypeScript support and the Turbopack bundler work out of the box.
Next.js has two routers. The App Router is the newer one and supports current React features such as Server Components. The Pages Router is the original and is still supported. New projects should use the App Router.
Where Next.js Stands in November 2026
| Version | Released | Status |
|---|---|---|
| Next.js 16 | October 21, 2025 | Active LTS. The latest release is 16.4, from October 6, 2026 |
| Next.js 15 | October 21, 2024 | Maintenance LTS. Security releases continue through January 31, 2027 |
| Next.js 14 and earlier | October 26, 2023 and before | Unsupported |
These dates are from the official support policy. A major version stays in Active LTS until the next major ships. It then gets critical fixes and security updates until two years after its first release.
Other facts worth knowing before a project starts:
- Next.js 16 needs Node.js 20.9 or later. Node.js 20 itself reached end of life in April 2026, so run Node.js 22, 24 or 26.
- It supports Chrome 111+, Edge 111+, Firefox 111+ and Safari 16.4+ without extra configuration.
- Next.js 16.4 ships with React 19.3.
- Cache Components, the new rendering and caching model, is switched on by default in new apps and will be the default for everyone in Next.js 17.
A developer starts a new project with one command:
npx create-next-app@latest my-app --yes
cd my-app
npm run dev
The default setup enables TypeScript, Tailwind CSS, ESLint, the App Router and Turbopack. The site then runs at http://localhost:3000.
When Next.js Is the Right Choice
- The product is an application. Customer portals, dashboards, booking tools and SaaS products need logins, forms and live data. That is the work Next.js was built for.
- Pages mix shared and personal content. A product page can serve its description from cache while the price for a logged-in customer is rendered fresh.
- You want a headless setup. Editors keep working in WordPress or another CMS, and Next.js renders the front end from its API. See our guide to using WordPress with Next.js.
- Content comes from several sources. A CMS, a commerce platform and a search service can be combined on the server before the page is sent.
- The team already works in React. A framework only pays off when the people who maintain it know it well.
When Next.js Is the Wrong Choice
- The client needs to edit pages and layouts alone. Next.js has no admin screen, themes or plugins. You must add a CMS and build every template.
- The site is a brochure or a blog. A site with a few dozen pages and a contact form gains little from a JavaScript framework and takes on its maintenance.
- There is no budget for a developer after launch. Every change to a Next.js site is a code change and a deployment.
- Nobody will apply updates. This one deserves its own section.
For the broader trade-off between the two approaches, read our React and WordPress comparison.
The Maintenance You Are Signing Up For
A Next.js site is software, and it has to be kept current like any other software.
In December 2025 a critical vulnerability in the React Server Components protocol, CVE-2025-66478, meant Next.js users had to upgrade to patched versions at once. In July 2026 the Next.js team moved to a formal security release process. Since then the Next.js blog has announced a scheduled security release in most months, plus out-of-band updates in September and October 2026.
Plan for three kinds of work:
- Patch releases. Apply security releases as they come out.
npx next upgradeupdates the framework. - Major upgrades. Versions 14, 15 and 16 each arrived in October, a year apart. With two years of support per major, a site should move up at least every second year.
- Node.js upgrades. The runtime underneath has its own end-of-life dates.
If an agency quotes for a Next.js build, ask what the monthly care plan includes and who watches for security releases.
Where a Next.js Site Can Be Hosted
Next.js is made by Vercel, but it does not have to run on Vercel. The deployment documentation lists four routes:
| Deployment option | Feature support | What it means |
|---|---|---|
| Node.js server | All features | Run npm run build, then npm run start on any host that supports Node.js |
| Docker container | All features | Package the app as an image and run it on any container platform |
| Static export | Limited | Output plain HTML, CSS and JavaScript for any web server. Features that need a server do not work |
| Adapters | Varies by platform | A platform adapts the build to its own infrastructure |
At the time of writing the verified adapters are Vercel and Bun. The documentation says Cloudflare and Netlify are working on verified adapters and offer their own Next.js integrations in the meantime.
If you self-host, the Next.js team recommends putting a reverse proxy such as Nginx in front of the Next.js server instead of exposing it directly to the internet.
Questions to Settle Before You Commit
- Who will edit content, and in which tool?
- Which parts of the site are the same for everyone, and which change per visitor?
- Where will it be hosted, and can it move if that host stops suiting us?
- Who applies security releases, and how quickly?
- Is there a developer available for the two to three years this site will live?
If the answers point to an application with a team behind it, Next.js is a strong choice, and our Next.js development team can help scope it. If they point to a content site with one busy marketing manager, WordPress is the better fit. More guides are in our Next.js articles.
