Course contentsShow
← React
Lesson 2327 of 2,39650. Performance: Optimization TechniquesFree lesson

Memoizing Context Providers

Using useMemo for context values and placing memo boundaries around provider subtrees to control re-render scope.

Memoizing Context Providers

What you'll learn: How to prevent unnecessary re-renders of context consumers by memoizing the value object passed to your provider.


The Problem

Every time your provider component re-renders, React checks if the context value changed. If you pass an object literal or create a new object inline, every render creates a new reference—even if the contents are identical. This triggers re-renders in all consumers, even when nothing meaningful changed.

function MyProvider({ children }) {
  const [user, setUser] = useState(null);
  
  // ❌ New object every render = all consumers re-render
  return (
    <UserContext.Provider value={{ user, setUser }}>
      {children}
    </UserContext.Provider>
  );
}

The Solution: useMemo the Value

Wrap your context value object in useMemo with appropriate dependencies. Now the reference only changes when the actual data changes:

function MyProvider({ children }) {
  const [user, setUser] = useState(null);
  
  // ✅ Stable reference until user actually changes
  const value = useMemo(
    () => ({ user, setUser }),
    [user] // setUser is stable from useState
  );
  
  return (
    <UserContext.Provider value={value}>
      {children}
    </UserContext.Provider>
  );
}

Memo Boundaries Around Provider Subtrees

If the provider's parent re-renders frequently, wrap the provider component itself in React.memo to create a boundary:

const MemoizedProvider = memo(MyProvider);

// Now parent re-renders won't cascade into provider subtree

This combination—memoized value and memoized provider component—gives you full control over when context consumers update.


Key Takeaway: Always useMemo the value object you pass to Context.Provider, and consider wrapping the provider component in memo to isolate it from parent re-renders—together they eliminate wasted renders across your context tree.