Course contentsShow
← React
Lesson 2226 of 2,39649. Performance: Identifying ProblemsFree lesson

Parent Re-renders Cascade to All Children

Recognize that when a parent renders, all descendants render by default, even if their props didn't change—the root cause of most waste.

Parent Re-renders Cascade to All Children

What you'll learn: Why updating one component often triggers dozens of unnecessary re-renders throughout your app.

The Default Cascade Behavior

Here's React's foundational rendering rule: when a parent component re-renders, all of its descendants re-render by default—regardless of whether their props changed or not.

This behavior catches many developers off-guard. You might update a single piece of state in a parent component, expecting only that parent to re-render. Instead, you trigger a cascading waterfall of renders through the entire component tree beneath it.

Why This Happens

React's default strategy is conservative. When a parent renders, React assumes the children might need to render too, so it just renders them. It doesn't compare props first—it renders then compares the resulting output to decide whether to update the DOM.

This is the root cause of most performance waste in React applications.

A Simple Analogy

Imagine a company manager updating their personal schedule. If the manager tells their entire department, who then tell their teams, who then tell every individual employee to "check if your schedule changed," you've created massive unnecessary work. Most employees' schedules didn't change at all—but they all had to check anyway.

That's what happens when state changes in a high-level component: every descendant component re-executes, re-calls hooks, and re-creates its virtual DOM output, even if its inputs (props) are identical.

What the Profiler Shows

When you record a profile and see a tall flame graph with many components stacked together, you're looking at this cascade in action. One parent at the top triggered renders for everything below it.

Key Takeaway: React's default behavior is to cascade re-renders from parent to all children, regardless of prop changes—this is the primary source of wasted renders you'll need to optimize.