Course contentsShow
← React
Lesson 1445 of 2,39636. Concurrent ReactFree lesson

When Deferred Values Update

Understanding that deferred values update after urgent renders complete, not on a timer.

When Deferred Values Update

What you'll learn: You'll understand the precise timing of when deferred values actually update in React's rendering cycle.

The Core Timing Rule

A deferred value created with useDeferredValue doesn't update on a schedule or timer—it updates after urgent renders complete. React prioritizes urgent updates (like typing in an input) first, renders those immediately, and then goes back to update the deferred value in a lower-priority render.

This means the deferred value is always "behind" the urgent value by one rendering cycle, but not by a fixed time interval.

How the Update Sequence Works

When you change a value that has both urgent and deferred versions:

  1. Urgent update renders first — React immediately re-renders with the new urgent value
  2. Browser paints the urgent update — User sees the responsive UI (like their keypress)
  3. Deferred update renders next — React schedules a lower-priority render with the updated deferred value
  4. Browser paints the deferred update — The expensive UI (like a filtered list) updates

The key insight: deferred values wait for breathing room. If the user keeps typing rapidly, the deferred value might skip several intermediate values and jump straight to the latest once typing pauses.

Why This Matters

This isn't throttling or debouncing—those work on time delays. Deferred values work on render priority. If your device is fast and idle, the deferred update might happen almost immediately. If your device is slow or the user is frantically interacting, it might take longer. React adapts automatically.

Key Takeaway: Deferred values update after urgent renders finish, not on a timer—they're priority-based, not time-based, ensuring responsiveness always wins.