Quick Answer
The FPS Test tool on /run/ runs a client-side WebGL stress scene in your browser, reporting live FPS, frame time, stability, and exportable JSON results without uploading data to a server.
Formula
Session Report = { avgFPS, minFPS, maxFPS, frameTimeMs, stabilityScore, duration }
Introduction
This guide is part of the FPS Test knowledge base. Use the FPS test tool on the run page for live browser measurement, then work through the sections below to interpret frame delivery quality beyond a single average number.
Live measurement beats guessing from menu animations. This guide explains what the on-site FPS test tool does, how it differs from in-game counters, and how to interpret the metrics panel during a session.
What the Tool Measures
The FPS Test tool lives exclusively on the run page at /run/. It is not embedded on the home pillar or blog articles by design: one canonical location keeps controls, canvas, and export behavior consistent.
During a session the tool stresses WebGL2 rendering (WebGL1 fallback), samples frame times each animation frame, and updates average, minimum, and maximum FPS plus a stability score derived from variance.
Browser FPS testing validates graphics pipeline health on your current machine, OS, and browser stack. Pair results with in-game FPS testing for titles you actually play.
If you are new to the vocabulary, start with what an FPS test is so you know how frame counts relate to smoothness before interpreting the live dial.
The tool is built for repeatability: same complexity slider, same duration, same resolution scale produces comparable sessions you can log week to week without installing extra software.
- Live FPS measurement with on-canvas dial and metric grid
- Browser FPS testing via WebGL stress workloads
- In-game FPS testing complements (not replaced by) browser runs
- Real-time monitoring of frame time and phase labels
- Performance reporting through optional JSON export
Reading the Live Panel
Average FPS summarizes the session; minimum FPS reveals worst dips; stability score compresses variance into one number for quick comparison.
Adjust scene complexity, render mode, resolution scale, and duration before starting. Controls lock while the test runs to prevent mid-session drift.
Export JSON when you want a paper trail. Naming files with dates and driver versions turns one-off runs into a history you can review using the workflow in FPS monitoring and tracking.
Resolution scale is especially useful on high-DPI displays: it simulates heavier pixel load without leaving the browser, giving a fast preview before you change in-game render resolution.
Stability ↑ when frame time variance ↓
- Start with 60 second duration for baseline
- Raise complexity gradually to find breaking point
- Export JSON after each configuration change
- Compare runs only at identical settings
Step-by-Step Tool Workflow
Follow this sequence for repeatable browser FPS tests. Skipping configuration or warm-up steps is the most common reason two back-to-back runs disagree.
-
Open /run/
Load the run page and confirm WebGL context initializes without errors. If the canvas stays blank, update the browser or check GPU blocklists first.
-
Configure workload
Set scene complexity, render mode, resolution scale, and duration. Write settings down if you plan to compare across weeks.
-
Start and monitor
Watch live FPS ring, frame time, and stability metrics during the session. Sudden dips often correlate with background tabs or thermal fan ramps.
-
Review results
Check average, min, max FPS and stability in the metrics grid. Compare min FPS to average; a wide gap suggests pacing issues worth investigating.
-
Export if needed
Save JSON locally for before-and-after comparisons. Store exports beside driver version notes so regressions are traceable.
-
Re-test after changes
Run again after one change only: driver update, browser swap, or power plan tweak. Multiple changes at once make results impossible to interpret.
Example Sessions
Baseline: complexity 5, mixed mode, 100% scale, 60 seconds after a driver update. Use this as your personal reference point before tuning games.
Stress: complexity 9, particles mode, 100% scale, 2 minutes to probe thermal stability on a laptop. Watch whether stability score drifts down in the second minute.
Quick sanity: complexity 3, 30 seconds after a Windows update. If average FPS drops 20% with no setting changes, investigate background apps before blaming hardware.
Scale test: complexity 5 at 50% then 100% resolution scale on the same machine. The ratio between runs approximates how pixel load affects your GPU in heavier titles.
- Quick 30 second sanity check after Windows update
- Long 5 minute session for laptop thermal behavior
- Half resolution scale on 4K display scaling test
FAQ
- Where is the FPS test tool?
- Only on /run/. Home and blog pages link to it; the interactive calculator is not duplicated elsewhere.
- Is data sent to a server?
- No. Tests execute locally. JSON export is optional and stays on your device.
- Can I use it on mobile?
- Yes, but mobile GPUs and thermals differ sharply from desktop. Treat mobile results as device-specific baselines.
- Which render mode should I pick?
- Mixed mode is a balanced default. Particles mode stresses fill rate; geometry mode stresses vertex throughput. Rotate modes when diagnosing where your system struggles.
Conclusion
The FPS Test tool on /run/ gives repeatable browser measurements with live metrics and export. Use it as a fast baseline before deeper in-game testing.
Open FPS Test Tool