Navigate
Search topics, hooks, and fundamentals
Rendering is the single most important concept in React. Once you get this, everything else clicks.
Rendering = React calling your component function
Your component is just a function. When React "renders" it, React calls that function. The function runs, returns some JSX, and React figures out what changed on screen.
Think of it like a recipe:
Every render follows the same 4 steps. Press play to watch them happen one by one:
There are exactly 3 things that make React render your component. Click each one to learn more, then try the live demo:
Live demo — click the button to trigger a state change render
I re-render when my parent does
This is the #1 misconception. "Rendering" does not mean React changed the screen. React may call your function, compare the output, and decide nothing changed — so the real DOM stays untouched.
"Rendering" just means React called your function. It does not mean the screen changed. React only touches the real DOM when the output is actually different.
1. Render
f()
Function called
#12. Diff
=?
Compare old vs new
same3. DOM
SKIP
Nothing to do
untouchedCurrent output:
Hello, Alice!
Try "Set same name" — React still renders (calls your function), but the DOM stays untouched because the output didn't change.
Now that you understand what rendering is, explore what happens during a render — and why it matters for every hook you'll learn: