1% Lows Explained: Why Average FPS Lies About Smoothness

Average FPS is the most misleading metric in gaming

Two PCs both report 120 FPS average. One feels silky. The other stutters every few seconds. Same number, completely different experience. The difference lives in 1% lows and 0.1% lows, the metrics that actually predict whether gameplay feels smooth.

If you have ever upgraded a part and felt no improvement despite higher average FPS, you almost certainly fixed the average and ignored the lows.

What 1% and 0.1% lows actually measure

During a benchmark run, your PC produces thousands of individual frames. A capture tool sorts them by speed.

• Average FPS: the mean across every frame.
• 1% low: the average of the slowest 1 in 100 frames.
• 0.1% low: the average of the slowest 1 in 1,000 frames.

Those slow frames are the ones you actually feel as stutter. A game running 120 FPS average with 30 FPS 1% lows feels worse than a game running 90 FPS average with 80 FPS 1% lows. The smoother of the two has the higher floor.

Why the floor matters more than the ceiling

Human vision is unforgiving on sudden frame-time spikes. A frame that takes 33 ms when surrounding frames take 8 ms reads as a hitch, even though you only "saw" one bad frame. Your eyes track the discontinuity, not the average.

This is why VRR (G-Sync, FreeSync) helps but does not save a build with bad lows. The display can sync to the slow frame, but the player still perceives it.

Common causes of bad 1% lows

CPU bottleneck

Single-thread starvation in CPU-heavy scenes (busy cities, large player counts) spikes frame times. The fix is a faster CPU, especially one with more L3 cache like AMD's X3D parts.

Insufficient or slow RAM

16 GB systems running out of headroom in 2026 AAA games trigger paging to SSD, which adds 30 to 100 ms hitches. Slow or single-channel RAM also crushes 1% lows even when capacity is fine.

Storage bottleneck

SATA SSDs and especially HDDs cause texture-streaming hitches in open-world games. NVMe Gen4 or better is the 2026 baseline.

Thermal throttling

CPUs that hit 95-100°C start clocking down. Average FPS slips, but 1% lows take the bigger hit because throttling is bursty.

Background processes

Discord overlays, antivirus scans, browser tabs, OBS recording, and Windows updates can all spike frame times for a fraction of a second. Test with a clean OS state.

Driver and shader compilation

First-time loads of unreal-engine games compile shaders on the fly. Until those caches build, expect terrible 1% lows. Wait 10 minutes before benchmarking.

How to measure your own 1% lows

The cleanest free tool in 2026 is CapFrameX (Windows). It records every frame time, shows percentiles, and exports clean charts.

Workflow:

1. Install CapFrameX, set it to record on F11.

2. Launch your most demanding game at your usual settings.

3. Hit F11, play through a 60-second representative section.

4. Stop recording, read the average, 1%, and 0.1% values.

MSI Afterburner with the on-screen overlay also displays live 1% lows if you enable the option in OSD settings.

What good 1% lows look like

Rule of thumb: 1% lows should be at least 60 percent of average FPS for smooth play, and 70 percent or more for excellent feel.

If your 1% lows fall below 50 percent of average, something is wrong, even when the average looks fine.

Fixing bad 1% lows

Step 1, narrow down the cause

Open MSI Afterburner overlay. During a stutter, watch:

• CPU usage near 100% with GPU dropping → CPU-bound, faster CPU or X3D upgrade
• GPU at 99% with frame-time spikes → VRAM saturation, lower textures
• RAM near full → upgrade to 32 GB
• SSD activity spikes during stutters → upgrade to NVMe Gen4
• Temperatures over 90°C → thermal fix (repaste, better cooler)

Step 2, free wins first

• Enable XMP/EXPO in BIOS
• Set Windows power plan to High Performance
• Disable Discord overlay, browser GPU acceleration, OBS background recording
• Update GPU driver, run DDU if needed
• Cap FPS slightly below monitor refresh to stabilize frame times

Step 3, hardware

• 16 GB → 32 GB DDR5-6000
• SATA SSD → NVMe Gen4
• Older CPU → Ryzen 7800X3D / 9800X3D for cache-heavy games
• Old thermal paste → repaste, drops 5-10°C easily

Frame pacing vs 1% lows

Related but not identical. 1% lows measure the slowest frames. Frame pacing measures the variance between consecutive frames. A game can have okay 1% lows but still feel jittery if frame times oscillate wildly. CapFrameX shows both, look at the frame-time graph for variance, not just the percentile bars.

Frequently asked questions

What is a good 1% low for 144 Hz gaming?

At least 100 FPS for 1% low when targeting 144 average. Below that you feel dips on every CPU-heavy event.

Are 1% lows more important than average FPS?

For perceived smoothness, yes. Average FPS matters for headroom, 1% lows matter for feel. Optimize both.

Does VRR fix bad 1% lows?

Partially. G-Sync / FreeSync hide tearing but cannot make a 30 ms frame feel like an 8 ms frame. The dip is still perceived.

Why are my 1% lows worse after a Windows update?

New driver mismatch, indexing service, or shader cache invalidation. Reboot, let shader compile finish, and re-test.

Can DLSS or FSR improve 1% lows?

Often yes. By reducing GPU load, the GPU completes frames faster and smooths out variance. In CPU-bound games it does nothing, the CPU is still the limiter.

Verdict

If you only chase average FPS, you optimize for the wrong number. Measure 1% lows, target 60-70 percent of average, and fix the bottleneck that is creating the dip, whether that is CPU cache, RAM capacity, storage speed, or thermals.

Run your CPU + GPU pairing through the bottleneck calculator and read our frame pacing guide for the deeper companion read.