A frame cap is most useful when it is treated as a pacing tool rather than a way to chase the highest FPS number. The priority is to set a cap your PC can sustain during the demanding moments of a game, then pair it correctly with your display’s refresh rate and VRR mode. A stable cap can reduce heat, fan noise, power draw, and frame-time swings while helping G-SYNC Compatible or G-SYNC displays stay inside their variable-refresh range.
For most players in 2026, start with the NVIDIA App or NVIDIA Control Panel’s built-in Max Frame Rate control. Use Nvidia Profile Inspector (NPI) when you need a game-specific profile, need to check for conflicting hidden limiter entries, or are troubleshooting a game that does not honor the normal driver setting. Do not stack multiple limiters unless you are intentionally testing them; the lowest active cap usually wins, but the interaction can create inconsistent pacing.
As an Amazon Associate we earn from qualifying purchases at no extra cost to you.
Our Top Picks
GIGABYTE GeForce RTX 3050 WINDFORCE OC V2 6GStandard7.5 x 4.4 x 0.1 Inches0.88 poundsCheck on Amazon
Top 3 picks at a glance
Quick Recommended Settings
| Setting | Recommended value | Why |
|---|---|---|
| Frame Rate Limiter | Off in NPI unless using it as the only driver cap | Avoids conflicts with NVIDIA Control Panel Max Frame Rate, in-game caps, and external limiters. |
| Frame Rate Limiter V3 | Off / default unless a tested game profile specifically requires it | This is a legacy or profile-level control; forcing it broadly can cause unexpected behavior. |
| NVIDIA Control Panel > Manage 3D settings > Max Frame Rate | Refresh rate minus 3 FPS with G-SYNC and V-Sync enabled | Keeps FPS below the V-Sync ceiling so VRR remains active. |
| Vertical sync | On in NVIDIA Control Panel; Off in the game | Prevents tearing above the VRR ceiling while avoiding duplicate in-game sync handling. |
| Low Latency Mode | On; use Ultra only if the game lacks NVIDIA Reflex | Can reduce queued frames, but Reflex should control latency in supported games. |
| Preferred refresh rate | Highest available | Ensures the game uses the intended monitor refresh mode. |
| Power management mode | Normal globally; Prefer maximum performance per game if needed | Per-game use can prevent downclocking without increasing idle power system-wide. |
Setting-by-Setting
Frame Rate Limiter: Off in Nvidia Profile Inspector by default
What causes it: NPI exposes the driver profile setting named Frame Rate Limiter. It may be tempting to set this first, but a cap can also come from the game, NVIDIA Control Panel, NVIDIA App, RTSS, Steam launch options, or an existing imported profile.
How to check: Open Nvidia Profile Inspector, select the game profile from the drop-down list near the top, and use the search field to find Frame Rate Limiter. Then open NVIDIA Control Panel and check Manage 3D settings > Program Settings > [your game] > Max Frame Rate. Also inspect the game’s Video, Graphics, or Display menu for an FPS limit.
What to do: Leave NPI’s Frame Rate Limiter at its default or Off state unless it is the only limiter you plan to use. Set the actual cap in NVIDIA Control Panel’s Max Frame Rate field: select the game under Program Settings, turn Max Frame Rate to On, and enter a whole-number value from 20 to 1000 FPS. For a 144 Hz VRR display, begin at 141 FPS; for 165 Hz, use 162 FPS; for 240 Hz, use 237 FPS.
How to undo: In NVIDIA Control Panel, set Max Frame Rate to Off or click Restore for that program. In NPI, choose the changed setting and return it to the profile default, then click Apply changes in the upper-right area.
Frame Rate Limiter V3: Leave at default unless troubleshooting a specific profile
What causes it: Some NPI versions show a second entry called Frame Rate Limiter V3, sometimes alongside related state entries. These controls exist in driver profiles and can be carried over from imported profiles, optimization packs, or old game tweaks.
How to check: In the selected game profile, search for Frame Rate Limiter V3. If it is not at the profile default, note the current value before changing anything. Use NPI’s export function to save a backup: click the small export icon or use Profiles > Export user defined profiles, depending on the version.
What to do: Do not enable or force V3 globally. Reset it to default and use the standard Max Frame Rate control instead. If an established, game-specific troubleshooting procedure requires V3, use only the specified value for that one executable and test it against the game’s internal cap. Verify frame pacing with a consistent test area rather than a menu screen.
How to undo: Return V3 to its prior recorded value or reset the game profile. In NPI, select the profile and use Profiles > Restore current profile if available. If you exported first, import the backup file through Profiles > Import profiles.
Max Frame Rate: Refresh rate minus 3 FPS for G-SYNC or G-SYNC Compatible
What causes it: When FPS reaches or exceeds the display refresh ceiling, VRR can stop operating and ordinary V-Sync behavior takes over. That can add latency or cause uneven feel during brief spikes.
How to check: Confirm the monitor’s active refresh rate in Windows Settings > System > Display > Advanced display. Then open NVIDIA Control Panel > Display > Set up G-SYNC and confirm G-SYNC or G-SYNC Compatible is enabled for the correct monitor. For a laptop, verify whether the internal panel or external display is selected.
What to do: Set a cap three FPS below the active refresh rate. Common starting points are 57 for 60 Hz, 72 for 75 Hz, 117 for 120 Hz, 141 for 144 Hz, 162 for 165 Hz, 237 for 240 Hz, and 357 for 360 Hz. Set it per game in NVIDIA Control Panel > Manage 3D settings > Program Settings, not globally, when different games need different targets.
How to undo: Turn Max Frame Rate Off for the program. If you are not using VRR, choose a cap based on what your hardware can sustain instead of using the minus-three rule.
Vertical sync: On in the driver, Off in the game
What causes it: A VRR setup without a ceiling safeguard can tear if FPS rises past monitor refresh. Enabling V-Sync in both the driver and the game can create confusing troubleshooting results because the game may apply its own frame queue or presentation behavior.
How to check: In NVIDIA Control Panel, open Manage 3D settings > Program Settings, select the game, and locate Vertical sync. In the game, find its V-Sync toggle. Also confirm that Windows is not accidentally using a lower refresh rate.
What to do: With G-SYNC enabled, set NVIDIA Control Panel Vertical sync to On for the game and turn the game’s V-Sync option Off. Keep the driver cap below refresh. If the game offers NVIDIA Reflex, enable Reflex in-game; do not depend on driver Low Latency Mode to replace it.
How to undo: Set driver Vertical sync back to Use the 3D application setting and restore the game’s original V-Sync choice. For non-VRR displays, test V-Sync On versus Off based on whether tearing or latency is your bigger concern.
Low Latency Mode: On, not Ultra, when Reflex is unavailable
What causes it: A GPU-bound game can queue frames ahead of rendering. That helps throughput in some cases but can increase input delay. Driver-level Low Latency Mode adjusts this queue behavior.
How to check: Look in the game’s graphics settings for NVIDIA Reflex Low Latency. If Reflex is available, it is normally the preferred control. In NVIDIA Control Panel, find Low Latency Mode under the game’s Program Settings.
What to do: For games without Reflex, set Low Latency Mode to On and test. Use Ultra only when testing shows better responsiveness without stutter; it can be counterproductive in CPU-limited games. If Reflex exists, set Reflex to On or On + Boost when appropriate and leave the driver setting at Off or the application default.
How to undo: Set Low Latency Mode to Off or Use the 3D application setting. Disable Reflex in the game if you need to return to its default behavior.
By Hardware Tier
Low-end hardware: Cap for consistency, not panel refresh
What causes it: Entry-level GPUs and older CPUs often produce large frame-time spikes when a game runs uncapped. A 144 Hz monitor does not mean the system should target 141 FPS.
How to check: Play a demanding area for several minutes and watch whether FPS repeatedly falls below your chosen cap. Use the game’s built-in performance overlay or the NVIDIA overlay if available.
What to do: Choose a cap slightly below the lowest FPS you can maintain in typical demanding gameplay. Practical starting points are 30, 40, 45, 50, or 60 FPS. Use the in-game limiter first if it is stable; otherwise use NVIDIA Control Panel Max Frame Rate. Avoid forcing NPI V3 settings.
How to undo: Raise the cap in 5 FPS increments or disable it. If stutter returns, restore the last stable value.
Midrange hardware: Use a sustainable VRR cap
What causes it: Midrange systems can often exceed their target in light scenes but dip heavily in combat, cities, or ray-traced sections.
How to check: Test the busiest gameplay segment, not a benchmark average or opening scene. If the cap is rarely reached, it is too ambitious.
What to do: For a 144 Hz or 165 Hz monitor, use 141 or 162 FPS only if the game can hold close to that level. Otherwise use a stable intermediate cap such as 90, 100, 117, or 120 FPS. Keep driver V-Sync On with VRR and the in-game V-Sync setting Off.
How to undo: Restore Max Frame Rate to Off, or move to a lower cap if demanding scenes still miss the target.
High-end hardware: Preserve VRR headroom and control heat
What causes it: Powerful GPUs can render far beyond refresh rate in older games, esports titles, menus, and loading scenes. Uncapped rendering can waste power and make fans ramp unnecessarily.
How to check: Watch GPU utilization, temperatures, and FPS in a repeatable gameplay area. If FPS is far above display refresh, a cap is worthwhile even when performance feels fine.
What to do: Use refresh-minus-three caps for VRR: 237 at 240 Hz, 357 at 360 Hz, or 477 at 480 Hz. For competitive games, test whether a higher cap above refresh is intentionally desired; if so, disable driver V-Sync and understand that tearing may occur.
How to undo: Disable Max Frame Rate for that game, then restore V-Sync to the application setting if you are changing to an uncapped competitive configuration.
Common Mistakes
What causes it: The most common error is running an in-game limiter, NVIDIA Control Panel Max Frame Rate, RTSS, and an NPI limiter simultaneously. Another is editing the global profile instead of the game profile.
How to check: Search the game profile in NPI, check Program Settings in NVIDIA Control Panel, inspect the game menu, and close external tuning tools one at a time. Make sure the executable selected in Program Settings matches the actual game .exe, not a launcher.
What to do: Use one limiter. Prefer the game’s limiter if it produces stable pacing; otherwise use NVIDIA Control Panel Max Frame Rate. Reserve NPI for examining and resetting profile overrides. Keep a backup before importing .nip profile files. NPI settings are stored in the NVIDIA driver profile database rather than a simple game config file; do not manually edit files under C:\ProgramData\NVIDIA Corporation\Drs while the driver is active.
How to undo: Reset the individual game profile in NVIDIA Control Panel or NPI, reboot, and rebuild the configuration with one cap source.
FAQ
Should I use Nvidia Profile Inspector or NVIDIA Control Panel for a frame cap?
Use NVIDIA Control Panel’s Max Frame Rate for normal per-game caps. Use NPI to inspect hidden profile settings, remove unwanted limiter overrides, or back up a profile before testing. Do not enable both NPI Frame Rate Limiter and Control Panel Max Frame Rate for the same game.
What frame cap should I use for a 144 Hz G-SYNC monitor?
Start at 141 FPS. Enable G-SYNC in NVIDIA Control Panel, set Vertical sync to On in the driver for that game, turn in-game V-Sync Off, and set Max Frame Rate to 141. If the game cannot sustain 141 FPS, choose a lower stable target such as 117, 100, or 90 FPS.
Why is my FPS stuck below the number I entered?
Another limiter is likely active, or the system cannot sustain the requested cap. Check the game’s FPS limit, RTSS, NVIDIA Control Panel Program Settings, battery-saving modes on laptops, and any NPI Frame Rate Limiter or Frame Rate Limiter V3 override. Disable all but one limiter, then retest.
Where are Nvidia Profile Inspector settings saved?
NPI writes changes into NVIDIA’s driver profile database. The relevant data is typically under C:\ProgramData\NVIDIA Corporation\Drs, including files such as nvdrsdb0.bin and nvdrsdb1.bin. Do not edit those files manually. Export a .nip backup from NPI before changing profile flags, and use NPI’s import or restore options to revert safely.
