Free, privacy-first
Last updated:
Turn raw frametime samples into jitter, spike, and percentile stability metrics: diagnose stutter that average FPS hides.
What this tool helps you answer
This analyzer reveals frame pacing quality that average FPS alone cannot show. Paste a raw frametime log to get variance, percentile bands, spike count, and a 1% low proxy.
Editorial review
This page combines the live tool, input guidance, worked examples, and operating limits so Frametime Variance Analyzer stays useful even before users interact with the calculator.
Reviewed by Klartext Tools against the current Frametime Variance Analyzer workflow on 2026-03-05.
Last updated:
Use with judgment
Page scope
This analyzer reveals frame pacing quality that average FPS alone cannot show. Paste a raw frametime log to get variance, percentile bands, spike count, and a 1% low proxy.
Review the output with Frametime samples set to 16.7 16.5 17.1 33.3, then compare it with the method and limitations on this page before changing other inputs.
Change Input unit to ms while keeping the rest of the Frametime Variance Analyzer scenario stable.
If the result moves sharply after changing Input unit, treat the tool output as sensitive and validate the source input before acting.
More context
The result above is the answer. The sections below help you understand it, compare it, or move to the next step.
Use this flow when your average FPS looks fine but gameplay still feels uneven, or when you want to compare two hardware configurations on equal terms.
Use a capture tool such as CapFrameX, RTSS, or a game's built-in benchmark to record a representative gameplay segment. Export the raw frame time column in milliseconds or microseconds.
Paste the raw frame time values into the input field and set the correct unit (ms or µs). Adjust the spike threshold if needed. 35% above the median is a reasonable default that filters minor jitter while flagging real stutter events.
Check median, P95, and P99 first. If P99 is more than twice your median, you have a significant stutter problem. Compare the 1% low proxy against your average FPS to measure the quality floor of your session.
High variance with low spike count points to systemic load variation: investigate CPU scheduling or GPU pipeline pressure. High spike count with moderate variance suggests discrete stall events such as shader compilation or thermal throttling.
After changing a driver, setting, or hardware configuration, recapture under the same scenario and paste the new data. Compare variance and spike count directly, not just average FPS, to confirm the improvement.
This analyzer reveals frame pacing quality that average FPS alone cannot show. Paste a raw frametime log to get variance, percentile bands, spike count, and a 1% low proxy.
Sample inputs
Sample outcome: Review the output with Frametime samples set to 16.7 16.5 17.1 33.3, then compare it with the method and limitations on this page before changing other inputs.
Change Input unit to ms while keeping the rest of the Frametime Variance Analyzer scenario stable.
Sample inputs
Sample outcome: If the result moves sharply after changing Input unit, treat the tool output as sensitive and validate the source input before acting.
Average FPS is a marketing number. What actually determines whether a game feels smooth or stuttery is frame time consistency: specifically, how much variation exists in how long each frame takes to render. A game running at 60 average FPS with high frame time variance will feel visibly worse than one at 55 FPS with tight, consistent delivery. This analyzer takes a raw frame time log and maps it to the metrics that capture subjective smoothness: 1% and 0.1% percentile frame times, spike count, variance, and the distribution shape that distinguishes hardware-limited performance from driver instability or thermal throttling. Frame pacing problems fall into two categories. Systemic variance occurs when every frame takes slightly different amounts of time due to background load, CPU contention, or GPU pipeline bubbles. This shows up as a wide variance number and inflated percentiles relative to the median. Spike events are isolated frames that take dramatically longer than the rest: often caused by shader compilation stalls, garbage collection, or temperature-triggered clock reduction. Spike count and the configurable threshold let you separate these two phenomena so you can prioritize the right fix. The 1% low proxy in this tool is approximated from high frametime percentiles and converted to FPS for comparability with standard benchmark reporting. Use it alongside median FPS to judge the floor of your experience, not just the ceiling. A session where median FPS looks solid but 1% lows are 30% below average is still a stutter-prone session.
Paste raw frame time samples from a benchmark, capture tool, or manual log to analyze pacing quality beyond average FPS. The tool computes median, percentile bands, variance, and spike count from your data. Use it when average FPS looks acceptable but gameplay still feels rough or inconsistent. Frame time analysis is particularly useful after driver updates, overclocking changes, or when comparing two hardware configurations side by side.
The tool parses all numeric tokens in the input, ignores non-numeric entries, and optionally trims extreme outliers from both tails before computing statistics. Variance and standard deviation are calculated from the trimmed dataset. Percentile bands (P95, P99, P99.9) show the frame time value at each threshold: lower is better. The 1% low proxy is derived by identifying the 99th percentile frame time and converting it to an equivalent FPS value for cross-benchmark comparability.
Median frame time should be close to the theoretical interval for your target FPS (e.g., 8.3 ms at 120 FPS). Variance quantifies how much frame times deviate from that median: values below 2–4 ms² typically indicate smooth delivery, while values above 10 ms² are perceptible as stutters. The spike count shows how many frames exceeded the configured threshold above median. Even a small number of extreme spikes can disrupt aim and readability in competitive play, so watch both the count and the severity of the highest outliers.
This tool is only as accurate as the data you provide. Captures shorter than 5 seconds may not include representative low-frequency stutter events. Samples taken during cutscenes, loading transitions, or benchmark intros will not reflect in-game pacing. For best results, capture during active gameplay in a scene that exercises your typical load: open-world traversal, team fights, or aim-training arenas as appropriate. Recapture under the same scenario after any change to ensure the comparison is fair.
eDPI is simple math, but players still misuse it because they skip the input checks around DPI, slider values, and game-specific context. This guide walks through the reliable workflow.
Players often lump input lag, refresh rate, and response time into one vague “monitor feel” problem. These tools split that confusion apart. One helps you think through total latency from input to display. The other helps you judge how panel refresh and response behavior shape motion clarity and perceived responsiveness.
These tools solve different parts of the same setup problem. Use Mouse DPI Checker to verify the hardware number you think you are using. Use Aim Sensitivity Visualizer when you need to translate that number into a repeatable in-game sensitivity workflow.
Mouse DPI is a hardware property: the sensor reports a fixed number of counts per inch regardless of what Windows does. Windows Pointer Speed is an OS-level multiplier applied after that signal arrives, and Enhance Pointer Precision adds a non-linear acceleration layer on top. Because these settings compound, players who adjust one without understanding the other end up chasing a moving target. Verifying the hardware layer first, then confirming the signal timing, gives a reliable starting point before any in-game sensitivity work.
Gaming calculators and test tools for DPI, sensitivity, FPS estimates, latency checks, and setup tuning.
Compare manual profiles or pro presets with game-specific eDPI benchmark ranges.
Calculate DPI, eDPI, and cm/360, then convert sensitivity between FPS games so your aim feels consistent across titles.
Estimate average FPS, lows, and bottleneck direction before you benchmark or upgrade.
If the job spills into another category, these tools help with the next step.
Model long-term growth from starting capital, recurring contributions, and inflation before you commit to a savings plan.
Open toolProject how a starting balance and regular monthly contributions grow with compound interest over any time horizon.
Open toolProject your retirement savings balance from a current portfolio, monthly contributions, expected return, and inflation rate.
Open toolSolve the equation and interpret the parabola in one run.
Open tool