A Server Component is a component that renders in a separate environment before the client app runs: once at build time, or on a web server per request. It's the default in an RSC app; there's no directive for it ("use server" is for Server Functions).
What it can do:
- Be async and
awaitdata: read the filesystem, query a database, use a secret, with no API endpoint in between. - Use heavy libraries for free. Its code and imports never reach the browser, so a Markdown parser used only there adds nothing to the bundle.
What it can't: anything interactive. It has no state, no Effects, no event handlers, and it can't create context. React's server build doesn't even export useState; use, useId, useMemo and useCallback are allowed. Interactivity comes from Client Components ("use client"), which it renders and passes props to.
Output. Rendering Server Components produces the RSC payload (the "Flight" format): the rendered elements as serialized data, with each Client Component replaced by a reference to its module. The client's React reads the payload, loads the referenced modules, and renders those. The Server Component's function itself is never sent.
Versus server rendering (SSR). SSR (react-dom/server) takes a tree and produces HTML for the first paint; then the client hydrates by running every component again. RSC produces a payload, not HTML, and its Server Components never run in the browser, so they never hydrate.
They're complementary: a framework renders Server Components to a payload, then server-renders that payload, Client Components included, to HTML, and ships the payload too so the client can hydrate. On navigation it can fetch a fresh payload instead of a whole new HTML page.