Introduction to React Server Components


Server Components are a research in progress and are by far production-ready. You don't need them to use React nor you shouldn't hurry to learn this. Continue reading just if you're curious about what's going on in the React community.

It's almost the end of the year and the React team decided to give us a sneak peak of their current research as a Christmas 🎄 gift: Server Components ⚛️.

React Server Components were announced a few hours ago. You can check the talk and demo that the React team prepared below and check the introductory blog post here.

What are React Server Components?

Here's a definition of React Server Components:

React Components are a research in progress that allows you to execute some components on the server and thus, reduce client-size bundle size.

Server Components execute on the server and on the server only. They never ship to the client.

To understand Server Components, let's visualize how a React app looks like:

A blue node represents a node that runs on the client. Let's add some Server Components (represented as orange nodes):

As you can see, Server Components gets rendered mixed with client components. They're not rendered to HTML but instead they're a representation of a React Component generated on the server so we can render Server Components that contain Client Components.

The main benefit of Server Components is that the bundle size is reduced because you don't need to send code that is used once to the client, but instead just run it on the server.

For example, below is a Note component that executes only on the server:

As you can see, since the Note component gets rendered only on the server, we can skip the need to download its dependencies on the browser. The result: zero -bundle-size React Server Components 🤯

Notice that Server Components are different than Server Side Rendering (SSR) because SSR works as follows:

  • Receive request.
  • Render response on the server.
  • Return HTML to the user as fast as possible (at this point the app isn't interactive yet).
  • Display response on the user's browser.
  • Start downloading the whole React app on the client
  • Load app on the client to enable interactivity.

On the other hand, Server Components Don't render to HTML, but instead, they render to a special format. Let's call it Server Component Tree for now. It looks like this:

Here's how it would look formatted (I modify it a bit to have syntax highlight enabled):

  M1: {
    "id": "./src/SearchField.client.js",
    "chunks": ["client5"],
    "name": ""
    M2: {
    "id": "./src/EditButton.client.js",
    "chunks": ["client1"],
    "name": ""

It doesn't matter what each piece here does. The important thing here is that Server Components is not the same that Server Side Render. In fact, Server Components are not a replacement or an alternative to Server Side Rendering, but instead, they're complementary so you can use them together.

How to Use Server Components

With the introduction of Server Components, we have three types of React components:

  • Shared Components: the components that you currently use. You can execute them both on the client and the server.
  • Server Components: only execute on the server and must have the .server.js extension.
  • Client Components: only execute on the client and must have the .client.js extension.

Note: Server Components can't have state nor event listeners. If you want interactiveness, you need to use client components.

Shared components will be executed on the server or the client depending on its parent component:

  • If the parent component is a Server Component, the Shared Component will be executed on the server.
  • If the parent component is a Client Component, the Shared Component will be executed on the client.


The initial adoption of Server Components will be through frameworks (e.g: Next.js) mostly because it requires integration with an application's routing system and bundler. Framework integration will make it easy for the community to understand how Server Components work. The idea in the future is to be framework-agnostic so you can run your own version of Server Components.

If you want to get an idea of the potential improvements of Server Components, Facebook saw a 30% of product code size reduction after the adoption of Server Components, and there's still work left so this number can increase!


Server Components are a promising proposal to React. They would allow us to reduce the bundle size of our apps without too much effort on our side. Here's a list of the main takeaways for Server Components:

One of the greatest things about Server Components is that you can decide where to add interactivity on a per-component basis.

And again, remember that this is still in research and development and it's presented to us so we can know what the react team is working on and how they envision the future of React (it looks promising 🚀).


  • Where in the stack are suppose to be Server Components? React Server Components are not mean to be added to React, but instead they are mean to be added to bundlers like webpack or parcel.

Should I use Server Components on a production app? Server Components are still on its early stages, so maybe it's not a good idea.

Server Components are a replacement for Server Side Rendering (SSR)? No. They're different techniques and are complementary they're complementary so you can use them together. SSR provides fast feedback to users by pre-rendering HTML on the server and adding interactivity on the client.

Server Components replace GraphQL? No. You can still have a GraphQL server if it makes sense for your application. In fact, some of Facebook's Server Components use GraphQL.

Do I need to learn Server Components to use React in the future? No. Server Components are completely opt-in so current React apps will not be affected by them.

**Can I mix Server and Client Components? Yes. You can have Server Components that render Client components inside and vice-versa.

Is safe to fetch data from a database in Server Components? Yes. Server Components only execute on the server and never reach the user's browser so it's safe to run database queries on them. Remember that you still need a wrapper like react-pg to be able to run queries on Server Components.