Quick answer

Set NVIDIA Reflex Low Latency to On in every game that offers it. NVIDIA’s own latency guide recommends that, and it says Reflex overrides the driver’s Ultra Low Latency mode when both are enabled. On + Boost keeps GPU clocks high for a small latency gain at a power cost, so I would only choose it if lowest latency matters more to you than power draw.

Contents

At a glance

Class
Gaming

Provenance

  • Nov 18, 2026Published

TL;DR · NVIDIA Reflex Low Latency

  • Reflex Low Latency: On, in every game that has the option. NVIDIA's own latency guide says to turn it on whenever the game offers it.
  • On + Boost only if lowest latency matters more to you than power draw. NVIDIA calls the benefit very modest.
  • Off is for comparing. The NVIDIA pages I read describe no cost for plain On beyond a developer checklist limit of 4 percent FPS impact.
  • Driver Low Latency Mode: leave it alone in games with Reflex. NVIDIA says Reflex overrides the driver's Ultra mode when both are enabled.
  • Where it lives: in the game's own settings menu. I found no Reflex Low Latency entry in the NVIDIA app's driver-settings strings.

I run an RTX 5080, and on the bench machine nvidia-smi reports driver 621.24 today. That is the card behind this page, but every claim below comes from NVIDIA’s own documentation, not from a latency test of mine. I did not launch a game for this page, so the in-game labels are as NVIDIA’s pages describe them.

What the three settings are

Reflex Low Latency is a mode a game developer builds into the game. NVIDIA’s launch article says it lines the game engine’s work up so it finishes just in time for rendering, which empties the GPU’s render queue and eases the back pressure that queue puts on the CPU. The switch is in the game’s own settings: NVIDIA’s latency guide tells you to find it in the game’s options menu.

The game offers up to three positions: Off, On and On + Boost. Boost is the part that needs a decision, and it is covered next. For compatibility, NVIDIA says the Reflex Low Latency mode supports GeForce GTX 900 series and newer, and NVIDIA keeps a list of supported games on its Reflex page.

NVIDIA’s developer guide for integrating Reflex also states that the mode’s default state should be On, and lists Off, On and On + Boost as the three modes a game has to support. It adds that Reflex On should not cost more than 4 percent of FPS. That is a developer’s pass/fail checklist item, not a measurement of any game, so I would not read it as a promise.

On or On + Boost

NVIDIA’s description of Boost is consistent across its pages. Boost overrides the GPU’s power-saving features so clocks stay high when the game is CPU-bound, and NVIDIA says that can reduce latency slightly when the GPU is significantly underutilized and the CPU submits the final rendering work in a large batch. It also says the higher clocks can consume significantly more power, and that if you do not want that trade you can use Reflex On without Boost. Its Reflex launch article calls the Boost benefit very modest, though it can help squeeze every last millisecond out of the pipeline.

Two more NVIDIA statements bear on the choice:

  • For Counter-Strike 2, NVIDIA says Enabled + Boost can reduce latency further at the cost of extra power usage and a slightly lower frame rate, and recommends it only for players who put lowest latency ahead of highest frame rate.
  • In the same Counter-Strike 2 article, NVIDIA also says Reflex is most effective when the system is GPU-bound or the GPU is under high utilization, because that is when the CPU can run ahead and build up the render queue.

My call follows from those lines. Start with On. Move to On + Boost only if you play a latency-sensitive game, want every last bit, and accept the extra power. NVIDIA’s pages give no reason to prefer On + Boost for general play. I have not measured the difference on my own system, so I will not tell you how many milliseconds it is worth.

Off is for A/B testing or for ruling Reflex out when you are chasing a problem in one specific game. NVIDIA’s pages describe no downside to plain On beyond that developer checklist figure.

Reflex versus the driver’s Low Latency Mode

They are different switches. Low Latency Mode is a driver setting with three values. NVIDIA’s Control Panel Help describes Off (default) as prioritizing render throughput by letting games queue frames, On as limiting queued frames to one, and Ultra as fully minimizing queued frames. When NVIDIA introduced the mode in August 2019, it said On limits the queue to one frame, Ultra submits the frame just in time for the GPU, and in DirectX 12 and Vulkan games the game decides when to queue the frame. I found no newer NVIDIA statement that changes that DirectX 12 and Vulkan point, so check it before you rely on the driver mode there.

For which one wins, NVIDIA is direct:

  • If the game supports Reflex, NVIDIA recommends the Reflex mode over the driver’s Ultra mode.
  • If Reflex is not available, NVIDIA’s guide names the driver’s Ultra mode as your next best option.
  • NVIDIA says Reflex operates independently of the driver’s Ultra mode, and that if both are enabled, Reflex overrides Ultra Low Latency functionality. The guide says nothing about the driver’s On setting.

NVIDIA’s reason for the ranking is that Reflex is built into the game, so it can control the back pressure the CPU gets from the render queue and later pipeline stages. The driver’s mode can often reduce the render queue, NVIDIA says, but it cannot remove that back pressure on the game and CPU side.

Where Low Latency Mode lives now. NVIDIA’s retirement notice for the classic Control Panel says the NVIDIA app’s Graphics > Program Settings replaces Manage 3D Settings. The app on this machine, NVIDIA App 11.0.9.585, ships a Low Latency Mode entry with Off, On and Ultra in its bundled UI strings. One detail from those strings: the entry carries an error message that says to disable Smooth Motion to configure the feature. The full list of driver settings, with what I would change, is on the NVIDIA Control Panel best settings page.

Does Reflex cap your FPS?

Not as a fixed number. NVIDIA’s launch article compares Reflex Low Latency to a good in-game frame limiter that stalls the game in the right places, and then says that unlike a limiter locked to one frame rate, Reflex lets your frame rate run faster than a limit would, which it likens to a dynamic limiter.

Two details sit on top of that. The Reflex SDK has a separate frame rate limiter sub-feature that a game can expose, and NVIDIA’s developer guide says the sub-features are distinct with no cross-dependencies. And with G-SYNC and V-Sync together, NVIDIA’s guide says Reflex automatically caps the frame rate below the refresh rate. The next section covers that case.

G-SYNC and V-Sync

NVIDIA’s latency guide says V-Sync causes back pressure that reverberates through the system, and that it recommends V-Sync off if you will tolerate tearing. For G-SYNC owners who do not want to tear, it says to keep V-Sync on while using Reflex or the driver’s Ultra mode, which automatically caps the frame rate below the refresh rate. It states that this gives slightly higher latency than uncapped frame rates with Reflex on.

The guide also says driver V-Sync only works for fullscreen applications and that Microsoft hybrid laptops do not support the driver setting. If you play in windowed mode or on one of those laptops, it says to use the in-game V-Sync for G-SYNC plus V-Sync plus Reflex. That guide dates from 2020, so treat the windowed-mode statement as NVIDIA’s 2020 position. For the current driver setup and the full table of V-Sync choices by monitor type, see my V-Sync on or off page and the screen tearing guide.

One result from NVIDIA’s Streamline guide matters if you do not have a VRR monitor. That guide is developer documentation on GitHub, the copy I read carries no date, and it gives no reason for any row of its table, so I am reporting the rows and nothing more. Its table of supported configurations lists V-Sync on, VRR off and frame generation off as a case with no latency reduction from Reflex. With V-Sync on, the table lists a reduction when VRR is on or when frame generation is on. It lists a GPU-bound game as a reduction regardless, and a CPU-bound game as no reduction. NVIDIA’s Boost description, covered above, is aimed at CPU-bound cases, and I did not find NVIDIA reconciling the two statements.

Frame generation

NVIDIA ties the two together. Its DLSS 3 announcement describes DLSS 3 as combining Super Resolution, Frame Generation and Reflex, and its Streamline developer guide says a game that integrates DLSS Frame Generation has to integrate Reflex through Streamline too. The pages I read do not say whether the in-game Reflex setting can still be changed once frame generation is on, so check your game’s menu rather than assume.

NVIDIA says its DLSS 4.5 Multi Frame Generation combines with Reflex so generated frames have minimal impact on responsiveness. NVIDIA gives no measurement with that statement, so I treat it as a design claim. The frame generation guide covers how the generation modes differ.

One NVIDIA instruction changes the sync advice above. NVIDIA’s March 2026 notes say the NVIDIA app’s Dynamic Multi Frame Generation mode is not compatible with frame rate limiters or V-Sync. If you use that mode, do not apply the G-SYNC plus V-Sync plus cap recipe on top of it.

Fortnite, Counter-Strike 2 and Valorant

NVIDIA documents the setting for all three, but in old articles: Fortnite is September 2020, Valorant’s steps are from a March 2022 guide written around the GeForce Experience overlay, and Counter-Strike 2 is September 2023. I did not launch any of the games, so confirm the label in your current build.

Fortnite

NVIDIA’s Fortnite article, dated September 17, 2020, tells you to scroll down the Video Settings menu to NVIDIA Reflex Low Latency and select On. On GeForce RTX GPUs it also offers On + Boost, which NVIDIA says overrides GPU power saving to deliver higher performance and lower latency. If you want to watch latency while you play, the same article says to enable Latency Markers in Video Settings and then Latency Debug Stats in the Game UI menu. NVIDIA’s April 2021 article says Fortnite got a Boost optimization for CPU-bound scenes where the render submission thread is the limit, and that Valorant’s was still to come as of that article.

Counter-Strike 2

NVIDIA’s Counter-Strike 2 article, dated September 27, 2023, says to open the game, go to Settings, then Video, then Advanced Video, and set NVIDIA Reflex Low Latency to Enabled. It also lists Enabled + Boost, with the power and frame rate trade described above. NVIDIA says it worked with Valve on the integration.

Valorant

NVIDIA’s Reflex Analyzer guide, dated March 7, 2022, says to click the cog at the top right of the main menu, go to settings, and enable NVIDIA Reflex under the General tab; it names no On or Boost choice. NVIDIA’s April 2021 article says each Reflex game has On and Boost Mode, and it is writing about Fortnite and Valorant. My advice is the same as above: On first, Boost only if latency outranks power.

Reflex Frame Warp

NVIDIA’s developer page says Reflex consists of two technologies, Reflex Low Latency mode and Reflex Frame Warp. The same page tells developers to sign up to be notified when Frame Warp is available for general integration. Everything on this page is about Low Latency.

If a game has no Reflex entry, there is nothing to switch. The next step is the driver’s Low Latency Mode for that game, covered above, and the setting list on the Control Panel page. If frame pacing rather than latency is the complaint, start with the stuttering guide, and make sure the driver you are running is the one you meant to install, as in Game Ready vs Studio.

Frequently asked questions

Should NVIDIA low latency be on or off?
If the game has a Reflex setting, turn Reflex Low Latency On and leave the driver’s Low Latency Mode where it is. NVIDIA’s latency guide says Reflex is more effective than the driver’s Ultra mode and overrides Ultra when both are enabled. If the game has no Reflex setting, NVIDIA’s guide names the driver’s Low Latency Mode, Ultra, as the next best option. NVIDIA’s Control Panel Help lists the driver setting’s default as Off.
Should I have NVIDIA boost on or off?
Two different settings carry the name. Reflex’s On + Boost overrides the GPU’s power-saving features to keep clocks high; NVIDIA describes the benefit as very modest and says it costs more power, and for Counter-Strike 2 it says Boost can also lower the frame rate slightly. The separate Dynamic Boost entry in the driver settings shifts power between the GPU and CPU, and NVIDIA’s help page lists it as On by default. They are unrelated settings.
What is NVIDIA Reflex Low Latency in Valorant?
It is the in-game switch for NVIDIA’s Reflex Low Latency mode, which NVIDIA says synchronizes the CPU and GPU so rendering work is submitted just in time. NVIDIA’s Reflex Analyzer guide (March 2022) says Valorant’s option is under the cog menu, Settings, General tab, and an April 2021 NVIDIA article says Valorant offers On and Boost Mode. I have not checked the label in the current game.
Should I turn on Allow Low Latency Mode?
I would leave the driver’s Low Latency Mode at its default globally and set it per game for titles that have no Reflex option. NVIDIA’s Control Panel Help gives Off, On and Ultra as the values and lists Off as the default. NVIDIA’s 2019 announcement says the mode applies to DirectX 9 and 11 games, and that in DirectX 12 and Vulkan games the game decides when to queue frames.
Does NVIDIA Reflex cap FPS?
NVIDIA describes Reflex Low Latency as a dynamic limiter that keeps you in the latency sweet spot, and says your frame rate can run faster than a fixed limit would allow. The Reflex SDK also has a separate frame rate limiter that a game can expose. NVIDIA’s guide adds that with G-SYNC and V-Sync on, Reflex automatically caps the frame rate below the refresh rate.
Does Reflex work with frame generation?
Yes. NVIDIA’s DLSS 3 announcement says DLSS 3 integrates Reflex, and NVIDIA’s Streamline guide says a Reflex integration is required for DLSS Frame Generation. NVIDIA says Reflex keeps the responsiveness impact of the generated frames minimal; treat that as NVIDIA’s design claim, because I have not measured it.
Does Reflex work with G-SYNC?
Yes. NVIDIA’s latency guide says G-SYNC owners who do not want tearing can keep V-Sync on while using Reflex, which caps the frame rate below the refresh rate. It adds that this gives slightly higher latency than letting the frame rate run uncapped with Reflex on.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 14 cited sources, listed below, each checked against the original page on 2026-11-17. Every behavioural statement on this page is NVIDIA’s, read from its own pages on 2026-11-17: the system latency guide, the Reflex launch article, the Control Panel Help reference for Low Latency Mode, the 2019 driver article that introduced the mode, the Streamline developer guides for Reflex and DLSS Frame Generation, and NVIDIA’s articles for Fortnite, Counter-Strike 2 and Valorant. Several of those pages are years old, and I say so where it matters. First-hand reads on the bench machine, 2026-11-17: nvidia-smi --query-gpu=name,driver_version --format=csv,noheader returned NVIDIA GeForce RTX 5080, 621.24; reg query on HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion returned CurrentBuild 26200 and DisplayVersion 25H2; reg query on the Uninstall key returned NVIDIA App 11.0.9.585. reg query on the same key also returned UBR 9974. I read the NVIDIA app’s bundled English UI strings (www\assets\i18n\en_US.json under Program Files\NVIDIA Corporation\NVIDIA App) to confirm that the app lists Low Latency Mode with Off, On and Ultra, and that its driver-settings strings carry no Reflex Low Latency entry; the app’s overlay strings (osc\assets\i18n\en_US.json) do mention a Reflex Latency Analyzer. I did not open the NVIDIA app, launch any game or measure any latency, so I quote no latency figure of my own and no in-game menu label here was checked in the running game.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

I am Lowell K. Wood IV. I research, write and maintain everything on TechFuelHQ from St. Louis County, Missouri.