Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

React state still shows the old value right after setState

Errorconsole.log(count) prints the old value right after setCount(count + 1)

Short answer

A setter does not change the variable in the code that is running. State is a snapshot of one render, and calling the setter asks React to render again with a new value. Compute the next value in a local variable, use an updater function to chain updates, and use an effect to react after the render.

  • Applies to React 18, React 19
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Log the value in the handler and again in the component body. The body log shows the new value after the re-render, the handler log does not.

    function handleClick() {
      setCount(count + 1);
      console.log('handler', count);
    }
    console.log('render', count);
  2. 2Match what you see, then jump to its fix

    1. 1console.log or an if check after the setter sees the old valueThe handler reads the variable of its own renderFix
    2. 2Calling the setter three times changes the state onceSeveral updates in one handler use the same stale valueFix

What does the error look like?

  • console.log(count) prints the old value right after setCount(count + 1)
  • three setCount(count + 1) calls raise the counter by 1, not 3

Cause 1 of 2

The handler reads the variable of its own render

1Check

The variable in a handler is fixed for that render. The setter only requests a new render, it does not change the variable.

// compare the 'handler' and 'render' logs from the first step

2Fix

Work out the next value first, then use it for both the setter and the code that needs it.

function handleClick() {
  const next = count + 1;
  setCount(next);
  console.log(next);
}

3Verify

The log shows the new value and the screen updates on the next render.

// click once and read the console

Confirmed by react.dev

Did this fix it?

Cause 2 of 2

Several updates in one handler use the same stale value

1Check

Each call is setCount(0 + 1) when count is 0 in that render, so every call queues the same value.

setCount(count + 1);
setCount(count + 1);
setCount(count + 1);

2Fix

Pass an updater function. React runs the queued functions in order during the next render, and each gets the result of the previous one. Keep them pure.

setCount(c => c + 1);
setCount(c => c + 1);
setCount(c => c + 1);

3Verify

One click now raises the counter by 3.

// click once and read the count on screen

Confirmed by react.dev

Did this fix it?

How do I stop it coming back?

  • Treat state variables as read-only values of the current render.
  • Use the updater form whenever the new state depends on the old one.
  • Keep logic that needs the committed state in the render body, not right after the setter.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.