Why is wrapping everything in useMemo a mistake?
Because memoization is not free. It adds complexity and overhead without benefit if there is no measured performance issue. The right approach is to measure, find the real bottleneck, and memoize only there.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in useMemo in React Explained: What It Does and When to Use It
useMemo takes a function and a dependency array and returns the cached result. On subsequent renders, if the dependencies have not changed, it returns the cached value instead of recomputing, avoiding expensive work.
When a computation is expensive and would otherwise run on every render, like sorting a large list or a complex calculation. Also to keep an object or array reference stable so memoized children do not re-render unnecessarily.
No. Memoization itself costs something, so wrapping cheap computations in useMemo adds overhead without benefit. Measure first and use it only for expensive work or stable references.
Still have questions?
Browse all our FAQs or reach out to our support team