Next.js

Create web applications with the power of React components

5.0•513 reviews•

7.8K followers

Create web applications with the power of React components

5.0•513 reviews•

7.8K followers

Visit website

Engineering & Development

•

Static site generators

•

UI frameworks

The React framework for production. Next.js provides zero-configuration automatic code splitting, filesystem based routing, hot code reloading and universal rendering.

Next.js Reviews

The community submitted 513 reviews to tell us what they like about Next.js, what Next.js can do better, and more.

5.0

Based on 513 reviews

Review Next.js?

Reviewers mostly see Next.js as the strong default for React teams that need one codebase for marketing pages, apps, and API routes. They repeatedly praise file-based routing, SSR and static generation, strong SEO, and the ability to ship production-ready products quickly with less setup. Makers of Bond and 1752vc Pitch Deck Analyzer say it supports smooth real-time UX and full-stack work in a single deploy. The main complaints are App Router complexity, confusing caching, uneven docs for advanced cases, and disruptive major-version changes.

+515

Summarized with AI

Pros

fast performance (46)

developer experience (26)

server-side rendering (25)

static site generation (17)

file-based routing (15)

React integration (15)

SEO optimization (14)

API routes (11)

scalability (11)

TypeScript support (6)

Cons

caching issues (4)

learning curve (3)

stability issues (2)

Pros

Cons

ReplayAutonomous app testing for teams who ship at AI-speed

Promoted

Reviews

All Reviews

Most Informative

•9 reviews

What's great

Next.js is the default choice for a reason.

Built a full SaaS product with Next.js App Router — from landing page to authenticated dashboard, push notifications, subscription payments, and PWA support.

App Router took some getting used to, but once it clicks, the separation of server and client components is genuinely powerful. You get SEO-friendly pages, fast initial loads, and a smooth client-side experience — all in one framework without stitching tools together.

What I appreciate most: you can ship something production-ready without fighting the framework. Middleware, route handlers, image optimization, internationalization patterns — it's all there.

If you're building a product solo or in a small team and you need to move fast without sacrificing quality, Next.js is hard to beat.

What needs improvement

App Router documentation is still catching up — there are patterns (caching behavior, revalidation, server actions) where the docs are ambiguous and you have to rely on GitHub issues or community posts to understand what's actually happening.

The build output can get heavy fast. For a solo developer watching infrastructure costs, the cold start behavior and memory footprint on self-hosted deployments (outside Vercel) requires more tuning than it should.

Error messages in server components can be cryptic — a missing "use client" directive or a serialization issue gives you an error that points to the wrong place.

And the caching model in App Router, while powerful, is genuinely confusing at first. It took me longer than I'd like to admit to understand when data was being cached, for how long, and how to bust it correctly.

vs Alternatives

I needed SSR for SEO on the landing page, client-side interactivity inside the app, and PWA support — all in one framework. Next.js was the only option that handled all three without stitching separate tools together.

Remix was a close second, but the ecosystem is smaller and I hit fewer answered questions when debugging edge cases. Vite + React was faster to start but would have required building the server layer from scratch.

Next.js also has the best PWA story through next-pwa, which was a hard requirement for the mobile experience.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

108 views4mo ago

•29 reviews

What's great

fast performance (46)developer experience (26)static site generation (17)SEO optimization (14)server-side rendering (25)file-based routing (15)

Next.js just works.

The file-based routing and built-in SSR/SSG means you spend less time on boilerplate and more time building actual features. Deployments on Vercel are dead simple but it plays fine with other hosts too.

The App Router took some getting used to but server components are a genuine step forward for performance.

What needs improvement

Caching behaviour is still confusing. The defaults have changed between versions and it's not always clear what's cached where or for how long.

Breaking changes between major versions could be handled better too.

The docs are good but the gap between "hello world" and "production app" could use more real-world examples.

vs Alternatives

Nuxt

Remix

Remix and Nuxt were the main alternatives. Remix has a great data loading model but the ecosystem and community around Next.js is just bigger, which matters when you're debugging at 2am.

Nuxt is solid if you're in the Vue world but we're a React team so it wasn't a real option.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

74 views4mo ago

•11 reviews

What's great

developer experience (26)file-based routing (15)

Arteza's whole frontend is Next.js and the reason is boring: one repo covers the marketing pages, the app, and the API routes that talk to our generation queue. File based routing means a new studio page is a folder, not a router config discussion, which for a small team is most of the value. Streaming server components also let us show partial output while a long job runs instead of a spinner, and that changed how the product feels more than any redesign did.

What needs improvement

caching issues (4)

Caching is the part that has cost me the most hours. A fetch that was fresh in dev came back stale in production with nothing on screen saying a cached copy was served, so debugging it means adding logs to find out whether your code even ran. I'd take a visible marker of what got cached and why over any new feature in the next release. The upgrade path between major versions is the other one, since the codemods handle the syntax and leave the behaviour changes for you to find in production.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

13 views14d ago

used Next.js to build Deplo instead of Astro

•3 reviews

We chose Next.js because we wanted a full-stack React framework with a mature ecosystem, strong deployment support, and flexibility to scale to a larger product. We considered Astro and other React-based frameworks. Astro was attractive for its performance and content-focused architecture, but Next.js offered the better balance of full-stack capabilities, ecosystem maturity, and flexibility for our product.

Alternatives Considered

Astro

Report

10 views6d ago

•15 reviews

I’ve built both my website and a full web app on top of Next.js, and it’s been such a smooth experience. The framework handles routing, APIs, and performance optimizations out of the box, so I can just focus on the actual product instead of wrestling with setup. It scales nicely too — works just as well for simple landing pages as it does for complex dashboards. What makes it even better is pairing it with AI tools like ChatGPT and Claude. They’re really good at helping with Next.js-specific code, whether it’s debugging an App Router issue or generating boilerplate. That combo makes building with Next.js feel faster and way less stressful. 🚀

What's great

scalability (11)API routes (11)file-based routing (15)built-in optimizations (5)app router (2)

Report

146 views12mo ago

We Are Learning

•6 reviews

In "We Are Learning," we've found Next.js to be an invaluable asset for front-end development, particularly because of its server-side rendering capabilities, which dramatically boost both SEO and user experience through faster load times. Its automatic code splitting and file-based routing have simplified our development workflow, allowing us to focus on feature development rather than boilerplate code. The built-in API routes and extensible architecture have made it straightforward for us to integrate various data sources and backend services, aligning well with our diverse training modules. Its robustness and scalability easily meet our enterprise-level requirements, contributing significantly to our platform's reliability and performance. Overall, Next.js has been a cornerstone in accelerating our development cycles, without any trade-offs in quality.

What's great

fast performance (46)scalability (11)SEO optimization (14)server-side rendering (25)API routes (11)file-based routing (15)automatic code splitting (4)

Report

118 views3yr ago

used Next.js to build Noxionite

•2 reviews

For all the developers checking this out, I wanted to share a bit about the tech stack. Noxionite is built with Next.js, and it was the perfect choice for this project. The goal was to make Notion-powered blogs feel as fast as a static site, and Next.js's Incremental Static Regeneration (ISR) was the key. Pages are pre-rendered at build time for instant loads, but they also pull updates from Notion in the background every 60 seconds. This gives you the best of both worlds: incredible performance and near real-time content updates. The core rendering is powered by the amazing react-notion-x library. The entire project is open-source under the MIT license. So if you're curious about a real-world example of using Next.js with Notion as a headless CMS, feel free to dive into the code on GitHub! I'm happy to answer any technical questions you might have.

Report

56 views1yr ago

•7 reviews

Next.js is a strong default for React apps: great DX, file-system routing, server components/Server Actions for fast data fetching, and built-in image/font optimization. Vercel hosting makes deploys trivial, but you can host anywhere. Could be better: App Router + RSC still have sharp edges (caching, server/client boundaries, hydration quirks), build times can creep, and debugging Server Actions isn’t fun. Watch for Vercel-specific patterns if you want to avoid lock-in. Compared: Next.js = ecosystem + hiring pool. Remix feels cleaner for forms/mutations; SvelteKit can ship leaner bundles. Verdict: Use Next for most production React work—stick to stable features and add RSC cautiously.

Report

20 views1yr ago

•3 reviews

Next.js has been central to the growth of Rubix Studios. As an agency focused on high-performance websites, we needed a framework that was flexible, reliable, and easy for developers to work with. Next.js delivered on all of these needs. The mix of server-side rendering and static site generation gives our projects fast load times, strong search visibility, and effortless scalability for both local and global clients. File-based routing, API routes, and hot reloading speed up development and make the workflow enjoyable for the team. We have tried many frameworks, but none match Next.js for prototyping speed and production stability. The developer experience is smooth, documentation is clear, and the community is active and supportive. TypeScript support and its seamless fit with React made it a natural choice for our stack. For agencies, startups, or solo developers wanting a framework for modern web apps, Next.js offers the right mix of speed, scalability, and developer experience. It is at the core of how we build at Rubix Studios and continues to set the benchmark for what is possible on the web.

Report

18 views1yr ago

used Next.js to build Qibble

•4 reviews

We love Next.js for its seamless blend of React and server‑side rendering. It’s faster, SEO‑friendly by design, and offers an outstanding developer experience with minimal setup. Next.js just gets us to production quicker—no heavy config required. Alternatives Considered: Create React App: Good for basic setups but lacks built‑in SSR. Gatsby: Great for static sites, but not as straightforward for dynamic or large‑scale needs. Remix: Promising features, but Next.js had the more mature ecosystem when we started.

Report

27 views1yr ago

1 2 3

•••