Course contentsShow
← React
Lesson 1536 of 2,39638. Server Components FundamentalsFree lesson

Default is Server: The New Mental Model

In RSC-enabled frameworks, components are server components by default unless marked with 'use client'.

Default is Server: The New Mental Model

What you'll learn: How React Server Components flip the traditional client-first assumption on its head.

The Mental Shift

In traditional React, every component you write is a client component by default. It runs in the browser, can use hooks, handle events, and adds to your JavaScript bundle. You had to explicitly opt into server rendering through frameworks.

React Server Components reverse this assumption entirely: components are server components by default unless you explicitly mark them with 'use client'. This is not a minor detail—it's a fundamental mental model change.

Why Default to Server?

Think of it like this: in a restaurant, the kitchen (server) does most of the preparation work. Only the final plating and serving happens at the table (client). Similarly, most components just render data—they don't need interactivity. Why send all that rendering logic to the browser if it only runs once?

By making server the default, React encourages you to keep components on the server unless they truly need client-side capabilities (state, effects, event handlers). This means:

  • You write normal components without thinking about the boundary
  • They automatically stay on the server with zero JavaScript shipped
  • You only add 'use client' when you actually need browser features

The Practical Impact

When you create a new component file, it's a server component. No bundle bloat. No hydration cost. Direct database access if you want. You're writing React, but it runs on the server and sends just the output.

Only when you need useState, click handlers, or browser APIs do you add that 'use client' directive at the top of the file.

Key Takeaway: In RSC-enabled frameworks, server is the default and client is the opt-in—reversing decades of client-first web development thinking.