Hub

This is a specialized spoke — for all-in-one estimates, open our FPS calculator homepage.

Updated October 2026Engine v2026.10"Can I Run It" & Optimization Guides

1% Low FPS Explained: The Smoothness Metric That Averages Hide

Average FPS is a highlight reel; 1% lows are the blooper reel your hands remember. This guide explains what 1% and 0.1% low FPS actually measure — and the interactive simulator diagnoses the classic complaint: "my PC runs 120 FPS average but feels choppy because my lows drop to 42."

This page covers what is 1% low fps and 0.1% low scenarios — including 1% low fps meaning, 0.1% low vs 1% low — using the same estimation engine as our FPS calculator homepage. Prefer the wide view? Browse every tool in "can i run it" & optimization guides.

Average FPS vs 1% Low — Smoothness Simulator

Average FPS120

1% Low FPS42

Smoothness Ratio

35%

1% low ÷ average

Worst Frame Time

23.8

ms at the 1% low

Feel Score

Choppy

Diagnosis

Same Average, Different Games: 1% Low Profiles That Explain "Feels Choppy" (1080p High)

Same Average, Different Games: 1% Low Profiles That Explain "Feels Choppy" (1080p High)
Game (5600X + RTX 4060)	Avg FPS	Est. 1% Low	Smoothness Ratio	Verdict
Counter-Strike 2	220	170	77%	Smooth
Fortnite	132	102	77%	Smooth
Cyberpunk 2077	63	49	78%	Smooth
Monster Hunter Wilds	60	46	77%	Smooth
Escape from Tarkov	90	69	77%	Smooth
Baldur's Gate 3	94	73	78%	Smooth

Both columns are real engine outputs on the same hardware class — high-variance engines (traversal, crowds) drag lows relative to averages. Smoothness ratio = 1% low ÷ average.

What is 1% Low FPS and 0.1% Low: The Engineering Detail

What 1% Low and 0.1% Low Actually Measure

Sort every frame time from your session from best to worst. The 1% low is the average of the worst 1% of frames; the 0.1% low is the average of the worst 1-in-1,000. They’re not "minimum FPS" — they’re percentile statistics of your frame-time distribution, which is why a single hitch doesn’t destroy your 1% low but a recurring one does.

1% lows map to "during fights": recurring, gameplay-relevant slowdowns.
0.1% lows map to "that one spot in the map": traversal hitches, shader comp, streaming stalls.
Frame-time graphs make percentiles visible — CapframeX and PresentMon compute both.
Smoothness ratio (1% low ÷ average) is the single best "feel" predictor: 70%+ feels locked.

Pro tip: quote both numbers when describing a problem — "120 avg / 42 lows in fights" diagnoses ten times faster than "it stutters sometimes."

Why 120 Average With 42 Lows Feels Worse Than Flat 75

Your visual system adapts to pacing within seconds. After twenty minutes at 120 FPS, a 25ms frame is a visible event — the same spike invisible in a 60 FPS session. That adaptation is why high-average/low-floor systems feel worse than modest-but-consistent ones, and why chasing average FPS can actively make a system feel worse.

Lows under 40% of average register as stutter regardless of the average — the simulator scores this precisely.
Common causes: draw-call spikes (CPU), VRAM residency swaps, shader compilation, and background processes waking up.
Frame caps convert spike-driven variance into flat pacing — capping at your low floor often "adds" perceived FPS.
VRR makes sub-cap spikes tear-free but doesn’t hide long frames — pacing fixes beat display fixes.

Pro tip: try a 15-minute session capped at your 1% low value. Most players immediately prefer the flat experience — consistency is a feature you can enable today for free.

The Fix Hierarchy: What Actually Moves 1% Lows

Lows respond to different levers than averages. GPU upgrades help GPU-side lows; cache, memory and background hygiene fix CPU-side lows. The simulator’s diagnosis points at the likely class of cause — the fix list below is ordered by effort-to-impact.

Free wins: XMP/EXPO on, dual-channel verified, overlays off, game on the NVMe, Windows Game Mode.
Cheap wins: shader cache warm (pre-launch compile), texture tier down (VRAM residency), FPS cap at lows.
Mid-cost: X3D-class CPU upgrade — cache moves lows 20–30% in draw-call-heavy engines.
Last resort: GPU upgrade — it only helps if the spikes are shader/pixel-side, not streaming or CPU.

Pro tip: benchmark once with RTSS’s frametime graph open and one change at a time — 30 minutes of measurement beats months of forum-guessing about what your "random" stutters are.

What is 1% Low FPS and 0.1% Low — FAQs

What does 1% low FPS mean?

It’s the average of the worst 1% of frames in your session, sorted by frame time. If your 1% low is 42 FPS, one frame in every hundred (the worst ones) averaged 42 — those are the frames you experience as stutter. 0.1% low is the same idea for the worst 1-in-1,000 frames.

Why is my 1% low so much lower than my average FPS?

Variance sources concentrate in the worst frames: draw-call spikes in crowded scenes, VRAM swaps, shader compilation, and background processes. High-variance engines (traversal-heavy UE5 titles, dense cities) naturally run lows at 40–55% of average; tight engines like CS2 run 75%+.

Is 1% low more important than average FPS?

For feel, yes. Human vision adapts to pacing, so dips from a high average are more visible than a consistent moderate frame rate. Competitive integrity also lives in the lows — peeker’s advantage and hit registration happen during your worst frames, not your best.

How do I fix low 1% lows without upgrading hardware?

In order: enable XMP/EXPO and verify dual-channel; close overlays and background apps; warm the shader cache; cap FPS at your low floor to flatten pacing; drop texture quality if VRAM-bound; and use VRR with a cap 3 under refresh. Most systems recover 15–25% of lows this way.

What’s the difference between 1% low and 0.1% low?

Sample depth: 1% lows average your worst 1 frame in 100 (recurring gameplay dips), while 0.1% lows average the worst 1 in 1,000 (rare hitches — streaming stalls, one-off compiles). 1% lows predict how fights feel; 0.1% lows explain "it hitched once entering this area."

More in "Can I Run It" & Optimization Guides

Can My PC Run It FPS CheckerCheckerOne-click playability verdicts across 30+ games with tier badges instead of spec-sheet pass/fail.What is a Good FPS for GamingGuideGenre-based FPS target matcher from cinematic 30 to pro-tier 360+, with monitor pairing.How to Increase FPS in PC GamesGuideInteractive per-setting FPS cost simulator plus the platform-level fix checklist.Best CPU and GPU Combos for GamingBuyer’s GuideFour budget tiers of zero-bottleneck pairings, each FPS-validated across eight games.

Next step — cross-silo

frame time to FPS converter →

1% lows are frame-time percentiles — convert yours to milliseconds and check them against refresh budgets.

Tool

Back to the hub

Done here? Our FPS calculator homepage covers every game, resolution and preset in one place — with the pre-built combo matrix and full benchmark tables.

Open our FPS calculator homepage ↗