Recommended Free Tools
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
If a game reports 100 FPS but camera movement still looks jerky, the average is not telling the whole story. FPS measures how many frames are produced on average; frame pacing describes how regularly those frames are delivered. A steady stream of frames usually looks smoother than a higher but erratic frame rate. To diagnose uneven motion, look at frame times and presentation—not just the FPS counter.
Frame pacing, in plain English
A frame is one rendered image in a game’s moving picture. The game updates its simulation, the CPU prepares work, the GPU renders an image, and the system submits it for presentation. The display then refreshes or scans that image. Each stage takes time, and frames do not always reach the screen at perfectly even intervals.
Frame pacing is the regularity and timing of that delivery. At a steady 60 FPS, frames arrive about 16.67 milliseconds apart. If delivery alternates between short and long intervals, motion can look uneven even if the average still works out to roughly 60 FPS. Epic’s performance-profiling documentation treats FPS and frame time as complementary: FPS gives a rate, while frame time helps show how long each frame takes.
FPS, frame time and refresh rate
FPS (frames per second) is a rate. Frame time is the time associated with producing a frame. Their simple average relationship is:
#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.
Frame time in milliseconds = 1,000 ÷ FPS
| Average FPS | Approximate frame time |
|---|---|
| 30 | 33.33 ms |
| 60 | 16.67 ms |
| 90 | 11.11 ms |
| 120 | 8.33 ms |
| 144 | 6.94 ms |
| 165 | 6.06 ms |
| 240 | 4.17 ms |
These are mathematical averages, not a promise that every frame—or every displayed image—will arrive at exactly that interval. A monitor’s refresh rate is another related but different number: it describes how often the display can update. A 144 Hz display does not make a game render at 144 FPS, and a game’s FPS counter does not necessarily show the exact cadence the display presents.
That distinction matters on PCs in particular. A counter may report frames rendered or submitted by the game, while presentation timing can be affected by buffering, synchronization, missed refresh deadlines and Windows’ display path. Microsoft’s DXGI frame statistics documentation distinguishes presentation calls from images actually presented.
How uneven frame times feel
Compare these illustrative patterns:
- Consistent 60 FPS: frames arrive about every 16.67 ms. Camera motion generally looks even.
- Uneven 60 FPS average: intervals alternate, for example, between 10 ms and 23 ms. The average can be similar, but movement may look lumpy.
- High average with spikes: a game runs quickly much of the time, then has occasional 20–40 ms frames. Those pauses can be more noticeable than the average suggests.
These examples are not universal perceptual thresholds. Whether a variation is noticeable depends on its size, frequency, scene motion, refresh rate, synchronization, and the viewer. Research on variable frame timing has found that people can perceive smoothness differences, while equally rated sequences did not necessarily produce different first-person-shooter task performance. Smoothness, responsiveness and gameplay performance overlap, but they are not the same thing (study).
Free tools Windows power users keep installed
One-click scans. No signup required.
Reading a frame-time graph
A frame-time graph plots the duration of frames over time. A relatively steady line suggests consistent rendering intervals. Tall, isolated spikes point to a hitch or sudden delay. Repeating rises and falls can reveal an alternating or rhythmic cadence. A graph can look steady while the image tears, because a graph of render timing does not itself prove that presentation was synchronized.
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
Average FPS can hide short disruptions. “1% lows” and other percentile FPS figures help summarize slower frames, but they do not show the shape of the problem: one large spike, many smaller delays, and a repeating pattern can produce similar summary figures. Use percentiles to compare runs, then inspect a frame-time plot to understand what happened.
Stutter, hitching, judder and tearing are different
| Term | What you see | Common explanation |
|---|---|---|
| Stutter | Motion pauses or jumps unevenly. | Frames are delayed or delivered inconsistently. |
| Hitch | A brief, noticeable interruption. | Often a sudden long frame, such as during shader work or asset loading. |
| Judder | Motion has an uneven cadence, sometimes in a repeating pattern. | Frame-rate conversion, refresh mismatch or repeated-frame timing. |
| Tearing | A horizontal split shows parts of different frames at once. | Presentation is not synchronized with the display’s scan. |
| Low FPS | Motion updates infrequently. | The system produces few frames; delivery can still be consistent. |
| Input lag | Visible response trails the input. | Delay anywhere from input sampling through rendering and display. |
These symptoms can coexist, but they are not interchangeable. A tear is not proof of bad frame pacing; a stable frame-time graph does not rule out input lag or a display-side motion problem.
Why high FPS can still feel bad
Frame pacing is an outcome of several parts of the system, not a single graphics setting. Uneven delivery can come from:
- CPU work that takes longer on some frames, or CPU/GPU synchronization and scheduling.
- GPU saturation or occasional rendering spikes.
- Shader compilation or pipeline-cache misses.
- Asset streaming, especially while traversing into new areas.
- Background applications, overlays, recording or other competing work.
- Thermal or power limits that change performance during play.
- A game, driver or external frame limiter that produces uneven intervals.
- Interactions among a limiter, V-Sync, VRR and latency features.
- Refresh-rate mismatch, frame-generation behavior, or different caps in menus and gameplay.
Lowering graphics settings helps when rendering load is the cause, but may do little for shader compilation, CPU limits, streaming or an incorrect display configuration. Likewise, a faster monitor or a synchronization toggle cannot repair every engine-level stall.
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.
What V-Sync does—and what it cannot do
Conventional V-Sync synchronizes frame presentation with the display’s refresh cycle, reducing or preventing tearing. When a game can meet the display’s timing consistently, it can also produce a regular presentation cadence. But if a frame misses its deadline, the previous image may remain for another refresh interval, creating a visible cadence change. Buffering and implementation also affect input latency.
V-Sync does not automatically fix long CPU or GPU frames, shader compilation, asset-streaming hitches or irregular game-engine timing. Unreal Engine’s frame-rate smoothing documentation describes how missing refresh targets can produce abrupt transitions between presentation opportunities. Treat V-Sync as a presentation choice with trade-offs, not as a universal frame-pacing repair.
VRR: G-SYNC, FreeSync and Adaptive-Sync
Variable refresh rate (VRR) lets a compatible display adjust its refresh timing to follow frame delivery within a supported range. Adaptive-Sync is a standards-based VRR mechanism; FreeSync is AMD’s branding and certification ecosystem; G-SYNC is NVIDIA’s branding, with G-SYNC Compatible displays validated for VRR operation with NVIDIA GPUs. The names describe related approaches, not a guarantee that every display, GPU, cable and port combination behaves identically.
Within its operating range, VRR can reduce tearing and make changes in frame delivery less conspicuous. It cannot make a game render faster or remove a CPU stall, shader hitch or asset-streaming delay. Check the display’s minimum and maximum VRR rates: if the game falls below the range, Low Framerate Compensation (LFC), when supported, can repeat frames so the display refreshes within range. AMD gives the example of a 40 FPS game on a 60–144 Hz display being shown with doubled frames at 80 Hz (FreeSync overview).
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.
If FPS rises above the display’s maximum refresh rate, tearing can return unless a cap or synchronization method prevents it. Laptop, console, connection type, resolution, HDR mode, driver and monitor settings all affect which VRR features are available. “FreeSync” on a display does not by itself guarantee the same behavior across every GPU and connection.
Choosing a frame-rate target and cap
A stable lower target can be preferable when the system cannot sustain a higher one without frequent spikes. A higher target can be worthwhile when the hardware sustains it, the display supports the rate, and responsiveness is a priority. Higher FPS shortens average frame time, but does not automatically halve all latency or double perceived smoothness; input sampling, queueing, synchronization and display behavior also matter.
On a VRR display, a cap slightly below the maximum refresh rate is a useful starting point if the game often exceeds that ceiling. It is a test, not a universal formula: the best cap depends on the VRR range, game limiter, workload, frame generation and latency features. If several limits are active, the most restrictive one may govern. NVIDIA documents using its Max Frame Rate setting to stay within a G-SYNC range (NVIDIA guidance).
| Limiter or setting | Possible advantage | Trade-off to test |
|---|---|---|
| In-game FPS cap | Simple, and sometimes integrated with the engine. | Quality and availability vary by game. |
| Driver FPS cap | Can be set per game in a driver profile. | Behavior varies by driver and presentation path. |
| External limiter | Can help where a game lacks a suitable cap. | Adds another layer; compatibility and interaction need checking. |
| V-Sync | Reduces tearing at the display ceiling. | Missed deadlines and buffering can affect cadence and latency. |
| Reflex or a similar supported latency feature | Can manage queueing in supported games. | Availability and behavior depend on the game and hardware. |
For a fixed-refresh display, V-Sync is an option if tearing is unacceptable. If the game cannot hold the refresh target, a stable lower cap may look better than fluctuating around it. If latency takes priority, testing without V-Sync may be reasonable, with tearing as a possible cost. For VRR, enable the feature on both the display and GPU where supported, then test the game’s cap and synchronization behavior rather than assuming one setting combination fits every title.
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 practical troubleshooting sequence
- Confirm the display mode. Check that Windows or the console is set to the intended resolution and refresh rate. A high-refresh display running at a lower setting cannot show its full refresh capability.
- Identify the symptom. Look for tearing, a single hitch, repeated uneven motion or delayed input; do not treat them as the same fault.
- Check caps and sync. Look for an in-game cap, driver cap and V-Sync setting. Multiple active limits can make FPS appear locked to a common refresh-related value.
- Enable VRR correctly if supported. Check the monitor’s on-screen menu, the GPU control panel, the selected display and the connection. Confirm the game’s FPS is within the display’s VRR range.
- Try a sensible cap. On VRR, test a cap below the maximum refresh if FPS regularly exceeds it. Compare the game’s limiter with a driver limiter rather than stacking them blindly.
- Inspect CPU and GPU timing. If tools expose separate CPU and GPU frame times, see which one spikes. Lower settings that create GPU spikes; a CPU bottleneck may call for different changes.
- Look for repeatable triggers. If hitches happen when entering new areas or effects first appear, shader compilation or asset streaming may be involved. Let caches warm, then replay the same section.
- Reduce testing noise. Temporarily close recording tools, overlays and unnecessary background applications to see whether the pattern changes.
- Change one thing at a time. Replay the same route or benchmark segment and compare the frame-time graph, average, low-percentile behavior and visible motion.
Quick checks for common problems
- FPS stuck at 60: check V-Sync, in-game and driver caps, the operating system’s refresh setting, and any power-saving or capture profile. A fixed number alone does not identify which limit is active.
- VRR enabled but tearing remains: check whether FPS is above the display’s ceiling or outside its VRR range, whether VRR is enabled for the correct screen, and whether the selected port, cable, resolution or display preset supports the feature.
- Flat graph but motion still feels wrong: the graph may describe rendered frames rather than displayed timing. Input delay, animation cadence, monitor response or VRR flicker can also affect the experience.
- Lower settings did not help: investigate CPU work, shader or traversal hitches, streaming, background tasks, frame limiting and display configuration before assuming the GPU is the cause.
Measuring frame pacing reliably
- Use a built-in frame-time graph when the game provides one.
- Choose a repeatable gameplay route, benchmark or scene.
- Record average FPS, frame times, percentile FPS and visible spikes.
- Change one setting, then repeat the same section.
- Repeat once caches and assets have warmed, if the first run stutters during loading or traversal.
- Where possible, compare render timing with present or display timing.
NVIDIA FrameView is an official free measurement and benchmarking utility. It reports average and percentile FPS and provides timing data; its user guide notes that overlay support varies by graphics API, although capture may still be possible when the overlay is unavailable. If its overlay does not appear, check the game/API and inspect captured data instead. A fixed FPS reading can also result from V-Sync or a game cap.
For developers, Microsoft’s DXGI frame statistics and flip-model documentation explain presentation timing and why reported render activity may not equal displayed cadence. Fullscreen and borderless behavior is not universally better in one mode; the game, graphics API, Windows presentation path and swap-chain mode matter.
Frame generation and platform differences
Frame generation can make motion appear smoother by inserting generated images between base rendered frames. It does not make the game’s simulation or input sampling run at the generated display rate. Generated frames may add processing delay or visual artifacts, so a high displayed FPS is not proof of equivalent native responsiveness. Use tools that distinguish base-rendered and generated or displayed frames where available.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Consoles and laptops expose fewer or different controls than a desktop PC. A console game’s performance modes and display VRR support depend on the console, game, display and connection. On laptops, power mode, thermal limits, internal-display routing and external monitor support can affect frame delivery. Diagnose what the platform exposes instead of assuming desktop control-panel options are available.
For game developers: pacing happens at multiple layers
Frame pacing can be influenced by the simulation loop, CPU/GPU synchronization, render submission, swap-chain presentation, driver queueing and display synchronization. Unreal Engine provides frame-rate smoothing and platform frame-pacing functionality; its documentation cautions that broad smoothing ranges can interact poorly with V-Sync or refresh constraints (frame pacer API; smoothing guidance). Its advanced low-latency synchronization features are engine-level tools, not universal end-user fixes (Unreal documentation).
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.
