React Fiber Explained: Lanes, Phases, and Why Your Renders Behave That WayOfficial sources8 of 8 sources come from the companies and standards bodies that own the technology.This rates where the sources come from. It doesn't prove every claim.
A working mental model for React Fiber — render vs commit phase, the Lane priority model, automatic batching, useTransition, and useDeferredValue.
By Amit UpadhyayPublished Updated 12 minArticle 5 of 6 in Frontend (React)
AI assistant · answers from this article
1 of 6
Screens that render quickly
Nothing to add yet
When rendering is fast, setting state and letting React batch the work is all you need.
On this page
React Fiber, in one sentence
Fiber is the part of React that can pause and prioritise rendering, so typing stays responsive while a heavy update finishes behind it.
You reach for it when a screen re-renders a lot of UI in response to user input. Not before: it costs understanding urgent versus non-urgent updates.
The cheat sheet
What to use when
You do not need all of this on day one. Each row is one signal and the piece that answers it. Stop at the row your system has reached, or pick one to see it in the picture above.
Where you areThe signalWhat to useWhat it costs
None. Every update finishes before anyone could notice.Nothing. Plain state updatesNothing
Filtering 5,000 rows takes about 150 ms for each keystroke, and typing feels sticky.A transition: mark the list update as interruptibleStep 2 ↓A pending state to show
The slow component is driven by a value that comes from somewhere you do not control.A deferred value for the slow componentStep 3 ↓A list that trails the input by a moment
The update is in a transition, and one 200 ms calculation still blocks the page.Move long synchronous work out: a Worker, the server, or smaller piecesHow rendering goes wrong ↓Code to restructure
React warns about an update during render, and effects run twice in development.A pure render phase, with side effects in effects that clean upStep 4 ↓Fixing what Strict Mode exposes
Nobody can say why a component re-rendered, so memoisation is added by guesswork.The React DevTools Profiler, before changing anythingFinding what is slow ↓A few minutes of measuring
Start With Plain State Updates
For screens that render quickly, set state and let React do its work. Scheduling matters when one update is expensive enough that the user can feel it while typing.
Take a typical case, made up for illustration. A back-office product grid filtered 5,000 rows on every keystroke. Each one took about 150 ms to render, so characters appeared in bursts and the filter box felt sticky. Wrapping the grid in useDeferredValue fixed it, and also exposed an older bug: rows keyed by index, so an inline edit stayed on row 3 while the product in row 3 changed.
Fiber is the engine inside React that makes rendering interruptible and prioritised. You never call it directly, but it explains why transitions work, why keys matter, why render must be pure and why Strict Mode runs things twice. Below is the mental model, without the source code: units of work, render and commit phases, and lanes.
If typing lags on heavy screens
You wrote setState three times in a handler and saw exactly one re-render — and weren't sure why
You wrapped state in useTransition and the "urgent" updates still felt slow
You see "React detected an update during render" warnings and don't know what fiber phase that refers to
You've heard "React 18 added concurrent rendering" but couldn't explain what changed
Pro deep dive12 min full read
Keep reading with Pro
This is one of our advanced production deep dives. Pro unlocks the rest of it, every other deep dive, and the See, Animate, Test and Build modes on every topic.
What it covers
A working mental model for React Fiber — render vs commit phase, the Lane priority model, automatic batching, useTransition, and useDeferredValue.