Prerenders

Prerenders are images, pages, or frames produced before they are needed by the user or system, and stored for quick retrieval at run time. The practice aims to reduce latency, smooth out variations in rendering time, and provide a stable baseline when data or hardware limits would otherwise cause delays.

In web contexts, prerendering often means generating static HTML for routes during the build process. The prerendered content is served directly to the client, while dynamic functionality is enabled later through JavaScript hydration. This approach improves first paint times and can aid search engine indexing, but it may be less suitable for content that changes frequently or requires user-specific data.

In game development and media production, prerenders refer to frames, textures, or cinematic sequences computed ahead of time rather than in real time. Pre-rendered assets guarantee presentation quality on hardware with limited processing power and help maintain consistent visuals across platforms. They are frequently used in conjunction with real-time rendering in hybrid workflows.

Implementation considerations include deciding which pages or assets to prerender, scheduling for build-time or incremental prerendering, caching and invalidation strategies, and handling dynamic or user-specific data. Prerendered content may be refreshed on a schedule or whenever underlying data changes.

Advantages of prerendering include reduced latency, improved user experience, and better search engine visibility. Disadvantages include longer build times, potential content staleness, increased asset size, and limitations on interactivity for prerendered assets.

See also static site generation, server-side rendering, hydration, and incremental static regeneration.