How to Cap Your Frame Rate to Stop Micro-Stutter on a High-Refresh Monitor (September 2026)

Your game says 240 FPS. Your monitor is a 240Hz panel. So why does the picture still feel choppy? I have been chasing this exact problem for years across competitive shooters and cinematic single-player titles, and I can tell you the FPS counter is lying to you.

The real culprit is something called frame pacing. When your GPU pushes frames faster than your monitor can display them, the delivery becomes uneven, and your eyes pick that up as micro-stutter. The fix is almost always the same: cap your frame rate 2-3 FPS below your monitor’s maximum refresh rate. In this guide, I will walk you through exactly how to do that, why it works, and what to do when the simple cap is not enough.

This is the resource I wish I had when I first built my 165Hz rig and could not figure out why my Valorant matches felt jittery despite perfect FPS readings. By the end, you will know how to lock in tear-free, buttery smooth motion on any 144Hz, 165Hz, 240Hz, or 360Hz display.

Why High FPS Can Still Stutter on a High-Refresh Monitor?

Here is the paradox that trips up almost every PC gamer at some point: you bought a 144Hz monitor, you upgraded your GPU, you crank up the settings, and your FPS counter shows 200+. Yet the game still feels choppy. Frame times, not average FPS, are what your eyes and brain actually perceive.

Frame Pacing 101

Frame pacing refers to how evenly your GPU delivers each frame to the monitor. A consistent 16.67ms interval between frames feels smooth at 60Hz. A consistent 6.94ms interval feels smooth at 144Hz. But if some frames arrive at 4ms and others at 12ms, your brain registers that as judder, even if the average works out to a high number.

I learned this the hard way running Cyberpunk 2077 on a pre-overclock RTX 3070. The benchmark said 138 FPS average, but every few seconds I would feel a small hitch. After enabling a frame cap, the hitch disappeared because the GPU was no longer swinging between idle and full load.

The Refresh Ceiling Problem

Your monitor can only refresh a fixed number of times per second. A 144Hz panel redraws every 6.94ms, no matter what. When your GPU outputs 200 FPS, half of those frames arrive at the wrong time and have nowhere to go.

Variable refresh rate (VRR) technologies like G-Sync and FreeSync exist to handle this exact mismatch. But VRR only works properly when FPS stays within the monitor’s supported range. Push past the upper limit and you reintroduce stutter, often worse than without VRR at all.

What 1% Lows Tell You

The 1% low metric represents the slowest 1% of frames in your session. If your average is 200 FPS but your 1% low is 45 FPS, you have a serious frame pacing problem. Tools like MSI Afterburner with RTSS overlay can show you both numbers in real time.

When I started monitoring 1% lows, I finally understood why some games felt worse than others despite similar averages. A game with 180 average and 110 1% low feels better than one with 220 average and 60 1% low. Capping your FPS eliminates the swings that drag those lows down.

What Is Micro-Stutter and How Does Frame Pacing Cause It

Micro-stutter is the perception of small, irregular pauses in motion, typically lasting a few milliseconds each, that occur too quickly to read as a dropped frame but slowly enough to break the illusion of smooth motion. Most gamers describe it as the game feeling “off” or “floaty” without being able to pinpoint why.

The root cause is almost always inconsistent frame delivery. Your monitor expects a frame every 6.94ms on a 144Hz display. If frame one arrives at 4ms, frame two at 12ms, and frame three at 5ms, you have visible judder even though your GPU is working overtime.

I have tested this with frame time graphs dozens of times using CapFrameX and PresentMon. The graphs tell a clear story: uncapped FPS produces a spiky, chaotic pattern. Capped FPS produces a tight, uniform line. Your eyes can absolutely tell the difference.

The FPS counter in your game only shows averages. It cannot represent how those frames are spaced. Two players can both report 180 FPS and have completely different experiences based solely on frame pacing quality.

The Core Fix: Cap FPS 2-3 Below Your Monitor’s Refresh Rate

If you take only one thing from this entire guide, make it this: set your FPS cap 2-3 frames below your monitor’s maximum refresh rate. On a 144Hz monitor, that means 141 or 142 FPS. On a 240Hz monitor, cap at 237 or 238 FPS. This single change solves micro-stutter for the vast majority of gamers.

Why the 2-3 Buffer Matters

That small buffer keeps your FPS firmly inside your monitor’s VRR window. The cap acts as a safety margin against momentary frame spikes that would otherwise push you above the ceiling and out of adaptive sync range.

Without the buffer, you might run at 142 FPS on average but spike to 146 during a less demanding scene. That spike exits the VRR range and triggers stutter. With a 141 cap, even worst-case spikes stay within the adaptive sync envelope.

How the Formula Works

The formula is simple: monitor refresh rate minus 2 or 3. This applies whether you are running a 144Hz, 165Hz, 240Hz, or 360Hz panel. I have validated this formula across gaming forums like Blur Busters, Reddit’s r/MotionClarity, and r/OptimizedGaming, and the consensus is unanimous.

If your monitor supports a wider VRR range, you can sometimes push the cap a bit higher. But starting with minus 3 is the safest baseline that works on every display I have tested.

FPS Cap Reference Table for Common Refresh Rates

Use this table as your quick reference. These are the values I run on my own rigs and recommend to friends.

• 60Hz monitor: 57 FPS cap

• 75Hz monitor: 72 FPS cap

• 120Hz monitor: 117 FPS cap

• 144Hz monitor: 141 or 142 FPS cap

• 165Hz monitor: 162 or 163 FPS cap

• 180Hz monitor: 177 FPS cap

• 240Hz monitor: 237 or 238 FPS cap

• 270Hz monitor: 267 FPS cap

• 360Hz monitor: 357 or 358 FPS cap

• 390Hz monitor: 387 FPS cap

• 500Hz monitor: 497 FPS cap

Notice the pattern: each cap is exactly 2-3 FPS below the panel’s native refresh. This is the formula that the competitive gaming community has settled on after years of testing.

If you have a newer OLED panel with extended VRR ranges (like 48-240Hz), you can sometimes set the cap at the maximum and still get smooth performance. But for traditional high-refresh displays, the formula above is your safest bet.

How to Set the FPS Cap: Step-by-Step Methods

There are four reliable ways to cap your frame rate, each with pros and cons. I will walk you through every method so you can pick the one that fits your setup.

Method 1: RivaTuner Statistics Server (RTSS) via MSI Afterburner

RTSS is the gold standard for frame limiting because it works at the driver level and produces the most stable frame pacing of any method available. Most esports professionals use RTSS as their primary cap.

1. Download MSI Afterburner from the official Guru3D website and install it.

2. During installation, ensure RivaTuner Statistics Server is also installed.

3. Launch MSI Afterburner, then click the settings gear icon.

4. Go to the “RivaTuner Statistics Server” tab on the left.

5. Find your game’s executable in the list, or add it using the search button.

6. Set “Framerate limit” to your target cap (141 for 144Hz, 237 for 240Hz, etc.).

7. Click OK and launch your game.

The RTSS overlay also gives you frame time graphs and 1% low readings, which are invaluable for verifying your cap is working correctly. If you only install one tool after reading this guide, make it RTSS.

Method 2: Nvidia Control Panel

If you prefer a built-in option without third-party software, Nvidia’s control panel offers a global frame cap that applies to every 3D application.

1. Right-click on your desktop and select “Nvidia Control Panel.”

2. Navigate to “Manage 3D Settings” on the left sidebar.

3. Click the “Program Settings” tab to customize per-game, or stay on “Global Settings.”

4. Find “Max Frame Rate” in the list.

5. Set it to your target value (141, 237, etc.).

6. Click “Apply” in the bottom right corner.

The Nvidia cap is slightly less precise than RTSS, but it is good enough for most gamers and requires no extra software. I keep this enabled as a backup to RTSS in case I forget to launch Afterburner.

Method 3: AMD Radeon Software

AMD users have an equivalent feature built into Radeon Software, with the bonus of per-game profiles.

1. Right-click your desktop and open “AMD Software” or “Radeon Settings.”

2. Click on the “Gaming” tab.

3. Select “Profiles” and find or create a profile for your game.

4. Look for “Radeon Enhanced Sync” or “Frame Rate Target Control” (FRTC).

5. Enable FRTC and set your target FPS.

6. Save the profile and launch your game.

FRTC works at the driver level similar to Nvidia’s cap. It is reliable and well-integrated with AMD’s ecosystem. The main limitation is that older drivers sometimes had FRTC conflicts with FreeSync, though modern Adrenalin releases handle this cleanly.

Method 4: In-Game Frame Limiter

Many modern games include a built-in FPS cap in their video settings. This is the easiest method but often produces the least stable frame pacing.

1. Launch your game and open its settings menu.

2. Navigate to the video or display section.

3. Look for “Frame Limit,” “Max FPS,” or “FPS Cap.”

4. Set it to your target value.

5. Save settings and restart the game if required.

In-game caps are convenient but inconsistent. Some games limit frames with high accuracy, others have frame time spikes even when capped. I always recommend testing with RTSS first, then comparing results.

Adaptive Sync, G-Sync, and FreeSync: When to Enable With Your Cap

Variable refresh rate technologies are designed to work hand-in-hand with a frame cap. Without VRR, your monitor refreshes at a fixed interval, and any frame timing mismatch shows as tearing or stutter. With VRR, the monitor adjusts its refresh to match your FPS, eliminating those artifacts.

Enable G-Sync (Nvidia) or FreeSync (AMD) in your monitor’s on-screen display first. Then enable it in your GPU driver control panel. This ensures the VRR handshake happens correctly.

VRR Range Explained

Every VRR monitor has a supported range, such as 48-144Hz or 60-240Hz. Your FPS cap must sit within this range for VRR to function. That is why the minus 2-3 formula matters: it keeps your cap inside the safe zone.

Some newer OLED panels offer ranges as wide as 0-240Hz, which gives you more flexibility. But most traditional IPS and VA panels have a narrower range, so check your monitor’s specs before assuming VRR is helping.

The V-Sync Question

With VRR enabled, V-Sync should generally be turned off in your GPU driver. Enabling both can introduce input lag and, paradoxically, reintroduce stutter in some scenarios.

However, many competitive players enable V-Sync in their GPU control panel as a hard ceiling to prevent any FPS spikes above the refresh rate. The trade-off is a small amount of input lag for guaranteed tear-free frames. Test both configurations to find what feels best to you.

Low Latency Mode

Nvidia’s “Low Latency Mode” and AMD’s “Anti-Lag” are designed to reduce input lag when using a frame cap. If you have a modern GPU, enable these features along with your VRR and cap for the best experience.

I run Low Latency Mode “On” in every competitive game, and the difference in responsiveness is noticeable compared to the default “Off” state. It is a free improvement that pairs perfectly with the frame cap strategy.

Additional Fixes: Windows Settings, Game Mode, and Background Apps

Capping your FPS solves most micro-stutter, but if you are still seeing hitches, the next layer to check is Windows itself. I have seen games go from stuttery to flawless just by tweaking a few power and background settings.

Power Plan Settings

Windows default power plans often throttle CPU and GPU performance to save energy. Switch to the “Ultimate Performance” or “High Performance” plan to keep your hardware running at full speed.

1. Press Win + R and type “powercfg.cpl” then press Enter.

2. Click “Show additional plans” if available.

3. Select “Ultimate Performance” or “High Performance.”

4. Close the window and restart your game.

If “Ultimate Performance” is missing, open Command Prompt as Administrator and run “powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61” to unlock it.

Game Mode Toggle

Windows Game Mode prioritizes resources for your active game and suppresses background tasks. In my testing, it provides a small but consistent frame pacing improvement.

1. Press Win + I to open Settings.

2. Go to “Gaming” then “Game Mode.”

3. Toggle “Game Mode” to On.

Game Mode is not magic, and some games benefit more than others. But with everything else in this guide applied, it adds another layer of stability to your frame delivery.

Closing Overlays and Background Apps

Discord, GeForce Experience, Xbox Game Bar, browser tabs, and RGB software all consume CPU cycles that could be dedicated to your game. Each of these is a potential source of frame time spikes.

Close anything non-essential before launching a competitive match. I keep only Discord, my audio drivers, and RTSS running. Closing GeForce Experience alone resolved mysterious stutter for one of my friends whose ShadowPlay recordings were causing background CPU load.

If you use RTSS, you can also monitor per-core CPU usage to identify which background process is spiking and causing frame drops. It is one of the most powerful diagnostic features of the tool.

Advanced Troubleshooting: DWM, MPO, and Thermal Throttling

If you have applied every fix above and still experience micro-stutter, the issue is likely deeper in the Windows rendering pipeline. These advanced fixes target the Desktop Window Manager (DWM) and Multi-Plane Overlay (MPO) systems.

DWM Frame Pacing

The Desktop Window Manager is the Windows compositor that combines your game output with the rest of your desktop. DWM bugs can introduce frame pacing issues even when your GPU is delivering frames perfectly.

Some users have reported improvements by disabling certain DWM features through registry edits. This is an advanced tweak and should only be attempted if you are comfortable editing the Windows registry. Always back up your registry before making changes.

MPO Issues

Multi-Plane Overlay (MPO) is a Windows feature designed to reduce GPU load by overlaying multiple surfaces. Unfortunately, MPO has been linked to stuttering and frame pacing issues on certain GPU and monitor combinations, particularly with Nvidia hardware.

You can disable MPO by creating a DWORD value named “OverlayTestMode” set to 5 in the registry path “HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsDWM.” After a reboot, this disables hardware overlays and forces all compositing through the standard path.

I tested MPO disabling on my personal 1440p 165Hz setup and saw a measurable improvement in frame pacing in several games. Your results may vary, but it is a worthwhile experiment if other fixes have failed.

Temperature Checks

Thermal throttling is one of the most overlooked causes of micro-stutter. If your GPU or CPU is hitting 90 degrees under load, performance will fluctuate wildly.

Use HWMonitor or HWiNFO to check your temperatures during gameplay. GPU should stay under 83 degrees and CPU under 85 degrees for sustained performance. If either is higher, consider cleaning your case fans, repasting, or adjusting your fan curve.

I once spent three weeks troubleshooting stutter in a competitive title, only to discover my AIO cooler pump was failing. Replacing it eliminated the issue overnight. Always check the basics before diving into software tweaks.

Common Mistakes to Avoid When Capping Your Frame Rate

Even experienced gamers make these errors. Avoid them and you will save yourself hours of troubleshooting.

Mistake 1: Setting the cap too high. Capping at 144 on a 144Hz monitor defeats the purpose. Always subtract 2-3 FPS to stay within the VRR window. The cap is meant to prevent overshoot, not match the refresh exactly.

Mistake 2: Using the wrong V-Sync combination. Running VRR with V-Sync on in your GPU driver can cause input lag and reintroduce stutter. Start with VRR on, V-Sync off, then experiment with V-Sync on if you still see occasional tearing.

Mistake 3: Forgetting to apply the cap globally. If you cap FPS in one game but not another, your system will have inconsistent frame delivery across your library. Use a global driver-level cap or set RTSS to apply to all applications.

Mistake 4: Ignoring thermals and background processes. A frame cap only works if your hardware can deliver frames consistently. Software conflicts and thermal throttling create frame time spikes that no cap can fully smooth out.

Mistake 5: Trusting the in-game FPS counter alone. The counter shows averages, not consistency. Always verify with frame time graphs from RTSS or CapFrameX to confirm your cap is producing the smooth delivery you expect.

Frequently Asked Questions

Final Thoughts: Lock In Your Frame Rate and Stop the Stutter

Capping your frame rate 2-3 FPS below your monitor’s refresh rate is the single most effective way to stop micro-stutter on a high-refresh monitor. The formula is simple, the tools are free, and the result is tear-free, buttery smooth motion that your hardware was always capable of delivering.

Start with RTSS as your frame limiter, enable G-Sync or FreeSync in your GPU driver, set Windows to High Performance power plan, and close any unnecessary background apps. That combination solves the vast majority of micro-stutter cases. If you are still seeing hitches, dig into thermal monitoring, MPO disabling, and frame time analysis to identify the remaining culprit.

Your eyes can absolutely tell the difference between a smooth 141 FPS and a spiky 200 FPS, even if the FPS counter looks impressive on paper. Take fifteen minutes to apply these fixes, and you will wonder how you ever gamed without them.