Next.js Latest Version June 2026: 16.2.7 Current Stable on npm
Abhishek Gautam7 min readQuick summary
Next.js 16.2.7 is the current stable on npm as of June 2026. Release timeline, Turbopack default, the 15 to 16 upgrade path and breaking changes.
Read next
- Next.js 15 vs 14: Every Breaking Change and How to UpgradeNext.js 15 breaking changes: async APIs, fetch caching defaults, Turbopack stable, React 19. Step-by-step upgrade guide with code examples.
- How to Build a SaaS with Next.js in 2026 — Complete Starter GuideComplete guide to building a SaaS with Next.js in 2026: auth, database, billing, and deployment. A practical starter stack for indie and small teams.
If you are searching for the current stable version of Next.js as of June 2026, here is the direct answer and what you need to know.
What Is the Next.js Latest Stable Version in June 2026?
The current stable version of Next.js as of June 10, 2026 is Next.js 16.2.7. That is the exact version npm install next resolves to today (patch numbers update frequently; confirm with npm show next version or nextjs.org). Next.js 16 became the stable major in October 2025 and the 16.x line has received steady minor and patch updates since.
| Version | Status (June 2026) | Notes |
|---|---|---|
| Next.js 16.x | Stable (current) | 16.2.7 on npm; recommended for new projects and planned upgrades |
| Next.js 15.x | Maintenance | Still receives fixes; fine short-term, plan the move to 16 |
| Next.js 14.x and older | Legacy | Upgrade for security and long-term support |
Release Date and Timeline
- Next.js 15 stable: October 2024 (React 19 support, async request APIs, Turbopack stable for dev).
- Next.js 16 stable: October 2025. Turbopack became the default bundler, Cache Components shipped in beta, and the minimum Node.js version moved to 20+.
- June 2026: 16.x is the current stable line;
npm show next versionreturns 16.2.7 as of June 10. Check the Next.js releases page for the exact latest.
Key Changes From Next.js 15 to 16
| Area | Next.js 15 | Next.js 16 (June 2026) |
|---|---|---|
| Bundler | Webpack default, Turbopack opt-in | Turbopack default for dev and build |
| Caching | fetch-level caching, opt-in | Cache Components (use cache) for explicit, composable caching |
| Request APIs | Async cookies / headers introduced | Async-only; sync access removed |
| Node.js | 18+ | 20+ required |
| React | React 19 | React 19.x line |
If you still run custom webpack config, that is the main thing to validate before moving to 16 — Turbopack is the default and webpack-specific plugins need review.
Should You Upgrade Today?
New projects: Use Next.js 16. It is the current stable and the right default.
Existing Next.js 15 apps: Upgrade when you can run a full build and test pass. For most App Router projects the 15 to 16 jump is smaller than 14 to 15 was; the work concentrates in webpack-to-Turbopack config and adopting explicit caching.
Existing Next.js 14 or older: Move to 15 first (async request APIs, fetch caching changes), then to 16. Two smaller migrations beat one big one.
Migration Steps (15 → 16)
- Bump versions:
npm install next@16 react@19 react-dom@19(or your package manager). Ensure Node.js 20+. - Run the codemod:
npx @next/codemod@canary upgrade latestto apply automated fixes where possible. - Validate the bundler: If you have custom webpack config, test it under Turbopack or migrate the config. Most projects without custom config need no changes.
- Review caching: Audit
fetch()calls and adopt explicit cache directives where you depend on caching behaviour. - Test: Run
next buildand your test suite. Test critical routes and any custom middleware/proxy. - Deploy: Ship to staging first, then production after validation.
For the older comparison of 14 vs 15 (features, breaking changes, and decision guide), see Next.js 15 vs 14: What Changed and Should You Upgrade?.
Key Takeaways
- Current stable (June 10, 2026): Next.js 16.2.7 — confirm the exact patch with
npm show next versionor nextjs.org. - Release: Next.js 16 stable shipped October 2025; Turbopack default, Cache Components beta, Node.js 20+ required.
- Main changes from 15: Turbopack replaces webpack as default; caching becomes explicit via Cache Components; async-only request APIs.
- Should you upgrade: New projects → use 16. Existing 15 → upgrade after a build and test pass. On 14 or older → step through 15 first.
- Migration: Bump next/react, run the codemod, validate webpack-to-Turbopack, audit caching, then test and deploy.
FAQ
Frequently Asked Questions
What is the latest stable version of Next.js in June 2026?
The latest stable version of Next.js as of June 10, 2026 is Next.js 16.2.7 — the version npm install next resolves to. The exact patch updates regularly; check nextjs.org or run npm show next version for the current number.
When was Next.js 16 released?
Next.js 16 was released as the stable major in October 2025. It made Turbopack the default bundler for dev and build, introduced Cache Components in beta for explicit caching, and raised the minimum Node.js version to 20. The 16.x line remains the current stable as of June 2026.
Should I upgrade from Next.js 15 to 16 in 2026?
Yes, for most App Router projects. The 15 to 16 migration is smaller than 14 to 15 was: the main work is validating custom webpack config under Turbopack (now the default bundler) and adopting explicit caching. New projects should start on Next.js 16.
What are the main breaking changes in Next.js 16?
The main changes in Next.js 16: Turbopack replaces webpack as the default bundler (custom webpack config needs review), request APIs like cookies and headers are async-only, Node.js 20+ is required, and caching moves to the explicit Cache Components model instead of implicit fetch caching.
Is Next.js 14 still supported in 2026?
Next.js 14 is legacy in June 2026. If you are on 14 or older, migrate to 15 first (async request APIs and fetch caching changes), then to 16. Two smaller migrations are safer than one large jump, and staying on a legacy line means missing security fixes over time.
Free Weekly Briefing
The AI & Dev Briefing
One honest email a week — what actually matters in AI and software engineering. No noise, no sponsored content. Read by developers across 30+ countries.
No spam. Unsubscribe anytime.
More on Web Development
All posts →Next.js 15 vs 14: Every Breaking Change and How to Upgrade
Next.js 15 breaking changes: async APIs, fetch caching defaults, Turbopack stable, React 19. Step-by-step upgrade guide with code examples.
How to Build a SaaS with Next.js in 2026 — Complete Starter Guide
Complete guide to building a SaaS with Next.js in 2026: auth, database, billing, and deployment. A practical starter stack for indie and small teams.
How Long Does It Take to Build a Website in 2026? (Realistic Timelines)
A simple business website takes 2–4 weeks. E-commerce takes 4–10 weeks. Web apps take 6–14 weeks. Here are realistic website build timelines by type, what causes delays, and how to keep your project on track.
What is a Full Stack Developer? Skills, Salary, and Do You Actually Need One
A full stack developer builds both the frontend and backend of a web application. Here is what that means in practice, what skills to expect, what they charge, and when hiring one makes sense for your business.
Free Tool
What should your project cost?
Get honest 2026 price ranges for any project type — website, SaaS, MVP, or e-commerce. No fluff.
Try the Website Cost Calculator →Free Tool
Will AI replace your job?
4 questions. Get a personalised developer risk score based on your stack, role, and what you actually build day to day.
Check Your AI Risk Score →Written by
Software Engineer based in Delhi, India. Writes about AI models, semiconductor supply chains, and tech geopolitics — covering the intersection of infrastructure and global events. 941+ posts cited by ChatGPT, Perplexity, and Gemini. Read in 167 countries.