Fallback Renders Immediately on Suspend
You'll learn how React responds the instant a component suspends by showing the fallback UI without delay.
The Zero-Delay Replacement
When any child component within a Suspense boundary throws a promise (suspends), React doesn't wait or show a partially-rendered tree. It immediately swaps out the entire Suspense subtree with your fallback UI. This happens synchronously during the render pass.
Think of it like a trapdoor in a stage performance. The moment an actor steps on the trigger (component suspends), the entire platform section drops away instantly—not gradually—and the understudy set (fallback) is revealed. There's no "partial transition" where you see half the content and half the fallback.
Why This Matters
This immediate replacement prevents users from seeing:
- Incomplete content with missing pieces
- "Flash of broken UI" where parts fail to render
- Confusing half-loaded states
React makes a clean cut: either you see the complete content (everything loaded successfully), or you see the fallback (something isn't ready yet). This binary approach keeps the UI predictable and coherent.
The Boundary Scope
Remember that the entire subtree under the Suspense boundary gets replaced. If you have ten components nested inside and just one suspends, all ten disappear and the fallback shows. This is why boundary placement matters—you control how much UI gets swapped out by where you position your <Suspense> component.
Example Without Code
Imagine a user profile with an avatar, bio, and posts list all inside one Suspense boundary. If the posts list data isn't ready and suspends, the user won't see the avatar and bio while posts load—they'll see your loading spinner for everything. The boundary defines the blast radius.
Key Takeaway: React replaces the entire Suspense subtree with the fallback UI instantly and completely the moment any child suspends—no partial renders, no delays.