There is no universally best FPS limiter. Start with the game’s built-in limiter when it delivers stable frame times and responsive input. Choose RivaTuner Statistics Server (RTSS) when smooth pacing and diagnostics are the priority, especially if the game’s cap is inconsistent. Choose NVIDIA Control Panel’s Max Frame Rate for a convenient driver-level cap, broad per-game coverage, and lower power, heat, or fan noise.
The “new NVIDIA limiter” framing is outdated: NVIDIA introduced Max Frame Rate with the R440 driver generation. Current NVIDIA documentation lists a configurable range of 20–1,000 FPS. The right choice depends on the game engine, graphics API, VRR settings, frame generation, workload, and whether you value latency, consistency, convenience, or power efficiency most.
As an Amazon Associate I earn from qualifying purchases.
What an FPS limiter actually changes
An FPS limiter prevents a game from rendering more frames than a chosen target. That can reduce GPU utilization, power consumption, temperature, and fan noise. On a variable-refresh-rate (VRR) monitor, it can also help keep output below the display’s refresh ceiling, avoiding unwanted transitions into a V-Sync-limited state.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Average FPS is only part of the experience. A nominal 141 FPS cap can feel worse than another 141 FPS cap if frame delivery is uneven. Frame-time graphs, percentile performance, input latency, and behavior during difficult scenes matter more than the number shown by an on-screen counter.
#1 Best Overall
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
In simplified terms, the path is:
Game engine → graphics API and driver → presentation/compositor → display
An in-engine limiter is coordinated by the game. NVIDIA Max Frame Rate operates at the driver level. RTSS is an external per-application limiter and monitoring utility. The exact timing and result vary by API, presentation mode, synchronization settings, and game implementation, so this diagram should not be treated as a universal latency ranking.
Quick comparison
| Priority | Best starting point | Why | Main caveat |
|---|---|---|---|
| Competitive input response | In-engine limiter | A well-designed cap can coordinate with the game’s input and render pipeline. | Quality varies considerably by title. |
| Consistent frame pacing | RTSS | Precise per-game caps and useful monitoring make pacing problems easier to identify. | It adds another background utility and may interact with overlays. |
| Simple per-game or global cap | NVIDIA Max Frame Rate | It is integrated into NVIDIA’s driver settings and does not require RTSS. | It provides less diagnostic visibility. |
| Laptop power and noise reduction | NVIDIA Max Frame Rate | NVIDIA explicitly documents Max Frame Rate for power-saving scenarios. | Battery Boost or WhisperMode may impose a lower limit. |
| No reliable in-game cap | NVIDIA or RTSS | Both provide an external fallback. | Test the specific game, API, and display mode. |
| Anti-cheat-sensitive game | In-game or NVIDIA limiter | These avoid relying on an external monitoring hook. | Always follow the game’s current policy. |
This is a practical starting recommendation, not a laboratory ranking. Claims that RTSS is always smoothest, that in-engine is always lowest latency, or that NVIDIA’s limiter always adds latency are too broad without controlled tests.
NVIDIA Control Panel Max Frame Rate
NVIDIA’s setting is found at NVIDIA Control Panel → Manage 3D Settings → Max Frame Rate. It limits the maximum frame rate rendered by a 3D application and can be applied globally or to an individual game profile. NVIDIA documents a range of 20 to 1,000 FPS. See the NVIDIA Manage 3D Settings reference.
Set a cap for one game
- Open NVIDIA Control Panel.
- Select Manage 3D Settings.
- Open Program Settings.
- Select the game, or choose Add and select its executable.
- Find Max Frame Rate.
- Enable it and enter the target FPS.
- Click Apply.
For a universal ceiling, use Manage 3D Settings → Global Settings → Max Frame Rate. Per-game profiles are usually better because a 60-FPS single-player title, a 165-Hz competitive game, and a battery-conscious laptop profile may need different limits.
Do not confuse it with Background Application Max Frame Rate
Max Frame Rate limits an active 3D application. Background Application Max Frame Rate is a separate control for applications that are running in the background. NVIDIA lists the two settings separately. A background cap will not replace the active-game cap.
Advantages and limitations
- Advantages: simple setup, global or per-game profiles, no separate limiter required, and useful power-saving behavior.
- Limitations: less frame-pacing feedback than RTSS, behavior can differ by API and presentation mode, and a particular game may feel smoother with its own limiter or RTSS.
NVIDIA’s software UI is changing. Recent NVIDIA App release notes describe selected legacy 3D settings moving from the classic Control Panel. That is a migration of selected functions, not proof that Control Panel has disappeared entirely. If a label or location differs on your system, check the current NVIDIA App and driver version.
Free tools Windows power users keep installed
One-click scans. No signup required.
Related settings
Low Latency Mode is separate from Max Frame Rate. NVIDIA describes On as limiting queued frames to one and Ultra as minimizing queued frames. Enabling a frame cap does not by itself guarantee the lowest input latency. GPU saturation, queued work, V-Sync, Reflex, and frame generation may matter more. NVIDIA’s settings reference documents these controls.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
On laptops, Battery Boost and WhisperMode can impose their own limits. NVIDIA’s guidance is that the lowest active limit can prevail. If a game refuses to reach your selected target, check these modes before assuming Max Frame Rate is malfunctioning. NVIDIA’s historical guidance is available in its GeForce driver article.
RivaTuner Statistics Server
RTSS is an external per-application limiter commonly used with MSI Afterburner, although MSI Afterburner is not required to cap frames. RTSS is also useful for on-screen statistics and frame-time monitoring. MSI Afterburner and RTSS are separate utilities; overclocking is not necessary for this use.
Use RTSS when a game’s internal cap is visibly uneven, when you need precise per-game profiles, or when you want to verify the cap with a frame-time graph. Its reputation for smooth pacing is useful practical guidance, but it is not a universal measured result. Do not assume that RTSS has a fixed latency penalty or advantage across every game.
Basic RTSS workflow
- Install RTSS from a current, verified distribution source.
- Launch RTSS and add the game executable if it is not detected automatically.
- Select the game profile.
- Enter the desired value in the frame-rate limit field.
- Launch the game and verify the result with a frame-time graph or another consistent measurement method.
- For troubleshooting, temporarily set the profile’s limit to zero or exit RTSS, then retest the game.
External overlays can conflict with some anti-cheat systems, capture tools, launchers, or other overlays. This is not a blanket claim that RTSS is unsafe; compatibility is title- and version-specific. If a game stops launching or behaves differently after RTSS is installed, disable the RTSS profile first and check the game’s current rules.
In-engine frame limiters
A built-in limiter is implemented by the game and may have access to its render loop, simulation timing, input processing, and presentation logic. A well-designed in-engine limiter can therefore be highly responsive and may be the best choice for a competitive game.
That does not make every in-engine limiter good. Some offer only coarse values, overshoot their target, produce uneven frame times during CPU-heavy scenes, or behave differently in DX11, DX12, Vulkan, and OpenGL. Menus and cutscenes may use separate limits or ignore the gameplay cap. Borderless mode can also behave differently from exclusive fullscreen.
Prefer the in-engine limiter when:
- the cap holds its target in actual gameplay;
- the frame-time graph is stable;
- input response is your primary concern;
- the title supports NVIDIA Reflex or another integrated latency feature; or
- you want to avoid external overlay compatibility issues.
Switch to RTSS or NVIDIA Max Frame Rate when the internal option is missing, unreliable, or visibly produces worse pacing.
VRR: G-SYNC, G-SYNC Compatible, and FreeSync
NVIDIA describes G-SYNC as matching the display’s refresh behavior to the GPU’s frame rate, reducing tearing and stutter. To configure it, open NVIDIA Control Panel → Display → Set up G-SYNC, enable G-SYNC or G-SYNC Compatible, and choose fullscreen-only or windowed-and-fullscreen operation. NVIDIA says the monitor should be connected, enabled, configured as the primary display, and set to the appropriate variable-refresh monitor mode. See the G-SYNC setup instructions and NVIDIA’s VRR explanation.
Rank #3
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
A common starting point is to cap a few frames below the display’s maximum refresh rate:
- 144 Hz: approximately 141 FPS
- 165 Hz: approximately 162 FPS
- 240 Hz: approximately 237 FPS
These are practical starting values, not mandatory NVIDIA settings or universal laws. The best value depends on the monitor’s actual refresh behavior, VRR range, cap variance, game workload, and synchronization configuration. If the cap still touches the refresh ceiling, lower it slightly and retest.
For FreeSync or Adaptive-Sync displays driven by an NVIDIA GPU, the same principle applies: enable the supported VRR mode, confirm that it works in the relevant display mode, and test the cap rather than assuming compatibility from the label alone.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsFixed-refresh monitors
On a fixed 60-Hz display, use the in-game cap if it delivers consistent 16.67-ms frame times and responsive input. Use RTSS if the game’s pacing is visibly uneven. V-Sync can eliminate tearing, but it can also change latency and behavior when the system cannot sustain the refresh rate. A 60-FPS cap does not guarantee perfectly timed frames.
Frame generation changes the comparison
DLSS Frame Generation, FSR Frame Generation, and similar technologies make “FPS” an ambiguous measurement. A counter may show displayed frames while the game’s simulation and input operate at a lower base-render rate.
Keep these quantities separate:
- Base or rendered FPS: frames generated directly by the game’s normal render path.
- Generated FPS: additional frames created by the frame-generation system.
- Displayed FPS: the frames presented to the monitor.
- Simulation rate: the rate at which game logic and input are processed.
- Input-to-photon latency: the time from an input event to its visible result.
Do not automatically cap the displayed generated-FPS number. The useful target depends on the game, the frame-generation implementation, the base render rate, Reflex or another latency feature, and the display’s VRR ceiling. Test the complete configuration you actually play.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.GPU-bound and CPU-bound systems behave differently
On a GPU-bound system, capping below the maximum can create rendering headroom, reduce queueing in some situations, and lower power draw. NVIDIA has historically described Max Frame Rate as useful for power savings, latency reduction in some scenarios, and staying within a VRR range.
On a CPU-bound system, changing the limiter may not fix stutter caused by main-thread spikes, simulation work, asset streaming, shader compilation, or inconsistent scheduling. A cap controls frame production; it cannot repair every source of uneven frame delivery.
Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
How to test the three limiters properly
A fair comparison requires the same game state and only one active limiter at a time.
- Choose a repeatable gameplay route or scene.
- Keep resolution, graphics settings, display mode, refresh rate, driver, and game build unchanged.
- Disable all but one limiter.
- Record an uncapped baseline, then test the in-engine cap, NVIDIA Max Frame Rate, and RTSS at the same target.
- Record average FPS, 1% low and 0.1% low results, a frame-time graph, GPU utilization, and power draw if available.
- Measure input latency with appropriate hardware where possible. Do not infer latency from the limiter’s name or location.
- Repeat each run several times in both an ordinary scene and a CPU- or GPU-heavy scene.
- Separately test menus, cutscenes, alt-tab recovery, borderless mode, and frame-generation modes.
Do not rely only on the game’s FPS counter. NVIDIA’s FrameView documentation notes that games may have internal caps and that V-Sync can also explain an apparently capped result. Check those settings when diagnosing output that is lower than expected.
Do not stack limiters casually
Running an in-game cap, NVIDIA cap, and RTSS cap simultaneously makes diagnosis difficult and can introduce competing timing behavior. Choose one primary limiter. During testing, standardize V-Sync, Reflex, frame generation, overlays, capture software, and any laptop power-management limit. Restore the game’s original settings after the comparison.
Recommended Free Tools
Troubleshooting
The cap does not work
- Confirm that the correct game executable is selected in the NVIDIA profile or RTSS.
- Check whether a launcher starts a different executable.
- Test fullscreen and borderless separately.
- Disable competing caps and overlays.
- Check V-Sync, frame generation, Battery Boost, and WhisperMode.
- Restart the game after changing driver or RTSS settings.
FPS is stuck below the selected cap
The limiter may be working correctly: the system may be CPU-bound or GPU-bound below the target. Other causes include V-Sync, a lower in-game cap, a laptop power mode, a refresh-rate limit, or frame-generation settings. Compare utilization and frame times rather than raising the cap blindly.
RTSS prevents the game from launching
Exit RTSS or disable the game profile and retest. If that resolves the problem, leave RTSS disabled for that title unless its current compatibility rules and a later software version provide a safe solution.
FPS is stable but the game still stutters
Inspect frame-time spikes. Traversal stutter, shader compilation, asset streaming, CPU scheduling, background activity, and simulation stalls can occur even when average FPS and the displayed counter look healthy.
The cap changes after alt-tab
Retest the game in the same display mode used during normal play. Borderless windows pass through the desktop compositor and may behave differently from exclusive fullscreen. Also check whether the game applies separate foreground and background limits.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Final decision matrix
- Choose the in-engine limiter if it holds a stable target and your priority is responsiveness, especially in a competitive game.
- Choose RTSS if you can see uneven pacing, need precise per-game control, or want detailed monitoring.
- Choose NVIDIA Max Frame Rate if you want a simple driver-level fallback, per-game profiles, or lower power and noise without running RTSS.
- Use no universal ranking when the game uses frame generation, has unusual presentation behavior, or is limited by CPU-side stutter.
The most reliable answer is empirical: select one limiter, cap below the relevant VRR ceiling when appropriate, and compare frame-time and latency behavior in the games you actually play.
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.
