Most React performance tutorials end with the same bad advice: wrap everything in and and call it a day. If you have fol

Most React performance tutorials end with the same bad advice: wrap everything in useMemo and useCallback and call it a day. If you have followed that advice, you have probably made your application slower. These hooks are not free. Each one allocates memory, compares dependencies, and stores cached values. Used without purpose, they become overhead instead of optimization.

Let’s strip this down to what actually matters.

What Each Hook Really Does

useMemo remembers a value. You hand it a function that does heavy work, and it returns the result. On the next render, if your dependencies have not changed, React skips the calculation and hands back the old result.

useCallback remembers a function. It does not run the function for you. It simply returns the same function instance between renders as long as its dependencies stay the same.

That is the entire difference. One caches a computed value. One caches a reference. Mixing these up leads to code that looks optimized but behaves identically to unwrapped code while costing extra memory.

Why Function Identity Breaks Your Tree

When a component re-renders, React executes the entire function body again. Every variable is recreated. Every inline function gets a brand new address in memory.

In JavaScript, two functions that contain the exact same logic are not equal. () => {} === () => {} evaluates to false. The same rule applies to objects and arrays. If your parent component defines handleSubmit and passes it to a child, that child receives a new prop on every single render. Even if the child is wrapped in React.memo, it cannot tell that the new function does the same thing as the old one. The reference changed, so the child re-renders.

This is the root problem useCallback was built to solve. It is not about speed. It is about stability.

When useMemo Earns Its Keep

You need useMemo when you are performing work that is objectively expensive and you can see a measurable lag.

Think about filtering a massive dataset. If you have a table with tens of thousands of rows and a search input, you might write something like this inside your component:

const visibleRows = rows.filter(r => r.name.includes(query));

Without useMemo, that loop runs on every render. If the user clicks a button that toggles a sidebar, the parent re-renders, and your filter runs again even though rows and query never changed. On a large dataset, that stutter is visible.

useMemo fixes this by pinning the result:

const visibleRows = useMemo(() => {
  return rows.filter(r => r.name.includes(query));
}, [rows, query]);

Now React only re-runs that filter when the dependencies actually change.

The same logic applies to complex mathematical calculations, transforming API responses into chart-friendly formats, or deriving state that would otherwise be recalculated constantly.

There is a second, less obvious use case. If you create an object or array locally and include it in a useEffect dependency array, you can accidentally trigger that effect on every render. Inline objects and arrays get new identities each time, so the effect sees a changed dependency and fires again. Memoizing that object with useMemo keeps the reference stable and lets your effect run only when the underlying data actually changes.

When useCallback Becomes Necessary

useCallback matters most when you are passing handlers into child components that are optimized with React.memo.

Imagine a parent component that holds a counter. It also renders an expensive child list:

function Parent() {
  const [count, setCount] = useState(0);
  
  const handleItemClick = (id) => {
    console.log(id);
  };
  
  return (
    <div>
      <button onClick={() => setCount(c + 1)}>{count}</button>
      <ExpensiveList onItemClick={handleItemClick} />
    </div>
  );
}

Every time count changes, Parent re-renders. A fresh handleItemClick is created. Because ExpensiveList receives a new prop reference, it re-renders too. If ExpensiveList is wrapped in React.memo, that memoization is completely wasted because the function prop changed.

useCallback preserves the reference:

const handleItemClick = useCallback((id) => {
  console.log(id);
}, []);

Now ExpensiveList only re-renders when it truly needs to.

Another critical situation involves useEffect. If an effect subscribes to a function defined inside your component, and that function changes identity every render, the effect will teardown and resubscribe repeatedly. Memoizing the function keeps the effect stable.

The Dependency Array Trap and Stale Closures

Both hooks rely on dependency arrays, and this is where most bugs hide.

Si omites una variable del array de dependencias, tu función o valor memorizado captura una versión antigua de esa variable. Esto es una clausura obsoleta (stale closure). La interfaz de usuario puede mostrar datos actualizados, pero tu callback sigue consultando el estado de hace tres renders. La solución es sencilla, pero fácil de pasar por alto durante las revisiones de código: incluye cada valor utilizado dentro del hook que pueda cambiar.

Ejecuta la regla de ESLint react-hooks/exhaustive-deps. Detectará omisiones obvias. Pero no la trates como a un robot. Comprende por qué cada dependencia es importante.

El impuesto oculto de la sobreoptimización

Los principiantes suelen blindar cada función y cada valor con estos hooks porque les da una sensación de seguridad. Ese hábito resulta contraproducente.

React debe almacenar los valores en caché en la memoria. En cada render, debe iterar a través de tu array de dependencias y comparar cada elemento usando Object.is. Esa comparación es económica, pero no es gratuita. Si envuelves un manejador de eventos trivial como onClick={() => setOpen(true)} dentro de useCallback, estás pagando costos de memoria y CPU para evitar la creación de una función que habría sido instantánea de asignar.

Los hooks también añaden ruido. El código envuelto en useMemo y useCallback es más difícil de leer y de mantener. Cada array de dependencias es una posible clausura obsoleta esperando para darte un susto.

La verdadera regla general es poco glamurosa pero efectiva: escribe código simple primero. Optimiza solo cuando tengas pruebas de un problema. Usa el React DevTools Profiler para identificar qué componentes son costosos y qué renders son innecesarios. Si un render tarda menos de unos pocos milisegundos, ningún usuario lo notará, y tu memorización no estará solucionando nada.

En conclusión

useMemo es para valores costosos. useCallback es para referencias de funciones estables. Ninguno de los dos hooks hace que tu componente se renderice más rápido por sí solo; lo que hacen es prevenir trabajo innecesario en las etapas posteriores. Empieza sin ellos, mide con herramientas reales y añádelos precisamente donde el profiler muestre un cuello de botella. El código limpio que se vuelve a renderizar ocasionalmente casi siempre vencerá al código sobre-ingenierizado que memoriza todo.