Post
The traditional single-pass rendering approach where each object is lit and shaded as it is drawn, simple but light-limited.
Forward rendering processes each object completely in a single pass: transform its geometry, apply all lighting calculations, texture it, and write the final pixel color. It is the straightforward, intuitive approach that every early 3D game used. The main advantage is simplicity and excellent handling of transparency and anti-aliasing, since everything is calculated in submission order. The main disadvantage is that lighting scales poorly: if you have N objects and M lights, you need N times M lighting calculations, even for lights that do not visibly affect an object. Modern variations like Forward+ and Clustered Forward rendering mitigate this by culling lights per tile or cluster, bringing the light count scalability closer to deferred rendering while maintaining its transparency and AA advantages.
Example
Doom Eternal uses a highly optimized forward rendering pipeline through id Tech 7, achieving incredibly high frame rates despite complex lighting because id Software meticulously manages light counts and visibility. Many mobile and VR games use forward rendering because it is more memory-efficient than deferred, which matters on bandwidth-constrained hardware. Fortnite originally used forward rendering on mobile and Switch to maintain performance, while the PC and console versions used deferred.
Why it matters
Forward rendering is far from obsolete despite deferred rendering's rise. It remains the better choice for VR applications, mobile games, and stylized titles where transparency and MSAA are priorities. Understanding the tradeoffs between forward and deferred rendering explains fundamental engine architecture decisions that shape what a game can and cannot do visually.
Related concepts