Frame Generation Explained: DLSS, FSR and XeSS Without the Marketing Fog
Frame generation is now common across NVIDIA DLSS, AMD FSR and Intel XeSS. All three can raise the displayed frame rate by creating intermediate frames instead of making the game engine render every frame from scratch.
What is a generated frame?
The system starts with real rendered frames and motion information, then predicts an image that belongs between them. NVIDIA’s DLSS 4 technical overview, AMD’s FSR Frame Generation documentation and Intel’s XeSS 2 whitepaper use different implementations, but the basic goal is similar: present more visual frames between expensive rendered ones.
Why FPS goes up
If a game renders 60 real frames and a frame-generation system creates an additional image between each pair, the display can receive roughly twice as many presented frames. Multi-frame systems can generate more than one intermediate image.
Why latency does not improve in the same way
A generated frame is not a new simulation step. The CPU and game engine did not process another input sample just because the display showed another image. That is why frame generation works best when the base frame rate is already healthy.
Image quality can break
Generated frames can struggle with fast UI changes, particles, transparent effects and motion that is difficult to predict. Modern versions use motion vectors, depth data and increasingly machine-learning models to reduce those artifacts, but no system is perfect.
Upscaling and frame generation are separate ideas
Upscaling renders at a lower internal resolution and reconstructs a higher-resolution image. Frame generation creates an additional time sample between frames. AMD explicitly separated FSR 3.1 frame generation from its upscaler so it can operate with other upscaling solutions.
When to use it
Use frame generation when your base performance is already playable and you want smoother presentation on a high-refresh display. If a game is struggling at a very low native frame rate, lower demanding settings or use upscaling first rather than expecting frame generation to fix responsiveness by itself.
