Loading video...
Video Failed to Load
Static vs. Dynamic rendering in Next.js
105,379 views • 2 years ago •via X (Twitter)
11 Comments

Static rendering provides an affordable (no runtime server compute), performant (no runtime server compute), and reliable (no runtime server compute) starting point. You can intentionally opt into rendering at runtime when you need to by using dynamic APIs.

RE: the "RSC doesn't require a server" discourse™️ Static rendering at build time would not be possible if React Server Components required a runtime server to work.

Wonderful explanation 🫶

How do you create the videos? Is it After Effects?

I use @Remotion

Beware, if you use certain props (like searchParams) the rendering will be quietly changed to be dynamic and it may be difficult to debug by static isn't working

Yes, using dynamic functions/APIs that depend on runtime information signals the developer's intention and opts the page (today) or section (future via Partial Prerendering) into dynamic rendering. More:

This looks beautiful!

That’s soo good, wow!

Thanks for the clear illustrations (and animations), they look amazing. Are these videos available on YouTube, too?

🫡
