A Zustand selector triggers extra renders

One value in my store changes, and a component that never even reads that value re-renders anyway.

IntermediateRead 7 minDoing: an hour6 steps

▶ Start

What you'll have at the end

The same feature with a render count checked in the profiler and shown to drop after the fix

Before you start

You need

A shared store already used by more than one component, with at least one component whose selector reads back more than one field from it at once.

Not covered

Reshaping the whole store into smaller pieces. That's the fix for a store that has grown too large to reason about, a different problem from one component simply reading back more than it needs.

Leans on

Frontend State Management Beyond Redux Cheat Sheetthe Selector Functions row names this exact mistake and its one-line fix
React Frontend Framework Cheat Sheetthe Profiler entry this recipe wires up to count renders before and after the fix

6 steps

Where to go next

Split a growing Zustand store into slices

for a store that has itself grown too large to reason about, a different symptom from one component reading back more than it needs

Checked 22 Aug 2026

Part of the Frontend State Management Beyond Redux cookbook