Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Short answer: use the game’s native NVIDIA Reflex option when it is available. Reflex controls CPU/GPU scheduling and render-queue latency rather than acting like a simple fixed FPS cap. Use RTSS when the game’s limiter is inconsistent, unavailable, or produces poor frame pacing—but measure the result, because an external cap is not automatically lower latency.
For tear-free G-SYNC or VRR, enable VRR, use V-SYNC as recommended by NVIDIA, and keep the frame rate below the display’s maximum refresh rate. That usually trades a small amount of latency for more consistent, tear-free output.
Reflex, RTSS, and an FPS cap solve different problems
“Latency” and “smoothness” are often treated as the same thing, but they are not. A setting can produce a steadier frame-time graph while adding a little delay, while another can minimize pipeline latency but show more pacing variation.
Recommended Free Tools
| Priority | Best starting point | Important caveat |
|---|---|---|
| Lowest practical latency | Native Reflex, initially uncapped | Tearing and refresh-ceiling behavior may be unacceptable. |
| Tear-free VRR | G-SYNC/VRR + V-SYNC + Reflex + a below-refresh cap | NVIDIA says this can be slightly slower than uncapped Reflex. |
| Best frame pacing | Native cap first; RTSS if the native cap is uneven | RTSS may trade some latency for steadier pacing. |
| No Reflex support | In-game cap, NVIDIA Max Frame Rate, or RTSS | Driver Low Latency Mode is not equivalent to Reflex integration. |
| DLSS Frame Generation | Native Reflex and title-specific testing | Rendered and generated frames create additional timing stages. |
There is no defensible universal rule that RTSS is always fastest, Reflex always caps at a particular number, or every display should be capped exactly three frames below refresh.
#1 Best Overall
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
NVIDIA describes Reflex as a game-integrated system for coordinating CPU and GPU work and reducing unnecessary render-queue delay.
What NVIDIA Reflex actually does
In a GPU-bound pipeline, the CPU can prepare frames faster than the GPU displays them. Those frames may wait in a queue, increasing the time between an input event and the frame that shows its result. Reflex coordinates CPU and GPU work so rendering happens closer to when the GPU can process it. It reduces or empties unnecessary queueing; it does not literally disable every render queue.
That is why Reflex is not simply another name for an FPS limiter. A conventional limiter aims at a user-selected frame rate. Reflex primarily manages the timing of work, although NVIDIA also describes its behavior as capable of dynamically regulating rendering to maintain a latency-efficient operating point.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteReflex Low Latency and On + Boost
- Reflex Low Latency: the normal game-integrated scheduling mode.
- On + Boost: keeps GPU clocks higher when power-saving behavior might otherwise add delay. The benefit is usually modest and can mean higher power use or a small performance cost.
Start with On. Try On + Boost only if testing shows a benefit in your game, particularly in situations where the GPU frequently reduces clocks. Do not assume Boost increases FPS; its purpose is latency consistency, not a guaranteed performance gain.
Frame Warp and Reflex markers
Reflex Frame Warp is a separate technology that can update the rendered image using the latest mouse position immediately before scanout. It should not be confused with the ordinary Reflex Low Latency setting.
Supported games and tools can also expose latency markers or PCL statistics for stages such as input, simulation, render submission, render queue, and GPU rendering. These measurements help identify where delay occurs. See the Reflex SDK and NVIDIA’s technical explanation of the latency pipeline.
Is Reflex itself an FPS limiter?
The answer depends on what “limiter” means.
- Fixed FPS cap: an in-game Max FPS setting, NVIDIA Max Frame Rate, or RTSS targets a specified rate.
- Dynamic latency control: Reflex regulates when work is submitted so the render queue does not become unnecessarily deep.
- VRR safety ceiling: G-SYNC with V-SYNC and a below-refresh cap keeps output from repeatedly hitting the display’s maximum refresh boundary.
Reflex can behave like a dynamic frame-rate limiter, but “Reflex On” is not a user-configurable fixed cap with a guaranteed numeric target. Its behavior varies with the game’s integration, CPU/GPU bottleneck, refresh rate, driver, and whether frame generation is enabled.
If Reflex appears not to cap your FPS, that may be normal. The game may be CPU-limited, another limiter may be active, frame generation may change which counter you are watching, or the title may implement Reflex differently from another game.
What RTSS adds
RivaTuner Statistics Server (RTSS) is an external frame-rate limiter and monitoring tool. It can be useful when:
Rank #2
- QHD Resolution (2560 x 1440) has 1.7 times the pixel density of Full HD for incredibly detailed pinsharp images
- HDR10 provides brighter highlights and nuanced shadow for added depth - making every scene feel more vivid and realistic
- The 180Hz refresh rate minimizes lag for gameplay with ultra-smooth action. Plus, the 1ms response time helps capture your moves in real-time, allowing you to react fast for gaming precision
- AMD FreeSync reduces choppiness, screen lag and image tearing, ensuring that your fast-paced, complex in-game action is stable with minimal stutter
- Ergonomic stand allows for tilt, pivot and height adjustments to maximize gaming comfort
- the game has no suitable FPS limiter;
- the native cap produces uneven frame times;
- you need a per-game external cap;
- you are troubleshooting pacing and want a consistent fixed target.
An external limiter can make frame delivery more regular, but it runs outside the game’s own scheduling path. A well-implemented engine-level limiter may place work more favorably in the pipeline and produce lower latency. Enthusiast testing discussed by Blur Busters describes this as a trade-off rather than a universal result: native limiters often have a latency advantage, while RTSS can improve pacing in particular games.
A smoother graph does not prove lower click-to-photon latency. Conversely, a lower average latency does not guarantee visually consistent frame delivery.
Using Reflex and RTSS together
Native Reflex plus a normal RTSS cap
The game’s Reflex scheduling remains active while RTSS imposes an external ceiling. This can be a sensible fallback if the native limiter is unstable, but the external cap may add some delay compared with a good in-game limiter. The exact result is game-specific.
Test three conditions rather than assuming one is best:
- Reflex with no fixed cap.
- Reflex with the game’s own cap.
- Reflex with RTSS at the same nominal cap.
Compare both latency and frame-time consistency under the same workload.
RTSS modes labelled as Reflex-related
Do not automatically treat an RTSS option containing “Reflex” in its name as identical to native, NVIDIA-integrated Reflex. Behavior can depend on the RTSS build, limiter mode, game, API, and implementation. Verify the specific release and test it as a separate configuration. A similar label is not evidence of NVIDIA endorsement or feature equivalence.
Avoid stacking ordinary caps
Do not casually enable an in-game cap, NVIDIA App or Control Panel Max Frame Rate, RTSS cap, and another third-party limiter at the same time. Multiple caps can fight one another, make the observed FPS difficult to interpret, and hide which setting affects latency.
Use one primary fixed limiter during each test. A deliberate two-cap technique can be tested separately, but it should not be the default troubleshooting configuration.
G-SYNC, V-SYNC, and the cap target
For tear-free VRR
A practical starting point for a G-SYNC or compatible VRR display is:
Rank #3
- Smooth motion: 240Hz refresh rate and fast 0.5ms response time provide crisp visuals and fluid movement with less input lag.
- Seamless gaming: FreeSync Premium and HDMI VRR eliminate tearing for smooth, responsive PC and console gameplay.
- Fast IPS: Faster 0.5ms response with excellent color accuracy across wide IPS viewing angles.
- Rich color: 99% sRGB color coverage delivers vivid, detailed imagery with strong accuracy.
- Eye comfort: TÜV Rheinland 3‑star certified display lowers blue light while preserving color quality.
- Enable G-SYNC/VRR for the display mode you actually use.
- Enable V-SYNC in the NVIDIA Control Panel or NVIDIA App.
- Usually disable in-game V-SYNC, unless your windowed or laptop configuration requires it.
- Enable Reflex in the game.
- Use a frame cap below the display’s maximum refresh rate.
- Prefer the game’s native cap if its pacing is stable; otherwise test RTSS or NVIDIA Max Frame Rate.
This arrangement is intended to keep the display inside its VRR range and avoid conventional V-SYNC backpressure. NVIDIA notes that properly configured G-SYNC, V-SYNC, and Reflex can still have slightly more latency than uncapped FPS with Reflex.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Control Panel V-SYNC behavior has limitations for some windowed applications, and NVIDIA documents additional restrictions on MSHybrid laptops. Borderless-window and hybrid-laptop users should test in-game V-SYNC rather than assuming fullscreen behavior applies.
For minimum latency where tearing is acceptable
Test Reflex uncapped first. This can provide the lowest practical latency in a particular game, but it may tear or repeatedly reach the display’s refresh ceiling. If you use VRR, add a cap below the maximum refresh rate and compare the result.
What should the cap be?
A below-refresh cap is a strategy, not a universal number. The required margin depends on:
- refresh rate;
- cap accuracy and overshoot;
- frame-time variance;
- workload spikes;
- display and driver behavior;
- whether the game is CPU- or GPU-limited.
For example, a nominal 162 FPS cap on a 165 Hz display may behave differently from a nominal 237 FPS cap on a 240 Hz display. The same numerical margin is not guaranteed to keep every display away from its VRR ceiling.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Check the frame-time graph, actual FPS behavior, and whether the display remains in VRR mode. If tearing is acceptable, uncapped Reflex may be preferable. If tear-free consistency matters more, accept the small latency trade-off of a below-refresh cap.
DLSS Frame Generation changes the analysis
Frame Generation separates rendered frames from displayed or interpolated frames. Depending on the game and limiter, a cap may apply before generation, after generation, or at a point chosen by the engine.
An external RTSS cap can therefore behave differently from an engine-integrated cap. It may restrict the source render rate, the displayed output rate, or interact with the generation pipeline in a way that is not obvious from an FPS overlay.
Native Reflex integration is particularly important to test when Frame Generation is enabled. NVIDIA’s Streamline Reflex documentation and programming guide describe separate timing stages for frame-generation paths, including render-to-frame-generation and frame-generation-to-display stages.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- 27” 240Hz 1500R Curved FHD 1080P Gaming Monitor for Game Play.
- Prioritizes Gaming Performance: Up to 240Hz high refresh rate, more immersive 1500R Curvature, FreeSync, MPRT 1ms Response Time, Black Level adjustment(shadow booster), Game Modes Preset, Crosshair.
- Cinematic Color Accuracy: 130% sRGB & DCI-P3 95% color gamut, 4000:1 contrast ratio, 300nits brightness, HDR, Anti-flicker; Anti-Glare.
- Plug & Play Design: HDMI & DP1.4 & Audio Jack(No built-in speakers), durable metal stand, tilt -5°~15, VESA 100*100mm compatible.
- Warranty: Money-back and free replacement within 30 days, 1-year quality warranty and lifetime technical support. Pls contact SANSUI service support first if any product problem.
Measure each game with Frame Generation both on and off. Do not assume that a cap that works well in a conventional rendering path is correct for every DLSS Frame Generation title.
Reflex versus NVIDIA Low Latency Mode
NVIDIA Reflex is game-integrated. Driver-level Low Latency Mode operates outside the game and is a fallback or alternative when native Reflex is unavailable. It is not equivalent to the Reflex SDK’s CPU/GPU coordination and in-engine markers.
Use this comparison:
- Reflex Off and driver Low Latency Mode Off.
- Reflex On and driver Low Latency Mode Off.
- Reflex On + Boost, if needed.
- In a game without Reflex, driver Low Latency Mode On or Ultra.
- In a game without Reflex, compare the native, NVIDIA, and RTSS frame caps.
Avoid casually stacking driver Ultra with native Reflex. Keep the test simple so you can identify which control is responsible for any change.
Recommended configurations
Competitive game, tearing acceptable
- Reflex: On
- Fixed cap: initially Off
- G-SYNC/V-SYNC: test according to your tolerance for tearing
- Boost: only if measurement shows a benefit
Use this as a latency-first baseline, not a promise that every system will measure best uncapped.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Competitive game, tear-free priority
- G-SYNC/VRR: On
- V-SYNC: On in NVIDIA Control Panel or App
- Reflex: On
- Cap: below maximum refresh, preferably in-game if pacing is stable
Compare the capped and uncapped results. NVIDIA’s guidance acknowledges a small latency trade-off for tear-free operation.
Single-player VRR game
Start with native Reflex if available, G-SYNC/VRR, V-SYNC, and a stable below-refresh cap. If the game’s limiter produces visible pacing variation, test RTSS. Smoothness may matter more than the smallest measurable latency difference.
Game without Reflex
- Enable VRR if supported.
- Start with the game’s own limiter.
- Test NVIDIA Max Frame Rate if the game’s cap is poor or missing.
- Test RTSS if pacing remains inconsistent.
- Use driver Low Latency Mode as a fallback, not as a claim of equivalent Reflex behavior.
Borderless window or MSHybrid laptop
Do not assume NVIDIA Control Panel V-SYNC behaves exactly as it does in exclusive fullscreen. Test the game’s V-SYNC option, confirm that VRR is active, and measure the actual result on the laptop’s intended display path.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to measure the difference properly
Use a repeatable workload rather than comparing settings by feel alone.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Choose the same training range, replay, benchmark, or repeatable scene.
- Keep resolution, graphics options, refresh rate, driver, power mode, and input device unchanged.
- Warm up the game before recording.
- Disable competing limiters initially.
- Change one setting at a time.
- Repeat every condition several times.
- Record average FPS, frame-time graphs, 1% lows, GPU utilization, CPU limitation, and latency where available.
- Report the spread between runs, not just the best result.
What the measurements mean
NVIDIA FrameView can report FPS, frame-time-related metrics, and PC Latency in supported titles. Its PC Latency measurement covers the interval from PC input reception to the frame being sent to the display. It does not include mouse-device latency or the monitor’s display latency. See the FrameView 1.7 User Guide.
Best Value
- 1800R curve monitor the curved display delivers a revolutionary visual experience with a leading 1800R screen curvature as the images appear to wrap around you for an in depth, immersive experience
- Hdmi, VGA & PC audio in ports
- High refresh rate 75Hz.Brightness (cd/m²):250 cd/m2
- Vesa wall mount ready; Lamp Life: 30,000+ Hours
- Windows 10 Sceptre Monitors are fully compatible with Windows 10, the most recent operating System available on PCs.Brightness: 220 cd/M2
A compatible G-SYNC display and mouse can use Reflex Analyzer for a broader click-to-visible-pixel measurement. A high-speed camera or photodiode-based setup is another option when you need independent end-to-end validation. Reflex Analyzer measures more of the complete path; its presence does not mean the monitor is automatically faster in every other respect.
If FrameView reports “NA,” the title may not support the metric, the game may be in a menu, or active gameplay or benchmark activity may be required before the value updates.
Troubleshooting common results
“Reflex does not cap my FPS”
- Disable RTSS, NVIDIA Max Frame Rate, the in-game cap, and other limiters.
- Compare Reflex Off and On in the same scene.
- Check whether you are CPU-limited.
- Separate native/rendered FPS from displayed FPS when Frame Generation is active.
- Inspect frame times and GPU utilization.
- Add a known fixed cap only after establishing the uncapped baseline.
“RTSS feels smoother, but latency is worse”
That is plausible, not contradictory. RTSS may regularize frame delivery while delaying some frames compared with an engine-level limiter. Compare PC Latency with frame-time consistency instead of using one as a substitute for the other.
“My FPS is below the cap, but latency is high”
Average FPS does not reveal every source of delay. Check GPU-bound queueing, CPU simulation time, V-SYNC boundary hits, frame-generation stages, background CPU activity, overlays, and whether the measurement is PC Latency or true click-to-photon latency.
“Reflex On + Boost reduces performance”
Boost can increase power use and may produce a small performance cost. Disable it if it does not improve the measured result on your system.
“The cap overshoots”
Nominal caps are not always exact. Examine the frame-time graph and repeated runs. Reduce the target enough to keep actual output below the VRR ceiling, or switch to a limiter with more suitable pacing for that game.
For developers: Reflex is not a user command
NVIDIA’s Streamline programming guide documents Reflex integration controls such as:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minutesl::ReflexOptions reflexOptions = {};
reflexOptions.mode = eLowLatency;
reflexOptions.frameLimitUs = myFrameLimit;
slReflexSetOptions(reflexOptions);The documented modes include eOff, eLowLatency, and eLowLatencyWithBoost, along with slReflexSleep and pipeline-timing markers. This is developer-side integration code, not a command that can configure Reflex in a retail game.
The Streamline documentation lists Reflex Low Latency support for NVIDIA GPUs beginning with GeForce 900 Series and a driver requirement of 456.38 or newer for the documented integration baseline. Those SDK requirements do not guarantee that every commercial game supports every Reflex feature or exposes every mode.
Bottom line
Start with native NVIDIA Reflex. If you want the lowest practical latency, test it uncapped first. If you want tear-free G-SYNC or VRR, pair it with V-SYNC and a below-refresh cap, accepting a possible small latency cost. Use the game’s native limiter when its pacing is good; use RTSS when it solves a real pacing or compatibility problem, then verify the latency trade-off rather than assuming it is faster.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
