Context re-renders have three causes, each with its own fix.
1. A new value every render. <Auth value={{ user, setUser }}> builds a new object each time the provider's component renders, even for unrelated state, so Object.is fails and every reader re-renders. Wrap the object in useMemo with the data as dependencies, and functions in useCallback. State setters and dispatch are already stable. A primitive value needs nothing.
2. No selectors. A reader subscribes to the whole value. A component that reads only theme from { theme, lang } re-renders when lang changes. Split the context by what changes together. The standard split is a reducer's state in one context and its dispatch in another: components that only dispatch never re-render on state changes, because dispatch never changes.
3. The provider re-rendering too much of the tree. If the state lives in a big component that also renders the page, every update re-renders the page as well. Move the state into a small provider component that takes children: an update re-renders the provider and the readers, while the children elements, created by its parent, are skipped. Keep providers as low as the readers allow.
What doesn't help: memo on components between the provider and the readers. Readers get their own update and render anyway; memo only stops renders that come from a parent rendering.
The React Compiler memoizes values like the inline object automatically, but it can't split a coarse context. When many components each need a slice of data that changes often, an external store read through useSyncExternalStore, typically via a state library with selectors, lets each component re-render only when its own slice changes.
Measure first: React's docs note that re-rendering readers is not a problem in smaller apps.