Course contentsShow
← React
Lesson 848 of 2,39622. Context PerformanceFree lesson

Objects Created Inline Cause All Consumers to Re-render

Every render creates a new object reference, making Context value !== previous value, triggering all consumers.

Objects Created Inline Cause All Consumers to Re-render

You'll learn why creating a new object inline for Context's value prop triggers re-renders in every consumer—even when the data inside hasn't changed.

The Core Problem

When you pass an object to Context's value prop, React compares references to determine if the value changed. If you create that object inline during render:

<MyContext.Provider value={{ user, theme }}>

...JavaScript creates a brand new object every single render. Even if user and theme haven't changed, { user, theme } is a new reference each time. React sees newValue !== oldValue and notifies all consumers to re-render.

Why This Happens

Think of it like this: you're handing someone a new envelope every day. Even if the letter inside is identical to yesterday's, it's still a different envelope—a different container. React can't peek inside efficiently, so it treats any new object reference as a change.

Every component using useContext(MyContext) will re-render, regardless of whether they only read theme or only read user. The entire object reference changed, so all subscribers are notified.

The Performance Impact

This becomes expensive when:

  • You have many consumers spread across the tree
  • The Provider's parent re-renders frequently
  • Consumers contain heavy rendering logic

Each Provider re-render creates a new object → all consumers re-render → potentially hundreds of unnecessary calculations and DOM reconciliations.

Key Takeaway: Creating Context values inline (like value={{ data }}) guarantees every consumer re-renders on every Provider render, because JavaScript always creates a new object reference—even if the contents are identical.