concurrent rendering
React ability to prepare several versions of the UI at once and to pause, resume or abandon rendering work so urgent updates are handled first.
In more detail
Concurrent Mode was the early name; since React 18 concurrent rendering is switched on per update by features such as transitions, Suspense and useDeferredValue. Rendering can be interrupted, but the commit that updates the page still happens in one go, so users never see partial results.
Related terms
- time slicing — Splitting a long job into short slices and giving control back to the browser between them so the page stays responsive.
- lane — The internal React label for the priority of an update, stored as one bit in a number so many priorities can be combined and compared quickly.
- transition — A React state update marked as not urgent, which React may interrupt or delay so urgent input stays responsive.
- preemption — Interrupting work in progress so something more urgent can run first.
- tearing — A visual glitch in which different parts of the screen show different versions of the same data at the same time.
Taught in
- Component Purity: Pure Functions, Idempotence And Side Effects — React 19 & Modern Component Architecture
- Virtual DOM vs Real DOM: The Reconciliation Cost Model — React 19 & Modern Component Architecture
- React Fiber Architecture: Work Units, Priority And Commits — React 19 & Modern Component Architecture
- useSyncExternalStore: Tearing-Free Store Subscriptions — React 19 & Modern Component Architecture
- Concurrent Mode: Interruptible Work And Lane Priority — React 19 & Modern Component Architecture