144Hz Monitor Frame Pacing Test: How to Check Smoothness

Part of our guide on triple buffering on or off for gaming

A monitor running at 144Hz can still stutter badly if frames arrive unevenly, and average FPS alone will never show you that problem.

What you need

You need frame time capture software, a game that pushes your GPU, and a way to confirm your monitor is actually running at 144Hz. Most players skip that last check and test a monitor stuck at 60Hz without knowing it.

The tools are free. CapFrameX works on any Windows 10 or 11 PC with .NET 6 installed. FrameView needs an Nvidia or AMD card. Both log frame times to a file you can review after the match.

• CapFrameX or FrameView – free frame time loggers that run in the background
• A game you actually play – testing in a menu or benchmark loop hides real-world pacing issues
• Windows display settings open – to confirm 144Hz is active before you start
• A typical match or round – 2 to 3 minutes of normal gameplay, not a stress test

How to confirm monitor is running at 144Hz

Open Windows display settings by right-clicking the desktop. Click Advanced display and look at the refresh rate dropdown. It should show 144Hz as the active setting. If it shows 60Hz, your monitor is not running at the speed you think it is.

Change it to 144Hz, click Apply, and test again. The monitor needs a DisplayPort or HDMI 2.0 cable to hit 144Hz. An old HDMI 1.4 cable caps you at 60Hz no matter what the settings say. We cover cpu hitting 100 percent lowers polling rate in its own article.

Online tools like testufo.com/refreshrate show a moving pattern that looks smooth at high refresh rates and choppy at low ones. Run it after changing the setting to confirm the change took effect. The UFO should glide across the screen without visible steps.

Which tools to use for frame pacing measurements

CapFrameX and FrameView are the two free tools that log frame times during gameplay. CapFrameX uses PresentMon under the hood and works with any GPU. FrameView comes from Nvidia but also supports AMD cards. Both write a CSV file with the timestamp of every frame.

CapFrameX shows a live overlay with frame time and percentiles while you play. FrameView runs quieter and logs in the background. Pick CapFrameX if you want to see results immediately. Pick FrameView if you want to record a session and review it later without distraction. The other half of this decision is identifying udp loss impact.

Download CapFrameX from GitHub or FrameView from Nvidia's site. Install it, launch it before the game starts, and hit the hotkey to begin logging. Both tools default to F11 for start and stop. Avoid MSI Afterburner's frame time graph: it samples too slowly and misses the spikes that cause stutter.

• CapFrameX – live overlay, detailed percentile stats, works with Intel, Nvidia and AMD, outputs CSV
• FrameView – background logging, cleaner in-game, Nvidia and AMD support, also outputs CSV
• PresentMon – command-line only, no GUI, but the engine behind CapFrameX if you want raw logs
• Not MSI Afterburner – its frame time graph updates too slowly and hides the 1% spikes

Run the test: capture frame times in a real match

Launch CapFrameX or FrameView, then start your game. Load into a match or a busy area, not the main menu. Menu frame rates are capped or unlocked in ways that do not match gameplay, so the data will be useless.

Play normally for 2 to 3 minutes. Do not stand still. Move, aim, and engage the way you would in a real fight. Frame pacing issues show up under load, not when you are staring at a wall. There is more on 64 tick server delay compared to faceit in a separate guide.

Press the logging hotkey to start, play the round, then press it again to stop. The tool writes a file to its log folder. Do not close the game yet: run a second test with V-Sync or G-Sync toggled to compare before and after.

1. Launch CapFrameX or FrameView before opening the game.
2. Start the game and load into a match or a populated area, not the menu.
3. Press F11 (or your chosen hotkey) to begin logging frame times.
4. Play normally for 2 to 3 minutes, moving and shooting as usual.
5. Press F11 again to stop logging. The tool saves a CSV file automatically.
6. Toggle V-Sync, G-Sync or FreeSync in the game settings and repeat the test.
7. Exit the game and open the CSV files to compare the results.

How to interpret frame time graphs or frame intervals

At 144Hz, each frame should arrive every 6.94ms. Open the CSV in Excel or import it into CapFrameX's analysis tab. Look at the frame time column. If most values sit between 6ms and 8ms with only rare spikes, pacing is smooth.

Jitter is the variation between frames. Calculate the standard deviation or just eyeball the range. If frame times swing from 5ms to 12ms constantly, that is uneven pacing. A spike above 10ms now and then is fine. A spike every few frames is stutter. People in this spot often ask about free-to-play tank games as well.

CapFrameX shows percentiles: 1% low and 0.1% low. These are the worst frame times in the session. If the 1% low is 15ms or higher, you will feel hitching even if average FPS is 140. That is the signature of bad pacing, not low performance.

What uneven pacing looks like and its impact on gaming

Uneven pacing feels like micro-stutter: the image jumps or hesitates for a frame, then continues. Your FPS counter shows 144, but the game does not feel smooth. That disconnect happens because the interval between frames keeps changing.

On the graph, you will see a sawtooth pattern or random spikes instead of a flat line. In-game, it shows up when you turn quickly or track a moving target. The crosshair does not glide: it stutters. That ruins aim in shooters and makes racing games feel jerky. Before you commit to anything, it is worth looking at how to enable raw input buffer.

The most common causes are V-Sync forcing frame delivery out of step with the GPU, background tasks interrupting the render thread, or a monitor that reports 144Hz but is fed 60Hz frames. The test shows which one. If toggling V-Sync flattens the graph, sync was the problem. If the spikes remain, check your cable and Windows refresh rate setting again.

Common mistakes when testing frame pacing

Testing in the main menu or a benchmark loop gives you pacing data that does not match real gameplay. Menus often unlock the frame rate or cap it differently. Benchmarks repeat the same scene, which hides hitching that only appears under varied load.

Another mistake is testing with FPS capped at 144 by the game's limiter, then blaming the monitor. In-game limiters add their own timing jitter. Test with the limiter off or use RTSS to cap frames instead: it delivers smoother pacing than most built-in options.

Recording too short a session (30 seconds or less) misses the spikes that happen once or twice a minute. Run the test for at least 2 minutes to capture the outliers. Those are the frames that ruin smoothness.

• Testing in the menu instead of gameplay – menus have different frame delivery and do not show real pacing issues
• Using the in-game FPS limiter at 144 – most built-in limiters add jitter; use RTSS or test uncapped
• Logging for under a minute – short tests miss the occasional spikes that cause noticeable stutter
• Ignoring the 1% and 0.1% lows – average frame time hides the worst outliers that you actually feel
• Not toggling V-Sync or G-Sync – you need a before-and-after comparison to know if sync tech helps or hurts

Questions people still ask

I have tested frame pacing on three different 144Hz panels, and the difference between a clean 6.94ms line and a jittery 5-12ms sawtooth is night and day: even when average FPS stays the same.