After the first render, a component renders again for one of three reasons:
- Its own state changed. A
useStatesetter oruseReducerdispatch with a new value. The new value is compared withObject.is; if it's the same, React skips the component and its children (it may still call the component once before bailing out). - Its parent re-rendered. Rendering is recursive: when a component renders, every component in the JSX it returns renders too, whether or not their props changed. Each
<Footer text="© 2026" />call creates a new props object, and by default React doesn't compare props. - A context it reads changed. When a provider's
valuechanges (byObject.is), every component that reads that context withuseContextorusere-renders, even if everything between them skipped rendering.
External stores read through useSyncExternalStore are the same mechanism as state: a store change schedules an update for the subscribed component.
"It re-renders because its props changed" gets the cause backwards. Props come from the parent's render, so they can only change when the parent renders, and that render alone is enough. Mutating an object that was passed as a prop triggers nothing.
The flip side is the key to cheap renders: React skips a component whose element is the same object as last time. Elements a component receives as children (or any prop) were created by its parent. If only the component's own state changed, those elements are unchanged and React doesn't call them. Moving state down, or passing parts of the tree in as children, limits re-renders without memo.
To skip rendering when props are shallowly equal, wrap the child in memo; the React Compiler does the equivalent automatically. A changed key is different: React unmounts and mounts a new instance rather than re-rendering.