Updated

Technology · Servers

Next.js

nextjs.org

Next.js is a React framework for building full-stack web applications. You build the interface with React components and use Next.js for routing, rendering and optimizations.[1]

Next.js is an open-source React framework developed by Vercel for building modern web applications. It extends React's capabilities by providing server-side rendering, static site generation, and other performance optimizations out of the box. Next.js simplifies the development process with features like automatic code splitting, optimized prefetching, and built-in CSS support. It's particularly well-suited for creating scalable, production-ready applications with excellent SEO performance. Next.js also offers API routes, allowing developers to build API endpoints as part of their Next.js application.

Next.js belongs toJavaScript frameworksStatic site generatorWeb frameworksWeb serverscategories.

What it is

A framework built on React[1]

Rendering

Per-page choice of server and client rendering[2]

Built-in tooling

Image, font and script optimizations[2]

Styling

CSS Modules, Tailwind CSS and community libraries[2]

375websites

use it — 14.7% of the 2,555 websites we scanned in the last 12 months

#1of 78

tools in its category seen in our scans (we recognize 295)

111public pages

on UptimeCard — open any of them to see how that site is doing

In short: a good fit when you already use React and want routing, server rendering and API routes in one framework. It is open source, so you pay only for where you host it.[1][2]

13.32% of all websites we track run Next.js▲ 0.07 points since 20 Sep

Should you use Next.js?

The 10-second version, from the vendor’s own pages and what we see in our scans

Next.js fits if…

  • Your team knows React and wants a full-stack framework on top of it[1]
  • You want to choose static or server rendering page by page[2]

Look elsewhere if…

  • Your team uses Vue rather than React[3]Nuxt describes itself as a full-stack Vue framework.
  • You build mostly content sites and want a framework made for them[4]Astro describes itself this way.
Defaults changed between major versions: fetch requests and GET Route Handlers stopped being cached by default in a later major release[5]
Request APIs became asynchronous in a later major release, which is a breaking change[5]

Next.js next to other web frameworks

Statements come from each project's own page; website counts and speed are ours.

Next.jsNuxt.jsAstro
What each one is
What it isReact frameworkfor full-stack web apps[1]Vue frameworkfull-stack[3]Web frameworkfor content-driven websites[4]
What we see in our scans
Websites running it37514.7% of 2,555 scanned sites471.8% of 2,555 scanned sites301.2% of 2,555 scanned sites
Typical page load time3.9 s✓96 public sites4.8 s12 public sites4.5 s10 public sites
Typical page weight3.8 MBtypical home page3.2 MB✓typical home page3.3 MBtypical home page

Scan rows count public pages only; a tool needs at least 5 measured sites to appear.

  • Nuxt.js: A full-stack framework for Vue[3]
  • Astro: A web framework for content-driven websites[4]

Choose Next.js if…

  • Your team knows React and wants a full-stack framework[1]

Choose Nuxt.js if…

  • Your team uses Vue[3]

Choose Astro if…

  • You build content-driven sites[4]

Support and help for Next.js

How the vendor says you can reach it, and the public help community

Stack Overflow

41,491 questions[9][10]

54% have an upvoted answer. [next.js] questions

Next.js versions

The newest release, the series that still gets fixes, and what changed

Latest release

16.4.3[6]

Maintained series

16

What changed in 16

  • Turbopack became the stable default bundler for all apps[7]
  • Cache Components added a caching model built on Partial Pre-Rendering[7]

What changed in 15

  • Support for React 19 arrived, with the React Compiler as an experiment[5]
  • Fetch requests and GET Route Handlers stopped being cached by default[5]

What changed in 14

  • Server Actions became stable, for mutations that work with forms[8]
  • Partial Prerendering arrived as a preview: a fast static response plus streamed dynamic content[8]

What Next.js sites add on top

How many of the 375 Next.js sites we scanned also run each tool, grouped by what the tool does

Tag manager

Google Tag Manager
63%236 sites

Analytics

Google Analytics
55%206 sites
Facebook Pixel
21%80 sites
Linkedin Insight Tag
18%68 sites

Cookie consent

OneTrust
25%92 sites

Online store

Cart Functionality
9%34 sites

The full bar means every Next.js site. A site can run several tools for one job, so the shares of tools in one group can add up to more than 100%.

How Next.js sites protect themselves

Share of the 375 sites we scanned that run each protection

HSTS73% · 272 sites

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS

reCAPTCHA22% · 81 sites

reCAPTCHA is a free service from Google that helps protect websites from spam and abuse

Cloudflare Bot Management17% · 62 sites

Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots

Protections add up, they do not replace each other: a site can run all of them.

What sites use Next.js for

An estimate from UptimeCard's technology map of 92 public sites

Runs the marketing site42 sites

ansarada.com · apphud.com · asana.com

Runs the whole site36 sites

abbyy.com · adaptavist.com · aegisys.com

Hosts help, docs or support content10 sites

alchemy.com · checklyhq.com · customerio.com

Runs a shop or catalog3 sites

empatica.com · getzowie.com · wwnorton.com

Rough guide, not a measurement: each description is written automatically from the site’s technology stack and the site has not confirmed it. A site is counted once, in the first group its description fits (shop, help and docs, blog, marketing site; otherwise the whole site). Descriptions that only guess (“likely”, “may”) are left out.

The speed trap: what fast Next.js sites do differently

96 public Next.js sites we measured, split by how fast their page loads

Fastest quarter

2.1 stypical page load time

2.6 MB page · 132 requests

Slowest quarter

8.3 stypical page load time

5.4 MB page · 179 requests

What differs between the two groups

Extras on the site
Piwik PRO Core13%38%
Google Tag Manager83%67%
OneTrust17%33%
Priority Hints21%38%
DoubleClick Floodlight17%29%
Cloudflare46%33%
Read this as a pattern, not a cause. The sites in the slower group more often add the extras above. Next.js itself is not what separates the two groups.

At a glance

UptimeCard's own scans and tests of 2,555 websites · refreshed weekly

How Next.js sites scoreout of 100 · hover or tap a score for details

45PerformancePooraverage site: 5090AccessibilityGoodaverage site: 8993Best practicesGoodaverage site: 9392SEOGoodaverage site: 92

Page load time

Loads about 10% faster than the average site

Next.js sites
3.9 s
All sites
4.3 s

Most Next.js sites load in 2.6–5.6 s. Home page weight: 3.8 MB vs 3.3 MB for all sites. 96 public sites measured.

Where are they hosted?

Mostly Amazon Web Services and Cloudflare

  • Amazon Web Services54%
  • Cloudflare20%
  • Google Cloud5%
  • Hetzner Online GmbH2%
  • Other19%
United States 62%Canada 27%BD 1%

Who uses it?

Technology and Software is the biggest group

Technology and Software61%
Business Services1.4× avg16%
Software as a Service (SaaS)6%
Educational Resources4%

Share of 110 classified public sites. “× average” compares with all 961 public sites.

Browser-security check

41% of graded sites pass

11of 27 score B or better

Rates each site’s own security settings, not Next.js. 27 public sites graded so far.

How Next.js sites are built

Closest partners. The number says how many times more often the tool runs on Next.js sites than on an average website. Hover a partner for its share of sites.

Turbopack7×Vercel4×Node.js4×Emotion4×styled-components4×Datadog3×Contentful3×Tailwind CSS3×Sentry2×

Stacks we see most. Tools that tend to run together with Next.js on the same websites. The percentage is the share of all 375 Next.js sites that run the whole stack.

13 stacks · swipe, drag or use the arrows
#1

Next.js + Tailwind CSS + Radix UI

6.4%24 of 375 sites
#2

Next.js + OneTrust + Emotion

6.1%23 of 375 sites
#3

Next.js + OneTrust + styled-components

5.3%20 of 375 sites
#4

Next.js + OneTrust + Contentful

4.8%18 of 375 sites
#5

Next.js + Tailwind CSS + Sanity + Sanity.io

3.5%13 of 375 sites
#6

Next.js + Sentry + Emotion

4.5%17 of 375 sites
#7

Next.js + Tailwind CSS + HeroUI

3.7%14 of 375 sites
#8

Next.js + Sentry + Google Sign-in

3.5%13 of 375 sites
#9

Next.js + Tailwind CSS + Algolia

3.2%12 of 375 sites
#10

Next.js + OneTrust + Sentry + Wistia

2.4%9 of 375 sites
#11

Next.js + Sentry + styled-components

2.7%10 of 375 sites
#12

Next.js + styled-components + Contentful

2.7%10 of 375 sites
#13

Next.js + styled-components + Google Cloud

2.1%8 of 375 sites

Similar tools in its category

JavaScript frameworks: 295 tools known, 78 seen in our scans

Nginx359 sitesAlternativeApache HTTP Server150 sitesAlternativeVue.js144 sitesAlternativeGSAP138 sitesAlternativeMicrosoft ASP.NET79 sitesAlternativeAngularJS64 sitesAlternativeNuxt.js47 sitesAlternativeAdobe Client Data Layer47 sitesAlternativeMarko149 sitesUsed togetherEmotion96 sitesUsed togetherstyled-components83 sitesUsed together

How websites combine Next.js with other tools

Relationships found on the websites that use it, from the same map status pages show.

Integrates with another 197Needs another tool 142Built on a platform 106Complements another tool 84Overlaps with another 13

Websites using Next.js

375 websites use Next.js: 14.7% of the 2,555 websites we scanned in the last 12 months. A selection is shown below.

Scores are out of 100: P Performance · A Accessibility · B Best practices · S SEO. Green 80+, yellow 65–79, orange 50–64, red below 50. The dot shows whether our last scan found the site failing (red) or not (green); Red, amber or blue: an active incident on the site's status page (outage, degraded, maintenance) or a failing scan; amber also means a certificate ending within 30 days. Hover the dot for details.

Who is behind Next.js

From its own pages and public records, with sources

Its story

  1. 2016

    The Next.js repository was created in October 2016 as an open source React framework under the MIT license.[11]

  2. 2019

    Next.js 9 added zero-config TypeScript support and API Routes. One project could now serve pages and backend endpoints.[12][8]

  3. 2021

    Next.js 12 introduced a Rust compiler built on SWC and a beta of Middleware. Builds and Fast Refresh got faster, and routing logic could run as code.[13]

  4. 2022

    Next.js 13 introduced the app directory in beta, built on React Server Components, and an alpha of Turbopack. Routing and layouts began to follow where React was heading.[14]

  5. 2023

    Next.js 14 made Server Actions stable and previewed Partial Prerendering. Mutations could use plain function calls, and a page could mix a static shell with streamed dynamic content.[8]

  6. 2024

    Next.js 15 supported React 19 and changed caching defaults. Fetch requests and GET Route Handlers were no longer cached by default, a breaking change for existing apps.[5]

  7. 2025

    Next.js 16 made Turbopack the default bundler and added Cache Components. Builds and Fast Refresh got faster, and caching became an explicit model built on Partial Pre-Rendering.[7]

Questions about Next.js

What is Next.js?
A React framework for building full-stack web applications.[1]
Can it build API endpoints?
Yes. Route Handlers let you build API endpoints for auth or webhooks.[2]
What bundler does it use?
Turbopack, an incremental bundler written in Rust and built into Next.js.[2]
Which license does Next.js use?
It is open source under the MIT license.[6]
Which license does Next.js use?
It is open source under the MIT license.[6]
How many websites use Next.js?
We found Next.js on 375 of the 2,555 websites we scanned in the last 12 months (14.7%). 111 of them have a public status page.
What is Next.js often used with?
Among the websites we scan, Next.js is often found alongside Node.js (76.3% of its sites), OneTrust (24.5% of its sites), Vercel (24.5% of its sites).
What are the alternatives to Next.js?
Other JavaScript frameworks we recognize include Nginx, Apache HTTP Server, Marko, Vue.js.

Is your website built with Next.js?

UptimeCard checks it around the clock, tells you the minute it stops answering, and gives your visitors a status page.

Monitor my site freeCreate a status page