render phase
The part of an update where React calls your components and compares the results with the previous tree, without touching the page.
In more detail
Because nothing visible changes yet, React can pause, restart or discard render work, and in Strict Mode it may run it twice. That is why render code must be pure. The changes it finds are applied later in the commit phase.
Related terms
- commit phase — The part of an update where React applies the calculated changes to the real DOM, all at once and without interruption.
- reconciliation — The process where React compares the new tree of elements with the previous one and works out the smallest set of changes to the page.
- pure function — A function whose result depends only on its arguments and which has no side effects, so the same inputs always give the same output.
- render — In React, calling a component to find out what it should display now; a re-render is any render after the first.
Taught in
- Component Purity: Pure Functions, Idempotence And Side Effects — React 19 & Modern Component Architecture
- State with useState: Immutability And Asynchronous Batching — React 19 & Modern Component Architecture
- Virtual DOM vs Real DOM: The Reconciliation Cost Model — React 19 & Modern Component Architecture
- Keys In Depth: Identity Preservation And Identity Resetting — React 19 & Modern Component Architecture
- Avoiding Effect Antipatterns: Derived State And Events — React 19 & Modern Component Architecture
- useRef Mechanics: DOM References And Mutable Persistent State — React 19 & Modern Component Architecture
- Rules of Hooks: Call Order, Hook Lists, And Fiber Storage — React 19 & Modern Component Architecture
- useSyncExternalStore: Tearing-Free Store Subscriptions — React 19 & Modern Component Architecture
- Creating Event Listener Hooks with Clean Teardown Logic — React 19 & Modern Component Architecture
- Concurrent Mode: Interruptible Work And Lane Priority — React 19 & Modern Component Architecture