React Server Components (RSC)
A React rendering model where components fetch data and render on the server, sending only minimal interactive JavaScript to the client.
Definition
React Server Components render on the server and ship only the minimal interactive payload to the browser, drastically reducing bundle size and improving LCP and INP. Per Web Development Best Practices 2026: Engineering Guide, RSC is the default rendering model for serious Next.js (15+) apps in 2026, paired with the React Compiler (which removes most manual memoization). The pattern: use RSC/SSR for the shell and data display, and client components only for truly interactive “islands.”
Consensus is established as the 2026 React/Next.js default (though this in-wiki assessment rests on a single, Next.js-centric source — other frameworks/stacks aren’t compared here). It is one option within the broader set of Rendering Strategies (CSR / SSR / SSG / ISR / RSC).
Key Properties
- Server-side data + render; minimal client JS → 40–70% smaller bundles (claimed).
- Default for new Next.js apps; client components reserved for interactive islands.
- React Compiler removes most manual
useMemo/useCallbackwork. - Improves LCP/INP and indexing vs. client-side rendering.
- Framework-specific (React/Next.js) — not a universal pattern.
Examples from Sources
| Example | Source |
|---|---|
| ”RSC dominant in serious Next.js apps (15+)”; RSC for shell + selective client components | Web Development Best Practices 2026: Engineering Guide |
In the Sources
| Source | Context |
|---|---|
| Web Development Best Practices 2026: Engineering Guide | Pillar 1 default architecture pattern; recurs in Performance and SEO pillars. |
Related
Concepts: Rendering Strategies (CSR / SSR / SSG / ISR / RSC), Core Web Vitals, Web Architecture & Scalability, Technical SEO from Architecture Entities: React, Next.js, Vercel