Next.js vs Remix

Reasonable defaults via code splitting and native packages, but React runtime and RSC payload wire format add weight. Good performance requires intentional investment.

SSR-first delivery ships HTML immediately and route-based code splitting keeps per-page payloads lean. The full React runtime ships on every page with no selective hydration model.

Can be excellent with optimization but inconsistent across production sites. Large JS bundles continue to drag INP on data-heavy pages at the median.

SSR-first delivery helps LCP and reduces layout shift versus pure SPAs. Full React hydration overhead means marketing pages require extra effort to match Astro scores.

React Server Components reduce client JS versus the Pages Router, but the React runtime is unavoidable. No automatic JS budget enforcement, discipline is required.

Automatic route-based code splitting works well. No island-style selective hydration to strip JS from content-only routes. Every route hydrates with React by default.

The cli sets up TypeScript, ESLint, Tailwind, and App Router preferences in under two minutes, one of the best scaffolding experiences in the JS ecosystem.

The cli spins up a Vite-powered project in under two minutes. Three available modes add minor friction for developers who just want to start an app.

First-class throughout. Page, layout, route, and Server Action types are auto-inferred. Next.js 15 added typed route params with practically no boilerplate.

Best-in-class per-route type inference. The Vite plugin auto-generates typed loader and action interfaces, no manual interface definitions needed. Ahead of Next.js on route-level type safety.

Turbopack stable in v15 dramatically improved HMR but large codebases with many RSC boundaries still stall. Vite-based competitors feel faster on complex projects.

Vite-based and fast on small projects. Confirmed GitHub issues report 30-40 second page renders on larger codebases, the Babel compiler in the plugin is the root cause.

Improved error overlay in v14 and v15, but RSC-specific errors and wrong-context cookie calls can produce cryptic stack traces requiring framework internals knowledge.

Route-level error boundaries catch errors cleanly with full stack traces in dev. In production, errors are sanitized and swallowed silently unless you implement custom error exports.

Strong static generation via generateStaticParams and ISR. Understanding when a route is actually static requires knowing the caching model, which changed between versions.

Added in v7 via the prerender config. Returns an array of URLs to pre-render at build time. Functional but manual, no automatic static path detection from file-system conventions.

Industry-standard SSR with streaming, React Suspense, partial pre-rendering, and Edge Runtime. The most capable SSR framework in the React ecosystem.

SSR is the core of the framework. Loaders run server-side before render, data arrives with initial HTML, and edge deployment via Cloudflare Workers is a first-class documented path.

Individual route segments can be static, dynamic, or streamed in the same project at the layout level. No other framework offers this level of per-segment rendering control.

SSR with per-route static pre-rendering via prerender config and clientLoader for CSR opt-outs. SSR is a global flag, not fully isolated per route without workarounds.

Every major headless CMS maintains official Next.js starters. Sanity, Contentful, Storyblok, and Prismic all treat Next.js as their primary integration target.

All major headless CMSes work via loaders. No official CMS adapter ecosystem comparable to Next.js. Integration requires standard fetch code in loaders, functional but more manual.

Draft Mode works well with a preview API route and RSC data fetching. Clean per-CMS integration but still requires some custom wiring - not zero config.

No built-in draft or preview mode equivalent to Next.js. CMS vendors document Next.js preview integrations primarily, React Router v7 is largely undocumented for preview workflows.

App Router supports nested layouts, route groups, parallel routes, intercepting routes, and loading or error conventions at every level. The most comprehensive file-system router available.

Nested routing is the defining architectural feature. URL-driven loaders, parallel data loading across sibling routes, deferred loading with Await, and resource routes are all built in.

RSC fetch with cache tags and revalidateTag is architecturally elegant, but the caching model changed defaults between v13, v14, and v15 - a major recurring pain point.

The loader and action model is the cleanest server-data abstraction in the React ecosystem. Colocated with routes, parallel by default, and testable in isolation using web standard Request and Response.

Route Handlers and Server Actions cover external APIs and form mutations cleanly once you understand which to use when. The separation is logical but takes time to internalize.

Resource routes handle JSON, file uploads, and webhooks cleanly. More boilerplate than Next.js Route Handlers for complex APIs, no built-in type-safe RPC layer.

App Router colocation of page, layout, loading, and error scales well. Server and client component boundaries require discipline to keep architecture clean on large teams.

Colocated loader, action, and component per route scales well; each route is a self-contained module. Teams must make more architectural decisions than in Next.js App Router.

Pages Router to App Router was a full paradigm shift. Cache behavior changed between minor versions. Many teams stay multiple majors behind by necessity.

The Remix to React Router merger caused community churn and the upcoming React-free Remix v3 adds uncertainty.

React developers can read page components, but RSC, async layouts, and cache segment config require dedicated onboarding. Less accessible than standard React for handoff.

Loaders and actions are explicit and route files map to URLs clearly. Three available modes and the convergence with Remix mean older docs may describe a different API.

Works well on Railway, Render, Fly.io, and self-hosted Node. Some advanced features like ISR and Edge Middleware require Vercel or a host implementing the Build Output API spec.

First-class adapters for Cloudflare Workers, Vercel, Netlify, AWS, Fastly, Deno Deploy, and Node. Cloudflare lists React Router v7 as a primary supported framework.

Turbopack stable for dev in v15 dramatically improved local iteration. Production builds still use Webpack and can reach 5-10 minutes on large codebases.

Vite-based production builds complete in 30-90 seconds for medium projects. The Babel dev plugin creates a gap between dev iteration speed and production build speed.

Vercel is generous on small projects but serverless invocations, edge compute, and bandwidth bill separately at scale. Self-hosting on a VPS significantly reduces cost.

Edge-first design via Cloudflare Workers means low cost at scale. Full SSG deployment to CDN is supported. Competitive with Next.js and better than always-on Node server deployments.

Solid choice especially with a headless CMS. More JS runtime overhead can affect CWV on pure content pages, but excellent for sites with interactive elements.

Technically capable but the wrong tool. Full React bundle on every page, no preview mode, and no CMS vendor support for preview workflows.

Best-in-class for complex React applications. Auth, streaming, caching, Server Actions, and edge deployment all compose well for SaaS and dashboard use cases.

Purpose-built for data-heavy interactive applications. The loader and action model, nested routing, progressive enhancement, and edge deployment combine to make this the strongest React option for app work.

RSC plus Client Components is architecturally correct for selective hydration. Context providers and animation libraries often force large client subtrees - requires discipline.

Progressive enhancement is a first-class design principle, forms work without JS and useFetcher enables optimistic UI. Achieving full progressive enhancement requires discipline and is not enforced.