Is React Front-end or Full-stack?

React itself is a front-end JavaScript library for building user interfaces, not a full framework for an entire application: it renders components and keeps the browser DOM in sync with application state, but it ships with no server, no database layer and no built-in authentication. Facebook open-sourced React at JSConf US in May 2013, after engineer Jordan Walke built an early internal version to solve rendering problems in the News Feed.

Where does the front-end versus full-stack mix-up come from?

Much of the confusion comes from how React is packaged and taught today: frameworks built on top of it, especially Next.js, add API routes, server actions and React Server Components, so a project described as a React app may in fact include real backend code that React itself never provides.

Job listings add to the mix by using React as shorthand for an entire JavaScript stack, often meaning React plus Node, Express and a database, even though only the UI layer is React proper.

What does React actually handle, and what does a full stack require?

React's job is component rendering and reconciliation: it compares a virtual representation of the UI against the previous version and updates only the parts of the real DOM that changed.

A full-stack application additionally needs server-side logic, a persistent database, authentication and authorization, and a network layer connecting the two sides, none of which are part of the react package installed from npm.

Next.js closes that gap by running React Server Components on the server and letting API routes and server actions replace a separate backend, which is why teams can now build full-stack products with React supplying the UI layer, but that capability comes from Next.js and Node, not from React's core library.

What does this mean when evaluating a React developer's skills?

When evaluating a React developer's skills, ask them to separate what React itself is responsible for, such as components, hooks and state, from what the surrounding framework or backend handles, such as routing, data fetching and persistence.

A candidate who describes themselves as full-stack in React should be able to name the specific server-side tooling they used, whether that is Next.js API routes, a Node and Express backend, or another server framework, rather than treating React alone as the explanation.

Updated: July 27, 2026