Next.js: React Framework for Full-Stack Web Apps
vercel/next.jsNext.js is a React framework from Vercel for building full-stack web applications, with file-based routing, server rendering, and static generation built in. Instead of wiring a router, bundler, and rendering strategy onto plain React yourself, you get those decisions made for you and pick a rendering mode per route.
Reach for Next.js if you're building a React app that needs server rendering, SEO-friendly pages, or a mix of static and dynamic routes, and you'd rather adopt sensible defaults than assemble routing, bundling, and data fetching yourself. Skip it if you're shipping a small client-only SPA where Vite plus React Router is lighter, or you specifically want to avoid coupling your architecture to Vercel's deployment defaults.
The problem it solves
Plain React ships as a client-side library: it renders in the browser and leaves routing, bundling, server rendering, and data fetching for you to wire together. That's a pile of decisions and glue code before you write a single feature, and client-only rendering hurts SEO and first paint on content pages. Next.js exists to answer those questions with defaults — a router, a build pipeline, and several rendering modes — so a React team can ship a full-stack app without assembling the stack from scratch.
What is it?
Next.js is an open-source React framework (MIT-licensed) maintained by Vercel for building full-stack web applications. It adds file-based routing, multiple rendering modes — server-side rendering, static site generation, and React Server Components — plus an integrated build system on top of React. The README says it extends the latest React features and uses Rust-based JavaScript tooling for faster builds. It's written mostly in JavaScript and is one of the most-starred web projects on GitHub, at roughly 140k stars.
Why it's getting attention
Next.js sits at the center of how a lot of teams write React today, and it's watched closely because it's where new React features tend to land first — the App Router and React Server Components shipped here before most other frameworks. The README notes it's used by some of the world's largest companies. With about 140k stars and 31k forks, it's one of the highest-profile framework repos on GitHub, and each major release tends to shift how people structure React apps.
Key features
- ✓File-based routing: the folder structure under app/ (or pages/) becomes your routes, with no separate route config to maintain
- ✓Multiple rendering modes — server-side rendering, static site generation (SSG), and client rendering — selectable per route
- ✓React Server Components and the App Router, so components can run on the server and stream to the browser
- ✓Integrated build tooling, including the Rust-based JavaScript tooling the README credits for faster builds
- ✓Full-stack in one project: API routes and server functions live alongside your UI code
- ✓MIT-licensed and open source, backed by Vercel with a large contributor community
Best use cases
- •Content sites and marketing pages that need SEO-friendly server-rendered or statically generated HTML
- •Full-stack apps where the frontend and backend API live in one React codebase
- •E-commerce and dashboards that mix static pages with dynamic, per-request data
- •Blogs and documentation built as static sites (the repo's own tags include blog and static-site-generator)
How to install / try
Next.js is published on npm as `next`. The usual starting point is `npx create-next-app@latest`, which scaffolds a project with React and the toolchain already configured. You can also add it to an existing app with `npm install next react react-dom`. Full setup steps are in the docs at nextjs.org/docs.
How to use
You define pages by adding files under the app/ (or pages/) directory; each file exports a React component that becomes a route. Run `next dev` for a local dev server, `next build` to produce an optimized build, and `next start` to serve it. Rendering mode is chosen per route — static by default, server-rendered or streamed where you need per-request data. See nextjs.org/docs for the App Router model and data fetching.
Strengths
- ✓Removes most of the setup a React app needs — routing, bundling, and rendering come configured out of the box
- ✓Server rendering and static generation produce SEO-friendly HTML that client-only React can't
- ✓New React features like Server Components and streaming tend to be usable here first
- ✓Large ecosystem and community — around 140k stars means most problems are already answered somewhere
- ✓MIT-licensed, so no licensing friction for commercial use
Limitations & risks
- △The App Router and React Server Components carry a real learning curve; the mental model of what runs on the server vs. the client trips up teams migrating from the older pages/ router
- △Defaults lean toward Vercel's platform — self-hosting or deploying elsewhere is possible, but you do more work for features that are turnkey on Vercel
- △A fast release cadence means churn: the App Router, caching behavior, and data-fetching APIs have shifted across major versions, so upgrades and older tutorials go stale quickly
- △It's a heavier abstraction than plain React; for a small client-only SPA it can be more framework than the job needs
Alternatives
Who should try it — and who should skip
Reach for Next.js if you're a React team building anything beyond a toy SPA — content sites, full-stack apps, or anything that benefits from server rendering and SEO — and you'd rather adopt sensible defaults than assemble routing, bundling, and rendering yourself. If you're shipping a small client-only widget, or you specifically want to avoid Vercel-flavored defaults and the App Router's complexity, a lighter setup like Vite plus React Router may fit better.
Frequently asked questions
Next.js is an open-source React framework maintained by Vercel. It adds routing, server-side rendering, static generation, and a build pipeline on top of React so you can build full-stack web applications instead of just the view layer.
React is a library for building UI components that render in the browser. Next.js is a framework built on React that adds routing, server rendering, static generation, and a build system, so you get a full-stack setup instead of only the view layer.
Yes. Next.js is open source under the MIT license, so it's free for personal and commercial projects. Hosting is separate — you can deploy on Vercel or self-host it elsewhere.
For a small client-only single-page app, Next.js can be more framework than you need, and a lighter Vite plus React Router setup is simpler. It's also a heavier lift if you specifically want to avoid Vercel-oriented defaults.
Next.js is maintained by Vercel and developed in the open on GitHub, where it has roughly 140k stars, 31k forks, and a large contributor community.