Stabilizing Props to Memoized Components
What you'll learn: How to combine React.memo, useCallback, and useMemo to prevent unnecessary re-renders when passing functions or objects as props.
The Problem
You've wrapped a component in React.memo to skip re-renders when its props haven't changed. But if you pass a callback or object as a prop, React.memo fails — the child re-renders anyway. Why? Because those props have new references on every parent render, even if their content is identical.
const MemoizedChild = React.memo(({ onClick, config }) => {
console.log('Child rendered');
return <button onClick={onClick}>Click</button>;
});
function Parent() {
// ❌ New function every render
const handleClick = () => console.log('clicked');
// ❌ New object every render
const config = { theme: 'dark' };
return <MemoizedChild onClick={handleClick} config={config} />;
}
Every time Parent renders, MemoizedChild re-renders despite React.memo, because handleClick and config are new references.
The Solution
Stabilize the references using useCallback for functions and useMemo for objects:
function Parent() {
// ✅ Stable function reference
const handleClick = useCallback(() => {
console.log('clicked');
}, []);
// ✅ Stable object reference
const config = useMemo(() => ({ theme: 'dark' }), []);
return <MemoizedChild onClick={handleClick} config={config} />;
}
Now React.memo works as intended — MemoizedChild only re-renders when handleClick or config actually change (based on their dependency arrays).
The Three-Part Pattern
- Wrap the child with
React.memo - Use
useCallbackfor function props - Use
useMemofor object/array props
Key Takeaway: React.memo alone cannot prevent re-renders if you pass unstable references as props — you must stabilize callbacks with useCallback and objects with useMemo to complete the optimization.