Next.js is the framework most production teams reach for when "a website builder" stops being enough. It’s a React framework with built-in server-side rendering, static generation, edge deployment, image optimisation, and routing — the things that used to require either custom infrastructure or a full backend team are now available out of the box. That’s why Next.js has become the default choice for technically-led teams building marketing sites, product landing pages, documentation sites, blogs, and any project where the marketing site and the product are sharing component code. The best Next.js sites in this collection don’t look "developer-built." They have the kind of typography, animation, and visual finish you’d expect from sites built on design-led platforms, with the performance characteristics and flexibility of a real codebase underneath. The weakest ones look exactly like they were built by engineers who didn’t hire a designer. The differentiator isn’t the framework; it’s whether design discipline got applied to the front-end at the same level as the engineering discipline that chose Next.js in the first place. Look at how the strongest Next.js sites handle the marketing-product boundary. They share components, design tokens, and content models between the marketing site and the product itself, so the brand experience is consistent across the funnel. Look at how they handle performance. Next.js gives you the tools (image optimisation, code splitting, edge rendering, prefetching) but doesn’t apply them automatically — the strongest sites in this collection are deliberately optimised, often achieving sub-second load times even on complex pages. Browse Next.js landing pages, Next.js AI sites, or Next.js software products for the dominant patterns. Compare against Framer and Webflow for the no-code alternatives.
Curated inspiration sent every Tuesday
Unsubscribe at any time
Three reasons, usually in this order: (1) the marketing site needs to share components or design tokens with the product, which is much easier when both are React; (2) the team has engineering capacity and prefers code-based version control over visual editor workflows; (3) performance and SEO requirements demand more control than no-code platforms provide. Teams with none of these reasons usually choose Framer or Webflow instead, because the no-code platforms ship faster for simple marketing sites. Next.js is the right choice when the project is genuinely complex enough to justify the engineering overhead.
Marketing sites for software products, landing pages, documentation sites, technical blogs, e-commerce storefronts (especially headless commerce on top of Shopify or BigCommerce), dashboards, and sites that integrate tightly with a SaaS product. Next.js is dominant in the developer-tools category, the AI category, and the open-source-project category — basically anywhere the audience expects fast pages and the team has engineering DNA. Browse Next.js AI sites for one of the strongest concentrations.
Out of the box, very well. Next.js supports static generation (pages built at deploy time, served as plain HTML), server-side rendering (pages built per request), and incremental static regeneration (pages rebuilt periodically). Image optimisation is automatic via the next/image component. Routing supports prefetching to make navigation feel instant. Sitemaps and structured data are easily configurable. The result is that Next.js sites can achieve performance scores no-code platforms struggle to match, and they’re indexed by search engines as cleanly as any traditional HTML site. The gap between "Next.js with effort" and "Next.js by default" is large — the framework gives you the tools but doesn’t enforce them.
Higher build cost, slower iteration cycles for non-engineers, and complete dependence on engineering capacity for any change. A marketing team that wants to update a hero image on a Webflow site can do it in 30 seconds; on a Next.js site they file a ticket. For teams without dedicated engineering time, Next.js is the wrong choice no matter how good the framework is — it’s a tool for teams that have engineers and want to use them. The cost savings of no-code platforms become significant for any site that gets edited weekly.
Vercel is the default and is built by the same team as Next.js, making the developer experience tightly integrated. Netlify is the other common choice. AWS, Google Cloud, and Cloudflare Pages all support Next.js with varying degrees of feature support. The choice usually comes down to existing infrastructure relationships and pricing — Vercel is the path of least resistance and the choice most teams default to.
The big shift over the last two years has been the move to React Server Components and the App Router, which fundamentally changed how data fetching, routing, and rendering work in Next.js. The transition has been bumpy — many teams are still on the older Pages Router — but the new model is significantly more powerful for sites that mix static and dynamic content. Performance improvements continue to ship in nearly every major release. Next.js is consolidating its position as the dominant React framework rather than facing serious competition.
Try out Next.js
Next.js is Vercel’s React framework for production apps, with built-in optimisations, dynamic HTML streaming, and the App Router using React Server Components. Ship fast with SSR, static generation, and zero-config deployment on Vercel.
