Frame Generation and Input Latency: Benefits and Trade-offs

Frame generation can make a game look much smoother on the same graphics card, but it is not free. This guide explains what it does, which cards support it, why input latency is part of the discussion, and how to decide for yourself whether to turn it on. We stick to what the makers say on their own pages and tell you where they give no numbers.

What frame generation does

A normal game draws every frame itself. With frame generation, the graphics card adds extra frames between the ones the game draws. NVIDIA describes its version as using AI to generate frames and boost performance. The result on screen is a higher frame rate counter and motion that can look smoother.

Seeing a higher number is not the same as feeling more responsive, and that is why latency comes up in every discussion of this feature.

Which cards support it

On its page, NVIDIA marks Frame Generation as supported on GeForce RTX 50 Series and RTX 40 Series cards, and does not mark it for RTX 30 or RTX 20 Series. The same page lists Multi Frame Generation, which can generate up to five frames per rendered frame, as an RTX 50 Series feature only.

AMD has its own frame generation under the FSR name. Support depends on the game, so check the settings menu of the game you want to play.

Why latency is part of the story

Input latency is the delay between your action and the result on screen. Both makers pair frame generation with a latency tool:

• NVIDIA Reflex. NVIDIA's page describes Frame Generation as boosting performance while maintaining responsiveness with Reflex.
• AMD Anti-Lag 2. AMD describes it as a way to reduce latency from input to presented image in GPU-bound games. Unlike the older driver version, it works inside the game logic, so the game developer has to add it. AMD lists support for Radeon RX 5000 Series and newer, with DirectX 11, DirectX 12 and Vulkan, and says its Unreal Engine plugin works with FSR Frame Generation on the native Direct3D 12 backend.

Neither page gives latency numbers for frame generation, and neither says how much latency it adds in a given game. We do not make up figures. The fact that both companies pair it with a latency tool is a reasonable hint that it matters, especially in fast competitive games.

When it makes sense

These are practical rules, not claims from the makers:

1. Slow or cinematic games. Single-player games and slower games usually care more about smooth motion than about reaction time.
2. Fast competitive games. If every millisecond counts, test it carefully, or leave it off.
3. A weak base frame rate. If the game is already choppy before the extra frames, the result can feel worse. Start from a base frame rate you are happy with.

How to test it yourself

1. Pick a scene that you can repeat, such as the same spot in a game.
2. Play for a few minutes with frame generation off, then on, and note how the controls feel.
3. Turn on the latency tool if the game offers one, such as Reflex or Anti-Lag 2.
4. Watch frame times and not only the average FPS. Our guide on FPS, frame time and 1 percent lows explains how.
5. If the game feels heavy to control, lower the settings that cost the most before you blame frame generation. Our guide on graphics settings that cost the most can help.

For other ways to improve responsiveness, see how to reduce input lag and ping and our guide to DLSS, FSR and XeSS upscaling, which is a different feature from frame generation.

Quick checklist

• More frames on screen do not automatically mean quicker controls.
• RTX 40 and 50 Series support NVIDIA's version, and AMD offers FSR frame generation.
• Pair it with Reflex or Anti-Lag 2 when the game supports it.
• Be careful in fast competitive games.
• Test it yourself and trust how it feels.