---
title: "Discussion on \"React.memo, useMemo, useCallback: When They Help vs Hurt\" | Hashnode"
description: "Discussion on \"React.memo, useMemo, useCallback: When They Help vs Hurt\". Most React memoization is premature. useMemo on every derived value, useCallback on every function, React.memo on every component — this pattern adds comparison overhead and memory cost on every rende"
url: "https://hashnode.com/posts/react-memo-usememo-usecallback-when-they-help-vs-hurt/69fa8b8f10483a73dec656cd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [React.memo, useMemo, useCallback: When They Help vs Hurt](https://helloashish.hashnode.dev/react-memo-usememo-usecallback-when-they-help-vs-hurt?utm_source=hashnode&utm_medium=feed)

Most React memoization is premature. useMemo on every derived value, useCallback on every function, React.memo on every component — this pattern adds comparison overhead and memory cost on every rende

May 6 · 10 min read · helloashish.hashnode.dev  
Read the article

-   [#react](https://hashnode.com/tag/react)
-   [#performance](https://hashnode.com/tag/performance)
-   [#usememo](https://hashnode.com/tag/usememo)
-   [#usecallback](https://hashnode.com/tag/usecallback)
-   [#frontend](https://hashnode.com/tag/frontend)

## Written by

[Ashish Kumar](https://hashnode.com/@helloashish)

@helloashish · Delhi, India

  
[View profile](https://hashnode.com/@helloashish)

Senior frontend engineer writing about React internals, browser performance, and how big tech builds things. renderlog.in

Senior frontend engineer writing about React internals, browser performance, and how big tech builds things. renderlog.in

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
